Ledger & audit

The ledger & audit view in the Recurso dashboard

Two integrity screens

Two screens back the integrity of your books:

Financial Ledger — the double-entry ledger of every posted transaction, browsable by account, with each account’s running balance.
Audit Log — an append-only trail of every config-grade change made in the workspace.

Both are read-only views: they show what happened, they don’t let you edit history.

Financial Ledger

The Financial Ledger shows double-entry transactions and account balances. PostgreSQL is the authoritative ledger; TigerBeetle, when enabled, is an optional mirror (see Reconciliation for the cross-check).

Select an account

The Select account dropdown lists your chart of accounts. Each entry shows the account name and its numeric code — for example Accounts Receivable (1100). Every customer has their own AR sub-account, so those entries are additionally labelled with the customer name to tell them apart. The first account is selected automatically on load.

Read the current balance

The Current Balance card shows the selected account’s balance in its own currency.

Review the entries

The table lists that account’s ledger entries (most recent first, up to 50).

Each entry row shows:

Column	Shows
Transaction ID	The ledger transaction’s identifier
Debit	The account debited (customer/account name where known, else the raw ID)
Credit	The account credited (customer/account name where known, else the raw ID)
Amount	The transaction amount, in the account’s currency
Code	The posting code that classifies the transaction

Because entries are double-entry, every transaction names both a debit and a credit account — the two sides always move together. To confirm the whole book balances, use the Trial Balance report.

Posting codes

Every ledger transaction carries a posting code — what the movement is, in words. The dashboard shows these as labels; the full glossary:

Code	Label	What it records
1	Invoice raised	The receivable at issue — customer AR against Deferred Revenue (subscriptions) or Revenue (one-offs), at the gross amount
2	Revenue recognized	One recognition event moving its slice from Deferred to Recognized Revenue
3	Payment	Cash settling the customer’s receivable
4	Refund	Cash returned to the customer
5	Refund — deferred reversal	The still-unearned portion of a refunded invoice leaving Deferred
6	Output tax	The tax slice reclassified from Deferred to Tax Payable
7	Credit applied	Account credit offsetting an invoice
8	Credit note	A credit note issued (Credits Issued against Customer Credit)
9	Refund — tax reversal	The tax slice of a refund leaving Tax Payable
10	TDS receivable	Tax withheld at source by the customer, recoverable against income tax
11	Wallet top-up	Prepaid wallet funding (booked as cash at top-up)
12	Wallet drain	Wallet balance consumed against an invoice
13	Wallet refund	Wallet balance returned to the customer
14	Wallet forfeit	Wallet balance forfeited on closure
15	Wallet expiry	Wallet balance expired per policy
16	Downgrade credit	Proration credit minted by a plan downgrade
17	Downgrade — tax reversal	The tax slice of a downgrade proration
18	Credit expiry	Account credit expired per policy
19	Payment reversal	A settled payment clawed back by the bank (e.g. an ACH return) — AR reinstated, cash removed
20	Credit void	A credit note voided before use
21	Downgrade — revenue reversal	Recognized revenue unwound by a downgrade
22	Write-off	An uncollectible invoice’s reversal — Deferred (or Revenue) and the receivable both relieved
23	Write-off — tax reversal	The tax slice of a write-off leaving Tax Payable
24	Write-off recovery	A written-off invoice paid after all — the receivable and Deferred re-established before the payment settles
25	Write-off recovery — tax	The tax slice re-established on recovery

Codes 19 and 22–25 can repeat for one invoice across settle → reverse → re-settle cycles; each cycle posts fresh legs, so the history stays complete and append-only.

Audit Log

The Audit Log records every configuration change, immutably. Updates and deletes are rejected at the database, so the trail can’t be rewritten — it’s append-only by design. Config-grade mutations across the product land here: plans, metrics, wallets, webhooks, team changes, and more. Each row shows:

Column	Shows
When	The timestamp of the change
Actor	Who made it — an API key badge, or the truncated user ID
Action	The action performed
Entity	The entity type affected, and its short ID
Status	The HTTP result code, badged green for success (`< 300`) or red otherwise

Filter by entity

Use the All entities dropdown in the toolbar to narrow the log to a single entity type (the options are drawn from the entity types present in the log). The view loads the most recent entries (up to 200).

Only successful config-grade mutations are recorded. Day-to-day billing activity (individual invoices, payments) is tracked in its own screens, not the audit log.

Finance reports

Trial balance, reconciliation, revenue recognition, and more.

Team & security

Members, roles, and sessions — the actors behind audit entries.

Getting Started

Customers & Subscriptions

Monetization

Retention & Risk

Finance & Records

Platform

Workflows

Two integrity screens

Financial Ledger

Posting codes

Audit Log

Filter by entity

Finance reports

Team & security

Posting detail

​Two integrity screens

​Financial Ledger

​Posting codes

​Audit Log

​Filter by entity

​Related

Finance reports

Team & security

​Posting detail

Two integrity screens

Financial Ledger

Posting codes

Audit Log

Filter by entity

Related

Posting detail