1. Import Customer Dishonored Riba

The function allows importing the unpaid bills file provided by the bank.

Import Customer Dishonored (CBI) – SUMMARY To access the function press ALT + Q and type “CBI” to search for the functionality.

Select “Import Customer Dishonored (CBI)” to open the following page.

Parameters to be entered:

Notes crediting bank account
The bank account must match the ABI, CAB, and account number in the unpaid file. If payments are credited to a different account than the one used for submission, a specific bank account must be created.

Procedure

1. The RiBa file is created in Business Central from “Customer Bill Card”.
2. Upon maturity, wait for the bank to process the results (usually 1–5 days), then download the unpaid file from Remote Banking.
3. Import the unpaid file into Business Central using the “Import Customer Dishonored (CBI)” function and post the accounting entries.
4. Run the “Closing Bank Receipts” procedure to apply the invoice with the payment entry.

Closing must occur after posting the unpaid bills, as the unpaid import assumes the related entry is still open. If few unpaid bills exist, you can close them at maturity and manually reopen them before importing.

Accounting Entries
The accounting entries proposed by the system are summarized here.

Unpaid import without transitory account
Depending on whether the S.B.F. account or the regular bank account is debited.

S.B.F account debt.

Ordinary bank account debt

Note: to automate balance account entry, set a default balance account no. on the batch used for import.

Unpaid import without transitory account
Usually the use of the transitory account is provided in case the treasury is managed with the DocFinance application. The accounting entries can be summarized as follows.

1. Accounting unpaid debit and bank charges

2. Accounting unpaid by “Customer Unpaid Bills Import (CBI)” procedure

Technical Information
The unpaid file follows CBI (Corporate Banking Interbancario) standards. The record format is defined by document “CBI-RIB-001 - Ricevute Bancarie (RiBa)", revision 6.03 (25/02/2019). The function used is “Flusso di ritorno Ri.Ba.". The file must start with a header record of type “IB”.

Note
Data used includes:

• Payment Date: from record 14, pos. 23–28.
• Creation Date: from header record “IB”, pos. 14–19.
• Reason Code: from record 14, pos. 29–33. Must be “42010” (unpaid bill) to proceed.

Outline summary of CBI services

2. Import Dishonored SDD

The function allows importing the unpaid SDD bills file provided by the bank.

Import Customer Dishonored (CBI) – SUMMARY
To access the function press ALT + Q and type “CBI” to search for the functionality.

Select “SEPA DD Dishonored (CBI)” to open the following page.

Parameters to be entered:

Procedure

1. The SDD file is created in Business Central from “Customer Bill Card”.
2. Upon maturity, wait for the bank to process the results, then download the SDD unpaid file from Remote Banking.
3. Import the unpaid file into Business Central using the “SEPA DD Dishonored (CBI)” function and post the accounting entries.
4. Run the “Closing Bank Receipts” procedure to apply the invoice with the payment entry (the procedure is the same as that used for closing bank receipts).

Closing must occur after posting the unpaid bills, as the unpaid import assumes the related entry is still open. If only a few unpaid bills exist, you can close them at maturity and manually reopen them before importing.

Technical Information Supported Record types:

• CBISDDStsRptLogMsg.00.01.00
• CBIBdySDDStsRpt.00.01.00

Outline summary of CBI services

3. Import customer payments CBI

The customer payment import feature allows you to import the reporting file made available by the bank.

This functionality is used to import bank transactions, including collections.

Import Customer Payment (CBI) – SUMMARY
To access the function press ALT + Q and type “CBI” to search for the functionality.

Select “Import Customer Payment (CBI)” to open the following page.

Parameters to be entered.

Notes The import function for bank transactions has some limitations.

• Transactions are not filtered by the bank reason for collection type, so all transactions in the reporting file are imported, not just, therefore, collections.
• Transactions are not filtered by bank account, so if there are transactions from multiple bank accounts in the file, they will all be imported to the balance bank account specified on the request page.
• The account number is not populated. Transactions are imported with account type “Customer”, but the Account No. field will not be valorized.

Record type CBI

4. Sepa Direct Debit (SDD) Collections

4.1 Setup

The basic settings for creating SEPA Direct Debit (SDD) collection dispositions are as follows.

4.1 Bank Export/Import Setup

A new export code must be created in the Bank Export/Import Setup with the characteristics highlighted in the image below.

Note: The new XMLport 18123335 - “SEPA DD pain.008.001.08”. has been implemented for data processing.

4.2 Bank Account Card Setup

In the “General” tab of the Bank Account card the following parameters should be set.

• SEPA Direct Debit Exp. Format (1): set the correct export code.
• Creditor No. (2): this field must contain the “Creditor Identifier Code”. The Creditor Identifier Code is a unique code that allows the creditor to be identified in the SEPA area. It is important because it is uniquely associated with the SEPA mandate number. It is mandatory information.
• Direct Debit Msg. Nos. (3): enter the No. Series to be assigned to the name of the SDD file that will be created.

A value must be entered in the “Transfer” tab of the Bank Account card in the “CUC” field. The CUC code (“Codice Univoco CBI”) is mandatory. It is an 8-character alphanumeric code that is assigned by the banking system.

4.5 SDD B2B\Core

The type of SDD (B2B\Core) can be selected via the “Partner Type” field of the Customer Bill card.

“Partner Type “Company”: SDD “B2B”. “Partner Type “Person”: SDD “Core”.

4.6 Creation of the SDD file

Customer Bill Card
To export the SDD file from the customer bill card, select the “Export Bill to File” action.

Issued Customer Bill Card
To export the SDD file from the Issued Customer Bill card, select the “Export Issued Bill to File” action.

Technical Information
The SDD file, in Italy, is subject to the standards of the CBI (Interbank Corporate Banking) service, which incorporates the ISO20022 standard layout.
The current format is governed by the technical manual “STIN-MO-001 - Sepa Direct Debit collections,” version 00.01.01 dated 02/11/2023.

Reference ISO20022 path: CustomerDirectDebitInitiation V08 - Pain.008.001.08

5. SEPA Credit Transfers Payment Transaction (SCT)

5.0 Setup

The basic settings for creating SEPA Credit Transfers payments are as follows.

5.1 Bank Export/import Setup

A new export format code will need to be created in the Bank export/import setup.

• Processing Codeunit ID: 1220 - “SEPA CT-Export Fil"e.
• Processign XMLport ID: 18123333 - “SEPA CT pain.001.001.09 CBI v00.04.01”.
• Check Export Codeunit: 1223 - “SEPA CT-Check Line”.

**Notes “Check Export Codeunit”**
Regarding the “Check Export Codeunit” to be set, it should be noted that codeunit 12178 of the Italian localization is present in the system. However, this object appears to be updated with a long delay. It is suggested, therefore, for the control when exporting the file to use codeunit 1223, as it is updated regularly.

5.2 Bank Account Card setup

In the “Transfer” tab of the bank account card the following parameters should be set.

• Payment Export Format (1): set the export format created.
• IBAN (2): IBAN code is mandatory.

In the “General” tab of the bank account card, the parameter should be set: Credit Transfer Msg. Nos.. Here the Serial No. to be assigned to the name of the SCT file that will be created should be indicated.

CUC Field
According to CBI standards, the CUC code (CBI Unique Code) is mandatory. It is an 8-character alphanumeric code that is assigned by the banking system. However, this data element is not always required by the bank, and to ensure continuity with previous versions, a specific check has not been implemented.

Therefore, it is suggested that the “CUC” field on the bank account card be valorized in order not to risk the discarding of the provision.

5.3 Company Information Setup

The VAT number of the company is a mandatory data element in the XML file of transfers. The “VAT Registration No.” field on the “Company Information” tab must be mandatorily filled in.

5.4 Creation of the SCT file (SEPA Credit Transfers)

Vendor Bill List Sent Card
To export the SCT file from the Vendor Bill List Sent Card, select the “Export Bill List to File” action.

5.5 Credit Transfer Cumulative Debit

It is possible to define how the bank should report the payments of the bill list on the periodic statement.

The credit transfer cumulative debit reporting request covers the entire bill list and with it, in practice, you are asking the bank to report, on the statement, a single transaction for the total of the bill and not the individual payment.

This mode of reporting is consistent with that used in Business Central in the bank entry, which creates a debit line on the bank account for the total of the bill.

The reporting mode should not be confused with the “cumulative transfers” option, which allows a single transfer to be arranged to pay multiple invoices for the same supplier.

Credit Transfer Cumulative Debit - Bank Account Card
Credit transfer cumulative debit is selectable, on the bank account, via the “Credit Transfer Cumulative Debit” field in the “General” tab.

Credit Transfer Cumulative Debit - Vendor Bill List Card
All payments, issued on a given bank, will automatically carry the bank’s “Cumulative Bill Debit” setting. The information is not editable in the Vendor Bill List and Vendor Bill List Sent Card.

***Tag “BtchBookg”***
The information, in the XML file, is carried via the tag “BtchBookg”. If “BtchBookg” is true the cumulative bill charge is requested.

Example

5.6 Technical Information

The SCT file in Italy is subject to the standards of the CBI (Corporate Banking Interbancario) service, which adopts the ISO20022 standard format.
The current version is defined by the technical manual “STIP-MO-001 Payments-v.00.04.01 ENG” version 00.04.01 dated 02/11/2023.
Reference ISO20022 format: CustomerCreditTransferInitiationV03 - pain.001.001.09.

6. XML Cross-Border Credit Transfer

6.0 Setup

The basic settings for creating XML Foreign Transfer payment are, below, reported.

6.1 Bank Export/import Setup

A new export format code will need to be created in the Bank export/import setup.

• Processing Codeunit ID:18123337 - “EOS005 Foreign CT-Export File”.
• Processign XMLport ID: 18123334 - “CBI CrossBorder Payment Request.00.01.01”.
• Check Export Codeunit: 18123336 - “EOS005 Foreign CT-Check Line”.

6.2 Bank Account Card setup

In the “Transfer” tab of the bank account card the following parameters should be set.

• Foreign Exp.Format (1): impostare il formato esportazione creato allo scopo.
• IBAN (2): IBAN code is mandatory.

CUC Field
According to CBI standards, the CUC code (CBI Unique Code) is mandatory. It is an 8-character alphanumeric code that is assigned by the banking system. However, this data element is not always required by the bank, and to ensure continuity with previous versions, a specific check has not been implemented.

Therefore, it is suggested that the “CUC” field on the bank account card be valorized in order not to risk the discarding of the provision.

In the “General” tab of the bank account card, the parameter should be set: Credit Transfer Msg. Nos.. Here the Serial No. to be assigned to the name of the SCT file that will be created should be indicated.

Note: foreign currency payments
To make transfers in a foreign currency, a bank in the same currency must be set up.

6.3 Company Information Setup

The VAT number of the company is a mandatory data element in the XML file of transfers. The “VAT Registration No.” field on the “Company Information” tab must be mandatorily filled in.

6.4 Information to be included in the provisions on the the vendor bill lines

The following information must be set on the rows of the vendor bill for foreign transfers.

Bank Charges
Specifies which party will bear the charges associated with the transaction. Takes one of the following values:

• Our Charge (“DEBT”)
• Shared (“SHAR”)
• Beneficiary (“CRED”)

Notes

• The commission type must be the same for the entire bill.
• According to CBI rules, the commission type field mandatorily takes the value “SHAR” if the payee is valorized with IBAN coordinate that contains a Country Code belonging to the European Economic Area.

Reason CVS
May take the following values:

• “INF” (below CVS threshold).
• “SNR” (non-resident party).
• “CVA” (assignment of a single currency code).
• “CDV” (transfer of currency between residents).

CVS Tariff Number
The field must be completed in the case of Reason CVS = “CVA”, in other cases it is optional.

6.5 Creation of the XML foreign transfer payment file

Vendor Bill List Sent Card
To export the XML foreign transfer payment file from the Vendor Bill List Sent Card, select the “Create foreign XML bank transfer” action.

6.6 Currency Management

The ability to define the exchange rate to be used in the Bill List entry has been implemented. The exchange rate is proposed based on the List Date, but can be changed by selecting the assist edit of the Currency Code field.

6.7 Technical Information

The XML Cross-Border Credit Transfer file in Italy is subject to the standards of the CBI (Corporate Banking Interbancario) service, which adopts the ISO20022 standard format.
The current version is defined by the technical manual “STPE-MO-001 Payments-v.00.01.01 ENG” version 00.01.01 dated 02/11/2023.

Reference ISO20022 format: CustomerCreditTransferInitiationV03 - pain.001.001.03

Feedback

Was this page helpful?

Glad to hear it! Please tell us how we can improve.

Sorry to hear that. Please tell us how we can improve.