Odoo Integration for Document Processing
Fluxity connects to Odoo to turn incoming financial documents into validated ERP records. Vendor bills, purchase orders, credit notes, and expense reports are extracted, mapped to your Odoo data model, and created as transaction records with full audit traceability.
The integration works through Odoo’s JSON-RPC and XML-RPC APIs, respecting your existing access rights, approval workflows, and multi-company structure. No intermediate staging layer, no CSV exports, no manual data re-entry.
Integration Overview
Fluxity communicates with Odoo through both JSON-RPC and XML-RPC interfaces, selecting the appropriate protocol based on the operation. Record creation and updates—vendor bills, journal entries, partner lookups—use JSON-RPC for its native support of Odoo’s ORM methods. Bulk read operations and external system callbacks can fall back to XML-RPC where compatibility is needed with older Odoo versions or third-party middleware.
The integration targets the Purchase module and Accounting module in Odoo. Incoming documents become draft vendor bills with fully populated invoice lines, tax references, and analytic account distributions. If a purchase order reference is found in the extracted data, Fluxity links the vendor bill to the corresponding PO record, enabling two-way and three-way matching against goods receipts before approval.
For organizations running Odoo in multi-company mode, Fluxity resolves the correct company context before creating any record. Journal assignments, chart of accounts, fiscal positions, and tax configurations all derive from the company selection, so a single Fluxity workspace can serve multiple Odoo companies without duplicating extraction rules. Odoo’s built-in approval workflows and activity scheduling continue to work normally on records that Fluxity creates—draft bills enter the same review pipeline as manually entered ones.
Supported Document Types
Vendor Bills & Invoices
Extract header fields, line items, tax breakdowns, and payment terms from supplier invoices. Fluxity maps each field to the corresponding Odoo vendor bill model, including journal assignment, analytic distribution, and multi-company routing.
Purchase Orders
Capture PO numbers, product references, quantities, and unit prices from purchase order documents. Extracted data links to existing Odoo purchase orders for three-way matching against goods receipts and vendor bills.
Credit Notes
Identify credit memo references, adjustment line items, and original invoice links. Fluxity creates refund records in Odoo with the correct reconciliation relationships to the original vendor bill.
Delivery Slips
Parse delivery notes, packing lists, and goods receipt confirmations. Extracted shipment references, quantities, and product identifiers map to Odoo stock picking records for receipt validation and inventory updates.
Expense Reports
Extract receipt data, expense categories, employee references, and cost amounts from submitted expense documentation. Mapped fields flow into Odoo expense records with analytic account coding and approval routing.
Data Mapping
Fluxity maps extracted document fields to Odoo model fields. The default mapping covers standard vendor bill records in the account.move model. Custom fields, analytic distributions, and company-specific overrides can be configured per workspace.
| Fluxity Field | Odoo Field |
|---|---|
| Vendor Name | Partner (partner_id) |
| Invoice Number | Bill Reference (ref) |
| GL Account | Account (account_id) |
| Line Items | Invoice Lines (invoice_line_ids) |
| PO Reference | Purchase Order (purchase_id) |
| Tax Code | Tax (tax_ids) |
| Analytic Account | Analytic Account (analytic_account_id) |
| Analytic Tags | Analytic Tags (analytic_tag_ids) |
| Company | Company (company_id) |
| Currency | Currency (currency_id) |
Getting Started
- 1
Connect your Odoo instance
Provide your Odoo server URL and generate an API key from your user profile in Odoo. Fluxity authenticates over JSON-RPC using your API key and database name. No passwords are stored, and access is scoped to the permissions of the connected user account.
- 2
Configure company and journal mappings
Map your Odoo companies and accounting journals to Fluxity workspaces. For multi-company environments, define which company context applies to each document source. Journal assignments determine where vendor bills, credit notes, and expense entries land in your chart of accounts.
- 3
Set up analytic account rules
Define how Fluxity distributes costs across your Odoo analytic accounts and tags. Rules can be based on vendor, document type, product category, or keywords found in line item descriptions. Analytic distributions apply automatically during bill creation, matching your existing cost allocation structure.
- 4
Test with sample vendor bills
Upload a batch of real documents to verify extraction, field mapping, and validation against your Odoo staging environment. Fluxity highlights any partner mismatches, missing account references, or tax configuration errors before you commit to production processing.
- 5
Enable automatic bill creation
Switch from test mode to live processing and enable automatic vendor bill creation in Odoo. Incoming documents are extracted, validated, and posted as draft bills ready for your approval workflow. Every record carries an audit trail linking the source document to the Odoo transaction it created.
See Fluxity and Odoo in action
Book a demo to see how Fluxity automates document processing for Odoo environments.