Odoo Integration
Connect Odoo (18 or later) to Muin, and use Muin AP Control for Odoo to check, approve, post and plan payment of vendor bills inside Odoo. It is not listed in the Odoo Apps Store yet.
What works today: connecting an Odoo database (Odoo 18, 19 or 20) to Muin with an API key, with a live connection test. Not in the store yet: the Odoo Apps Store listing for Muin AP Control, the Odoo app described on this page. It is built and in final review; this page will say when you can install it from the store.
Connect Odoo
You need an Odoo user who can read purchase orders and create vendor bills, and an API key for that user.
- In Odoo, open your user menu > Preferences > Account Security and click New API Key. Copy the key.
- In Muin, open Connections, go to the Catalog tab, find Odoo ERP and click Connect.
- Enter a connection name, the Odoo login email of that user, and the API key.
- Click Create Connector, then enter your Odoo server URL (for example
https://yourcompany.odoo.com) and database name. - Click Complete Setup. Muin tests the connection with Odoo before it says connected. If Odoo refuses the key, the wizard shows Odoo’s reason and lets you enter the key again.
The key is stored encrypted. To replace it later, reconnect from Connections.
Muin AP Control for Odoo
Muin AP Control is an Odoo app. It runs inside Odoo and sends your vendor bills to Muin to be checked. Muin reads each bill, codes its lines, matches it to its purchase order and receipt, checks for duplicates, contract price differences and vendor bank-detail changes, and routes it for approval. Odoo makes every payment. Muin never moves money.
It works on Odoo 18, 19 and 20, on Odoo.sh and on-premise. Odoo Online does not allow store apps, so it cannot run there.
What it adds to Odoo
Everything is under the Muin AP Control menu in Odoo.
| Menu | What it does |
|---|---|
| Bills > Exceptions, Checked by Muin | The bills Muin flagged, each with its reason, and the bills Muin has checked. |
| Insights and reports | Muin’s Exceptions report and Money recovered (duplicates caught, contract overcharges and other money you may get back). |
| Agents inbox | Each Muin agent’s actions that wait for a person, with approve and reject. A rejection needs a note. |
| Ask AP | Ask a question about your vendor bills in plain words. The answer uses only the bills you can open in Odoo, and lists the bills it used. |
| Configuration > Connect, Settings, My Muin key | Connect the database to Muin, set tolerances and approval tiers, and add your own Muin key. |
Set it up
- An Odoo administrator opens Muin AP Control > Configuration > Connect and signs in to Muin (or creates a Muin account there).
- The administrator accepts the data-transfer notice. Nothing leaves your Odoo database before this step.
- Each person who approves, rejects, changes settings or uses Ask AP adds their own Muin key under Configuration > My Muin key, so Muin applies their Muin permissions too.
Pricing
The first 100 bills are free, once per Odoo database. After that there are two ways to keep checking bills:
- Muin AP Control Pro: install it from the Odoo Apps Store. It costs $49 once per Odoo version, with no subscription, and covers fair use of 500 bills a month. When the free bills run low, the bill panel in Odoo links to it.
- A direct Muin account: move your organization to a Muin plan, with Muin support. Your Odoo connection keeps working. An owner or admin does this in Muin under Settings > Billing.
Muin does not sell bill packs for Odoo. $49 is the launch price.
Check a bill
Open a vendor bill in Odoo and click Send to Muin. Muin checks it and writes the result back on the bill’s panel: each flag with its reason, for example a possible duplicate of a bill already on file, or a price above the purchase order. Click Refresh from Muin to read the latest result.
When you send a bill with your own Muin key, Muin records you as its submitter, so your approval rules apply to you (a rule that blocks self-approval keeps you from approving your own bill).
Approve or reject from Odoo
On a bill Muin has checked, use Approve in Muin or Reject in Muin.
- Approve decides the approval step that waits on you. If the step is with someone else, Odoo tells you who, for example “It is waiting on Dana Reyes (step 1 of 2), not on you”, and nothing is approved.
- Reject rejects the bill, or its open approval step, as you.
- Once a bill is approved, Muin posts it on the Odoo bill it came from, shortly after the approval. This happens whichever way the last approval was given: in Odoo, in the Muin Inbox or on the bill in Muin.
- If Muin cannot post it, for example because the Odoo bill now differs from the approved bill or pays a bank account the vendor never used, the bill stays a draft in Odoo and an alert in the Muin Inbox says why.
Approving never pays a bill.
Settings
Administrators open Muin AP Control > Configuration > Settings to set:
- price and quantity tolerances for purchase order matching;
- Bill approval tiers: click Add a line, give the tier a name, its amount limits in your company currency and one approver (a Muin role or a member’s email). Limits are inclusive, so two active tiers may not meet or overlap. A save that would make them overlap is refused, naming both tiers;
- each agent’s on/off switch, including the Payment Run Planner.
Muin holds these settings, so they also apply to bills checked in Muin. If Muin refuses part of a save, Odoo lists what was saved and what was not.
To choose the Odoo accounts an approved bill posts to, open Connections in Muin, select your Odoo connection and, on its Settings tab, map each GL code to an Odoo expense account and each fund or program to an Odoo analytic account under Odoo accounts. A bill line Muin has not coded keeps the Odoo account already on the bill in Odoo, and a line coded with a GL code posts to the Odoo account mapped for that code.
Paying vendors: the Payment Run Planner
The Payment Run Planner runs once a week (Monday, 07:00) and plans which approved bills to pay.
- It reads each bill’s open balance from Odoo and takes every bill due in the next 7 days, paid on its due date (today if it is overdue), for what Odoo says the bill still owes.
- It leaves a bill out, and names it with the reason, when Odoo shows it paid or cancelled, when a payment for it is already waiting in Odoo, or when only its early-pay discount is left open. A bill not due yet waits for a later run.
- It holds back a bill whose vendor bank account Muin cannot check, or whose bank details changed, and says why.
- One run pays at most 200 bills; the rest wait for the next run.
The plan waits in the Agents inbox for a person. Nothing is written to Odoo before someone approves it. Once approved, Muin creates a draft payment in Odoo for each bill, linked to the bill, into its vendor bank account. This is the same on Community and Enterprise. You review and confirm them in Odoo, and Odoo pays. Muin never confirms or posts a payment.
Early-pay discounts: the Payment Run Planner pays what a bill owes and does not take an early-pay discount off. To take a discount, register the payment in Odoo’s payment dialog, which offers the discount while it is open.
When Odoo pays someone other than the vendor
Muin reads the bill payments Odoo makes every hour and marks each paid bill as paid. If a payment went to another Odoo partner, or into a bank account that belongs to another partner, Muin does not mark the bill paid. It opens an alert in the Inbox and shows a notice on the bill in Muin, with the Odoo payment, the partner paid and the bank’s name. It never shows the account number.
If the payment is correct, for example the vendor uses a factoring company, open the bill in Money Out > Bills, write how you checked it in Why is this payment correct?, and press Accept this payment. You need permission to manage vendor bills. The next Odoo sync then marks the bill paid. Dismissing the Inbox alert does not accept the payment: the bill stays unpaid until someone accepts it from the bill.
Your data
After the administrator’s consent, the app sends Muin the company name, the database UUID, the Odoo and app versions and the owner email (once, when connecting), each bill you send (its document, lines, amounts, vendor and purchase order references), and the payments Odoo records against those bills. AI runs on AWS Bedrock, and customer data is never used to train models. Muin AP Control Pro is sold through the Odoo Apps Store; a direct Muin account is billed by Muin.
Troubleshooting
| What you see | Why | What to do |
|---|---|---|
| Muin refuses the API key when you connect | Odoo rejected the key or the login email. | Create a new API key in Odoo and reconnect from Connections. |
| Approve in Muin says the bill is waiting on someone else | The open approval step belongs to another approver. | That person approves it, from Odoo or from their Muin Inbox. |
| Saving approval tiers is refused | Two active tiers would meet or overlap. | Start the higher tier above the other tier’s upper limit. |
| A bill is missing from the payment run | The run names each bill it left out and why, in its summary. | Read the reason. A bill with a payment already waiting in Odoo is never planned twice. |
Next Steps
- AI Invoice Extraction - How Muin reads invoices automatically
- Document Processing - The AI extraction pipeline
- Bank Reconciliation - Matching payments to invoices