Orcha captures, codes and routes your supplier invoices, then creates them in SAP Business One as A/P invoice drafts through the Service Layer, with your G/L accounts, tax codes, cost centres and projects. We set up the connection with you during onboarding.
Everything before the A/P invoice runs in Orcha. Your ledger, business partners and payments stay in SAP Business One.
Orcha reads the master data it needs from SAP Business One and creates each approved invoice 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 G/L account, tax code and cost centre, and route it for approval.
The approved invoice is created as a draft with its lines, coding and the PDF, ready for your team to add.
| Object | Direction | Interface |
|---|---|---|
| Business partners, G/L accounts | SAP Business One to Orcha | Service Layer |
| Tax codes, cost centres, projects | SAP Business One to Orcha | Service Layer |
| A/P invoice draft | Orcha to SAP Business One | Service Layer Drafts |
| Original document (PDF) | Orcha to SAP Business One | Attachments2 |
SAP Business One is SAP's ERP for small and midsize companies, usually run by a partner on SQL Server or SAP HANA. It is a separate product from SAP S/4HANA, which has its own Orcha page.
Each SAP Business One company is its own database. Orcha works with each one you use, with its own accounts and tax codes.
Orcha creates A/P invoice drafts, so nothing reaches your ledger until someone in SAP Business One adds it.
Orcha uploads the original invoice to your attachments folder and link it to the draft.
We go through your SAP Business One setup and invoice volume.
Your partner or IT makes the Service Layer reachable for Orcha over HTTPS.
With rights for A/P drafts, master data and attachments.
So Orcha codes the way your team does.
Every invoice type once, end to end.
Orcha signs in with a SAP Business One user and the rights you assign.
The Service Layer, no changes to your ledger logic.
Hosted in the EU, processing under a GDPR data processing agreement.
Every coding and approval recorded with its author and reasoning.
Anything else? Talk to the team that builds the integration.
Book a demoYes. Orcha creates A/P invoice drafts in SAP Business One and reads your master data through the Service Layer. We set up the connection with you during onboarding.
No. Orcha's SAP page covers SAP S/4HANA. SAP Business One is a separate product with its own interface, the Service Layer, and this page is about it.
Through the Service Layer, SAP Business One's REST interface, with a dedicated user for each company database. Your partner or IT makes it reachable over HTTPS.
No. Approvals run in Orcha, in the browser, by email link or in Slack.
Invoices ready to book, without an add-on in the SAP core.
Orcha × SAPCoded supplier invoices for Sage, set up per Sage product.
Orcha × SageCoded 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 365