Your numbers, safe and provable

Accounting software asks for a lot of trust. Here's what we do to earn it, in plain language — and, for anyone who wants the detail, exactly how.

History cannot be rewritten

Once a transaction is posted it can't be silently edited or deleted. Fixing a mistake creates a visible correction, so last quarter's numbers stay the numbers you reported.

immutable posted journals

Every cent is exact

Amounts are stored as exact decimals, not the approximate numbers most software uses. Totals don't drift by a penny and then argue with your bank statement.

no floating-point money, anywhere

Closed months stay closed

When you close a period, nothing can sneak a transaction back into it — not an import, not a recurring job, not an old draft.

period locks on every source

Your data is only ever yours

Every business's records are separated at the database level as well as filtered in the app, adding a backstop if application filtering is ever wrong.

row-level security plus explicit checks

Permissions say no by default

People see and do exactly what their role allows. Anything not explicitly permitted is refused rather than quietly allowed.

fail-closed authorization

An audit trail worth the name

Who did what and when, with the affected record and key event details — recorded as part of the change itself, so it can't be missing later.

append-only, written in the same transaction

Give your bookkeeper a login, not your password

Workspace invitations and fail-closed roles are available now: a bookkeeper signs in as themselves, and read-only or member access cannot quietly become administrator access. Time-boxed external-advisor grants, bilateral revocation and advisor-specific scopes are part of the published roadmap and are not available yet.