CSV ports FAQ

If you are having trouble working with CSV ports, this FAQ addresses common issues and provides solutions.

Where can I import a CSV file?

The import target of the port decides this:

• Ports with the import target Transactions import into the Payment Reconciliation Journal.
• Ports with the import target Account Statement import into the Payment Reconciliation Journal or the Bank Acc. Reconciliation.
• Ports with the import target PSP import files from a payment service provider, such as PayPal, Klarna, or Adyen, into a cash receipt journal.

Ports with the import target Transactions or Account Statement need a bank account setup. Ports with the import target PSP are used by a payment service agreement and need no bank account setup.

For more information, see Setting up bank accounts for CSV ports and Adding a payment service agreement.

When should I use a CSV port instead of a CAMT file?

Use a CSV port for generic transaction files from external sources, where the bank or the provider delivers no supported format. If a CAMT file is available, use it. A supported format needs no column mapping, and it doesn't differ from customer to customer.

Before you set up a CSV port, check whether the bank can deliver CAMT files. Banks often hide these files by default, and they can be turned on for your user in the online bank.

The error appears the moment you click the import action. You never reach the dialog where you select the file, so the file isn't the cause.

Why can't I import my file even though the setup looks correct?

Symptoms

The import runs, but the file is rejected or no lines reach the journal.

Possible causes

• The file is saved with ANSI encoding instead of UTF-8.
• Date Format on the CSV port doesn't match the dates in the file.
• CSV Separator, Delimiter, Decimal Separator, or Thousands Separator don't match the file.

Solution

1. Check Text Encoding on the General FastTab against the encoding of the file.
2. On the CSV Port - Continia Banking page, on the Setup FastTab, check that Date Format uses the .NET date pattern of the file, for example, dd-MM-yyyy.
3. Check the separator and delimiter fields against the file.

For more information, see Setting up CSV ports.

Why do I get a date format error for every file I upload?

Symptoms

• When you upload a new file, the system still uses data from a previously imported file instead of the current CSV Port settings.
• The same import error continues to appear even after you have corrected the CSV Port configuration.
• Changes made to the CSV Port don't seem to affect the import results.
  

Possible causes

• Unprocessed files remain in the File Archive and are evaluated again during subsequent imports.
• Existing imported data in journals, bank statements, PSP headers, or bank transactions causes the system to reuse previous import information.
• The Handle Data setting in the CSV Port isn't configured to overwrite existing data.

Solution

1. Check the File Archive for unprocessed CSV files and delete any files that are no longer needed.
2. Delete all existing lines from the relevant journals and bank statements.
3. Check PSP Headers and Bank Transactions, and make sure all records have Imported to Company set to blank.
4. Open the CSV Port setup and verify that Handle Data is set to Rewrite.
   Import the file again.

If the issue persists after updating the CSV Port settings, verify that no unprocessed files remain in the File Archive and that all previously imported data has been cleared before attempting another import.

Why can't I change the date format on a CSV port?

Possible causes

• The CSV port is delivered and managed by Continia Banking, so its setup is read-only.

Solution

• Click Copy to create your own port, and then adjust the date format on the copy.

Why isn't the import action available in the Payment Reconciliation Journal?

Symptoms

• The Import action isn't available in the Payment Reconciliation Journal.
• Adding the action through personalization doesn't make it available.
• The journal doesn't show Import and Apply CSV Transactions.
• The bank account isn't configured for CSV import, so no CSV import actions are available.
  

Possible causes

• The CSV Port's Import Target is set to PSP, so the port can't be used in the Payment Reconciliation Journal.
• The bank account hasn't been configured to use a CSV Port for transaction imports.
• No bank accounts are available that support the CSV import functionality.

Solution

1. Search for and select CSV Ports - Continia Banking.
2. Open the relevant CSV Port and verify that Import Target is set to Transactions or Account Statement.
3. In the Payment Reconciliation Journal, use Setup Bank Account to configure one or more bank accounts for CSV import.
4. Make sure the selected bank account is linked to a CSV Port that supports transaction or account statement imports.
5. Return to the Payment Reconciliation Journal.

After a bank account is configured for CSV import, the Import and Apply CSV Transactions action becomes available.

How do I import fees separately from the transaction amounts?

Some bank files include fee information in addition to transaction amounts. When importing transactions, you can configure the CSV port to import fees separately into the Charges table. To do this, specify where the fee information is located using the fee-related fields on the Setup FastTab of the CSV Port page.

Solution

1. Open the CSV Port and specify how fees should be identified:
   • In Fee Alternative Descriptions, enter the descriptions that represent fees. If there are multiple descriptions, separate them with commas (for example, Fee,VAT).
   • In Fee Column Names, enter the names of the columns that contain fee amounts. If there are multiple fee columns, separate them with commas. This setting is available only when First Line Is Header Line is enabled.
2. If you're using a PSP port, create a Payment Service Agreement and set up the search rules that identify fee transactions.

Can I move a CSV port to another environment?

Yes. A CSV port definition exports as a JSON file. Keep the .json extension, because the file is the port definition, not a transaction file.

To export, open the CSV Ports - Continia Banking page, and then click Actions > Export on the action bar. To import, click Actions > Import, and then upload the file.

Exporting a payment service agreement also includes its payment service provider and its CSV port.

Troubleshooting the import in the Bank Acc. Reconciliation

Troubleshooting the import in the Payment Reconciliation Journal