Printing
Odoo & SQL Accounting Integration
A Windows bridge service and a custom Odoo module that keep customers, suppliers, invoices and payments in step between Odoo and SQL Accounting.
The problem
Operations ran in Odoo while the books stayed in SQL Accounting, a Windows desktop package that can only be driven through its COM SDK. Master data and documents had to move between the two reliably, with a record of every call.
What I built
- A FastAPI bridge on the accounting PC that drives SQL Accounting through its COM SDK and exposes signed REST endpoints for customers, suppliers, sales invoices, credit notes, purchase orders, payments with knock-offs, deposits and units of measure.
- e-Invoice fields (tax ID, classification, submission type) carried through on sales invoices.
- A custom Odoo 18 module for the business: paper master data, company tax fields, customer and vendor tagging, outstanding-credit detail and calls to the bridge from Odoo.
- A scheduler that pushes customers from SQL Accounting into Odoo, matching on code first and then on name.
- Operator pages for the dashboard, schedules, settings and audit logs, plus a tray app on the accounting PC.
Technical highlights
- The API uses readable field names, so Odoo never has to deal with SQL Accounting's internal import headers.
- The accounting session is kept warm between calls instead of restarting the desktop process for every request.
- Every bridge call is logged in Odoo as the audit trail.
- 34 versioned data migrations shipped with the Odoo module.