Payment Management Supported Bank Files
The core functionality of Payment Management is the bank integration that allows you to communicate data between Business Central and your bank. This article explains what happens when bank files are exported and imported using Payment Management, depending on the ordered file format.
Not all banks support all the file formats listed in this article. For information about which file formats are supported by your bank, go to Bank Integration. Be aware, that your bank may require subscription to, or purchase of, some of the files. Contact your bank for more information about your bank's terms and conditions for the file transfer. Also, the information delivered in the files imported from the banks into Business Central may vary from bank to bank.
ISO-files supported by Payment Management
| File format1 | If you want to | Description |
|---|---|---|
| ISO PAIN.001 and ISO PAIN.002 (first edition) | Send payments to your bank from the payment journal and import status into the payment journal | When creating an agreement with your bank, some banks will ask you to specify in which format you want to send payments to the bank. In this request for "ISO PAIN.001". The ISO PAIN.001 payment file is either sent automatically to the bank by Payment Management when you select Transmit (direct communication), or it is exported to the local file system (manual communication), where you must manually upload the file to the bank. The ISO PAIN.002 file is then sent back to you, by the bank, as a status update, but in two different editions: First edition is sent immediately upon receipt of the ISO PAIN.001 file. This edition confirms the receipt of the file and that the file is validated. The second edition of the file is sent when each payment line has been validated by the bank. The time between the two files can vary from seconds to minutes. Payment Management automatically searches for and imports the ISO PAIN.002 file (first edition) immediately after a payment file is successfully transferred to the bank, assuming you use direct communication. The second edition of the file is imported when you select Update status on the payment journal. The file is used, by Payment Management, to update the Status field on payment lines in the payment journal. We assume that the status of the payment line was Valid before sending the payment. At this stage of the payment process the following possible results are available: Sent: The payment has been exported in a file using manual communication. This is also the final status a payment line will get when using manual communication, because no status files is available for Payment Management. Processing: The payment has been sent to the bank using direct communication, and is currently being processed by the bank. Rejected: The payment line has been rejected by the bank. Use the Payment File Errors-function, located in the lower right corner of the payment journal page, to identify how to fix the error. |
| ISO PAIN.002 (second edition) | Import status into the payment journal | As described above, the ISO PAIN.002 file is sent by the bank in two editions. First edition is sent immediately upon receipt of the ISO PAIN.001 file. This edition confirms the receipt of the file and that the file is validated. The second edition of the file is sent when each payment line has been validated by the bank. When you press Update status in the payment journal, Payment Management automatically searches for the second edition of the file, and if available, imports the file. The ISO PAIN.002 (second edition) file is used, by Payment Management, to update the Status field on payment lines in the payment journal. At this stage of the payment process the following possible results are available: Awaiting: The payment is awaiting to be approved by a 2. approver in the bank. Rejected: The payment line has been rejected by the 2. approver or the bank. Use the Payment File Errors function, located at the right corner of the payment journal page, to identify how to fix the errors or contact the 2. approver. Paid: The payment has been completed in the bank. |
| ISO PAIN.008 | Send SEPA Direct Debit collections to your bank | Payment Management Direct Debit uses this file when you export a Direct Debit Collection Entries to your bank. |
| ISO CAMT.052 | Update status into the payment journal | This is your intraday information. This report provides you with a near real-time view of your account(s). ISO CAMT.052 is mostly used by banks not sending updated ISO PAIN.002 second edition, but instead offering this file. When you press Update status in the payment journal, Payment Management automatically searches for the file, and if available, imports the file. You can, of course, also import the file manually from file. The ISO CAMT.052 file is used by Payment Management to update the Status field on payment lines in the payment journal exactly the same way as for ISO PAIN.002 (second edition), described above. More benefits using ISO CAMT.052: If the bank has changed the payment date, for example, if the payment was not approved in time, this is also changed automatically on the payment line in the payment journal. You thus avoid the entries being posted on the wrong date. Amount adjusted: The amount of the payment line has been adjusted according to currency differences. If you have paid in a foreign currency, the currency exchange rate used in Business Central might not reflect the currency exchange rate used by the bank. If this type of status file is ordered in your bank, the currency exchange rate (and thus the Amount LCY) will automatically be updated on the payment line. This will ensure posting of the correct Amount LCY, avoiding exchange rate adjustments later, and a perfect match when reconciling the bank statement in the bank account reconciliation. |
| ISO CAMT.054D | Update status in the payment journal | This is the final confirmation that outgoing payments (debits) have been made. The file contains the day's completed outgoing payments and includes for example changes in exchange rates on foreign payments. The file is also called "DEBMUL". When you press Update status in the payment journal, Payment Management automatically searches for the file, and if available, imports the file. You can, of course, also import the file manually from file. The ISO CAMT.054D file is used by Payment Management to update the Status field on payment lines in the payment journal exactly the same way as for ISO PAIN.002 (second edition), described above. More benefits using ISO CAMT.054D: If the bank has changed the payment date, for example if the payment was not approved in time, this is also changed automatically on the payment line in the payment journal. You thus avoid the entries being posted on the wrong date. Amount adjusted: The amount of the payment line has been adjusted according to currency differences. If you have paid in a foreign currency, the currency exchange rate used in Business Central might not reflect the currency exchange rate used by the bank. If this type of status file is ordered in your bank, the currency exchange rate (and thus the Amount LCY) will automatically be updated on the payment line. This will ensure posting of the correct Amount LCY, avoiding exchange rate adjustments later, and a perfect match when reconciling the bank statement in the bank account reconciliation. |
| ISO CAMT.054C | Import payments into the cash receipts journal | This is the final confirmation that customer payments (credits) have been made. The file contains the day's completed incoming payments, both deposits via manual account transfers to the account and OCR payments, including FIK, GIK, KID or OCR payments. When you press Import Payments in the cash receipts journal, Payment Management automatically searches for the file, and if available, imports the file. You can, of course, also import the file manually from file. The ISO CAMT.054C file is used by Payment Management to import customer payments into the cash receipt journal and, as mentioned above, the file includes both deposits via manual account transfers to the account and OCR payments, including FIK, GIK, KID or OCR payments. Recommendation: We recommend that you import the ISO CAMT.054C file before importing ISO CAMT.053, as the ISO CAMT.054C file contains extended information on all deposits, including associated notifications. This will help Payment Management match the correct payment/invoice in Business Central. Note: The file must contain details of each payment (called specified or detailed when ordering the file at the bank). Sum files are not supported as a single sum does not indicate who conducted the payment. |
| ISO CAMT.054 | Import payments into the cash receipts journal and update status in the payment journal | This file can contain both statuses for the payment journal and information about customer payments to the cash receipt journal. When the CAMT.054 file is received in Business Central, Payment Management will automatically allocate the payment information into the cash receipt journal and the payment journal. To read more about the data in the file, please see the sections CAMT.054D for information about updating status in the payment journal, and CAMT.054C for information about importing payments into the cash receipts journal. |
| ISO CAMT.053 Standard and Extended | Reconcile bank statements and import payments | Provides you with detailed and structured information on all entries booked to your account for the previous day, as well as extended information on all deposits and withdrawals, including notifications associated with a deposit or withdrawal. The extended information ensures that Payment Management, with greater accuracy, can match and offset the correct entry/invoice and set the correct posting description in the reconciliation journal. Some banks offer two types of the bank account statement: ISO CAMT.053 Standard This is the standard bank account statement report, offered by most banks. It provides you with detailed and structured information on all entries booked to your account for the previous day, as well as extended information on all deposits and withdrawals, including notifications associated with a deposit or withdrawal. However, due to lack of notification information on deposits in some banks, when ordering CAMT.053 (standard) account statements, you must expect some manual matching of your deposits. With these banks, ordering CAMT.053 (standard) is best suited for customers who have very few deposits. If available, in your bank, we recommend ordering CAMT.053E, the extended account statement described below. ISO CAMT.053E Extended This is the extended bank account statement offered by some banks. Because this is the extended report it also provides you with detailed and structured information on all entries booked to your account for the previous day, as well as extended information on all deposits and withdrawals, including notifications associated with a deposit or withdrawal. What's the Account Statement used for? When you create a Bank Account Reconciliation in Business Central, and press Import and Match, Payment Management automatically searches for the file, and if available, imports the file. You can, of course, also import the file manually from file. The ISO CAMT.053 file is used by Payment Management to reconciliate bank entries in Business Central with the bank's bank account statements. But, as Payment Management imports the statement, it also helps you create new entries made to your bank account, but not registered in Business Central, for example payment made by your customers or withdrawals made by the bank for interest, fee or other expenses withdrawn as direct debit entries. Importing ISO CAMT.053 includes: - Import and matching of all withdrawals created with Payment Management with 100 percent certainty, due to the Transaction ID. - Import and matching of new withdrawals not created with Payment Management. Matching is made possible by setting up posting rules for fixed expenses, for example fee, interest, rent, canteen, subsidy, etc. If a match is found, Payment Management will automatically create general journal lines in the general journal batch, ready for posting. - Import of new deposits, made via manual account transfers to the account, find their matching entry in Business Central, and automatically create cash receipt lines in the cash receipt journal, ready for posting. - Import of new deposits, made via OCR payments and including FIK, GIK, KID or OCR payments, find their matching entry in Business Central, and automatically create cash receipt lines in the cash receipt journal, ready for posting. Should there be unresolved entries, e.g. in the event of an incorrectly stated invoice number, these entries can be automatically transferred to a journal, where you can make posting proposals yourself. You can read more about how the Statement Intelligence reconciliation works, later in this chapter. What's it not used for? ISO CAMT.053, either it is the standard or extended edition, is not used for updating statuses of outgoing payments, although they may be visible in the payment journal (not posted). That, for example means, that if you use manual communication and imports an ISO CAMT.053 file where an outgoing payment is present in the file with status Paid, this will not update the status of the associated payment line in the payment journal. You must post your payment journal with status Sent when using manual communication. Recommendations - When ordering ISO CAMT.053E, there will normally be no need to order the ISO CAMT.054C files, as the extended account statement also contains all payments. On the other hand, it is important that you order ISO CAMT.053E per. day if you want to be able to import all new payments every day. - Conversely, it is still necessary to order ISO CAMT.054D, as Payment Management cannot use the information on ISO CAMT.053E, to update the status of outgoing payments in the payment journal. |
| PSD2 API | Send payments to your bank and reconcile bank statements and import payments | Because the PSD2 directive does not set specific requirements for file formats, security protocols etc. we cannot describe the integration in detail. We recommend you ask your PSD2 service provider for details. |
- Applicable to all file orders is that one file is ordered per. account per day.
Available non-ISO files supported by Payment Management
| Format Code | If you want to | Notes | Description |
|---|---|---|---|
| UTF | Send payments to your bank from the payment journal | Nordea's old file format for sending payments. | What's in the file UTF-format for payments to Corporate Netbank for payments from Danish accounts and for Request for Transfers. |
| BDF | Send payments to your bank from the payment journal | Bankdata specific file format for sending payments. Version 20-03-2018 | What's in the file The BDF format is supported by Danish banks primarily in the Bankdata alliance and is used when manual import into your online banking system is required. The following payment and transfer types is supported: - Transfer between own accounts Domestic transfer - Foreign transfer / check - Transfer from accounts abroad - Salary transfer - Payment card |
| ERH | Send payments to your bank from the payment journal | BEC specific file format for sending payments. ERH – Bankens Erhvervsformat (BEC) Version 2.0 | What's in the file The ERH format is supported by Danish banks primarily in the BEC alliance and is used when manual import into your online banking system is required. The following payment and transfer types is supported: - Transfer between own accounts. - FI71 debit card without notification. - GIRO payment card type 04 or 15 without notification. - GIRO payment card card type 01, 41 or blank with notification. - Bank to bank transfer with address information on the debtor and 41 lines of advice (advice to the creditor is sent at the same time as the account statement). - FI73 debit card with notification and address information. - FI75 payment card with notification and without address information. - Foreign transfer (MT103). - Foreign request - Foreign request own - Foreign check |
| KaSel | Send payments to your bank from the payment journal | SDC specific file format for sending payments. Version 2.1 Denmark. | What's in the file KaSel is supported by many Danish banks primarily in the SDC alliance and is used when manual import into your online banking system is required. The following payment and transfer types can be imported depending on whether the functions are registered in the agreement: - Account transfers, both with short and long advice via letter or account statement (also with currency accounts) - Payment cards - both FIK and GIK - Salary transfers - Transfer abroad - Account for account (currency) - Take home amounts from abroad - Payment from account abroad |
| MT940 | Reconcile bank statements and import payments. | MT940 is a format used by the SWIFT network to send and receive end-of-day bank account statements. | What's in the file Bank account statement with a detailed description of all yesterday's transactions. One file is ordered per. account. |
| HB01 MT101 | Reconcile bank statements and import payments. | Handelsbanken specific format. Celenia Bank (copy of SKB version 1.02 (Jyske Bank) | What's in the file Bank account statement with a detailed description of all yesterday's transactions. One file is ordered per. account. |
| BD-V3 | Reconcile bank statements and import payments. | Bankdata specific format. Version 3, single entries with a period as a decimal separator. | What's in the file Bank account statement with a detailed description of all yesterday's transactions. One file is ordered per. account. |
| EKP format | Reconcile bank statements and import payments. | BEC specific format. | What's in the file Bank account statement with a detailed description of all yesterday's transactions. One file is ordered per. account. |
| .DAT format | Reconcile bank statements and import payments. | SDC specific format. | What's in the file Bank account statement with a detailed description of all yesterday's transactions. One file is ordered per. account. |
| PD-V3 Posteringsdata version 3 | Reconcile bank statements and import payments. | Nordea's old file format for bank account statements. | What's in the file Bank account statement with a detailed description of all yesterday's transactions. One file is ordered per. account. |
| PBS-sector | Import NETS PBS FIK (DK) customer payments in the cash receipts journal. | NETS specific format for FIK 71, 73 and 75 payments. The Fælles IndbetalingsKort (Joint Deposit System) has been developed jointly by the banks and PBS A / S, now Nets. The system is based on a "Payment Card", which you (recipient of the amount) issues and sends or delivers to your customer (the payer). Your customer can optionally: - deposit at a bank or at a post office - or transfer from his account (online banking). You choose which account the deposits are to be credited to. | What's in the file A detailed confirmation of yesterday's payments from NETS. The reporting file contains detailed information about each payment and facilitates reconciliation work, while also helping to create simpler and more efficient everyday routines. |
| BG Max | Import BG Max (SE) customer payments in the cash receipts journal. | Bankgirot specific format. Bankgiro Receivables (Bankgiro Inbetalningar) is a flexible service that is suitable both large and smaller companies that want smooth processing of receivables and customer accounts receivable. Bankgiro Receivables (Bankgiro Inbetalningar) reports all receivables completely electronically in a uniform file format, called Bg Max, regardless of whether the customer has paid electronically or manually. All Swedish banks, except Nordea, supports BG Max. Nordea customers normally use Total IN. | What's in the file A specified debit description of the customer's payments. The reporting file contains detailed information about each payment and facilitates reconciliation work, while also helping to create simpler and more efficient everyday routines. Advantages for your company - You can tell immediately and clearly which customers have paid and which receivables in the customer accounts receivable can be marked as paid. - This also means less paperwork for you - You get improved conditions for automated processing in your finance system. - Receivables are reported the same day they are dealt with by Bankgirot. |
| OCR-NO | Import OCR-Giro (NO) customer payments in the cash receipts journal. | DNB specific format. OCR service is a product which automatically updates your accounts receivables. By using OCR service you can eliminate your company's need for any manual registration of incoming payments. Information about each received payment is delivered in a file which is used for the subsequent automatic updating of your accounts receivable ledger. | What's in the file A specified debit description of the customer's payments. The reporting file contains detailed information about each payment and facilitates reconciliation work, while also helping to create simpler and more efficient everyday routines. How OCR works The payee sends the payer an invoice where customer identification (KID) is specified. The KID reference identifies the customer and invoice, and may contain elements such as: Customer number, Invoice number or Instalment number - or various combinations of these. Advantages for your company - Better overview of outstanding accounts receivable - Simpler reconciliation of bank statements - The accounts receivable ledger is updated no later than the day after payment is received |
| Total IN | Import TotalIn (SE) customer payments in the cash receipts journal. | Nordea specific format. Total IN and Total IN Basic are two services available to companies aiming to simplify the reconciliation of incoming payments. While the file type is the same for both services, Total IN Basic is primarily for companies with a smaller volume of in-payments whereas Total IN is better suited to companies with a larger number of in-payments. | What's in the file A specified debit description of the customer's payments. The reporting file contains detailed information about each payment and facilitates reconciliation work, while also helping to create simpler and more efficient everyday routines. Advantages for your company Total IN and Total IN Basic include all in-payments to PlusGiro, Bankgiro and incoming cross-border payments to one single file for automatic reconciliation of the customer sales ledger. All transactions, including images from document-based payments to PlusGiro and Bankgiro, are available via the Total IN Internet interface which is included in the services. How to order The company signs an agreement with Nordea for the Total IN or the Total IN Basic service. Upon connection to the service the company receives a Total IN ID number which identifies all connected accounts and Bankgiro numbers in the service. |
- Applicable to all file orders is that one file is ordered per. account per day. If applicable, please order "Detailed files" as "Sum-files" is not supported.