Every cent, accounted for.
Every payment, fee, refund, transfer, conversion and payout on Lyria is written to a double-entry ledger. Balances come from the record, not alongside it, so finance, operations and auditors are always looking at the same numbers.
| Account | Debit | Credit |
|---|---|---|
| Provider receivable | 125.00 | |
| Merchant balance | 121.25 | |
| Processing fees | 3.75 |
Finance-grade data, from the first transaction.
Reporting is a view of the ledger, so every number can be traced back to the entries that produced it.
Double-entry accounting
Every movement creates balanced debit and credit entries that cannot be edited, only reversed.
Real-time balances
Available, pending and reserved balances per account and currency, at any moment.
Provider reconciliation
Provider reports are matched to ledger entries automatically, with breaks flagged for review.
Analytics
Approval rates, decline reasons, fees and volumes by provider, method, market and period.
Exports
Scheduled files, API access and warehouse delivery for your finance stack.
Audit trail
Each entry links to the event, request and user that caused it.
From event to report.
Event
A payment, transfer or payout changes state.
Entry
Balanced ledger entries are written.
Match
Provider data is reconciled against them.
Report
Balances and reports update in real time.
Ledger & Reporting at a glance.
- Model
- Immutable double-entry ledger with reversal entries for corrections.
- Granularity
- Per transaction, fee, account and currency.
- Access
- Operations console, API and scheduled exports.
- Formats
- CSV and JSON, with data warehouse delivery on request.
- Retention
- In line with Canadian record-keeping requirements.
- Permissions
- Role-based access for finance, operations and audit users.
Query every entry by API.
One request style across every Lyria product, with idempotency, signed webhooks and a sandbox that mirrors production.
- Immutable entries, corrected only by reversal
- Every entry links to the event that caused it
- Export to your warehouse or finance stack
GET /v1/ledger/entries?payment=pay_9KD [ { "account": "provider_receivable", "debit": 125.00 }, { "account": "merchant_balance", "credit": 121.25 }, { "account": "processing_fees", "credit": 3.75 } ]
Complete your stack.
Every product shares the same ledger, data model and controls, so adding the next one is a configuration change.
Questions about Ledger & Reporting.
Can ledger entries be edited?
Can we send data to our own warehouse?
How do you handle reconciliation breaks?
Is reporting real time?
Give finance one source of truth.
Tell us about your flows and volumes, and we will show you how Ledger & Reporting fits alongside the rest of your stack.