Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Busy Accounting Software (dominant among Indian trading, wholesale, and CA-firm segments) runs on DBF tables or proprietary indexed binary (Busy 21+) with no sanctioned real-time API — so CA firms managing 20+ client companies on Busy cannot reconcile bank, TDS, and GSTR-2B across entities without an overnight ASCII/XML batch job.
Run scheduled ASCII or XML exports from each Busy company directory at end of day, drop files over SFTP to a central location, ingest into an external reconciliation layer that handles multi-company bank, TDS, and GSTR-2B matching, resolve exceptions outside Busy, and post cleared status back via ASCII import. GSTR-2B JSON from the GST portal is consumed externally and matched against the Busy purchase voucher extract.
Busy company directory registry, ASCII and XML export templates aligned to Busy schemas (MASTERS.DBF, VOUCHERS.DBF, GSTINFO.DBF), SFTP job scheduler at EOD, CA-firm client mapping for multi-company consolidation, and ASCII import writeback for cleared voucher status.
A CA-firm or multi-branch trading house running 20+ Busy companies reconciled overnight across bank, TDS, and GSTR-2B streams — GSTIN typo and timing-mismatch exceptions handled externally, cleared status pushed back to each Busy company, and consolidated audit trail available at partner review.
Busy Accounting Software is the second most common ERP among Indian SMEs after Tally, particularly strong in the trading, wholesale, and CA-firm segments. Its GST module is one of the most comprehensive in the price band, and its multi-company support makes it a fit for CA firms managing multiple client entities. Reconciliation on top of Busy, particularly at CA-firm scale or multi-branch scale, requires working within the constraints of its DBF data layer and its ASCII/XML export paths.
What Busy Handles Natively
For the single-company SME use case, Busy delivers:
- GSTR-2A and GSTR-2B reconciliation (Busy Professional / Enterprise, from Busy 18 onwards)
- TDS deduction with section-wise tracking, challan entry, and Form 26Q generation
- Bank reconciliation screen with Excel/ASCII import
- Multi-company support with per-company data directories
- Audit trail features compliant with CARO 2020 from April 2023
For the CA firm managing 10–30 client books, Busy’s multi-company handling is one of its differentiators.
The DBF Data Layer and What It Means for Integration
Busy’s data layer was originally DBF — the same dBASE-derived format used by a generation of Indian accounting software. From Busy 21, the data format moved to a proprietary indexed binary. Either way, direct third-party reads are not supported by Busy Infotech. The sanctioned integration path is the ASCII/XML import-export interface built into the Busy UI.
This has practical implications:
- Real-time sync is not a standard option. Integration runs on scheduled extracts.
- Every export is a file drop; ingestion happens from a file, not a message queue.
- Data contracts between Busy and the external layer are the ASCII format definitions published in the Busy Help.
Import/Export Reference
| Format | Use case | Direction | Volume comfort |
|---|---|---|---|
| ASCII (delimited) | Voucher, ledger bulk | Both | Up to 50,000 rows |
| ASCII (fixed-width) | Master data | Both | Up to 10,000 rows |
| XML | GST return data | Both | As per return size |
| Excel | Small master creation | Import only | Under 500 rows |
| PDF/print | Report distribution | Export only | Unlimited |
Multi-Company Reconciliation Pattern
For a CA firm running Busy across 25 client companies, the typical reconciliation flow is:
- End-of-day ASCII/XML export from each client’s Busy data directory, scheduled via Windows Task Scheduler.
- SFTP or shared-drive drop to a central location.
- External layer reads all client extracts, applies bank + GSTR-2B + TDS matching.
- Exceptions routed to the CA firm’s review queue, classified by variance type.
- Cleared status returned to each client’s Busy instance via ASCII import at start of next day.
The alternative — doing reconciliation within each Busy instance separately — works for one or two companies but does not scale to 20+.
For Indian CA firms and mid-market businesses on Busy, a reconciliation software India layer that consumes the ASCII/XML exports and handles cross-client reconciliation is the standard architecture. GSTR-2B handling at portfolio scale is covered by dedicated GST reconciliation software that reads the Busy purchase export and GSTR-2B JSON together.
India-Specific Considerations
Busy’s GST module enforces GSTIN validation at voucher entry but does not validate challan-level TDS acknowledgement against TRACES — a pattern shared with Tally and the other SME ERPs covered in reconciliation in SAP, Oracle and Tally India. The GSTR-2B reconciliation guide details the matching logic that sits on top of any Indian ERP export. Busy’s full ASCII format documentation and DBF schema are published via the Busy Infotech Support Portal.
The FAQ below covers the most common Busy automation questions from Indian users.