Bi-Directional Xero & Odoo Sync

Bi-Directional Xero & Odoo Sync Build a two-way Odoo Online and Xero integration matching our ServiceM8 accounting sync We are United Barrel Services in Australia. We are replacing ServiceM8 with an existing customised Odoo Online system and keeping Xero for accounting. Please quote an external integration using n8n Cloud or another supported API service. We must stay on Odoo Online; no installable backend module or Odoo.sh migration. Please read the attached accounting-data brief before quoting. No forms, reports, PDFs, file attachments or photos are to be sent to Xero. No Google storage work is required. CURRENT SETUP Our ServiceM8 account connects to the Xero organisation Pro Barrel Services. Invoices export as Approved, use the job number, and partial invoices use A/B/C suffixes. Prices are tax exclusive. The default terms are 30 Days, with customer-specific terms/due dates to preserve. Payments use the configured PRO BARREL SERVICES PTY LTD account. Xero Tracking Categories, Partial/Progress Invoicing and Bundles are enabled. There are ten Region choices and six tax definitions detailed in the attachment. CURRENT DOCUMENTED TIMING - Invoice export begins on approval. Total-changing edits can resync invoice lines. - New ServiceM8 customers/items first export with an approved invoice. Linked customer/item updates sync both ways within approximately 30 minutes. - Payments entered before approval accompany the invoice; later receipts export immediately. Payments on linked invoices in Xero return within 30 minutes. - Tax definitions and Sales/Revenue account codes import automatically from Xero; exact ongoing intervals are not published. - Tracking definitions refresh daily, taking up to 24 hours. Region selections travel with invoice export. - Xero-origin invoices do not import into ServiceM8. This is not full two-way general ledger synchronisation. These are ServiceM8 published timings, not measured latency in our account. Full sources and lifecycle rules are in the attachment. REQUIRED WORK 1. Two-way customers and catalogue items, with stable Xero IDs, field ownership and conflict handling. 2. Office-approved Odoo invoices to Xero, with correct GST/TaxType, accounts, dates, PO, descriptions and Region on invoice lines. 3. Partial invoices from one job, unique numbers, correct charge allocations, independent balances and bundle component handling. 4. Recorded payments both ways, without duplicates or feedback loops; return part-paid/paid/balance state and handle Xero reversals/credits affecting the balance. State whether you implement native Odoo reconciliation or a separate Xero balance display. 5. Visible sync status/errors, safe retry, durable queue/ID mappings, rate-limit handling, daily reconciliation and catch-up after outages or quota exhaustion. 6. Match existing ServiceM8-era records before cutover, preserve historical invoice identities and prevent re-export. TARGET TIMING Start approved invoice/receipt export immediately, proposed normal completion within 60 seconds. Return linked customer/item/payment changes within 30 minutes, 24/7. Refresh tracking daily. Proposed tax/account refresh: within 30 minutes. Disclose limitations and any changes needed to meet these targets. ODOO Existing jobs use planning.slot; invoices use account.move/account.move.line; job charges use x_job_price_line. Studio custom fields and internal split billing already exist. Confirm Odoo 20/current JSON-2 API compatibility and the required access. Reuse our existing workflow rather than rebuild it. QUOTE AND DELIVERABLES Provide a fixed/capped AUD price, GST status, milestones, timeline, platform/hosting costs, warranty and ongoing support. Separate discovery, Studio changes, cutover/history work, and any conditional stock-visibility allowance. We are considering 2,500 n8n executions/month: show an execution budget from measured volumes and recommend the correct plan without slowing the required sync. Include exported workflows/source, field mappings, configuration, successful test evidence, administrator training and a recovery/key-renewal runbook. All accounts/workflows must be owned by us. Demonstrate normal, partial, reversed and duplicate payments/invoices, invoice edits, mapped taxes/regions, outages and safe retries before authorised production rollout. Please provide examples of similar Odoo Online/Xero work, describe your proposed architecture, identify what remains manual and list all exclusions.