Odoo banking and accounting integrations
Banking, in production
Cemseal runs ICICI banking on its Odoo install: token issue, UPI redemption, and reconciliation against bank status.
The first version of any voucher system trusts the callback. That is the assumption that costs money. The ICICI page is the landing for that work: payout, token state, and the scheduled pass that raises the gap rather than a support ticket doing it three days later. Statement-level ICICI reconciliation is the same shape, built to order.
Two-way accounting sync
A Norwegian accounting platform and Odoo, each authoritative on different fields, writing to each other in both directions. Customers, invoices, payments and ledger entries move continuously. There is no monthly export ritual and no spreadsheet holding the difference.
The interesting question is not the API. It is which system owns a field when they disagree, and that a replay is not a second invoice. The PowerOffice page is the landing for that work: two-way masters, AR status back, AP and timesheets out, carried from Odoo 14 through 19.
Where the invoice has to leave the building
Peppol runs in production on the same Norwegian engagement. Invoices leave Odoo in the network format and reach the buyer’s access point without a manual upload step, and a validation failure surfaces against the invoice that caused it rather than in an email from a service provider two days later.
Statutory e-invoicing is the part of this category with a deadline attached, and the regimes do not resemble each other. India files IRNs through a Suvidha Provider. Zambia posts to a virtual sales data controller. Peppol transmits over a four-corner network. Each gets its own page here rather than a shared paragraph, because the useful answer is country-specific.
What holds across all three
Every integration in this category is judged the same way, which is not on whether it connects. It is on whether the number in Odoo and the number at the counterparty still agree at month end, and on whether anyone finds out promptly when they don’t.
So the shape is consistent. Field ownership settled before code. Idempotent writes, because every write is assumed to arrive twice. A reconciliation job on a schedule that raises the delta rather than absorbing it. Failed messages land in a queue you can inspect instead of a log line that scrolled past.
What we don’t do
Resell bank or platform access, hold your credentials, or build against a screen-scrape where the counterparty offers no API and no file interface. We also won’t take on a statutory integration without sandbox access from the authority, because a compliance system that has only ever been exercised with real documents is one nobody has actually tested.
We have delivered 20+ integrations across 12+ active geographies. Banking, accounting and e-invoicing stay bespoke; payments are the part of the category we have published.
Integration engineering · ICICI banking · PowerOffice Go · Payments · Odoo implementation
Which two systems have stopped agreeing?
Bring the counterparty, the field that keeps drifting, and what the mismatch costs when it happens. We can usually tell you in one reply whether that is an integration problem or a process one.