US QuickBooks Online /
QuickBooks Online / Desktop Two-Way Bridge (BYOK) — sync customers, vendors, invoices, vendor bills and journal entries between Odoo and QuickBooks with conflict handling and IIF export
QuickBooks Online / Desktop Two-Way Bridge (BYOK) — sync customers, vendors, invoices, vendor bills and journal entries between Odoo and QuickBooks with conflict handling and IIF export
Key Features
Two-way record sync
Two-way record sync — push Odoo customers, vendors, customer invoices, vendor bills and journal entries up to QuickBooks Online, and pull the same entity types back down (journal entries now round-trip both ways too), keyed by a persistent cross-reference so nothing is duplicated.
Vendor bill sync
Vendor bill sync — Odoo vendor bills push to QuickBooks as Bill objects with vendor and expense-account lines mapped across, and QuickBooks Bills pull back into draft Odoo vendor bills matched to the vendor, keyed by the QuickBooks Bill Id so re-runs update instead of duplicating.
Bidirectional journal entries
Bidirectional journal entries — journal entries push from Odoo to QuickBooks and QuickBooks JournalEntry objects pull back into balanced Odoo journal entries, with debit/credit lines mapped to the matching Odoo account by code.
BYOK QuickBooks Online connection
BYOK QuickBooks Online connection — store your own client id, client secret, realm id and refresh token; the app builds the OAuth2 bearer request, refreshes the access token when it expires and offers a one-click Test Connection button that
QuickBooks Desktop IIF export
QuickBooks Desktop IIF export — for QuickBooks Desktop / Enterprise, emit a tab-delimited IIF file for customers, vendors and transactions that imports straight into the desktop company file — no API required.
Conflict detection & resolution
Conflict detection & resolution — every synced record is fingerprinted; when both sides changed since the last sync the bridge raises a conflict and applies your policy (Odoo wins, QuickBooks wins, newest wins, or manual).
Field mapping engine
Field mapping engine — a serializer converts Odoo partners and moves into the QuickBooks Customer / Vendor / Invoice / JournalEntry shapes and a parser converts them back, with sensible defaults for names, emails, addresses, tax lines and a
Sync jobs with a full audit line log
Sync jobs with a full audit line log — each run creates a job record with per-record lines (created / updated / skipped / conflict / error) so you can see exactly what moved and why.
Selective, filtered sync
Selective, filtered sync — choose direction and which entity types to include, and cap how many records a single run processes.
Scheduled background sync
Scheduled background sync — an optional cron runs the enabled connections on a schedule so QuickBooks and Odoo stay reconciled hands-free.
Sync token safety
Sync token safety — stores the QuickBooks SyncToken for each record so updates never clobber a newer QuickBooks revision.
Company-scoped & multi-connection
Company-scoped & multi-connection — run separate connections per Odoo company or per QuickBooks realm.
Screenshots
Why Choose This Module
The connector is bring-your-own-key (BYOK). You paste your own QuickBooks Online app credentials (client id, client secret, realm/company id and OAuth refresh token) and every request is made with your QuickBooks account. We never proxy your data through a third party and we never hard-code any credentials. For QuickBooks Desktop, where there is no live REST API, the same mapped records are written out as a clean IIF import file you drop into the desktop company file.
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: OPL-1
- Languages: English
- Author: Pokutsoft
- Dependencies: base, mail
- Support: support@pokutsoft.com
Update date: 2026-07-16