Overview

Lithic Reporting Suite are daily flat files delivered via SFTP. They are generated from Lithic's settlement data and contain transaction-level detail, network summaries, ACH activity, ledger balances, and more. Banks use these for internal accounting, ledger posting, and regulatory reporting.

Access: Lithic Reporting Suite are included for banks where Lithic acts as Program Manager. For other program types, this is available as a paid add-on. Contact support.lithic.com to discuss access and configuration.

Report types

The following reports are available as part of the Bank Reporting Suite. Not all report types are enabled by default — your configuration determines which reports are generated for your program.

PAN availability

Several reports contain card number data. By default, files are delivered without the full PAN. If your institution is PCI compliant, Lithic can be configured to include the full PAN in the Cards and Card Transactions reports.

How the reports relate

The reports are designed to be joined to each other using shared keys. The relationships below show the primary join paths.

Daily Network Settlement Summary
  └── joins to Settlement Detail on report_date + institution_id

Settlement Detail
  ├── joins to Card Transactions on transaction_id
  │     (or transaction_event_id via transaction_event_ids array)
  ├── joins to Accounts via account_id
  ├── joins to Cards via card_id
  └── joins to Ledger Accounts via account_id → ledger_account_id

Card Transactions
  ├── joins to Cards via card_id
  ├── joins to Accounts via account_id
  └── joins to Ledger Accounts via account_id → ledger_account_id

Ledger Accounts  (universal join key: ledger_account_id)
  ├── joins to Card Transactions via account_id
  ├── joins to Settlement Detail via account_id
  ├── joins to Accounts via account_id
  ├── joins to ACH Entries via ledger_account_id
  ├── joins to External Payments via financial_account_id
  ├── joins to Ledger End User Balances via financial_account_id
  ├── joins to Ledger Program Balances via program_id
  ├── joins to Statement Detail via ledger_account_id
  ├── joins to Loan Tape Detail via ledger_account_id
  └── self-joins via parent_ledger_account_id and business_account_id

Loan Tape Detail  (credit programs only)
  ├── joins to Statement Detail on previous_statement_id → statement_id
  └── joins to Ledger Accounts via ledger_account_id

Statement Detail  (credit programs only)
  └── joins to Ledger Accounts via ledger_account_id

Ledger Accounts is the central join file. It consolidates multiple ID types — account_id, program_id, financial_account_id — into a single ledger_account_id column, enabling consistent joins across all reports using the same method. See the Ledger Accounts section for query examples.

Delivery timing

Typical availability: ~11:00 PM ET
Deadline: 12:01 AM ET

Bank Reports are generated after settlement processing is complete for the day. If settlement processing is delayed due to late network file delivery, Bank Report delivery will be delayed accordingly. In most cases this does not affect the 12:01 AM ET deadline, but significant upstream delays can push delivery past target.

Field references

Daily Network Settlement Summary

Daily totals for settled card transactions, interchange, disputes, and miscellaneous fees. Use this report to reconcile daily wires from the networks. Distinct on institution_id and report_date. Can be joined to Settlement Detail on those same fields.

Spec last updated: January 5, 2026

Settlement Detail

Transaction-level breakdown of daily settlement activity including interchange, disputes, and fees. Distinct on settlement_id. Can be joined to Daily Network Settlement Summary on report_date and institution_id, to Card Transactions on transaction_id (or via individual transaction_event_ids in the transaction_event_ids array), and to Ledger Accounts via account_id.

Spec last updated: October 3, 2026

Card Transactions

All card transaction events at the event level. Distinct on transaction_event_id. One row per transaction event — a single transaction (e.g., an authorization followed by clearing) produces multiple rows linked by transaction_id.

PAN availability: By default the pan field is omitted. PCI-compliant institutions can request PAN delivery — see PAN availability.

Fields to know:

transaction_id vs. transaction_event_id — transaction_id groups all events belonging to the same transaction lifecycle (authorization, clearing, settlement). transaction_event_id identifies each individual event. Use transaction_id to join across the lifecycle or to link to Settlement Detail.

is_financial — filter on is_financial = true to work only with events that affect balances. Authorizations appear in the file with is_financial = false.

amount vs. settled_amount — amount is the requested amount at authorization time. settled_amount is the final settled amount and may differ due to partial settlements, reversals, or tip adjustments. Will be null for non-financial events.

network vs. acquiring_network vs. card_issuing_network — network is the parent network (e.g., VISA). acquiring_network is the specific network that processed the transaction (e.g., INTERLINK). card_issuing_network is the network the card belongs to according to its BIN.

Spec last updated: October 20, 2026

Cards

All existing cards, their states, and characteristics. Distinct on card_id. Can be joined to Card Transactions, Settlement Detail, and Accounts via card_id and account_id.

PAN availability: By default the pan field is omitted. PCI-compliant institutions can request PAN delivery — see PAN availability.

Spec last updated: October 27, 2026

Accounts

Cardholder identifying information. Sometimes referred to as an AML report. Distinct on account_id. Can be joined to Settlement Detail, Card Transactions, and Cards via account_id.

Note: This report contains sensitive PII including government IDs, dates of birth, and addresses. Access is restricted to authorized recipients only.

Spec last updated: October 27, 2026

ACH Entries

Daily ACH entries. Distinct on financial_transaction_id, as well as entry_trace_number and settlement_date. Can be joined to Ledger Accounts using ledger_account_id.

Spec last updated: October 3, 2026

Transfers

Event-level data for book transfers and management operations. Captures internal fund movements, fee assessments, rewards, adjustments, and other operational activities that affect account balances.

Bank-level transfers, such as network settlement funding, belong to no program, so their program and organization fields are empty.

Spec last updated: October 20, 2026

External Payments

Event-level data for external payments: funds movements a program processes outside Lithic, such as ACH or wires through another provider, and records in the Lithic ledger through the External Payments API. Lithic records these payments but does not originate or settle them.

One row per payment event per ledger account moved. Distinct on event_id and financial_account_id. A single payment produces multiple events over its lifecycle (e.g., settled and then released), linked by transaction_id. See External Payments Lifecycle.

Rows are limited to accounts whose balances the sponsor bank is responsible for:

• Accounts holding funds on behalf of an owner, as reported in Ledger End User Balances
• Receivables, such as ISSUING_ACCOUNT_RECEIVABLE on credit programs
• Lithic's settlement account at the sponsor bank

Movements on Lithic's internal clearing accounts are excluded, so a payment that moves only clearing accounts does not appear. Events that do not change a balance are also excluded.

Amounts are signed, in the smallest currency unit, using the same convention as the ledger balance reports: adding total_amount to the account's total_balance gives the balance after the event. total_amount equals pending_amount + available_amount.

Report period: each file contains events posted on the day before the report date and recorded in the ledger before 19:00 UTC on the report date. Programs supply the effective date of a payment, so an event can be recorded after that cutoff. That event is included in the next file, with a posted_at earlier than the report period. Each event appears in exactly one file.

Can be joined to Ledger Accounts and Ledger End User Balances using financial_account_id. transaction_id is the external payment token in the Lithic API.

Spec last updated: October 22, 2026

Wires

Event-level data for settled wire activity, covering inbound and outbound wires and reversals. One row per wire event — a single wire can produce multiple rows (e.g., a settlement and a later reversal) linked by transaction_id. Only settled events are included.

Spec last updated: October 15, 2026

Intrabank Transfers

Event-level data for transfers your bank makes between Lithic's settlement account at your bank (its RTN subaccount) and your core, without going through the Fed. One row per transfer event, including reversals. Delivered at the bank level only.

These transfers move Lithic's settlement account balance, which appears in the ledger balance files as the IN_TRANSIT row. How a transfer shows up in the ledger balance files depends on its other side. When the other side is a program's account, as with program funds (BANK_PROGRAM_TRANSFER), that program's balance changes by amount_cents and IN_TRANSIT doesn't change. When the other side is a Lithic account outside the file, as with Lithic's own funds (BANK_LITHIC_TRANSFER), IN_TRANSIT changes by amount_cents. Either way, the change shows in the balances as of the transfer's posted_at. See Ledger Program Balances.

Timing: each file covers transfers that took effect on the day before the report date, by posted_at. A transfer can be recorded in Lithic's ledger after it took effect, so event_at can fall on a later day than posted_at.

Spec last updated: October 27, 2026

Ledger Accounts

A unified mapping file that consolidates multiple ID types (account_id, program_id, financial_account_id) into a single ledger_account_id column. Use this as the central join file across all other reports. Distinct on ledger_account_id.

Hierarchical structure: ledger_account_id creates a parent-child hierarchy via parent_ledger_account_id. Account holders can have multiple financial accounts that roll up to a primary account_id. Business accounts map to their owner via business_account_id. All relationships use the same self-join pattern: child.parent_ledger_account_id = parent.ledger_account_id.

Spec last updated: May 7, 2026

Ledger Program Balances

Daily ledger balances at the program level. Can be joined to Ledger Accounts using program_id and ledger_account_id.

IN_TRANSIT row: depending on your configuration, the file includes a row with program_id of IN_TRANSIT. It isn't a program. It's Lithic's ledger balance for its settlement account at your bank, less the total of every other row in the file: funds held in that account that aren't yet reflected in a program or bank-level balance. The full value is reported in pending_balance, and available_balance is 0. Intrabank transfers of Lithic's own funds move this row by their amount_cents; transfers of program funds move the program's row instead. Both are itemized in the Intrabank Transfers report.

Spec last updated: October 27, 2026

Ledger End User Balances

Daily ledger balances at the most granular level — account, card, end user, etc. Can be joined to Ledger Accounts using financial_account_id and ledger_account_id.

IN_TRANSIT row: depending on your configuration, the file includes a row with financial_account_id and program_id of IN_TRANSIT. It carries the same value as the IN_TRANSIT row in Ledger Program Balances, which describes it.

Spec last updated: October 27, 2026

Statement Detail

Statements created or updated since the previous file, one row per statement. Distinct on statement_id within a file. Can be joined to Ledger Accounts using ledger_account_id, and to Loan Tape Detail on statement_id to previous_statement_id.

Available only for credit programs. Rows appear only for accounts on a credit product that has statements enabled, so a program without one receives a header-only file.

Report period: each file contains statements created or updated from 15:00 UTC the day before the report date to 15:00 UTC on the report date, by statement_updated_at. A statement is generated after its period ends, so it usually appears within two days of its statement_end_date. An updated statement appears again in a later file with a later statement_updated_at; keep the latest row per statement_id.

Spec last updated: October 27, 2026

Loan Tape Detail

Daily snapshot of a credit account's balances, limit, and delinquency state. One row per ledger account per day, for every day the account is open, whether or not anything changed. Distinct on loan_tape_id within a file. Can be joined to Ledger Accounts using ledger_account_id, and to Statement Detail on previous_statement_id to statement_id.

Available only for credit programs, under the same conditions as Statement Detail.

Report period: each file contains loan tapes written or restated from 15:00 UTC the day before the report date to 15:00 UTC on the report date, by loan_tape_updated_at. A day's loan tape is written the following day, so a file normally carries the snapshots dated the day before the report date. A loan tape written late or restated appears in the file covering when it was written, with a later loan_tape_updated_at; keep the latest row per loan_tape_id.

Monetary fields are in the currency's smallest unit (cents for USD). available_credit is credit_limit less total_balance.

Spec last updated: October 27, 2026