AI agents capture, match, code and route your supplier invoices, then hand them to SAP S/4HANA through its standard interfaces. SAP stays the system of record.
Everything between an invoice arriving and its posting runs in Orcha. What your auditors rely on stays in SAP.
Many SAP companies capture and approve supplier invoices in an add-on inside SAP: custom transactions, template-based OCR, workflows only the SAP team can change. Orcha replaces that layer and leaves SAP to keep the books.
Templates and rules per supplier, workflows inside SAP, and every upgrade or S/4HANA migration has to carry the add-on along.
Orcha reads each invoice without templates, matches it against the purchase order and goods receipt in SAP and routes the approval in the browser, in Slack, in Teams or by email.
Both run on the same invoices side by side. Once the results match, the cockpit is switched off and stays out of your S/4HANA migration.
Orcha reads the master data it needs to code like your team, and hands over each invoice once it is approved.
Supplier invoices arrive by email, upload or portal, as PDF or as XRechnung and ZUGFeRD e-invoices.
Agents read each invoice, match it to the order, propose the coding and route it for approval.
The approved invoice reaches SAP as an FI or MM invoice, with the original document attached.
| Object | Direction | Interface |
|---|---|---|
| Vendors (business partners) | SAP to Orcha | OData API_BUSINESS_PARTNER |
| G/L accounts, cost centres | SAP to Orcha | OData or file |
| Purchase orders, goods receipts | SAP or another system to Orcha | OData, file or database |
| Coded supplier invoice or credit note | Orcha to SAP | IDoc INVOIC02 or SOAP |
| Original document (PDF) | Orcha to SAP or your archive | Agreed during setup |
| Posting and payment status | SAP to OrchaPlanned | OData or IDoc status |
IDoc, SOAP or the OData APIs of S/4HANA, with a technical user and no add-on in the core.
If your company routes interfaces through SAP Integration Suite, Orcha connects there and your iFlows stay in charge.
Already run MuleSoft, Boomi or another integration platform? Orcha plugs into it like any other system.
With or without purchase orders in SAP, on S/4HANA today or on the way there.
Invoices are matched against the purchase order and goods receipt in SAP. Orcha flags quantity and price differences before the handover.
If your purchase orders live in another system, Orcha matches against them there and hands the invoice to SAP as an FI document.
Orcha sits outside the SAP core, so nothing has to be migrated with it. Moving to S/4HANA only changes the connection.
Agree on the interface and the invoice types.
With exactly the authorisations the handover needs.
So Orcha codes the way your team does.
Every invoice type once, end to end.
Switch over once the results match.
No add-on and no custom development in the SAP core, directly or through your integration platform.
One technical user with access to the objects the handover needs.
Hosted in the EU, processing under a GDPR data processing agreement.
Every coding and approval recorded with its author and reasoning.
SAP S/4HANA on-premise, private cloud and public cloud. Each edition offers standard interfaces; which one is used depends on your setup. If you still run SAP ECC, we look at IDoc or file-based handover in the first call.
SAP Business One is a separate product with its own interface, the Service Layer. We set up Orcha's integration for it with you during onboarding; see the SAP Business One page.
SAP's standard interfaces: IDoc, SOAP or OData. Your SAP team decides which one. Orcha needs no add-on and no custom development in the SAP core.
Yes. If your interfaces run through SAP Integration Suite on SAP BTP, or through middleware such as MuleSoft or Boomi, Orcha connects to that platform instead of to SAP directly.
Orcha hands over the coded invoice with the original document. The final posting stays in SAP, with your team, and every step before it is recorded in Orcha.
Yes. Orcha captures, checks and codes supplier credit notes like invoices and hands them to SAP the same way, with the original document.
Yes. Orcha checks every incoming invoice for duplicates, split invoices and changed bank details before it is handed to SAP. Unusual cases go to a person instead of passing through.
No. Approvals run in Orcha, in the browser, in Slack, in Microsoft Teams or by email.
Yes. Orcha matches invoices against purchase orders and goods receipts from your other system and hands them to SAP as FI vendor invoices.
Yes. Orcha takes over capture, matching, coding and approval outside the SAP core. During a parallel run you compare both results, then the cockpit can be switched off, which also keeps it out of your S/4HANA migration.
Pre-coded invoices straight into DATEV Unternehmen Online.
Orcha × DATEVFinance & Operations, through its OData interfaces.
Orcha × Dynamics 365For companies that run SAP's ERP for small and midsize businesses.
Orcha × SAP Business OneAgents on top of the ERP you already run, with your rules and audit trail.
See the enterprise page