General information

Generating reconciliation files gives you the possibility to keep your accounting up to date more easily.
Since separate payments are often compressed into one bigger transaction and then transferred to your business bank account, it is difficult to keep record of all payments correctly and generates a lot of manual work in most cases.

When generating a reconciliation file, all transactions are listed instead of one big transaction.

• Payment link files can be generated once each day, when a link was paid the file is available the next day.
  Example: Bob and Julia have paid using their respective links on Monday,the file is available Tuesday and contains both payments.
• Direct Debit files can be generated every 3 business days after receiving feedback from the bank.
• Generate Direct Debit files directly: This feature can be activated on demand, you can generate a reporting file the second you sent a batch to the bank. All transactions are returned as paid. Even when you received feedback from the bank, all transactions are always returned in the reconciliation file as paid.

Overview:

• Search files (1)
• Filter (2) everything (by default), archived and non archived
• Upload account info (3)
• Generate (4) CAMT53, MT940 or CODA file(s) for Direct Debit transactions and Payment links
• View archived files and reset filters (5)
• List of generated files
• Download (6) button

Generate CAMT53, MT940 or CODA files

Reconciliation Account

When you click on the Generate button, the reconciliation account that will be used in your reconciliation file for each Target is displayed:

This account is defined in this particular order, and depending on the target:

Transactions

1. The default Twikey account is used: BE71088260500969
2. A custom account of your choice is used: Contact your Business Support Agent to configure one.

Payment links

1. You configured a reconciliation account in your Payment Provider Gateway, that one is used
   Settings > Payment Hub > Payment provider Gateway > Configure > Advanced:

2. No specific account is configured on your Payment Provider Gateway:
   We use the IBAN from that Payment Provider if known in our system:

• Mollie: NL30ABNA0524590958
• MultiSafePay: BE15399104252630
• CCV: Depending on your registered address:
  • Belgium: BE79363065348233
  • Netherlands: NL26INGB0006865503

In case we do not know the IBAN, there won't be any account displayed. Configure one on your Payment Provider Gateway first in order to generate payment link reconciliation files.

How to generate files

• Click on 'Generate' (1) on the top right.
• Select the format (2).
• Select the target(s) (3) (both are possible).
• Click on 'Generate' (4).

Files

Different Formats:

• CAMT-053: Standard CAMT-053 format (BE & NL).
• CODA: Standard CODA format (BE).
• CODA (as details): Detail version with digit 6 in the transaction reference (BE).
• MT940 (Beta): Compatible with Exact Online and other bookkeeping software (NL).
• MT940 (Twinfield) (Beta): Compatible with Twinfield (Kluwer) (NL).
• CSV

Target

• Transactions: paid with Direct Debit (DD) or Recurring Credit Cards (RCC).
• Payment links: paid with Payment Service Provider (PSP) as Mollie or CCV or MSP etc.

Filenames:

The file icons:

• : Direct Debit transactions
• : RCC transactions
• : Payment links payments
• : Reporting (uploaded account information or received from the bank)

File source:

The filename starts with 'sdd_twikey' or 'rcc_twikey' depending if the transactions originate from Direct Debit (Direct Debit) or RCC (Recurring Credit Card).
The template ID is also included in the filename.

• CODA:
  • sdd_twikey_BE81ZZZ1234567891-210322033017-2223.cod: Combination of the creditor id, date and coda reference, template id.
  • Verifications.cod: This file contains the transactions used to sign a mandate.
• CAMT: sdd_twikey_BE81ZZZ1234567891-210319152443-2223_camt53.xml
  Combination of the creditor id, book date and uid, template id.

The source can be from Twikey or from Bank (only via api)

Content

The content of the files use the general standards.
In the CODA files we include a reference to the batch id on the first line:

Transactions

When generating CODA, CAMT053 or MT940 files, only transactions are included in the files for which we received a paid state back from the bank. When the transaction had a failure code but was paid via another method (dunning workflow or manually marked as paid by) it is not included in the file.
This way, the file is 1-on-1 with information received from the bank.

On screen, only for transactions, the Twikey reversal zero sum/reverse payment is included in the total number of transactions.

When generating a CSV file, all the transactions from the batch are listed and with the status received from the bank (failed or paid).
On the reconciliation files overview you will only see the number of paid transactions in the CSV file.