Feature · Books cleanup
BeanStack reviews the ledger it inherits — reclasses, duplicate accounts, splits, treatment errors — and sends a governed correction batch for your approval. It proposes; it never rewrites history on its own.
Early access — onboarding a limited number of PE-backed companies.
An AI books review walks the chart and the postings — misclassified expenses, split-account sprawl, treatment inconsistencies, stale balances.
Fixes arrive as reversible reclass proposals with the reasoning and evidence attached — never destructive edits.
Duplicate and fragmented accounts are consolidated or split under approval, so the chart converges instead of sprawling.
Duplicate vendors and customers are detected before they fragment the books; safe merges apply under policy, ambiguous ones come to you.
The full history comes over — mess included. Nothing is silently "fixed" during migration.
Corrections arrive as one review batch: each item with its evidence, reasoning, and effect on the statements.
Approved corrections post through the normal controls, with the full audit trail linking every change to its approval.
Cleanup runs on the same governed ledger and approval controls as everything else.
Early access — onboarding a limited number of PE-backed companies.