TRUSTODI TRUSTODI

Supporting Documents & Invoice Guidelines

Last updated: June 10, 2026

Certain rails and currencies require supporting documents for a payment to be processed. Providing proper documentation reduces the chance of a Request For Information (RFI), payment failure, or refund. Please follow the guidance below.

Accepted supporting documents by payment reason

Payment reasonSupporting document(s)
CONSULTING_FEESInvoice, contract, or agreement between parties
DOWN_PAYMENTS_FOR_REAL_ESTATEPurchase contract, mortgage contract
EMPLOYEE_SALARIES_OR_WAGESEmployment contract, pay-slip
EXPENSES_REIMBURSEMENTReceipts, expense reports
PURCHASE_OF_GOODSInvoice, contract, or agreement between parties
PURCHASE_OF_SERVICESInvoice, contract, or agreement between parties
REMITTANCEBank statement, remittance confirmation letter
RENTRental agreement
ROYALTIESInvoice, royalty contracts
For a remittance confirmation letter, please include the main purpose of the remittance (e.g. family support), the name of the sender and beneficiary, the amount, and the date.

Invoice best practices

To ensure consistent and reliable deliverability of payments, follow these best practices when submitting invoices as supporting documents. Failure to follow them may lead to RFIs, payment failure, or refunds.

Responding to RFIs

Certain payments may trigger a Request For Information (RFI), where our compliance team or a banking partner requires more information about a payment. An RFI can be raised while a payment is processing or even after it has completed. RFIs are sent to your team, and you can then share them with your customer as needed. Responding as quickly as possible is critical — failure to answer an RFI may lead to the beneficiary being blocked, the payment being refunded, or further compliance action.

Questions?

Need help with documentation for a specific corridor? Contact support@trustodi.com.