4.6 Accounting software (Tally, Zoho Books, Busy, Marg, Vyapar, QuickBooks)
Why accounting data matters for SME WC
Section titled “Why accounting data matters for SME WC”For the SME segment this spec targets, accounting software data is the strongest qualitative cash-flow and operational signal — better than bank-statement alone, because:
- It includes the business’s view of receivables, payables, inventory — bank doesn’t show this.
- It includes cost-of-goods-sold — bank only sees cash movements.
- It includes debtor / creditor concentration at line-item granularity.
- It is what the CA sees — and CAs are a primary acquisition channel.
The big constraint: SME accounting data is locked inside on-premise software (Tally) or proprietary cloud (Zoho, Busy, Marg) with no clean cross-vendor API.
The software landscape
Section titled “The software landscape”| Software | Estimated India SME share (orientation) | Access mechanism |
|---|---|---|
| Tally Prime | Largest by far — millions of installations | Tally Connector API (limited), file export, partner ecosystem |
| Zoho Books | Mid-tier; cloud-native | Official REST API |
| Busy | Mid-tier; on-prem | File export |
| Marg | Tier 2/3 SMEs, especially pharma/distribution | File export |
| Vyapar | Smallest businesses, mobile-first | API for partners |
| QuickBooks (Online India) | Small share; cloud | API |
| GeniusOffice / Profitbooks / others | Niche | Vendor-specific |
How to access data
Section titled “How to access data”- Tally backup file (.tcp / .tally) — borrower (or CA) exports and uploads.
- Tally Connector / Tally Definition Language (TDL) — custom Tally module installed on borrower’s machine that exposes APIs; requires CA / IT involvement.
- Tally Edge / Tally on Cloud — if borrower uses, can integrate via API.
- Vendor extractors — Karza, Perfios, specialised players parse Tally backups.
Zoho Books
Section titled “Zoho Books”- Official REST API — OAuth-based; borrower authorises access.
- Smooth, modern integration.
Busy / Marg / Vyapar
Section titled “Busy / Marg / Vyapar”- File export — borrower exports common-format file (Excel / XML / proprietary); platform parses.
- Partner programmes — vendor-specific; harder to standardise.
Manual / fallback
Section titled “Manual / fallback”- P&L + balance sheet PDF / Excel — borrower / CA uploads; OCR / parse; lowest-quality fallback.
Data extracted
Section titled “Data extracted”- P&L — revenue, COGS, operating expenses, EBITDA, net profit, period.
- Balance sheet — assets, liabilities, equity.
- Receivable ageing — by buyer, by bucket (
0-30, 31-60, 61-90, 90+, 180+). - Payable ageing — by supplier, by bucket.
- Inventory — value, days.
- Bank ledgers — useful for reconciliation with BSA.
- Sales / purchase ledgers — for reconciliation with GST.
- Top debtors / creditors — concentration.
Derived signals (underwriting)
Section titled “Derived signals (underwriting)”- Revenue trend + margin trend.
- Receivable concentration —
top-3 buyers > X%. - Payable strain —
payables > X days. - Inventory turn.
- Reconciliation health — accounting sales vs GST sales vs bank credit.
- ROCE estimate.
- Cash conversion cycle.
Pricing proxy
Section titled “Pricing proxy”- Tally parsing via vendor:
₹50 – ₹250per backup file (12-month). - Zoho Books API: usually free for borrower-authorised access; integration cost is engineering.
- Custom build for any single software:
4 – 12weeks of engineering.
Implementation complexity
Section titled “Implementation complexity”- Zoho Books OAuth + REST:
~2 – 4weeks. - Tally backup parsing:
~4 – 8weeks if building in-house; or buy via vendor. - Busy / Marg / Vyapar: each is its own integration; outsource via vendor or accept lower coverage.
Failure cases
Section titled “Failure cases”- Borrower / CA can’t / won’t share Tally backup — common at first; CA-channel education helps.
- Backup encrypted with password.
- Multi-company Tally backup; need to select the right entity.
- Old Tally version → format quirks.
Fallback
Section titled “Fallback”- Bank + GST + bureau still allows underwriting; accounting data is value-add, not strictly mandatory.
- For higher-ticket loans, accounting data should be required.
CA channel implication
Section titled “CA channel implication”The CA acquires the borrower with their accounting data already in hand. A CA portal that lets the CA push the SME’s Tally backup + GST snapshot + bureau consent in one motion is a massive distribution lever. This is the single biggest product moat the platform can build for the SME WC wedge.
Compliance implications
Section titled “Compliance implications”- DPDP — accounting data is personal / business sensitive; consent + purpose.
- Outsourcing MD — accounting-data vendors governed.
Build vs buy
Section titled “Build vs buy”- Tally extractor: Buy initially (vendor parsing); revisit at scale.
- Zoho Books integration: Build (simple REST API).
- Busy / Marg / Vyapar: Buy where vendor coverage exists; otherwise accept manual upload.
- Derived features: Build (your underwriting IP).
- CA portal UX: Build (highly product-specific).