ERP connectors

Pull data from your ERP, push journals back. OAuth handled, refresh transparent.

Supported systems

Add a connection from Connections in the side rail (Settings → Connections in some builds). The type picker lists every adapter HISAB ships:

ConnectorHow it connectsReadWrite
XeroOAuth 2.0 (your own developer app: client_id + client_secret)
QuickBooks OnlineOAuth 2.0 (Intuit developer app: client_id + client_secret)
Zoho BooksOAuth 2.0 (Zoho API console app: client_id + client_secret)
OdooXML-RPC — URL + database + username + password
Generic OData (v2/v4)For Dynamics 365 or any OData endpoint
CSV folderA local folder of .csv exports from any system

Reads work on every connection and every plan — and so do writes: ERP write-back is included in every plan. Xero, QuickBooks Online, Zoho Books, Odoo and Generic OData support write-back, while CSV folders are read-only by design.

Setting up a connection

Click + Add connection, pick the type, and fill in the details for that adapter (a folder path, or an ERP URL + credentials). For the OAuth connectors (Xero, QuickBooks, Zoho), you connect through your own developer app:

Connections are encrypted at rest with Windows DPAPI (per-user, per-machine) and stored at %APPDATA%\HISAB\connections.json. Secrets like client secrets, passwords and tokens are never returned to the AI — only non-secret metadata (name, kind, public params) is.

Pulling data

Just ask in the chat:

Pull the May trial balance from Zoho Books into a new sheet.

The AI inspects the connection's schema, fetches rows (paged automatically for large pulls), and lands them in your workbook. Every read is restricted at the connection layer to read-only: HTTP requests are limited to GET/HEAD/OPTIONS, SQL is SELECT-only, and the read adapter exposes no methods that can write, post or delete anything in the source system. Every read is logged to %APPDATA%\HISAB\Telemetry\.

Save it as an automation. Once a pull-and-report flow works, you can save it as an automation that re-runs offline against fresh data later — no need to re-prompt the AI each month.

Writing back to your ERP (every plan)

Writing to an ERP is opt-in per connection, never on by default. When you add or edit a write-capable connection (Xero, QuickBooks, Zoho, Odoo, or a Generic OData endpoint), pick the capability mode:

Writes do not go through a simple “push” call. They use a staged-sheet workflow so you can review the exact rows before anything leaves Excel:

  1. Stage — HISAB builds a staging sheet with the required columns (and reference sheets with valid ids to pick from).
  2. Validate — it checks each filled row against the ERP's rules and flags problems before submission.
  3. Submit — validated rows are posted as drafts or final entries.

Before each batch posts, a confirmation card shows the entity counts and a data preview; approving it mints a short-lived token bound to that batch. There are no silent writes.

Writes need the right scopes and approval. Write-back is included in every plan, so if a submit is blocked, check two things: the connection is set to Read + Write with the write OAuth scopes granted (re-authorise if you only granted read scopes), and you approved the batch confirmation card.