BUSY will reconcile your bank ledger. Your opening balance is a different FAQ page entirely
Bank reconciliation in BUSY is enabled under Administration > Configurations > Feature/Options > Accounts per BUSY's FAQs, or Settings > Features/Options > Accounts per BUSY's own product page, then worked from Display > Bank Reconciliation > Show Uncleared Entries, where pressing F4 on an entry opens the clearing-date window. Opening-balance mismatches are a separate problem with their own FAQ path — a Trial Balance mismatch report, a prior-year fix, and a Change Financial Year carry-forward — and even once both are clean, BUSY's own FIFO bill-reference auto-matching assigns a payment to the oldest open vendor Bill, not necessarily the one it actually paid, which is exactly the match Rule 37's 180-day test needs done correctly.
BUSY's bank reconciliation module is real and documented, built around one key — F4 — to clear an entry, even though BUSY's FAQs and its own product page don't fully agree on the menu path to switch it on. What BUSY's FAQ help centre doesn't have is a single page that walks setup through to a clean statement — "balances don't match" is split across more than a dozen separate answers, by cause, by year, and by account — and BUSY's own FIFO bill-matching still can't guarantee it closed the specific vendor Bill a payment was actually meant for.
Turning it on: Feature/Options, not a setup wizard
BUSY's bank reconciliation module is documented under two different paths, not one. BUSY's FAQs (answerid-48511, answerid-65773, answerid-39008) all point to Administration > Configurations > Feature/Options > Accounts, where ticking the Bank Reconciliation checkbox and saving switches the feature on. BUSY's own product page documents what looks like a newer UI for the same switch — Settings > Features/Options > Accounts > Bank Reconciliation — plus an additional screen the FAQs don't mention, Smart Bank Reconciliation, reached via Payments & Banking > Smart Bank Reconciliation > Bank Reconciliation > Bank Entries. Which one your installation actually shows depends on the release. Neither version adds a bank-linking step or a live feed connection (as of 28 October 2026); every bank account you reconcile is one you've already created as an account master. Whether a bank-statement import precedes the matching is a point where BUSY's own sources disagree. The product page says BUSY supports bank statement import in compatible Excel or CSV formats, can compare the imported transactions against ledger entries to match them, and separately claims an "automatic bank reconciliation" that leaves only unmatched entries for review. BUSY's own FAQ on the subject (answerid-65773) says the opposite for the direct case — "BUSY does not have a default option to directly import bank statement into the software" — and instead documents an indirect route, importing transactions from a prepared Excel sheet via Administration > Data Export Import > Import Vouchers from Excel. Both routes land on the same manual keypress regardless: the product page's own Step 4 of its Smart Bank Reconciliation walkthrough has the user select an entry and press F4 to enter the clearing date, the identical action the FAQ (answerid-65773) then continues to at its own Display > Bank Reconciliation F4 step. What the page's separate "automatic" claim actually skips before reaching that point isn't described anywhere on the page itself. BUSY's release notes confirm statement import and auto-matching are a current, maintained feature without closing that gap — Release 14.1 (22 February 2026) fixed an error generated "while importing Excel for Auto Bank Reconciliation when the number of records exceeded 1000" — so this is a maintained module, not an abandoned one, even where its own marketing and its own steps don't quite line up. The step-by-step FAQs this article otherwise follows for the manual clearing path — answerid-48511 and answerid-65773 — both name F4 specifically; check what your own BUSY release actually shows rather than taking either source as the last word (as of 28 October 2026).
The reconciliation screen and the F4 clearing workflow
Once the feature is on, the working screen is Display > Bank Reconciliation > Show Uncleared Entries. Select the bank account and a date range, and BUSY lists every voucher posted to that ledger that hasn't yet been marked cleared. To clear one, locate it in the list, press F4, and a clearing-date window opens — enter the date the entry actually cleared on your bank statement, confirm, and the entry drops off the uncleared list. That's the entire mechanical loop: it runs per entry, per account, against a statement you're reading line by line.
Why opening balances still won't match — a different FAQ path entirely
An uncleared-entries problem and an opening-balance problem are not the same fault in BUSY, and BUSY's help centre treats them as genuinely separate topics with separate fixes. The general version — this year's opening balance not agreeing with last year's closing balance, for any ledger — is addressed by a dedicated FAQ (answerid-26470): open Display > Trial Balance, select the "Opening Trial - Mismatch from previous year" report, and generate it to list every account where the two figures diverge. To correct a figure, you switch back to the prior year (F11), fix it there, take a full backup, run Update Master Balances from Housekeeping, then go to Administration > Change Financial Year, pick the source year, accept the carry-forward prompt, and choose whether to recompute All masters or only New and changed masters — then re-run the mismatch report to confirm it's clear.
The bank-specific version of the same complaint is a different FAQ again (answerid-39008), whose fix implies a narrower cause: uncleared cheques issued or deposited in the previous year that were never carried into this year's Bank Reconciliation screen. Its fix is to enable the feature (same Feature/Options step as above), then go to Administration > Master > Account > Modify, select the bank account, and when saving, enter the previous year's uncleared entries directly — after which the Bank Reconciliation screen's uncleared list should include them and a cleared statement should match. There's a third variant again for a specifically wrong carried-forward balance (answerid-29912) — check the P&L against the Balance Sheet, run Update Master Balances after a backup, and confirm the carry-forward prompt at year-end — the same pattern as the general Trial Balance fix but filed as its own separate answer. BUSY runs more than a dozen separate pages under its Bank Reconciliation FAQ category alone — by symptom, by cause, by financial year — with no single page walking setup through to a clean statement. That's not a criticism of any one answer; it's a description of what happens when "balances don't match" is one support category instead of one documented workflow, and doing that reconciliation by hand across several BUSY ledgers every month is exactly the work that falls through the gap between those FAQ pages.
What a cleared BUSY ledger still can't tell you
Suppose every one of those steps works: the feature's on, every entry is cleared via F4 against the right statement date, and the Trial Balance mismatch report comes back empty. What you have is more than a bare ledger-to-statement match. BUSY does carry bill references — enabled as "bill-wise details" under Feature/Options, tracked as a New Reference on whichever entry comes first and an Adjustment on the entry that settles it (answerid-65809) — and, per BUSY's release notes (Release 12.2, 11 March 2025), "bill references will now adjust automatically on a FIFO basis during the import of bank statements." BUSY also runs a dedicated Bill wise ITC Reversal report, listed under Display > GST Reports > GST Other Reports.
What that reporting doesn't do, on the sourcing available, is compute Rule 37's 180-day non-payment test automatically. BUSY's own GST-reports FAQs on vouchers showing under "ITC Reversal" name two causes only — a manually entered Journal Voucher with GST Nature set to GST Tax Adjustment and GST Adjustment Type set to ITC Reversal/Ineligible ITC, or a purchase voucher whose ITC eligibility is set to "Ineligible ITC section 17(5) or section 16(4)" — and neither is a payment-ageing check.
FIFO cuts the other way too: an auto-adjusted reference assigns a payment to the oldest open Bill on that ledger, not necessarily the specific Bill a human accountant would match it to — pay a supplier's second invoice out of order while the first sits disputed, and BUSY's FIFO logic still closes the first one.
That gap is exactly what Rule 37 needs closed correctly, not approximately: the second proviso to Section 16(2) of the CGST Act, read with Rule 37, requires reversing input tax credit, with interest, where the supplier hasn't been paid the value of the supply plus tax within 180 days of the invoice date. The reversal is proportionate to whatever remains unpaid, not all-or-nothing, and it's discharged in the GSTR-3B for the tax period immediately following the 180-day period — not on day 180 itself. Reverse-charge supplies are excluded from this test entirely. None of that ages correctly off a FIFO-matched bank line: GSTR-2B carries invoices, not payment status, no GSTN advisory provides any portal-side 180-day ageing, and a payment matched to the wrong Bill ages the wrong invoice. The record Rule 37 needs is a bank line tied to the specific Bill it actually closed — which BUSY's FIFO auto-match, by construction, approximates rather than guarantees.
That gap is the same one found in Tally's older reconciliation screen and, in a different form, in TallyPrime's Auto BRS — a matched or cleared bank line answers "did this amount leave the account," never "which vendor invoice did it close." Zoho Books can match a payment to a bill, as that guide shows, but nothing in the feed itself ages that bill against Rule 37's 180-day clock.
What Recoup does once the bank side is reconciled
Recoup matches each outgoing bank payment to a vendor Bill on references and amounts rather than an oldest-first default, flags payments it can't tie to a single Bill for review, ages every Bill against its Rule 37 180-day clock from the invoice date, stops the clock at the matched payment date, and flags the unpaid proportion for reversal in the next GSTR-3B after day 180. That's independent of whether the ledger underneath it is a live bank feed or a BUSY account reconciled via its F4 clearing workflow and FIFO reference matching. It separately reconciles claimed ITC against GSTR-2B before filing. A clean BUSY reconciliation, with bill references tracked and FIFO-adjusted on import, is still worth having — it's the ground truth Recoup's matching starts from. The gap is narrower than "BUSY can't do this": it's FIFO's oldest-first assumption, and the absence of any documented automatic 180-day check in BUSY's own ITC-reversal reporting, that Recoup is built to close.
Reconciling BUSY by hand and still tracking Rule 37 on a spreadsheet?
Recoup matches bank payments to vendor Bills on references and amounts — not just the oldest open reference — flags the ones it can't tie down, ages the Rule 37 180-day clock per invoice, and reconciles your ITC against GSTR-2B before you file — whatever accounting software sits underneath.
Book a demo →Related guides
Rule 37 — ITC reversal on non-payment
Why a cleared bank entry, matched to the right vendor Bill, is the only record that can answer "was this paid within 180 days."
Bank reconciliation across multiple accounts in Tally
The same single-ledger-at-a-time limit, worked through for Tally's older reconciliation screen.
Connected banking in TallyPrime
What Auto BRS confirms about statement import and match buckets, for contrast with BUSY's own F4 clearing step and FIFO bill-reference matching.
Connecting Zoho Books to your Indian bank feed
A live bank-feed connector with named banks, for comparison with BUSY's statement-import-plus-F4 clearing workflow.