Orcha captures, codes and routes your supplier invoices, and approved invoices go to Sage with their coding and documents. Tell us which Sage product you run and we set up the connection with you during onboarding.
Everything before the booking runs in Orcha. Your ledger, VAT returns and payments stay in Sage.
Orcha reads your chart of accounts and suppliers from Sage and sends each approved invoice back with its coding.
Supplier invoices arrive by email or upload, as PDF or as XRechnung and ZUGFeRD e-invoices.
Agents read each invoice, propose account and tax code, and route it for approval.
The approved invoice goes to Sage with its coding and the original document.
| Object | Direction | Interface |
|---|---|---|
| Chart of accounts, tax codes, suppliers | Sage to Orcha | Depends on your Sage product |
| Coded supplier invoice | Orcha to Sage | Depends on your Sage product |
| Original document (PDF) | Orcha to Sage | Depends on your Sage product |
Sage comes in several products and versions. We agree the connection with you for the one you use.
Sage's products differ in their interfaces, so we confirm the connection for yours first.
Orcha proposes accounts and tax codes from your Sage chart of accounts.
Each invoice reaches Sage with its original document.
We confirm how Orcha connects to it.
Set up with your Sage admin.
So Orcha codes the way your team does.
Check the first invoices in Sage together.
Once the tests pass.
Connected through the interfaces of your Sage product, no changes to your ledger logic.
Orcha only gets the rights the integration needs.
Hosted in the EU, processing under a GDPR data processing agreement.
Every coding and approval recorded with its author and reasoning.
Yes. We set up the connection with you during onboarding, per Sage product.
We confirm the connection per Sage product. Tell us which one you run.
Approved invoices go to Sage with their coding; the booking stays with your team.
No. Approvals run in Orcha, in the browser, in Slack, in Microsoft Teams or by email.