Every transaction, balanced and posted — on books you can trust
A real double-entry general ledger — balance-enforced, approval-gated, and auto-posted from every source document.
Everything General Ledger & Accounting handles
True double-entry, balance-enforced
Journal entries reject any imbalance before they can be saved or posted, and the ledger layer re-verifies balance independently — your books stay balanced by construction.
Approve-then-post with segregation of duties
Posting is a distinct, permission-gated step, and the entry’s own creator can’t post it — the segregation-of-duties control PH CAS books require.
Amount-tiered approval workflows
A posting-rules engine routes high-value entries to the right approval level and blocks posting until the matching authority signs off.
Auto-posting from source documents
GL Account Assignments map each transaction type to the right accounts, so sales invoices, payments, and stock moves post themselves — no hand-picking accounts per entry.
Recurring journal entries
Define an accrual or standard entry once and let it generate on schedule, with catch-up, pause, and resume — instead of re-keying it every period.
Validation-gated period close
Posting respects open-period constraints, and the close runs pre-close validations that block a close from starting on critical failures — with reopen and entry reversal supported.
From action to ledger, in four steps
- 1Capture
Record a journal entry — or let a source document like a sales invoice create one — with lines that must balance to the cent.
- 2Assign
For source-document postings, the account resolver maps the transaction to your assigned GL accounts automatically.
- 3Approve
The entry moves through approval; posting rules route high-value entries to the right tier, and no one posts their own entry.
- 4Post
On posting, period constraints are enforced and an authoritative, balanced ledger record is written — the source of truth for every report.
Real screens, real data
The ledger is the source of truth
Posted GL document lines are the authoritative ledger of record — journal-entry totals are a derived cache. Posting is written so a cache or mirror failure can never block or corrupt the committed ledger.
What you get
- Books stay balanced by construction — unbalanced entries can’t be saved or posted.
- Less manual coding: source documents post to the correct accounts automatically.
- Segregation of duties and tiered approvals are enforced in code, not policy.
- Recurring accruals generate on schedule instead of being re-keyed each period.
- Ask Sebee, your AI CFO, to explain a movement or draft an entry — you review and approve before it posts.
Frequently asked questions
Can someone post their own journal entry?
No. Posting is a distinct, permission-gated step, and the entry's own creator can't post it — the segregation-of-duties control PH CAS books require. A posting-rules engine also routes high-value entries to the right approval tier.
Do the books have to balance?
Yes, by construction. Journal entries reject any imbalance before they can be saved or posted, and the ledger layer re-verifies balance independently — so your books stay balanced.
Do source documents post to the GL automatically?
Yes. GL Account Assignments map each transaction type to the right accounts, so sales invoices, payments, and stock moves post themselves — no hand-picking accounts per entry.
What is the authoritative source of truth?
Posted GL document lines are the authoritative ledger of record — journal-entry totals are a derived cache. Posting is written so a cache or mirror failure can never block or corrupt the committed ledger.