Every subledger posts through one ledger
GenLedge's general ledger is the posting engine at the core of the platform. AP, AR, banking, and inventory all write journal entries through a single GLPostingService, so double-entry validation, multi-book accounting, five dimensions, and fiscal-period control live in one place and your trial balance always ties. Agents can draft, preview, and post entries, but every posting works with them switched off.
Every subledger posts through one service
Parallel GAAP, IFRS, and tax ledgers
Dimensions on headers and journal lines
Trial balance straight from posted entries
Explore General Ledger
Everything below is a working part of the platform. Pick a capability to see what it does.
One posting path for the whole platform
Every subledger (AP, AR, banking, inventory) writes journal entries through GLPostingService. It validates the entry, resolves the right accounts, and checks idempotency before anything reaches the ledger.
- AP, AR, banking, and inventory post through one service
- Balance and account checks run before every post
- Idempotency checks stop duplicate entries
- Post, reverse, void, preview, and validate operations
A trial balance that always ties
Trial balance is computed straight from posted journal lines, grouped by account with debits, credits, and balance. Filter it by fiscal period, as-of date, or accounting book. Because every subledger posts through the same engine, the numbers reconcile by construction rather than by after-the-fact matching.
- Aggregated live from posted entries, not a snapshot
- Filter by period, as-of date, or book
- Account activity with running balances
Agents draft entries; the ledger stays in control
Journal entries carry AI tracking metadata: the agent, workflow, overall confidence, and field-level decisions behind each posting. Low-confidence entries are flagged for review and every override is counted. The posting engine runs the same whether agents are on or off.
- Per-entry agent, workflow, and confidence recorded
- Low-confidence postings flagged for human review
- Preview and approval before anything posts
Control accounts that repair themselves after a re-sync
When you re-import a chart of accounts from QuickBooks, Xero, or NetSuite, control-account flags can drift. A classifier re-detects which accounts play the AP, AR, inventory, and revenue roles and re-stamps them, so subledger postings keep resolving. It stamps one account per role per subsidiary, and an operator can always override the pick.
- Re-detects control roles after an external re-sync
- Matches by subtype, type, name, then number range
- Operator can always override the pick
Built into General Ledger
Recurring entries
Schedule journals by frequency with optional auto-reversal a set number of days after posting.
Reversals and voids
Reverse a posted entry with a mirrored counter-entry, or void drafts before they post.
Fiscal periods
Open and close periods with soft close, hard close, and audited reopen.
Multi-currency
Post in any currency with base-currency amounts and dated exchange rates on every line.
Approval workflows
Route entries through sequenced approvers with delegation and escalation before they post.
Provider sync
Map accounts and dimensions to QuickBooks, Xero, and NetSuite with echo-safe posting.
Integrates with your existing tools
Questions about General Ledger
Yes. AP, AR, banking, and inventory create their journal entries through GLPostingService, the single posting path. It validates the entry, resolves control accounts, and checks idempotency, so there is one consistent way ledger balances are formed.
See General Ledger on your own data
Book a demo and we'll set up a sandbox with your real data so you can judge it for yourself, before you commit to anything.