Funding Report
The Funding Report contains all funds transferred (credits and debits). All transactions are part of a batch that Trustly sends to the merchant's bank account for the reporting period.
The Funding Report structure
The Funding Report consists of individual rows of data. Each row provides one of four types of data, identified by a unique Record Type Indicator:
- Header (
H): Always the first row of the report. - Funding Record (
F): Represents a single batch settlement from the payment processor. - Item Record (
I): Represents an individual transaction (the core data). - Trail (
L): Always the last row, providing a final summary of the report.
Understand transaction status
To properly reconcile funds, you need to understand how the Funding Report categorizes pending and settled transactions.
Pending transactions
If an item record is pending (not yet settled), it appears at the top of the report, above the funding records. Pending item records have an amount of $0, do not have a funding trace identifier, and Trustly includes them in the report to show status changes that affect future settlements.
Settled transactions
Transactions that have settled appear as item records under a funding record. This indicates which batch settlement they were in. A single report may contain multiple funding records.
Trail items
The Trail provides a summation of the report's contents. It shows the total number of transactions, the total number of funding records, and the total amount settled to the merchant.
File format
Each line in the Funding File uses a Record Type Indicator as a prefix to identify the type of information it conveys.
Header
The first line of the report is always the Header. For example:
The following table lists the fields and information contained in the Header.
| Field name | Max length | Format | Required | Sample data | Notes |
|---|---|---|---|---|---|
| Record Type Indicator | 1 | H | Yes | H | Always H. |
| Magic | 7 | P11KFUN | Yes | P11KFUN | Magic number. |
| Version | 11 | Alphanumeric | Yes | 1.0.0 | File version. |
| Start Date | 24 | UTC Date Time in ISO 8601 format | Yes | 2017-01-21T12:00:00Z | Report start date. |
| End Date | 24 | UTC Date Time in ISO 8601 format | Yes | 2017-01-22T12:00:00Z | Report end date. |
| Merchant ID | 50 | Numeric | Yes | 10000000234 | Merchant identifier. |
| Sequence | 10 | NNNNofNNNN | Yes | 0001of0002 | File sequence. A report can break into multiple files. |
Funding record
A Funding Record is created for each batch settlement that takes place with the payment processor. The individual Item Records under each Funding Record make up the sum of the settlement. For example:
The following table lists the fields and information contained in the Funding Record line.
| Field name | Max length | Format | Required | Sample data | Notes |
|---|---|---|---|---|---|
| Record Type Indicator | 1 | F | Yes | F | Always F. |
| Processor | 50 | Alphanumeric | Yes | ProfitStars | Payment processor |
| Reserved | 0 | No | V3 Default Layout - Receiver Account Number last four digits. | ||
| Batch ID | 50 | Alphanumeric | Yes | A12341234 | Batch identifier. Links the funding record and item record. |
| Amount Currency | 3 | Alphanumeric | Yes | USD CAD | Amount currency. |
| Amount | 18 | Decimal String | Yes | -100.00 | Amount. |
| Funding Date | 24 | UTC Date Time in ISO 8601 format | Yes | 2017-01-21T13:42:03Z | Funding date and time. |
Item record
An Item Record is a transaction that occurred with the merchant. For example:
The following table lists the fields and information contained in the Item Record line.
| Field name | Max length | Format | Required | Sample data | Notes |
|---|---|---|---|---|---|
| Record Type Indicator | 1 | I | Yes | I | Always I. |
| Transaction ID | 50 | Alphanumeric | Yes | 100000234235 | Transaction identifier. |
| Transaction Created At | 24 | UTC Date Time in ISO 8601 format | Yes | 2017-01-21T13:42:03Z | Transaction create date and time. |
| Parent Transaction ID | 50 | Alphanumeric | Yes | 100000234234 | Parent Transaction identifier. |
| Merchant ID | 50 | Numeric | Yes | 10000000234 | Merchant identifier. |
| Payment Provider Type | 20 | Numeric | Yes | 1 | Payment provider type. |
| Payment Provider ID | 9 | Alphanumeric | Yes | 023456737 | Payment provider identifier |
| Payment Account | 4 | Numeric | Yes | 1234 | Last four digits of the payment account. |
| Merchant Reference | 90 | Alphanumeric | No | MREF122344 | Merchant reference. |
| Transaction Type | 30 | Alphanumeric | Yes | Refund | Transaction type. |
| Transaction Status | 30 | Alphanumeric | Yes | Authorized | Transaction status. |
| Transaction Updated At | 24 | UTC Date Time in ISO 8601 format | Yes | 2017-01-21T23:42:03Z | Transaction last update date and time. |
| Transaction Processed At | 24 | UTC Date Time in ISO 8601 format | Yes | 2017-01-21T23:42:03Z | Transaction processed date and time. |
| Amount Currency | 3 | Alphanumeric | Yes | USD CAD | Amount currency. |
| Amount | 18 | Decimal String | Yes | -100.00 | Amount. |
| Funding Trace ID | 50 | Alphanumeric | No | A12341234 | Funding trace identifier. |
| Payment Provider Transaction Status | 5 | Alphanumeric | No | R03 | Payment provider transaction status. For returned items, this is the return reason code. |
| Batch ID | 50 | Alphanumeric | No | 3424 | Batch identifier representing a group of transactions. |
| Settlement Type | 3 | Alphanumeric | No | 20 | Internal. |
| Parent Merchant Reference | 90 | Alphanumeric | No | MREF122 | Merchant reference of the parent transaction. |
| Payment Provider Transaction ID | 40 | Alphanumeric | No | ptx-5sq8ku8smVrss6Pc7-cOVBbI- | Payment Provider Transaction ID. Trustly sends this as the identifier to the Automated Clearing House (ACH) processor. |
| Transaction Fee | 18 | Decimal String | No | -0.29 | Fee deducted from the funding of the transaction. This is only applicable if you participate in Net Settlement. |
V3 - Default layout displays item records that are not linked to transactions, such as returned sweep and adjustment (ATP).
Trail
The Trail indicates the end of the report and is a summation of the records within the report. For example:
The following table lists the fields and information contained in the Trail line.
| Field name | Max length | Format | Required | Sample data | Notes |
|---|---|---|---|---|---|
| Record Type Indicator | 1 | L | Yes | L | Always L. |
| Num Item Records | 9 | Numeric | Yes | 300 | Total count of the item records. |
| Total Items Amount | 18 | Decimal String | Yes | 100.00 | Total sum of the transaction records amount. |
| Total Funding Records | 9 | Numeric | Yes | 300 | Total count of the funding records. |
| Total Funding Amount | 18 | Decimal String | Yes | 100.00 | Total sum of the funding records amount, less any transaction fees (if participating in Net Settlement). |
Funding report cut offs
Based on the payment type, funds settle to the merchant or consumer account according to the cutoff days and times and the expected settlement date. This information helps you determine when the transactions appear in the merchant settlement report.
Most transactions appear in the funding report on the business day following settlement to the merchant account. Contact your Customer Success Manager for the exact cutoff days and times based on the payment types you use.
Updated 22 days ago