FNI payment files
Header Record - record Type 0 - Initial Record - Batch
The record header contains the records that are created once per cash code, pay group, payment code.
| Number | Position | Data size/type | Field | Description | Instructions | Notes |
|---|---|---|---|---|---|---|
| 1 | 1-4 | Alpha/numeric (4) | Application Code | LUM2 | ||
| 2 | 5-5 | Numeric (1) | Record Type | 0 | Record Type | |
| 3 | 6-6 | Numeric (1) | Type of Material | 0 | ||
| 4 | 7-7 | Numeric (1) | Reserve | Blank | ||
| 5 | 8-18 | Alpha/numeric (11) | Payer Company ID | OrganizationIdentifier in PayablesElectronicTransferID | With leading zeros, without hyphens | |
| 6 | 19-23 | Alpha/numeric (5) | Additions to customer name | Blank |
See bank spec With the help of the addition to the customer name, you can designate different business units or different locations where they operate, and are to be classified as independent users of the service. If no addition is required, then the field is left blank |
|
| 7 | 24-25 | Alpha/numeric (2) | Reserve | Blank | ||
| 8 | 26-26 | Numeric (1) | Approval Code | Zero | ||
| 9 | 27-36 | Numeric (10) | Timing of Material/return information creation | System Date and Time | YYMMDDHHMM See bank spec |
All records are written into a batch and given a unique id different from the time when the rest of the records were created. If 2 records on the same batch have the same unique id and payee name, currency code, amount and the first line in the message field of the first payment is the same, interpret the 2nd records as “double” and reject it. |
| 10 | 37-50 | Numeric (14) | Reserve | Zero | ||
| 11 | 51-58 | Numeric (8) | Payment Date | Electronic Payment Creation Payment Date | YYYYMMDD | Specifies the due date when the payer intended
that all payments in a batch should be paid. If the entered date
is: A maximum of 5 business days old, pay the item in no particular order after it is received more than 5 business days old or more than 60 calendar days in the future, reject the entire batch. If the date is missing or if only zeros were entered, use the due dates on the individual payment records. |
| 12 | 59-598 | Alpha/numeric (540) | Reserve | Blank | ||
| 13 | 599-599 | Alpha/numeric (1) | Carriage Return | 0D | ||
| 14 | 600-600 | Alpha/numeric (1) | New Line | 0A |
Payee/Payment record - Record Type 1
The payment/Payee records are created for each payment record.
| Number | Position | Data size/type | Field | Description | Instructions | Notes |
|---|---|---|---|---|---|---|
| 1 | 1-4 | Alpha/numeric (4) | Application Code | LUM2 | ||
| 2 | 5-5 | Numeric (1) | Record Type | 1 | Record Type | |
| 3 | 6-6 | Numeric (1) | Approval Code | Zero | If payment was rejected, specify the reason in field 22 | |
| 4 | 7-146 | Alpha/numeric (140) | Recipients Name and Address | VendorName in Vendor and PostalAddress.DeliveryAddress.AddressLine1, DeliveryAddress.Postal Code and PostalAddress.Municipality in VendorAddress | 4 x 35 | The first character in field recipient name and address can not be blank. Moreover, the field must be entered in free form. We recommend that the recipients name information is entered on the first 2 lines and address on the following 2 lines |
| 5 | 147-148 | Alpha/numeric (2) | Recipient Country | PostalAddress.Country in VendorAddress or PostalAddress.Country in BankEntity | If SWIFT code is missing enter the country code of the recipient’s bank (VEN.VLO) | Country Code for the recipient country . If SWIFT code for the recipients bank is missing, enter the country code of the recipients bank |
| 6 | 149-159 | Alpha/numeric (11) | Recipient’s Bank SWIFT Code | SwiftId in Vendor/VendorLocation | SWIFT code for the recipient’s bank. The payment is sent by this address. SWIFT code includes the country of the recipients bank. We recommend that the SWIFT code is always entered | |
| 7 | 160-299 | Alpha/numeric (140) | Recipients Bank bank name and city | BankName + PostalAddress.Municipality in BankEntity | 4 x 35 | If an internal claring system is used in the country where the recipient’s bank is (eg CH (Chips), FW (Fedwire), SC (Sort Code), BL (Bankleilzahl), then enter 2 slashes at the beginning of the first line and the clearing code without spaces (??CH123456 or BL12345678). The task is part of the recipients bank details. If you use the IBAN account number, do not enter the clearing code. |
| 8 | 300-333 | Alpha/numeric (34) | Recipients Account number | BankAccountNumber from Vendor/VendorLocation | IBAN no | If invoice has an international IBAN (International Bank Account Number), enter it in electronic form in this field. Eg Dutch IBAN: NL91ABNA0417164300. Nordea batch transfer control to the recipient’s IBAN is entered in the correct format. If the IBAN is incorrect, the payment is rejected. SWIFT code for the recipients bank should be used the same way as the IBAN. |
| 9 | 334-473 | Alpha/numeric (140) | Payment Base for information to the receiver | Invoice PayablesInvoice |
||
| 10 | 474-488 | Numeric (15) | Payment Amounts | Sum of paid invoices by vendor NetPaymentAmount |
13 whole + 2 decimal places | Fields 10 and 21 are alternative. If the payment amount in field 10 is 0, you can charge the fee amount entered in field 21 |
| 11 | 489-491 | Alpha/numeric (3) | Currency Code ISO standard | InvoiceCurrency in PayablesInvoicePayment | ||
| 12 | 492-494 | Alpha/numeric (3) | Reserve | Blank | ||
| 13 | 495-508 | Alpha/numeric (14) | Contract Number for exchange rate | Vendor/VendorLocation AssignmentNumber |
The number of the exchange contract with the bank is entered left aligned in the field. The required part is CUD (=spot) + 7 digits and the futures FWD + 7 digits. The agreed exchange rate for the payment does not need to be communicated separate for the payment. | |
| 14 | 509-509 | Alpha/numeric (1) | Payment Method | M | M= Money Orders | T= transfer, i.e., to pay a payment in the
currency in the form of a credit transfer of Nordea Bank Finland..
K= self-transfer, i.e., transfers between the group members accounts
and the company’s won accounts with Nordea Bank Finland. For NCC they want to use only one type with all payments (LUM2), then the type is M = payment order. M=payment order P=urgent payment Q= SWIFT check S= Check T= Transfer between account in Nordea Finland K= Transfers between own accounts in Nordea Finland |
| 15 | 510-510 | Alpha/numeric (1) | Service Fee |
ChargeCode in Vendor/VendorLocation 9= T else J If the charge code = 9 then the value of the service fee is T otherwise it will be a J |
J or 9 8= The payer and the recipient pays their own bank charges (SHA) 9= payer must also pay fees for the recipient’s bank (OUR) |
J= the payer and the recipient pays their own
bank fees T= Payer must also pay the fees of the recipient’s bank (OUR) |
| 16 | 511-518 | Numeric (8) | Payment Date | Electronic Payment Creation Payment Date | DDMMYYYY | The specific payment date. If the entered date
is: Not more than 5 business days old, pay the payment when received. More than 5 business days old or more than 60 calendar days in the future, rejected the payment. If the date is missing or if only zeros were entered and no specific payment date for entered for the item pay the payment when received. |
| 17 | 519-533 | Numeric (15) | Payment exchange | Zero | Only for return info | |
| 18 | 534-544 | Numeric (11) | Payment rate | Zero | Only for return info 5 whole + 6 decimals | |
| 19 | 545-558 | Numeric (14) | Account to be charged | Identif Number PayablesElectronicTransferID according to Pmt Code | PayablesElectronicTransferID.ElectronicTransferID | |
| 20 | 559-561 | Alpha/numeric (3) | Currency of the account to be charged | Invoice Currency Code | Required field API-INV-CURRENCY | |
| 21 | 562-576 | Numeric (15) | Amount Charged | Blank | 13 whole + 2 decimal places (If field 10 = 0) The fee amount can be entered for the payment amount (field 10 is 0). This field conans fee size in the account’s currency. |
|
| 22 | 577-596 | Alpha/numeric (22) | Archiving code or reason for rejecting | Blank | Only for return info | |
| 23 | 597-597 | Alpha/numeric (1) | Denomination of return information | Blank | Only for return info | |
| 24 | 598-598 | Alpha/numeric (1) | Reserve | Blank | ||
| 25 | 599-599 | 1 | Carriage Return | 0D | ||
| 26 | 600-600 | 1 | New Line | 0A | ||
| 600-600 | 1 | Total |
Payee/Payment record - Record Type 2 - Invoice item
The payment/Payee records are created for each payment record.
| Number | Position | Data type/size | Field | Description | Instructions | Notes |
|---|---|---|---|---|---|---|
| 1 | 1-4 | Alpha/numeric (4) | Application code | LUM2 | ||
| 2 | 5-5 | Alpha/numeric (1) | Record Type | 2 | Record Type | |
| 3 | 6-6 | Numeric (1) | Type of material | Zero | 0 | |
| 4 | 7-7 | Numeric (1) | Approval | Zero | ||
| 5 | 8-10 | Alpha/numeric (3) | Currency | PayablesInvoicePayment CurrencyCode (same as
field 20 in payment record) InvoiceCurrency |
Currency Code | |
| 6 | 11-11 | Numeric (1) | Invoice Type | PayablesInvoice Type I (Invoice) = 0 C (Credit note) = 2 |
0 = invoice 2= credit note |
|
| 7 | 12-26 | Numeric (15) | Currency Amount | PayablesInvoicePayment Trans Amount NetPaymentAmount |
13 whole + 2 decimal places | Enter the total amount of the invoices (the entries in field 10 of the payment record). |
| 8 | 27-37 | Numeric (11) | Payment Rate | Zero | Only for return info 5 whole + 6 decimal places |
|
| 9 | 38-52 | Numeric (15) | Exchange Rate | Zero | Only for return info 13 whole + 2 decimal places |
The DR/CR number counts (fields 9 and 10) are the same. They both are the total of debit records and credit records |
| 10 | 53-72 | Alpha/numeric (20) | Invoice Number. For customer’s account information | PayablesInvoice Invoice | API-INVOICE | The DR/CR number counts (fields 9 and 10) are the same. They both are the total of debit records and credit records |
| 11 | 73-80 | Numeric (8) | Reserve | Zero |
Total amount of all payments, without currency. The amounts are a total of all debit and credit amounts, however both amounts are totaled as whole amounts. So if you have a payment of $100 and a credit memo of -$70 the total will not be $30. It will be $170 |
|
| 12 | 81-130 | Alpha/numeric (50) | Customer’s own information | Blank | ||
| 13 | 131-598 | Alpha/numeric (469) | Reserve | Blank | ||
| 14 | 599-599 | Alpha/numeric (1) | Carriage Return | 0D | ||
| 15 | 600-600 | Alpha/numeric (1) | New Line | 0A |
Total Record - Record Type 9
The trailer record is created once per Cash Code, Pay Group, Payment Code.
| Number | Position | Data type/size | Field | Description | Instructions | Notes |
|---|---|---|---|---|---|---|
| 1 | 1-4 | Alpha/numeric (4) | Application code | LUM2 | ||
| 2 | 5-5 | Alpha/numeric (1) | Record Type | 9 | Record type | |
| 3 | 6-6 | Numeric (1) | Type of material | 0 | 0 | |
| 4 | 7-7 | Alpha/numeric (1) | Reserve | Blank | ||
| 5 | 8-18 | Alpha/numeric (11) | Payer Company ID | BankTransactionCode.ElectronicPaymentOrganizationIdentifier | With leading zeros, without hyphens | |
| 6 | 19-23 | Alpha/numeric (5) | Additions to Customer | Space | ||
| 7 | 24-25 | Alpha/numeric (2) | Reserve | |||
| 8 | 26-26 | Numeric (1) | Approval Code | Zero | ||
| 9 | 27-31 | Numeric (5) | Number of payments | Number of invoices | Total # of db records | |
| 10 | 32-36 | Numeric (5) | Number of invoices | Number of invoices | Total # of CR records | |
| 11 | 37-51 | Numeric (15) | Payments amounts | Sum of NetPaymentAmount in PayablesInvoicePayment | Total NetPaymentAmount of DB and CRs 13 whole + 2 decimal places |
|
| 12 | 52-598 | Alpha/numeric (547) | Reserve | Blank | ||
| 13 | 599-599 | Alpha/numeric (1) | Carriage Return | 0D | ||
| 14 | 600-600 | Alpha/numeric (1) | New Line | 0A |