Corporate LinX - Documentation Library
Fundable Set (Returns)
This page describes the expected structure of the "fundable set" of transactions, also known as a "return file", used by the Corporate LinX B2B process for our clients. Each row in the file represents a funding accepted transaction item.
The file should use semicolon delimiters and include the fields listed below.
If you require any help with the file format, reach out to our support team.
Example
The data below shows an example of what we expect the data in a return file to look like. Each row represents a returned-funded transaction item.
CLXId;BuyerReference;SupplierReference;FunderReference;BuyerDocumentReference;SupplierDocumentReference;AcceptanceDate;FunderPaymentDate;BuyerPaymentDate;DiscountApplied;TransactionValue;FundableValue;Currency 4d4f2e59-2a7e-4a72-8fd4-0ff9b6a8f9c1;BUY001;SUP001;FND001;INV-10001;SUP-INV-10001;2024-01-15;2024-01-18;2024-01-20;25.00;1000.00;975.00;EUR 9b6d1b4a-5f1f-45d2-9049-c2a16c0f5a7e;BUY001;SUP002;FND001;INV-10002;SUP-INV-10002;2024-01-16;2024-01-19;2024-01-22;12.50;500.00;487.50;GBP
Data Overview
| Element Name | Type | Description | Required? |
|---|---|---|---|
| CLXId | Guid | The Corporate LinX unique identifier for the funded transaction item | Yes |
BuyerReference | String | Client's reference for the buyer. | Yes |
| SupplierReference | String | Client's reference for the supplier. | Yes |
| FunderReference | String | Client's reference for the funder. | Yes |
| BuyerDocumentReference | String | The Client's reference for the document or transaction being returned | Yes |
| SupplierDocumentReference | String | The supplier's reference for the document of transaction being returned (often known as the invoice number_ | Yes |
| AcceptanceDate | String | The date on which the funding offer or transaction was accepted | No |
| FunderPaymentDate | String | The date on which the funder made, or is expected to make, payment | No |
| BuyerPaymentDate | String | The date on which the buyer made, or is expected to make, payment | No |
| DiscountApplied | Number | The discount amount applied to the transaction | Yes |
| TransactionValue | Number | The gross transaction value before discount | Yes |
| FundableValue | Number | The value of the transaction that was fundable before the discount has been applied | Yes |
| Currency | String | 3-letter currency code | Yes |
Notes
- Dates should be in the format yyyy-mm-dd. This applies to AcceptanceDate, FunderPaymentDate, and BuyerPaymentDate.
- Monetary values should be formatted using UK number formatting, for example, 1000.00.
- CLXId should be treated as the unique Corporate LinX identifier for the returned item.
- Empty date values are permitted where the corresponding date has not yet been set.
- The CSV file should use semicolon delimiters, matching the existing B2B CSV file examples.