Reconciliation for Zoho Books in India — Bank, TDS, GST, Settlement
Zoho Books is the leading cloud accounting product for the Indian SMB and mid-market segments. It carries native GST features, TDS deduction, multi-organisation support for multi-GSTIN, and a documented REST API with OAuth 2.0 authentication. What Zoho Books does not do at scale is reconcile against external Indian banking realities — narration-driven bank statements, GSTR-2B mismatches across thousands of vendors, settlement net-of-fees from payment gateways, and TDS deductions aligned to the new payment-code regime against Form 26AS. TransactIG reads Zoho through its standard API and runs the matching layer alongside.
What Zoho Books Handles Natively, and Where the India Gap Appears
What Zoho does well
Zoho Books is built for cloud-first Indian accounting. Native GST features, e-invoice and e-way bill generation, TDS deduction with section configuration, multi-organisation for multi-GSTIN, and a clean OAuth-authenticated REST API. Bank auto-feeds for select Indian banks pull statements directly into the bank ledger.
For single-organisation SMB customers with one or two bank accounts and clean vendor flows, Zoho's built-in reconciliation handles the simple cases without external tooling.
Where the India gap appears
Bank auto-feed coverage is partial; PSU banks, co-operative banks, and many corporate accounts still require manual statement upload. Narration parsing for UPI VPAs, NEFT fragments, and cheque clearing is not configurable. Multi-bank consolidation across 3 to 5 accounts requires bank-by-bank handling.
GSTR-2B reconciliation against vendor bills at line level is not native — exports and manual checking are common. TDS section-to-payment-code mapping under Sections 393, 394, 413 of the Income Tax Act 2025 sits outside Zoho's master configuration during transition.
TransactIG Plug Points on Zoho Books
Six matching surfaces that sit alongside Zoho without modifying the bookkeeping workflow.
Data ingestion
OAuth 2.0 read-only API pulls per organisation. Token rotation managed by the customer's Zoho admin. No code deployed inside Zoho.
Section 393 TDS handling
Zoho TDS lines mapped to the new payment codes 1001-1092 under Sections 393, 394, 413 of the Income Tax Act 2025. Reconciled against Form 26AS and AIS at code level.
GSTR-2B and IMS
Zoho vendor bills matched to GSTR-2B and IMS at GSTIN + invoice + tax-amount level. ITC eligibility and Rule 36(4) provisional credit visible per bill.
NACH batch matching
Outbound NACH batches reconciled against bank response files; bounce codes mapped to ageing and re-presentation at vendor or customer level.
Platform settlements
Razorpay, PayU, Cashfree, Amazon, Flipkart, Meesho settlements disaggregated and matched to Zoho invoices and payments received.
Bank statement ingestion
MT940, CAMT.053, CIB Excel, YONO Business, and PDF parsed natively. Matched to Zoho bank transactions where auto-feed is active, or directly to the bank ledger where it is not.
Zoho Books Integration Architecture
Each row is a discrete API feed configured during implementation, reading from Zoho's documented REST endpoints under OAuth 2.0.
| Zoho source | Read method | Sync cadence | Field mapping | Variance codes |
|---|---|---|---|---|
| Bank transactions | GET /banktransactions (per account, paginated) | Daily | Zoho bank account → Indian bank narration profile | TXN_UNMATCHED, NARRATION_ONLY, CHARGE_UNCLASSIFIED |
| Vendor bills | GET /bills (filtered by date and status) | Daily | Vendor → counterparty GSTIN | BILL_OPEN, 2B_MISSING, ITC_BLOCKED |
| Customer invoices | GET /invoices | Daily | Customer → counterparty | INVOICE_OPEN, ADVANCE_UNAPPLIED, CREDIT_NOTE_PENDING |
| TDS deduction lines | Bill-level TDS detail, plus dedicated TDS report extracts | Per deduction cycle | Zoho section → new payment code (1001-1092) | TDS_NOT_IN_26AS, RATE_MISMATCH, SECTION_RECLASSIFIED |
| Payments received and made | GET /customerpayments, GET /vendorpayments | Daily | Payment → bank transaction match key | PAYMENT_UNAPPLIED, REVERSAL_PENDING |
| GST returns data | GST register endpoints (per organisation) | Per GST cycle | Bill → GSTR-2B row | ITC_INELIGIBLE_2B, INVOICE_MISSING_IN_2B |
Common Reconciliation Gaps in Zoho Books Deployments
Partial bank feed coverage
Auto-feed works for select private banks; PSU and co-op bank accounts require manual statement upload. Mixed-feed environments need a unified parser.
2B at scale
Reconciling thousands of bills against GSTR-2B for a multi-GSTIN setup is a manual export-VLOOKUP exercise without an integrated matching engine.
TDS section vs payment code
Zoho's TDS master may still label deductions by legacy section; Form 26AS shows new payment codes. External mapping required.
Multi-org intercompany
Transactions between Zoho organisations must net at group level; one-sided or timing-mismatched postings drift.
Settlement net vs gross
Payment gateway settles net of fees; invoices were raised gross. Disaggregation needed before bank credit can be applied at invoice level.
Statutory audit evidence
CARO 2020 and tax-audit 3CD evidence files require ageing reports, variance taxonomy, and maker-checker timestamps that Zoho does not surface natively.
How TransactIG Works with Zoho Books
Ingest
OAuth-authenticated read pulls fetch bank transactions, vendor bills, customer invoices, payments, and TDS lines per Zoho organisation. External feeds (bank statements, GSTR-2B, 26AS, NACH responses, settlement reports) land alongside.
Match
Zoho records matched to external sources. Narration-pattern parsing handles Indian bank narration; TDS payment-code mapping aligns Zoho deductions to Form 26AS; GSTR-2B match runs per-organisation.
Exception queue
Unmatched items route to a structured queue with variance codes, ageing, suggested resolution, and maker-checker workflow. Reconciliation artefacts exported per GSTIN for the audit team.
Frequently Asked Questions
How does TransactIG read data from Zoho Books?+
Zoho Books exposes a documented REST API with OAuth 2.0 authentication. TransactIG authenticates against the customer's Zoho Books organisation, requests scoped read-only access, and uses the published endpoints for bank transactions, vendor bills, customer invoices, payments received, payments made, and TDS deductions. The customer's Zoho admin owns the OAuth client; the access token is rotated on Zoho's standard schedule. No code is deployed inside Zoho.
Does TransactIG handle multi-organisation and multi-GSTIN setups?+
Yes. A Zoho Books customer with multiple GSTINs typically operates one organisation per GSTIN, sometimes with branch sub-orgs. TransactIG configures one read connection per organisation, runs reconciliation per organisation (matching that organisation's bank, TDS, and GST data), and rolls up to a consolidated group view. The reconciliation register, exception queue, and audit artefacts are per-GSTIN, which mirrors how the GST return filing and statutory audit teams operate.
How does Zoho's TDS module reconcile to Form 26AS?+
Zoho Books captures TDS deduction at bill level with section, deductee PAN, and rate. The new payment-code regime (1001-1092) under Sections 393, 394, 413 of the Income Tax Act 2025 introduces codes that Zoho's master configuration may still capture against the legacy section labels. TransactIG reads the TDS deduction lines via the API, applies the section-to-payment-code mapping configured during implementation, and reconciles against Form 26AS and AIS at payment-code level. The customer-facing TDS entry in Zoho is unchanged.
Does TransactIG reconcile vendor bills in Zoho against GSTR-2B?+
Yes. Zoho Books captures vendor bills with GSTIN, invoice number, taxable value, and tax amounts. TransactIG ingests bills via the bills endpoint and matches them line-by-line against the GSTR-2B and IMS feed downloaded from the GSTN portal. ITC eligibility, blocked-credit handling, supplier-not-filed flags, and Rule 36(4) provisional credit are surfaced. The reconciliation status is visible per bill, exportable to the AP team.
How does TransactIG handle Zoho Banking auto-fetch?+
Zoho Books supports auto bank feeds from select Indian banks. Where auto-feed is active, TransactIG reads the bank transaction list from Zoho via the API — the same data the auto-feed populates. Where auto-feed is not available (most PSU and co-operative banks, and many private bank corporate accounts), TransactIG ingests the bank statement directly in its native format (MT940, CAMT.053, CIB Excel, PDF), parses narration patterns, and matches against the Zoho bank transaction list. The match approach is the same; the source path differs.
How long does Zoho Books integration take?+
2 to 4 weeks for most Zoho Books customers. Week one establishes OAuth credentials and tests the API read flow. Week two maps the chart of accounts, GSTIN list, TDS section configuration, and tax codes to TransactIG's matching schema. Weeks three and four configure bank narration patterns for the banks involved, TDS payment-code mapping, GSTR-2B alignment, settlement disaggregation for active payment gateways, and the maker-checker workflow. The customer continues working in Zoho Books unchanged.
Reconciliation that fits the Zoho Books workflow your team already runs
OAuth read-only. No Zoho deployable code. 2 to 4 weeks to first reconciled close, ISO 27001:2022 certified, running from AWS Mumbai.