4️⃣ Pending payments
If you want to check your payment campaigns (also known as pending payments) via Trustpair before sending the corresponding payments to your bank, please follow the following format for your file after performing the extraction from your database:
File types for payment campaigns
2 types of files are accepted:
- CSV extraction of your pending payments (before validation of the payment proposal and initiation of the payment to the bank).
For this type of file, a dedicated format should be used (see File format and content section below)- XML extraction corresponding to the file sent to the bank.
For this type file, the format is the standard norm ISO20022 in the version pain.001.001.03. Trustpair adapts its logic to this generic file format, so there's no need to format the extracted file.
File format and content
Your CSV file must contain all the columns shown below. They may be empty if the content is not mandatory.
To ensure proper processing of the file, the headers (without spaces) must be respected.
Note that the order of columns is not important.
| Header/column name | Content for legal entities | Content for individuals | Description | Example |
|---|---|---|---|---|
| company_country_code | Mandatory | - | Country code in format ISO 3166 (2 or 3 car.) | FR or FRA |
| company_name | Mandatory | - | Name of the company | Trustpair |
| company_registration | 1 of the 3 IDs is mandatory | - | National identification number of the vendor | 832940670 |
| tax_number | 1 of the 3 IDs | - | European VAT number | FR40123456824 |
| duns | 1 of the 3 IDs | - | 9-digit identification number issued by the private company Dun & Bradstreet | 270243120 |
| natural_person_country_code | - | Mandatory | Country code in format ISO 3166 (2 or 3 car.) | FR or FRA |
| natural_person_tax_number | - | Optional | Used for countries with tax ID for natural persons | 12345678 |
| last_name | - | Mandatory | Family name | Dupont |
| first_name | - | Mandatory | First name | Marie |
| other_name | - | Optional | Other name | |
| birthdate | - | Optional | birthdate | JJ/MM/AAAA |
| bank_account_country_code | Mandatory | Mandatory | Country code in format ISO 3166 (2 or 3 car.) | FR or FRA |
| iban | Mandatory - for IBAN zone | Mandatory - for IBAN zone | Supplier's account number in IBAN format | FR7612548029981234567890161 |
| bank_account_number | Mandatory - for non-IBAN zone | Mandatory - for non-IBAN zone | Bank account number of the vendor | 123550679 |
| bic or bic_code | 1 of the 2 is mandatory - for non-IBAN zone | 1 of the 2 is mandatory - for non-IBAN zone | Account number bic code | 019389857 |
| routing_number | 1 of the 2 is mandatory - for non-IBAN zone | 1 of the 2 is mandatory - for non-IBAN zone | Routing number or bank code | Depending on countries |
| control_key | Optional | Optional | Control key | Depending on countries |
| supplier_id | Mandatory | Mandatory | Unique identifier of the supplier in your database. Its content should never change for a supplier | Specific to your company |
| supplier_status | Optional | Optional | Status of the supplier in the database allowing to indicate a deactivated supplier but still present in the supplier database | 2 types of values are accepted: empty - provider has not been disabled disabled - supplier disabled |
| amount | Mandatory | Mandatory | The amount of the payment (decimal separated by a point or a comma) | 2746.12 or 2746,12 |
| payment_currency | Mandatory | Mandatory | The currency of the payment in ISO 4217 format (3 char) | GBP, USD, EUR |
| payment_status | Mandatory | Mandatory | The payment status indicating that the payment has been made | Pending |
| payment_id | Mandatory | Mandatory | The uniqueness of the "payment_id" is required for the analysis of payments in the Trustpair solution. Depending on the ERP, it may be necessary to combine different concepts into one field | It could be necessary to do some concatenation of fields |
| execution_date | Mandatory | Mandatory | Payment date in ISO 8601 format YYYY-MM-DD or DD/MM/YYYY | 2019-09-17 or 30/01/2020 |
| invoice_id | Optional | Optional | The unique identifier of the invoice in your database | Specific to your company |
| invoice_number | Optional | Optional | The invoice number (external reference indicated on the invoice) | Specific to your company |
| batch_id | Optional | Optional | Payment campaign batch to which the payment is attached | Specific to your company |
Template & examples
Please reach out to your Customer Success Manager for an example
If needed, we can provide you with a .csv sheet that displays all the columns required with several examples. You can then duplicate it, fill-it with your extraction file informations and name it according to the conventions above.
Updated 3 months ago