Payment Documentation

Documentation Expectations

Payment documentation provides evidence that payments are being created within the allowed activities and restricted activities guidelines. Common supporting documents include invoices, purchase orders, contracts/agreements, delivery receipt/completion, expense report, bank statement/details, tax documents, etc.

Regardless of the type of document, we expect that the document to be authentic, legible, and consistent, and that it will explicitly lay out at a minimum:

• Who is the recipient of the payment (e.g. who is issuing the invoice)
• Who is the sender of the payment (e.g. to whom is the invoice issued)
• The amount to be sent and in what currency
• Details about the relationship between the two entities (e.g. itemization of what was purchased, services renderedholding-subsidiary relationship)
• Dates applicable (e.g. when was the service provided)

While our Payments API endpoints at the moment do not automatically require payment documentation to be uploaded, we expect all payments to have readily available support documents upon request with details that match the payment information being submitted. Any information discrepancies may result in additional questions and payment delays.

Invoice Financing/Factoring

We recognize that many businesses, especially in emerging markets, make use of invoice financing/factoring. At Reap we are open to supporting this use case as long as proper documentation exists, including documentation of the financing deal/invoice purchase and the relationship between the parties involved. Please reach out if you are interested in making payments associated with invoice financing/factoring so we can work together to understand your needs.