Operational Subledger

An operational subledger retains detailed records for a defined business process, such as payments or prepaid balances, that can support reconciliation and accounting mappings. In this article the term describes the payment movement view. It is not a claim that the table is a complete accounting subledger or general ledger.

A capture of 100 USD and a processor fee of 3 USD can appear as signed movements +100 and −3 from the processor-balance perspective. Their net is +97 USD. This does not imply a 97 USD bank deposit or 97 USD recognized revenue: settlement, other balance movements, and the applicable accounting mappings remain to be established.

Keep stable movement IDs, source references, original currency and scale, effective and observed times, and correction lineage. An event delivery is not necessarily a new movement. Preserve reversals and approved corrections without erasing the evidence behind an issued report; access and retention rules still apply.

A double-entry journal adds debit and credit accounts and balanced entries under an approved policy. Reconcile the operational detail to mapped journal totals and explain differences such as timing, taxes, or omitted scope. A table’s name and append-only storage do not supply those mappings or prove completeness.

See Integrating Payment, Commerce, and Finance Data for worked examples.