Reconciliation for Busy Accounting in India — Bank, TDS, GST, Settlement
Busy is the multi-branch accounting standard for Indian retail, distribution, and trading businesses across north and west India. Strong on regional accounting practices, GST registers, TDS deduction, and multi-branch consolidation. What Busy does not do at scale is parse Indian bank statement narration across HDFC, ICICI, SBI, Axis, and Kotak; reconcile vendor bills against GSTR-2B at line level; or map TDS deductions to the new payment-code regime against Form 26AS. TransactIG reads Busy via its documented DBF/CSV exports or read-only SQL connection and runs the matching layer alongside.
What Busy Handles Natively, and Where the India Gap Appears
What Busy does well
Busy is built for Indian regional accounting practice. Voucher-level entry, multi-branch synchronisation, GST registers, TDS deduction at voucher level, e-invoice/e-way bill, and consolidation across branches under one GSTIN or across GSTINs all run natively. Trading businesses with high voucher volumes operate Busy on the DBF backend for performance; multi-branch operations with shared masters use the SQL Server backend.
Documented export utilities and a SQL backend option give clean read access without modifying Busy's voucher workflow.
Where the India gap appears
Busy's bank reconciliation view is a comparison tool, not a matching engine. CIB Excel, YONO Business, MT940, and PDF formats are not natively parsed. UPI VPA, NEFT fragment, and cheque clearing narration extraction is not configurable. Multi-bank consolidation across 3 to 5 accounts requires bank-by-bank reconciliation.
TDS section-to-payment-code mapping under Sections 393, 394, 413 of the Income Tax Act 2025 lives outside Busy's master. GSTR-2B reconciliation against thousands of purchase vouchers at line level is a manual export-and-VLOOKUP.
TransactIG Plug Points on Busy
Six matching surfaces sitting alongside Busy — no code customisation, no voucher workflow change.
Data ingestion
Scheduled DBF/CSV exports to shared folder or SFTP, or read-only SQL connection to the Busy database. No Busy code customisation, no schema changes.
Section 393 TDS handling
Busy TDS deduction vouchers mapped to new payment codes 1001-1092 under Sections 393, 394, 413 of the Income Tax Act 2025. Reconciled to Form 26AS at code level.
GSTR-2B and IMS
Busy purchase vouchers matched to GSTR-2B and IMS at GSTIN + invoice + tax-amount level. ITC eligibility and Rule 36(4) provisional credit per voucher.
NACH batch matching
Outbound NACH batches reconciled against bank response files; bounce codes mapped to ageing and re-presentation at voucher level.
Platform settlements
Razorpay, PayU, Cashfree, Amazon, Flipkart, Meesho settlements disaggregated and matched to Busy sales vouchers and bank receipts.
Bank statement ingestion
MT940, CAMT.053, CIB Excel, YONO Business, and PDF parsed natively; matched to Busy bank ledger vouchers with narration-pattern extraction.
Busy Integration Architecture
Each row is a discrete data feed configured during implementation against Busy's documented export interfaces. The customer's IT or Busy partner team owns the export configuration.
| Busy source | Read method | Sync cadence | Field mapping | Variance codes |
|---|---|---|---|---|
| Master ledger and groups | DBF/CSV export, or read-only SQL on master tables | On configuration change | Busy ledger → TransactIG counterparty class | MASTER_DRIFT |
| Purchase vouchers | DBF/CSV export filtered on purchase voucher type, or SQL view | Daily | Vendor ledger → counterparty GSTIN | BILL_OPEN, 2B_MISSING, ITC_BLOCKED |
| Sales vouchers | DBF/CSV export, or SQL view on sales tables | Daily | Customer ledger → counterparty | INVOICE_OPEN, ADVANCE_UNAPPLIED, CREDIT_NOTE_PENDING |
| Bank ledger vouchers | DBF/CSV export, or SQL view filtered on bank ledger | Daily | Bank ledger → Indian bank narration profile | VOUCHER_UNMATCHED, NARRATION_ONLY, CHARGE_UNCLASSIFIED |
| TDS deduction vouchers | DBF/CSV export on TDS-related voucher types | Per deduction cycle | Busy section → new payment code (1001-1092) | TDS_NOT_IN_26AS, RATE_MISMATCH, SECTION_RECLASSIFIED |
| GST registers | GSTR-1/3B export from Busy | Per GST cycle | Purchase voucher → GSTR-2B row | ITC_INELIGIBLE_2B, INVOICE_MISSING_IN_2B |
Common Reconciliation Gaps in Busy Deployments
BRS scope
Busy BRS compares ledger and statement lines but cannot extract UTR or VPA from narration text; manual matching the default.
TDS section vs payment code
Busy TDS configuration retains legacy section labels; Form 26AS shows new payment codes (1001-1092); external mapping required.
Purchase voucher vs 2B
Vendor voucher booked; supplier has not filed GSTR-1; ITC provisional under Rule 36(4) until 2B catches up; not surfaced natively.
Branch consolidation drift
Multi-branch Busy installations synchronise to head office; branch-to-branch and branch-to-HO entries drift on timing.
Settlement net vs gross
Payment gateway settles net of fees; Busy sales voucher raised gross; manual breakup needed without disaggregation.
DBF data volume
High-volume trading customers on DBF backend find Busy's reporting slow on multi-year data; external matching offloads the heavy reads.
How TransactIG Works with Busy
Ingest
Scheduled DBF/CSV exports or SQL reads feed bank, purchase, sales, TDS, and GST data per branch and company. External feeds (bank statements, GSTR-2B, 26AS, NACH responses, settlement reports) land alongside.
Match
Busy vouchers matched to external sources. Narration parsing handles Indian bank narration; payment-code mapping aligns TDS to 1001-1092 codes; GSTR-2B match runs per GSTIN; multi-branch consolidation runs in parallel.
Exception queue
Unmatched items route to a structured queue with variance codes, ageing, suggested resolution, and maker-checker workflow. The Busy accounts team continues working in Busy unchanged.
Frequently Asked Questions
How does TransactIG read data from Busy?+
Busy supports two backend modes — the classic DBF (Visual FoxPro) backend for SMB installations and the SQL Server backend for multi-branch and larger deployments. TransactIG reads from both. For DBF installations, the integration uses Busy's documented export utilities (Excel/CSV/XML exports per voucher type) delivered to a shared folder or SFTP. For SQL installations, TransactIG uses a read-only SQL connection to the Busy database. No Busy code customisation is required; the customer's IT team or Busy partner owns the export configuration.
Does TransactIG handle Busy multi-branch and multi-company setups?+
Yes. Busy is widely used in multi-branch retail, distribution, and trading businesses across India. Each branch typically runs its own Busy installation with synchronisation to a head office. TransactIG ingests per-branch and per-company data, runs reconciliation per entity, and rolls up to a consolidated group view. Branch-to-branch inter-company transactions auto-match on amount-and-date pair; consolidation drift is surfaced for the corporate accounts team.
How does Busy's TDS module reconcile to Form 26AS?+
Busy captures TDS deduction at voucher level with section, deductee, and rate. The new payment-code regime (1001-1092) under Sections 393, 394, 413 of the Income Tax Act 2025 introduces codes that Busy's master configuration captures against legacy section labels. TransactIG reads Busy's TDS deduction lines via the DBF or SQL export, applies the section-to-payment-code mapping configured during implementation, and reconciles against Form 26AS at payment-code level for both deductor and deductee perspectives.
Can TransactIG reconcile Busy vendor bills against GSTR-2B?+
Yes. Busy captures purchase vouchers with GSTIN, invoice number, taxable value, and tax break-up. TransactIG reads the purchase voucher register and matches line-by-line against the GSTR-2B and IMS feed from the GSTN portal. ITC eligibility, blocked-credit handling, supplier-not-filed flags, and Rule 36(4) provisional credit are all surfaced. The reconciliation status is exportable per GSTIN for the AP and audit teams.
How does TransactIG handle Busy bank reconciliation in India?+
Busy's bank reconciliation view compares bank ledger entries to statement lines for the simple case. The challenge is that Indian bank statements arrive in CIB Excel, YONO Business Excel, MT940 from private bank corporate accounts, and PDF from co-op banks — formats Busy's BRS was not built for. TransactIG parses every major Indian bank statement format natively, extracts narration match keys, and matches against Busy's bank ledger or directly against purchase and sales vouchers. The accounts team continues working in Busy unchanged.
How long does Busy integration take?+
2 to 4 weeks for most Busy customers. Week one configures the export interface — DBF/CSV exports or read-only SQL access — and establishes the scheduled data flow. Week two maps the chart of accounts, branch and company hierarchy, tax codes, and TDS configuration to TransactIG's matching schema. Weeks three and four configure narration patterns, TDS payment-code mapping, GSTR-2B alignment, and the maker-checker workflow. The customer's accounts team continues working in Busy unchanged throughout.
Reconciliation that fits the Busy installation your branches already run
No Busy code customisation. Read-only export or SQL. 2 to 4 weeks to first reconciled close, ISO 27001:2022 certified, running from AWS Mumbai.