Corporate LinX - Documentation Library
Funder Response File
This section describes the expected structure of the Funder Return File returned by a funder after processing the transactions provided in a Return File. Each row in the file represents the funder's outcome for a single transaction.
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 funder response file to look like. Each row represents a transaction that has either been paid or rejected by the funder.
CLXId;State;GrossValue;Currency;PaymentReference 4d4f2e59-2a7e-4a72-8fd4-0ff9b6a8f9c1;Paid;975.00;GBP;PAY-983746 9b6d1b4a-5f1f-45d2-9049-c2a16c0f5a7e;Rejected;487.50;GBP;
Data Overview
| Element Name | Type | Description | Required? |
|---|---|---|---|
| CLXId | Guid | The Corporate LinX unique identifier for the funded transaction item. This should match the CLXId provided in the original return file. | Yes |
State | String | The funder's processing outcome for the transaction, accepted values are Paid or Rejected | Yes |
| GrossValue | Number | The gross value of the transaction being paid or rejected. | Yes |
| Currency | String | 3-letter currency code | Yes |
| PaymentReference | String | The funder payment reference. Required when the state is paid; leave blank if the state is rejected. | Yes |
State Values
| State | Description |
|---|---|
| Paid | The funder has accepted and paid for the transaction |
Rejected | The funder has rejected the transaction and will not pay it |
Notes
- CLXId should be used to match each row back to the transaction submitted in the original return file.
- State must be populated for every row and must be either Paid or Rejected.
- PaymentReference is required when the State is Paid.
- PaymentReference should be left blank when the State is Rejected.
- GrossValue should be formatted using UK number formatting, for example, 1000.00.
- Currency should be supplied as a three-character ISO currency code.
- The CSV file should use semicolon delimiters, matching the existing B2B CSV file examples.
- Each transaction submitted to the funder should have one corresponding row in the Funder Return File.