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.

Header / column nameMandatory contentDescriptionExample
company_country_codeYes (if moral person)Country code in format ISO 3166 (2 or 3 car.)FR or FRA
company_nameYes (if moral person)Name of the companyTrustpair
company_registration1 of the 3 ID is mandatory - your choice (if moral person)National identification number of the third party832940670
tax_number1 of the 3 IDEuropean VAT numberFR40123456824
duns1 of the 3 ID9-digit identification number issued by the private company Dun & Bradstreet270243120
last_nameYes (if natural person)Family nameDupont
first_nameYes (if natural person)First nameMarie
other_nameOptionalOther name
ibanYes, if IBAN zoneSupplier's account number in IBAN formatFR7612548029981234567890161
bank_account_country_codeOptionalCountry code in format ISO 3166 (2 or 3 car.)FR or FRA
bank_account_numberYes, if non-IBAN zoneBank account number of the third party123550679
bic or bic_codeYes, if non-IBAN zoneAccount number bic code019389857
routing_numberOptionalRouting number or bank codeDepending on countries
control_keyOptionalControl keyDepending on countries
supplier_idYesUnique identifier of the supplier in your database > Its content should never change for a supplierSpecific to your company
supplier_statusOptionalStatus of the supplier in the database allowing to indicate a deactivated supplier but still present in the supplier database2 types of values are accepted:
empty - provider has not been disabled
disabled - supplier disabled
amountYesThe amount of the payment (decimal separated by a point or a comma)2746.12 or 2746,12
payment_currencyYesThe currency of the payment in ISO 4217 format (3 char)GBP, USD, EUR
payment_statusYesThe payment status indicating that the payment has been madePending
payment_idYesThe 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 fieldIt could be necessary to do some concatenation of fields
execution_dateYesPayment date in ISO 8601 format YYYY-MM-DD or DD/MM/YYYY2019-09-17 or 30/01/2020
invoice_idOptionalThe unique identifier of the invoice in your databaseSpecific to your company
invoice_numberOptionalThe invoice number (external reference indicated on the invoice)Specific to your company
batch_idOptionalPayment campaign batch to which the payment is attachedSpecific 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.