For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dashboard
GuidesAPI ReferenceSDKs
GuidesAPI ReferenceSDKs
  • Get Started
    • Overview and Solutions
    • Choose an Integration
    • Quickstart
    • Branding Guidelines
    • Get Support
  • Accept Payments
    • Instant Payments
    • Trustly Pay
    • Recurring Payments
    • Scan and Pay
    • Remember Me
    • Payment Integration Checklist
  • Send Money
    • Send Payouts Using Online Banking
    • Send Payouts Using Account Information
    • International Transfers
  • Retrieve Data
    • Verify Accounts Using Online Banking
    • Verify Accounts Using Micro-Deposits
    • Retrieve Bank and User Information
    • Tokenize Bank Information
    • Trustly ID
    • Insights Data
  • Core Concepts
    • Key Concepts
    • The Establish Data Object
    • Transactions and Transaction IDs
    • Tokens and Account Security
    • Redirect URLs and Return Flow
    • Webhooks and Events
    • Content Strings
  • API Fundamentals
    • Authentication and OAuth
    • Secure Requests and Signature Validation
    • Idempotency
    • Testing
    • Status codes and type definitions
  • Manage Your Integration
    • Go-Live Checklist
    • Merchant Portal
    • Reports and Reconciliation
      • Funding Report
      • Reconciliation and Funding Report
      • Reconciliation Report-BNY
      • RTP Report
      • VIP Program
    • Refresh Bank Authorization
    • Override Risk Declines
    • VIP Tiers
    • Financial Institution Status
Dashboard
Products
PaymentsDataPayouts
Company
AboutCareersContact Sales

Terms of Use | Privacy Policy | © 2026 Trustly, Inc.

Developer-friendly docs for your API
GitHub|Contact Support|Business Help Center|Merchant Portal
Terms of Use|Privacy Policy|© 2026 Trustly, Inc.
Developer-friendly docs for your API
LogoLogo
North AmericaEurope
North AmericaEurope
On this page
  • Reading the Reconciliation Report
  • Reconciliation Report Fields
  • Header
  • Transaction Record
  • Trail
Manage Your IntegrationReports and Reconciliation

Reconciliation Report-BNY

|View as Markdown|Open in Claude|
Was this page helpful?
Previous

Reconciliation & Funding report

Next

RTP Report

Built with

Reading the Reconciliation Report

The Reconciliation Report contains any transactions that were created during the reporting period (excluding RTP transactions).
How to Read the Reconciliation Report
The Reconciliation Report consists of individual rows of data. Each row provides one of three types of data:

  • Header
  • Transaction Record
  • Trail

Each row contains only one type of data and begins with a Record Type Indicator, which conveys the data type. For example, the file header rows indicator is H while the individual transaction rows have an indicator of T.

Every report begins with the Header and ends with the Trail.

All transaction records in the report reflect the transaction events created during the reporting period. The event status will reflect the status after the event for the record.
Some transactions will have a parent transaction ID, or original transaction ID, as shown in the example below.
The original transaction was an authorization, and then the child transaction was the capture.

The trail shows how many transactions were part of the report and the total amount of the transactions created during the reporting period.

Reconciliation Report Fields

Each line in the Reconciliation File is prefixed with a Record Type Indicator that dictates the type of information it is conveying.

Header

The first line of the report is always the Header and it looks like this:

This line contains the following fields and information:

Field NameMax LengthFormatRequiredSample DataNotes
Record Type Indicator1HYesHAlways H
Magic7P11KRECYesP11KRECMagic numberAlways P11KFUN
Version11AlphanumericYes1.0.0File version
Start Date24UTC Date Time in ISO 8601 formatYes2017-01-21T12:00:00ZReport start date
End Date24UTC Date Time in ISO 8601 formatYes2017-01-22T12:00:00ZReport end date
Merchant ID50NumericYes10000000234Merchant identifier
Sequence10NNNNofNNNNYes0001of0002File sequence. A report can be broken into multiple files

Transaction Record

A transaction record provides details for an event that occurred with the merchant and it looks like this:

This line contains the following fields and information:

Trail

The Trail indicates the end of the report and is a summation of the records within the report. It looks like this:

This line contains the following fields and information:

Field NameMax LengthFormatRequiredSample DataNotes
Record Type Indicator1LYesLAlways L
Num Item Records9NumericYes300Total count of the item records
Total Items Amount18Decimal StringYes100.00Total sum of the transaction records amount
Currency3AlphanumericNoUSDCurrency of total value of financing records.