Every controller running a month-end close in ERPNext knows the gap: the General Ledger and Trial Balance reports tell you the balance of a GL account, but they never tell you whether that balance is proven. Cash, prepaid expenses, accrued liabilities, intercompany, fixed-asset clearing, tax payable, suspense and other balance-sheet accounts each need a schedule that ties the number to reality — bank statements, aging, amortization tables, third-party confirmations. ERPNext core has Bank Reconciliation and Payment Reconciliation, but there is no native DocType that lets you reconcile an arbitrary balance-sheet account, attach its supporting schedule, flag the variance, and route it through a preparer-then-reviewer sign-off. Teams end up doing this in spreadsheets outside the system, so the close has no single source of truth and no audit trail.

This build-to-order app closes that gap as a proper Frappe application installed on your bench. We ship a custom app with a Balance Sheet Reconciliation DocType keyed to Company, Fiscal Year and period-end date, with a child table for line-item supporting schedules and a File-attach field for evidence. A server script (or app-level controller in hooks.py doc_events) pulls the GL closing balance for the selected account and posting date straight from GL Entry, so the "book balance" is always live and never rekeyed. The reconciled balance, variance, and a variance-tolerance check are computed on validate; anything outside tolerance is blocked from sign-off or flagged for explanation. Open-item aging is generated for sub-ledger-backed accounts (receivable/payable/advances) so reviewers see exactly which vouchers make up the balance.

The workflow itself is a real Frappe Workflow: Draft → Prepared → Under Review → Approved (with a Rework state), gated by role profiles such as Reconciliation Preparer and Reconciliation Reviewer so a preparer can never approve their own work. Transitions stamp the user and timestamp, and every field change is captured in the standard Frappe version/audit trail. A scheduler_events hook auto-creates the period's reconciliation records from a close checklist at period-end and can email owners the accounts still outstanding. Client scripts drive the form UX — live variance display, conditional evidence requirements, one-click "pull GL balance." Everything is exposed over the Frappe REST API and @frappe.whitelist() methods so your close dashboard, Power BI, or an external audit tool can read reconciliation status programmatically. The app targets Frappe/ERPNext v15 and v16.

Because this is build-to-order, nothing is downloaded and dropped in blind. We start from a short scoping call, confirm which balance-sheet accounts and tolerance rules matter for your entity, then build against your actual chart of accounts and role structure. Typical delivery is one working week from confirmed scope. You get the installable source, UAT on a staging bench with a rollback plan, install and configuration on your environment, documentation, a training session, and a post-go-live support window — plus the git repository handover so the code is yours.