Bank reconciliation is how you confirm that what your bank says happened matches what Sevenledger recorded. Upload a statement — CSV, PDF, scanned image, or even a handwritten sheet — and the system automatically extracts each transaction, matches it against your journal entries, and flags anything that doesn’t line up.
Reconciliation is a paid add-on. Each time you finalize a reconciliation run, one unit is consumed from your monthly entitlement. Draft and in-review runs don’t cost anything — only finalization does.
Create a Reconciliation Run
Navigate to Reconciliation
Go to Financials and select Reconciliation. Click New to start a fresh run.
Select your bank account
Pick the account from the Bank Account dropdown. This should match the account on the statement you’re reconciling (e.g., “NIC Asia - Current Account”).
Set the statement period
Enter the Statement Start Date and Statement End Date. These define the window of transactions the system will search for matching journal entries.
Enter the closing balance
Type in the Statement Closing Balance exactly as it appears on your bank statement. This is the figure Sevenledger will compare against once all matches are made.
Choose the source type and upload
Select how you’re providing the statement:
| Source Type | When to use |
|---|---|
| CSV | Exported directly from your bank’s online portal — cleanest and fastest |
| Standard bank-issued PDF statement | |
| Image | A photo or scan of a printed statement |
| Handwritten | A physical count sheet or manually written ledger |
Upload your file, then click Process. The system sends it through OCR extraction — this usually takes a few seconds for CSV and up to a minute for scanned images.
File limits: Maximum 20 pages per document, 12 MB file size. If your statement is longer, split it across multiple runs covering different date ranges.
Review extracted lines
Once extraction completes, you’ll see a table of all detected transactions — each with a date, description, amount, and direction (Debit or Credit). Scan through them before matching:
- If OCR misread a value, click the line to edit the Description, Amount, or Direction directly.
- Lines where extraction failed are flagged — use Re-extract Line to retry OCR on that specific row.
Match Lines to Journal Entries
With your lines extracted, you’re ready to match. The system does most of the heavy lifting automatically — you step in for the edge cases.
Auto-matching
As soon as extraction finishes, Sevenledger runs an auto-match pass across all lines. It looks for journal entries in your ledger that fall within tolerance:
- Amount: ±0.5% of the statement line amount
- Date: ±5 days of the statement line date
Matched lines show a green Auto badge. Unmatched lines stay open for manual review.
Match Workspace
For unmatched lines, open the Match Workspace to see a list of candidate journal entries. You can:
- Select one or more journal entries to match against a single statement line — useful when a single bank transfer covers multiple smaller transactions recorded separately in your books.
- Override an auto-match if you know the system got it wrong.
The match source updates to Manual so you can always tell which matches you confirmed yourself.
Many-to-one matching: One bank line can match to several journal entries. If your bank batched three supplier payments into a single transfer of Rs 45,000.00, match that one line to all three journal items at once.
Finalize and Void
Finalize
Once you’re satisfied with your matches, click Finalize. The run moves to Completed, all edits are locked, and one entitlement unit is deducted from your plan.
Use Finalize only when you’re done — you can’t un-finalize without voiding.
Void
Changed your mind or caught an error after finalizing? Click Void. This reverses the finalization, restores your entitlement unit, and unlocks the run so you can make corrections. Once you re-finalize, another unit is consumed.
Reconciliation Status Lifecycle
| Status | What it means |
|---|---|
| Draft | Run created; no extraction yet |
| In Review | Extraction complete; matching in progress |
| Completed | Finalized and locked — entitlement unit consumed |
| Void | Finalization reversed; run is editable again |