Read and write your Odoo ERP from inside Excel — approval-gated and logged
Prefer YouTube? Watch this walkthrough on YouTube →
This demo shows how to work with your Odoo data without leaving Excel. The HISAB 360 chat agent pulls live records — invoices, bills, journals, partners — straight into a worksheet, and when you need to push changes the other way, it builds a staging sheet you can review row by row before anything reaches your live database.
Crucially, no change is posted silently. Every write-back is staged in Excel, validated, held at an approval card you click, and journalled to an audit log. The same read-and-write pattern shown here for Odoo also drives Xero, QuickBooks Online and Zoho Books.
Connect Odoo (read-only by default)
From Settings, add an Odoo connection with your instance URL, database, username and password. New connections are read-only — the adapter only allows read-shaped Odoo calls (search, read, fields_get), so you can explore safely. Write-back is enabled separately and requires re-authorising the connection with write access.
Pull live data into a worksheet
Ask the agent in plain English — for example, "pull this month's posted customer invoices from Odoo into a new sheet". It queries the live instance and lays the records out in Excel with headers and real values, so you can sort, filter, reconcile or build formulas against current ERP data rather than a stale export.
Stage a write-back sheet
When you want to post data back — new bills, a journal, partner records — the agent never writes directly. It generates a staging sheet that mirrors the target Odoo entity, with the correct columns plus reserved engine columns (_status, _erp_id, _message). You fill or paste rows below the header, using the built-in reference sheets to look up valid partner and account IDs.
Validate before anything leaves Excel
Run validation and the engine checks every row in the sheet first: required fields, date and number types, and — for journals — a double-entry balance check per group, so debits must equal credits before a post is attempted. Failures are written back into _status and _message on the row, so you fix problems in Excel instead of chasing a cryptic ERP error.
Approve, then post — the gate you click
Submission is a separate, deliberate step. The agent presents an approval card in the chat panel and stops — nothing is posted until you click Approve. The approval is bound to that exact batch, sheet and entity and expires after a few minutes, so you are authorising the specific write in front of you, not a blanket permission.
Confirm results and the audit trail
After you approve, HISAB posts each record through its safety stack and writes the result back to the sheet: the Odoo record ID lands in _erp_id and the status flips to Posted (or Draft on partial success). Every write is recorded in the audit log, and already-posted rows are skipped on any retry so you never double-post.
Why this matters for finance teams
For a finance team, the risk in connecting Excel to a live ERP is an accidental bad write. HISAB 360 is built so that Excel is the review surface: data is staged, validated and balance-checked before submission, every post pauses at an approval card you click, and the engine's idempotency handling stops duplicate entries on retry. That turns an ad-hoc paste-back into a controlled, reviewable process.
It also keeps you in control of your data and your tooling. Your workbook stays local — only sheet names, ranges, headers and sample rows are sent to the AI — and every change is captured in an audit log. You bring your own Anthropic or OpenAI key with no markup, and ERP write-back is available on the Professional plan ($30/month) and Team plans, with a 14-day free trial and no card required.
Frequently asked questions
Can I edit my Odoo data directly from Excel?
Yes, but not blindly. HISAB 360 stages your changes on an Excel sheet that mirrors the Odoo entity, validates each row, and holds the post behind an approval card you click before anything reaches your live instance. The connection also has to be re-authorised with write access first — read-only is the default.
Is the connection to Odoo safe and read-only by default?
Yes. New Odoo connections only allow read-shaped calls (search, read, fields_get), enforced by a method whitelist in the adapter, so you can pull and explore data without any risk of mutation. Write-back is a separate, opt-in capability that requires explicitly enabling write access on the connection.
Does this also work for Xero, QuickBooks Online and Zoho Books?
Yes. The same stage-validate-approve-post flow shown here for Odoo drives Xero, QuickBooks Online and Zoho Books. You stage the relevant entity (for example a Xero ManualJournal or a QBO Invoice), validate it in Excel, then approve the write — the safety gates are identical across ERPs.
How do I avoid double-posting if a write fails partway?
The engine mints an idempotency key per row during validation and writes the ERP record ID back into the sheet once a row posts. On any retry, rows that already have an ID are skipped, and a record created-but-not-posted is marked Draft and resumed rather than duplicated, so you don't post the same entry twice.
Try it on your own workbook
The 14-day trial is the full product — no card, no feature gates. The fastest way to evaluate HISAB 360 is on a real file from your own month-end.