3️⃣ Payment history
To strengthen Trustpair's analysis we highly recommend to send us your payment history.
This file gathers all the payments made on your third parties.
For the first import, we recommend to send us at least the 18months of history. For all subsequent imports, the delta of payments made since the last imports.
File format and content
Your CSV file must contain all the columns described 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.
File "payment history" imported into Trustpair
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.
| Header / column name | Mandatory content | Description | Example |
|---|---|---|---|
| company_country_code | Yes (if moral person) | Country code in format ISO 3166 (2 or 3 car.) | FR or FRA |
| company_name | Yes (if moral person) | Name of the company | Trustpair |
| company_registration | 1 of the 3 ID is mandatory - your choice (if moral person) | National identification number of the third party | 832940670 |
| tax_number | 1 of the 3 ID | European VAT number | FR40123456824 |
| duns | 1 of the 3 ID | 9-digit identification number issued by the private company Dun & Bradstreet | 270243120 |
| last_name | Yes (if natural person) | Family name | Dupont |
| first_name | Yes (if natural person) | First name | Marie |
| other_name | Optional | Other name | |
| birthdate | Optional | birthdate | JJ/MM/AAAA |
| iban | Yes, if IBAN zone | Supplier's account number in IBAN format | FR7612548029981234567890161 |
| bank_account_country_code | Optional | Country code in format ISO 3166 (2 or 3 car.) | FR or FRA |
| bank_account_number | Yes, if non-IBAN zone | Bank account number of the third party | 123550679 |
| bic or bic_code | Yes, if non-IBAN zone | Account number bic code | 019389857 |
| routing_number | Optional | Routing number or bank code | Depending on countries |
| control_key | Optional | Control key | Depending on countries |
| supplier_id | Yes | Unique identifier of the supplier in your database > Its content should never change for a supplier | Specific to your company |
| supplier_status | 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 | Yes | The amount of the payment (decimal separated by a point or a comma) | 2746.12 or 2746,12 |
| payment_currency | Yes | The currency of the payment in ISO 4217 format (3 char) | GBP, USD, EUR |
| payment_status | Yes | The payment status indicating that the payment has been made | Paid or Cancelled |
| payment_id | Yes | 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 | Yes | Payment date in ISO 8601 format YYYY-MM-DD or DD/MM/YYYY | 2019-09-17 or 30/01/2020 |
| invoice_id | Optional | The unique identifier of the invoice in your database | Specific to your company |
| invoice_number | Optional | The invoice number (external reference indicated on the invoice) | Specific to your company |
| batch_id | 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 6 months ago