How does Transformance integrate with Odoo?

Key Takeaways

Transformance connects to Odoo and runs in production with customers today; it reads AR data and writes clearing postings, journal entries and reversals back.
In Odoo, clearing an invoice means reconciling its receivable journal item with a payment or bank transaction; the invoice then shows Paid.
Nothing posts to Odoo without human sign-off: 100% posting validation, thresholds by amount, entity and customer, and a full audit trail.
The ERP connection typically takes 2-3 days and your IT team may be involved; full rollout takes 4-8 weeks.
Before connecting, check your Odoo version, hosting, plan, outstanding-account setup and lock dates (checklist below).

Key Takeaways
How does Transformance connect to Odoo?
What does Transformance read from Odoo?
What does Transformance write back to Odoo, and who approves it?
How does a customer payment go from bank line to Paid in Odoo?
What happens with short payments, differences and currencies in Odoo?
How do lock dates, reversals and corrections work with Transformance in Odoo?
How does AR collections work on top of Odoo follow-ups?
What should you check in Odoo before the integration?

How does Transformance connect to Odoo?

Transformance connects to Odoo, runs in production with customers today, reads your AR data and writes approved postings back; the connection typically takes 2-3 days.

Transformance and Odoo at a glance: what it reads, what it writes back, how it connects

Area	Where it lives in Odoo	Transformance	Who controls it
Customer master	Contacts: payment terms, preferred payment method	Reads	Odoo stays the master
Invoices and credit notes	Customer invoices and credit notes; payment state In payment, Paid, or open with a Partial banner	Reads	Odoo stays the system of record
Open items	Unreconciled receivable journal items per partner; outstanding receipts account if configured	Reads	Odoo
Bank transactions	Bank journal transactions from bank sync or a CAMT.053, CSV or OFX import, held on the suspense account until reconciled	Reads bank statements	Odoo
Remittances	Usually outside Odoo: email body, PDF, portal	Reads (DocSense, over 97% extraction accuracy)	Transformance
Clearing	Reconciling the invoice’s receivable item with the payment or bank transaction; the invoice moves to Paid	Writes after approval	A person approves, within thresholds by amount, entity and customer
Journal entries	For example a payment difference posted to a write-off, bank fee or cash discount account	Writes after approval	A person approves
Reversals and corrections	Credit note (Reverse), unreconcile, reversal entry; lock dates apply	Writes after approval	A person approves
Connection	Odoo Online, Odoo.sh or on-premise; external API on Custom plans	Method follows your environment; typically 2-3 days, IT may be involved	Your IT team or Odoo partner, with Transformance

The connection method follows your Odoo environment (hosting, version, plan) and is agreed in the connection step; your IT team or Odoo partner may be involved. Across ERPs, Transformance’s connection options include APIs, file or SFTP, middleware and its own on-premises agent.

On Odoo’s side, the version matters. Since 19.0, “part of the Models API is easily available over HTTP via the /json/2 endpoint”, with an API key sent “as a bearer token”, and the older XML-RPC and JSON-RPC endpoints “are scheduled for removal in Odoo 22 (fall 2028) / Odoo Online 21.1 (winter 2027)” (Odoo 19.0 documentation, 2026). The same page notes that “access to data via the external API is only available on Custom Odoo pricing plans”, not on One App Free or Standard. Check your plan before the first call.

Odoo stays the system of record; Transformance adds cash application, deductions, AR collections and cash forecasting as an execution layer on top of the ERP. The other systems are in the ERP integrations overview.

‍

What does Transformance read from Odoo?

Transformance reads customer master data, open items, invoices and credit notes, journal entries, bank transactions and remittances, in the form Odoo already keeps them.

In Odoo, contacts are the customer master. Customer invoices, credit notes and journal entries are all journal entries made of journal items, and the open receivable is the set of unreconciled receivable journal items per partner. Developers know the models as account.move, account.move.line and account.bank.statement.line.

Payment state decides what counts as open. A registered payment marks the invoice In payment. With outstanding accounts, the counterpart sits “in an outstanding receipts or payments account” and the Amount Due is reduced; without them, “no journal entry is created”. Either way, the invoice is marked Paid once it is reconciled with a bank transaction (Odoo 19.0 documentation, 2026). An AR layer has to read both states, or it chases invoices that a customer has already paid.

Bank transactions follow one rule in Odoo: “every transaction is linked to a journal entry that debits/credits the journal’s main account and its suspense account until it is fully reconciled” (Odoo 19.0 documentation, 2026). They arrive in one of two ways:

Bank synchronisation. Odoo supports “over 26,000 financial institutions worldwide”, requires a valid Odoo Enterprise subscription and syncs bank journals every twelve hours by default (Odoo 19.0 documentation, 2026).
File import. Odoo imports CAMT.053, CSV, XLSX, OFX, QIF and, for Belgium, CODA (Odoo 19.0 documentation, 2026).

Remittances usually arrive outside Odoo, in an email body, a PDF or a portal. DocSense reads them with over 97% extraction accuracy across 100+ document types and 170+ languages, with no templates (Transformance platform data, 2026). The cross-ERP map: what AR automation reads and writes.

What does Transformance write back to Odoo, and who approves it?

Transformance writes clearing postings, journal entries and ERP updates, including reversals, back to Odoo, and nothing posts without a person’s sign-off within your thresholds.

In Odoo’s terms, clearing means reconciling the invoice’s receivable journal item with the payment or bank transaction; the reconciled items share a matching number and the invoice moves to Paid. Journal entries cover the amounts around the match: a written-off difference, a bank fee, a cash discount.

Every write passes the same controls:

Approval. A multi-level approval model with thresholds by amount, entity and customer. Administrators configure the rules; finance users approve. The four levels are read, recommend, execute and post.
Validation. ClearMatch validates 100% of postings, reaches a 95% auto-match rate and runs end to end in under 8 minutes (Transformance customer data, 2026). See ClearMatch.
Audit trail. Each step records the timestamp, what the system did, what the user did, who approved, the input and the confidence.
Access and data. SSO/SAML and role-based access control. Your data is hosted in your region, VPC deployment in your own cloud is available, and no customer data is used to train models (how AI agents access ERP data safely).

An illustrative rule: every reconciliation above a set amount, or for a key account, goes to a named approver (approval thresholds in depth).

How does a customer payment go from bank line to Paid in Odoo?

A customer payment goes from bank line to Paid in seven steps: import, identify the payer, match, classify the difference, approve, reconcile and review, with a person approving every posting.

From bank line to Paid in Odoo in 7 steps

The bank transaction arrives in the Odoo bank journal, by bank synchronisation or a CAMT.053 or CSV import, and sits on the suspense account.
The payer is identified: the partner on the transaction, a partner-mapping rule, or the remittance and Customer 360 history when the name does not match.
Open items are matched from the bank line, the remittance and the customer’s history; Vero investigates what does not match.
Any difference is classified: short pay, deduction, cash discount, bank fee, overpayment or currency difference.
A person approves the proposed reconciliation and any journal entry, within thresholds by amount, entity and customer.
The approved clearing is written to Odoo. The receivable item is reconciled, the invoice shows Paid, and differences post to their accounts.
Exceptions and reversals follow the same approval and land in the audit trail; AR collections then work only on what is still unpaid.

In Odoo bank reconciliation, without a partner on the transaction, Odoo compares the transaction’s Label with the Number, Customer Reference and Payment Reference of existing invoices and payments. With a partner, it matches on amount in a fixed order: exact match, discounted match for early-payment terms, then amount in label (Odoo 19.0 documentation, 2026). Reconciliation models add custom rules on journal, amount or label, including “Match Regex” conditions and partner mapping (Odoo 19.0 documentation, 2026).

‍

From bank line to Paid

1Read bank line

2Propose match

3You approve

4Reconcile in Odoo

5Invoice Paid

AutomatedYou

‍

Vero is built for the payments that need more than a reference and an amount: a wrong or missing reference, one payment for many invoices, a remittance in a PDF, a different payer. It investigates from Customer 360, fetches information from internal and external sources and proposes the match with the evidence; a person approves. The method in detail: how AI reads remittance advice and matching a payment with no reference.

Illustrative example (fictional customer and amounts). One bank line of USD 48,210.00 arrives with the reference “remittance attached”. The emailed PDF lists three invoices of USD 18,400.00, 16,950.00 and 13,360.00, together USD 48,710.00, less USD 500.00 for damaged goods.

DocSense reads the PDF; Vero proposes reconciling the bank line with all three invoices.
The USD 500.00 stays open on the third invoice, Odoo’s Keep open outcome, and goes to the deduction workflow.
The AR lead approves the proposal before anything reconciles.

The arithmetic: 18,400 + 16,950 + 13,360 = 48,710, less 500 is 48,210. Across ERPs: how external systems clear open items.

What happens with short payments, differences and currencies in Odoo?

Odoo either keeps a short-paid invoice open as a partial payment or marks it fully paid and posts the difference to an account; Transformance proposes which, and a person decides.

For a payment below the amount due, Odoo’s Payment Difference field offers two options. “Keep open” keeps the invoice “open and mark[s] it with a Partial banner”. “Mark as fully paid” asks for an account in Post Difference In, and “a journal entry will be created to balance the accounts payable or receivable with the selected account” (Odoo 19.0 documentation, 2026).

‍

Short payment: keep open or close

Vero checks evidence

You decide

Keep open

ClosePost difference

Odoo updated

AutomatedYou

‍

Three more cases come up in every close:

Overpayment. If the transaction is larger than the invoice, it “is only partially reconciled”, and the rest is reconciled like any other amount (Odoo 19.0 documentation, 2026).
Recurring small differences. Odoo’s default Bank Fees and Cash Discount reconciliation models move a transaction’s remaining balance to a bank fees or cash discount account. Models are Manual (a button) or Automated; when several automated models match, “the first one in the sequence of models is applied” (Odoo 19.0 documentation, 2026).
Currency. “If a payment is (un)reconciled in a different currency, a journal entry is automatically created to post the currency exchange gains/losses (reversal) amount” (Odoo 19.0 documentation, payments, 2026). Odoo records exchange differences “in a dedicated journal” (Odoo 19.0 documentation, 2026).

A short pay is often a deduction. ClaimIQ identifies deductions with 97% accuracy and classifies each into one of six categories in under 15 seconds, against 45 minutes by hand (Transformance customer data, 2026). See ClaimIQ.

How do lock dates, reversals and corrections work with Transformance in Odoo?

Odoo’s lock dates block postings in closed periods, a credit note reverses an invoice, and unreconciling unlinks a payment without deleting it; Transformance’s reversals follow the same approvals.

A Lock Everything date “prevents modifications to any posted journal entries with an accounting date on or before the lock date” and prevents posting new ones there; “the system automatically sets the accounting date to the day after the lock date”. Administrators can configure exceptions, but the Hard Lock date “is irreversible” (Odoo 19.0 documentation, 2026). For example, with October locked on 31 October, a write-off approved on 3 November for a 30 October payment gets the accounting date 1 November. Agree that rule with your controller before go-live.

Odoo’s documentation states that “issuing a credit/debit note is the only legal method for canceling, refunding, or modifying a validated invoice”. Reverse opens a draft credit note; Reverse and Create invoice creates one “automatically validated and reconciled with the related invoice” and opens a new draft invoice (Odoo 19.0 documentation, 2026). Separately, “unreconciling a payment unlinks it from the invoice or bill but does not delete the payment” (Odoo 19.0 documentation, payments, 2026).

Transformance writes ERP updates including reversals. A reversal goes through the same approval thresholds and lands in the same audit trail (what an AI agent’s audit trail records).

Two more Odoo details are worth agreeing before go-live:

Duplicate bank transactions from a human or sync error: Odoo’s Bank Matching view has a Find Duplicate Transactions action (Odoo 19.0 documentation, 2026).
Company-specific records. In a multi-company database, invoices are visible only inside their company, while new contacts are shared by default (Odoo 19.0 documentation, 2026).

How does AR collections work on top of Odoo follow-ups?

Odoo sends follow-ups by overdue days through email, WhatsApp, SMS or post; CollectPulse runs B2B collections on the same Odoo data, once payments are matched.

Odoo’s follow-up levels trigger actions by overdue days: Send Email, Send WhatsApp message, Send SMS Message and Send a Letter (letters, WhatsApp and SMS run through Odoo In-App Purchase). A level can run automatically and schedule an activity for a responsible user (Odoo 19.0 documentation, 2026).

Odoo’s own advice puts cash application first: “Reconcile all bank transactions before starting the follow-up process to avoid sending reminders for invoices that have already been paid.”

CollectPulse works on the open items that remain:

100% of overdue invoices actioned within 24 hours; manual teams reach 30-40%.
Vero handles 60-80% of routine touches, in Microsoft Teams.
The AI calling agent makes 15-20 calls an hour in 70+ languages and identifies itself as AI at the start of every call.
Promise-to-pay capture is 3x the manual rate, and DSO falls 8-12 days on average (Transformance customer data, 2026).

On Customer 360, one graph per customer, promises to pay, disputes and payment history sit next to the Odoo invoices they refer to. More on AI calling agents and automated dunning and CollectPulse.

What should you check in Odoo before the integration?

Before the integration, check eight things in Odoo: version, hosting, plan, the Accounting app, outstanding accounts, the bank transaction source, lock dates, and companies with their admin rights.

Odoo checklist before you connect AR automation

Version. 19.0 introduced the JSON-2 external API; XML-RPC and JSON-RPC are scheduled for removal in Odoo 22 and Odoo Online 21.1.
Hosting. Odoo Online, Odoo.sh or on-premise, and the region your database is hosted in.
Plan. Odoo documents that Odoo API access is only available on Custom plans, not One App Free or Standard.
Accounting app. Odoo’s editions page lists comprehensive Accounting, including bank statement reconciliation, under Enterprise; Community includes Invoicing.
Outstanding accounts. Which payment methods on your bank journals use outstanding receipts accounts; this decides when an invoice shows In payment or Paid.
Bank transactions. Bank synchronisation or file import (CAMT.053, CSV, OFX), and whether duplicates are cleaned.
Lock dates. Your Lock Everything and Hard Lock dates, and the posting-date rule after period close.
Companies and rights. How many companies and branches the database holds, which contacts they share, who owns admin rights, and which user the connection runs under.

The list speeds up scoping and is based on Odoo’s documentation. The ERP connection then typically takes 2-3 days, and your IT team may be involved; a proof of value runs 4-5 weeks on one entity, and full rollout takes 4-8 weeks (what drives the implementation timeline).

Who Transformance is for

ERPs: Odoo, running in production with customers today, alongside SAP S/4HANA, SAP ECC, NetSuite, Microsoft Dynamics 365 Finance & Operations and Business Central; Oracle and Infor supported.
Size: mid-market to large enterprise, 250 to 2,000+ employees, including groups with several entities and shared service centres.
Payment volume: from under 1,000 to over 100,000 payments a month.
Industries: manufacturing, consumer goods and food and beverage, logistics, e-commerce, agriculture, energy and professional services.
Scope: cash application alone, or the full order-to-cash (cash application, deductions, AR collections, cash forecasting).

Conclusion: Odoo keeps the books, Transformance does the matching and chasing

On Odoo, Transformance reads the open items and the documents behind them, matches and investigates in its own layer, and writes back only what a person approves.

Odoo’s own rules still govern every posting. Start with one company and one bank journal, then extend; Book a Call to scope it.

Key terms

Cash application: matching incoming payments to open invoices and clearing them in the ERP.
Bank reconciliation: validating bank transactions against the items they settle; in Odoo, the Bank Matching view.
Remittance advice: the payer’s note of which invoices a payment covers and why amounts differ.
Credit memo: in Odoo a credit note, the document that reverses or reduces a validated invoice.
Short pay: a payment below the invoice amount; Odoo keeps it open or posts the difference.
CAMT.053: the ISO 20022 bank statement format, one of Odoo’s import formats.

Related guides

‍

Frequently Asked Questions

Does Transformance integrate with Odoo?

Yes. Transformance connects to Odoo and runs in production with customers today, reading contacts, invoices, open items and bank transactions and writing approved clearing postings, journal entries and reversals back.

Which Odoo version, edition or plan does the connection need?

The connection method follows your Odoo environment, so bring your version, edition, hosting and plan to the first call. Odoo documents that external API access requires a Custom plan.

How long does it take to connect Transformance to Odoo?

The ERP connection typically takes 2-3 days, and your IT team or Odoo partner may be involved. A proof of value runs 4-5 weeks on one entity, and the full rollout takes 4-8 weeks.

Is Transformance a fit for our company size and payment volume on Odoo?

Transformance is built for mid-market to large enterprises with 250 to 2,000+ employees, including groups with several entities, processing from under 1,000 to over 100,000 payments a month.

Can we start with cash application only?

Yes. You can run cash application alone on Odoo, or the full order-to-cash with deductions, AR collections and cash forecasting.

Does Transformance post to Odoo without approval?

No. Every reconciliation, journal entry and reversal is approved by a person within thresholds by amount, entity and customer before it posts, and the audit trail records who approved it.

What does the Odoo integration cost?

The cost depends on your scope and the number of entities, for example cash application alone or the full order-to-cash across several companies. Book a Call to scope it.

SAP, SAP S/4HANA, Microsoft, Dynamics 365, Business Central, Oracle, NetSuite, Odoo and Infor are trademarks of their respective owners (SAP SE, Microsoft Corporation, Oracle Corporation, Odoo S.A., Infor). Transformance is not affiliated with or endorsed by them.