Netherlands Entity Bank Details
This table shows which fields are required for every payment file format when you create bank details for customers, vendors, employees and partners, either through the Bank Details page or through the CSV Import Assistant.
Payment File Format |
Field |
Description |
Required |
---|---|---|---|
All Belgium payment formats |
Name |
Unique name for this entity bank detail record. |
Yes |
Type |
Indicates whether it is the entity’s primary or secondary bank account. |
Yes |
|
Equens-ClieOp Equens-ClieOp (ING Bank) |
Bank Account Number if using ING specifications, or Account Number |
Bank account number of the entity with whom you have a transaction. This field must contain seven to 10 characters. |
Yes |
Bank Account Payment Description |
Text that will be displayed on the entity’s bank statement. |
Yes |
|
Note:
The following formats, which are also used in the Netherlands, are provided by the EMEA Localization SuiteApp. For more information, see EMEA Localization Payment Templates. |
|||
SEPA Credit Transfer (ABN AMRO) |
IBAN |
The entity’s International Bank Account Number (IBAN) which should contain the two-letter code BE for Belgium, and the IBAN check digits. |
Yes |
BIC |
Business Identifier Code, also called SWIFT Code, of the entity’s bank. It has eight or 11 characters. |
Yes |
|
SEPA Credit Transfer (HSBC) |
IBAN |
The entity’s International Bank Account Number (IBAN) which should contain the two-letter code BE for Belgium, and the IBAN check digits. |
Yes |
Swift Code/BIC |
Business Identifier Code, also called SWIFT Code, of the entity’s bank. It has eight or 11 characters. |
Yes |
|
SEPA Direct Debit (ABN AMRO) |
IBAN |
The entity’s International Bank Account Number (IBAN) which should contain the two-letter code BE for Belgium, and the IBAN check digits. |
Yes |
BIC |
Business Identifier Code, also called SWIFT Code, of the entity’s bank. It has eight or 11 characters. |
Yes |
|
Billing Sequence Type |
Indicates whether a collection is:the first (FRST) of a series or a recurrent one (RCUR).
Note:
Select FRST if Original Debtor Agent is selected in the Reference Amended field. |
Yes |
|
Reference Mandate |
Authorization identification or mandate. This information must be supplied by the customer. |
Yes |
|
Date of Reference Mandate |
The date the mandate was signed. |
Yes |
|
Reference Amended |
Indicates if the mandate has been amended since it was originally issued. The following options are available:
|
Yes |
|
Remittance Message |
Short message to show in your customer’s bank statement every time a direct debit is initiated. |
Yes |
|
Original Reference Mandate |
The unique reference assigned to the mandate before it was amended. |
No |
|
Original Debtor IBAN |
The original International Bank Account Number of the entity that owes an amount of money. |
No |
|
Original Creditor ID |
ID of the creditor used for the mandate before it was amended. |
No |
|
Original Creditor Name |
Name of the original creditor used before the mandate was amended. |
No |
|
Electronic Signature |
Placeholder for electronic signature data for non-paper authorizations. |
No |
|
Final Payment Date |
This field is automatically updated with the customer payment date, if the value of the Billing Sequence Type is OOFF or FNAL. |
No |
|
Payments Made |
Indicates the number of payments made. It is automatically updated by an increment of 1 for every payment made. |
No |
|
First Payment Date |
This is the date of the first customer payment created against a mandate or authorization with initial Billing Sequence Type of FRST. |
No |