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 [email protected] 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 Ledger End User Balances via financial_account_id
  ├── joins to Ledger Program Balances via program_id
  └── self-joins via parent_ledger_account_id and business_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: January 5, 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: January 5, 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: January 5, 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: January 5, 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: January 5, 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.

Spec last updated: January 5, 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: January 5, 2026

Ledger Program Balances

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

Spec last updated: January 5, 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.

Spec last updated: January 5, 2026