What a connector actually has to do

Beyond sending the document, a working connector has to:

  • Map your Zoho Books invoice to the ETA document structure, including the fields Zoho does not require but the ETA does.
  • Handle signing and submission, with an audit trail.
  • Show status per document — accepted, rejected, pending — so nobody has to check the portal.
  • Let you correct and resubmit a rejected invoice without leaving the tool.
  • Cover credit notes and e-receipts, not only sales invoices, if you issue them.

Want to know how this works out for your company? Send us the question as you would ask it.

The questions worth asking before you pick one

Several connectors exist, including our own TaxBridge. Ask these about any of them, ours included.

  • Who maintains it when the ETA specification changes, and is that written into what you pay?
  • What happens to invoices sent while the connector is down — queued and retried, or silently lost?
  • Does it handle several companies or branches, or one tax registration only?
  • Is the pricing per invoice, per company, or flat — and what does that come to at your real volume?

Where TaxBridge fits

TaxBridge is the connector we built after implementing the same bridge for clients on different accounting systems. It connects Zoho Books — and ERPNext, or any system with an API — to the ETA, submits invoices, and tracks status per document from one dashboard.

If you already have a working, maintained connector, there is no reason to change. Look at TaxBridge if your answer to "who maintains this when the ETA changes" is nobody in particular.

What to do first

Still choosing an accounting system? Evaluate the ETA connector at the same time. The connector can change which accounting system is the right one.

Already on Zoho Books? Confirm what you submit with today, who maintains it, and whether it covers every document type you issue.

Either way, test it on your real invoices before you rely on it.