What is a ledger?

A ledger is the workspace context your receipts, members, and settings belong to. In current shared code, ledger management is closely tied to organisation management.

The number of ledgers you can manage is subject to your current subscription and deployment policy.

Creating a ledger

Current shared organisation / ledger creation flows prove support for fields such as:

name,
country code,
optional subdivision code,
organisation / ledger type,
optional description.

Common ledger patterns

Use case	Suggested setup
Freelancer with personal and client expenses	One Personal ledger, one ledger per active client
Family household	One shared Household ledger with multiple members as Editors
Small business owner	Business Operations, Travel & Meals, Equipment — matched to tax schedule categories
Accountant managing clients	One organisation per client, one ledger per expense period

Switching between ledgers

Shared clients let you switch the active ledger / organisation context. Receipt lists, capture flows, reporting, banking, and other views then operate inside that current context unless the client explicitly supports cross-ledger filtering.

Editing ledger settings

Current shared settings surfaces support updating organisation / ledger metadata such as name, country / subdivision, description, type, and logo.

Delete, restore, and ownership-transfer behavior depends on the specific client and permission level exposed by your deployment.

Moving entries between ledgers

Current shared receipt detail flows prove that a receipt can be moved to another ledger / organisation:

Open the receipt detail view.
Use the switch-ledger action if your client exposes it.
Select the destination ledger / organisation.
Confirm the move.

This page does not assume a universal default-ledger toggle, archive flow, billing-cycle field, or unlimited-ledger model unless your current client explicitly exposes those controls.