Ledger is being built for side-by-side review of a ledger and bank statements. The central requirement is a consistent allocation history across all accounts, so switching banks does not make a completed ledger item available again.
FOLLOW THE WORKFLOW
See how the work fits together.
01Confirm account & statement period
02Preview debit & credit interpretation
03Match supported movements
04Leave exceptions for investigation
FICTIONAL WORKFLOW EXAMPLE
A transfer that should not look like a receipt
Illustrative only: a statement line shows a ₹40,000 credit that is in fact a transfer between the business’s own accounts, not a customer receipt. Matching it to an open invoice would close the wrong item, so the intended review leaves the line unmatched until its meaning is established.
A match explains a movement; it does not establish the accounting classification. Source compatibility, statement coverage and production readiness still need validation.
Validate both sides first
Before matching, confirm dates, signs and statement coverage. A receipt in a ledger and a credit in a bank export may represent the same movement, but headings alone are not enough to establish the interpretation.
Confirm the account and statement period.
Preview debit and credit interpretation and inspect rejected lines.
Check for overlapping or duplicate statement uploads.
Allocate only the amount still available
Consider a fictional receipt of ₹12,000 paid as ₹7,000 into one account and ₹5,000 into another. After the first allocation, only ₹5,000 should remain available against the ledger item. After both, it must be complete across every account.
Support a clear distinction between original, allocated and remaining amounts.
Recheck remaining amounts when confirming a match.
Review a reversal explicitly before making an amount available again.
Investigate exceptions separately
Bank fees, date differences and missing entries should not disappear inside a convenient match. An unresolved difference needs a reason and the appropriate source record or accounting follow-up.
Leave unexplained amounts unmatched for investigation.
Keep transfers separate from customer receipts where their meaning differs.
Review the supporting evidence before closing an exception.
Questions about reconciliation
Can Ledger connect directly to our bank?
The starting approach uses uploaded statements and supported exports. A live bank feed or automatic connector is not implied and would need separate confirmation.
What happens to a difference we cannot explain?
It should stay visible as an unmatched exception rather than being forced into a convenient match. A bank charge or a date difference is one possible explanation, not an automatic conclusion.
What to bring to the discussion
The number of bank accounts and how often statements are exported.
A fictional split payment and a bank-charge example.
Who reviews matches and who can reverse a decision.
