Orcha captures, codes and routes your vendor bills, then creates them in Odoo as drafts, with accounts, taxes, analytic distribution and the PDF. We set up the connection with you during onboarding.
Everything before the vendor bill runs in Orcha. Your journals, payments and reports stay in Odoo.
Orcha reads the master data it needs from Odoo and creates each approved vendor bill there as a draft.
Supplier invoices arrive by email or upload, as PDF or as XRechnung and ZUGFeRD e-invoices.
Agents read each invoice, propose account, tax and analytic distribution, and route it for approval.
The approved bill is created in Odoo with its lines, analytic distribution and the PDF, ready for your team to post.
| Object | Direction | Interface |
|---|---|---|
| Vendors, accounts, taxes | Odoo to Orcha | JSON-2 API |
| Analytic plans and accounts | Odoo to Orcha | JSON-2 API |
| Vendor bill (draft) | Orcha to Odoo | account.move |
| Original document (PDF) | Orcha to Odoo | ir.attachment |
No two Odoo databases are configured alike. Orcha's integration is designed to read your setup rather than assume one.
Coding includes your analytic distribution per line, split by percentage where you need it.
Each bill is created in the right company, with that company's accounts and taxes.
Orcha reads your chart of accounts and taxes, whether you run SKR03, SKR04 or your own.
We go through your Odoo version, setup and invoice volume.
Your admin creates a user with accounting rights and an API key.
So Orcha codes the way your team does.
Set up with you once for your structure.
Every bill type once, end to end.
Orcha connects as its own Odoo user, with the access rights you grant.
Odoo's external API, no changes to your accounting logic.
Hosted in the EU, processing under a GDPR data processing agreement.
Every coding and approval recorded with its author and reasoning.
Yes. Orcha creates draft vendor bills in Odoo and reads your master data. We set up the connection with you during onboarding.
Through Odoo's external JSON-2 API, with an API key for a dedicated user. On Odoo Online, the external API is only included in the Custom plan.
No. Orcha creates each vendor bill as a draft with its coding and the PDF. Posting stays with your team in Odoo.
Orcha uses the JSON-2 API that Odoo introduced with version 19. If you run an older version, tell us which one: Odoo is retiring its older XML-RPC and JSON-RPC APIs.
No. Approvals run in Orcha, in the browser, by email link or in Slack.
Coded vendor bills for NetSuite, set up during onboarding.
Orcha × NetSuiteApproved invoices posted and vendor master data kept current, every change approved in Orcha.
Orcha × Dynamics 365Invoices ready to book, without an add-on in the SAP core.
Orcha × SAPApproved bills and sales invoices straight into Xero.
Orcha × Xero