Design partners We're building agentic inventory management and are looking for design partners to shape it with us. Agentic inventory design partners Contact us
OrchaSAP

Orcha × SAP. No add-on in the SAP core.

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.

  • Direct, via SAP Integration Suite or your middleware such as MuleSoft
  • Approvals in the browser, in Slack, in Teams or by email
  • Hosted in the EU, GDPR-compliant
Editions
SAP S/4HANA on-premise, private and public cloud
Connection
IDoc, SOAP or OData, SAP Integration Suite, or middleware such as MuleSoft
Direction
Invoices to SAP, master data from SAP
Changes in SAP
None. No add-on, no custom code in the core
Final posting
In SAP, by your team
Availability
Available today, set up with your SAP team

Orcha does the work. SAP keeps the books.

Everything between an invoice arriving and its posting runs in Orcha. What your auditors rely on stays in SAP.

Orcha takes over
  • Intake of supplier invoices and credit notes from inboxes, uploads and e-invoices
  • Capture of header data and line items
  • Matching against purchase orders and goods receipts
  • Coding: G/L account, cost centre, tax code
  • Approval routing by amount, cost centre and supplier
  • GoBD-compliant archive with a full audit trail
Stays in SAP
  • General ledger and accounts payable
  • Master data: vendors, G/L accounts, cost centres
  • Payment runs
  • The final posting

Still running an invoice cockpit in SAP? Move the work out of the core.

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.

BeforeA cockpit in the core

Templates and rules per supplier, workflows inside SAP, and every upgrade or S/4HANA migration has to carry the add-on along.

AfterAgents outside SAP

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.

SwitchingParallel run, then off

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.

How data flows between Orcha and SAP.

Orcha reads the master data it needs to code like your team, and hands over each invoice once it is approved.

01 · InEvery channel

Supplier invoices arrive by email, upload or portal, as PDF or as XRechnung and ZUGFeRD e-invoices.

02 · OrchaCapture, match, code, approve

Agents read each invoice, match it to the order, propose the coding and route it for approval.

03 · SAPReady to book

The approved invoice reaches SAP as an FI or MM invoice, with the original document attached.

ObjectDirectionInterface
Vendors (business partners)SAP to OrchaOData API_BUSINESS_PARTNER
G/L accounts, cost centresSAP to OrchaOData or file
Purchase orders, goods receiptsSAP or another system to OrchaOData, file or database
Coded supplier invoice or credit noteOrcha to SAPIDoc INVOIC02 or SOAP
Original document (PDF)Orcha to SAP or your archiveAgreed during setup
Posting and payment statusSAP to OrchaPlannedOData or IDoc status
Three ways to connectOrcha fits the integration architecture you already have.
DirectSAP standard interfaces

IDoc, SOAP or the OData APIs of S/4HANA, with a technical user and no add-on in the core.

SAP BTPSAP Integration Suite

If your company routes interfaces through SAP Integration Suite, Orcha connects there and your iFlows stay in charge.

MiddlewareMuleSoft and other platforms

Already run MuleSoft, Boomi or another integration platform? Orcha plugs into it like any other system.

What Orcha covers with SAP.

Built for how SAP works. And how you use it.

With or without purchase orders in SAP, on S/4HANA today or on the way there.

With a POLogistics invoice verification

Invoices are matched against the purchase order and goods receipt in SAP. Orcha flags quantity and price differences before the handover.

Without an SAP POFI vendor invoices

If your purchase orders live in another system, Orcha matches against them there and hands the invoice to SAP as an FI document.

ECC or S/4HANAReady for the migration

Orcha sits outside the SAP core, so nothing has to be migrated with it. Moving to S/4HANA only changes the connection.

Set up with your SAP team. Live after a parallel run.

  1. 01
    Kick-off with your SAP team

    Agree on the interface and the invoice types.

  2. 02
    Technical user

    With exactly the authorisations the handover needs.

  3. 03
    Master data and booking history

    So Orcha codes the way your team does.

  4. 04
    Test postings in your SAP test system

    Every invoice type once, end to end.

  5. 05
    Parallel run, then go-live

    Switch over once the results match.

Connected securely.

Standard interfaces only

No add-on and no custom development in the SAP core, directly or through your integration platform.

Least privilege

One technical user with access to the objects the handover needs.

EU data residency

Hosted in the EU, processing under a GDPR data processing agreement.

GoBD and audit trail

Every coding and approval recorded with its author and reasoning.

Orcha and SAP: questions.

Anything else? Talk to the team that builds the integration.

Book a demo
Which SAP editions does Orcha support?

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.

Does Orcha work with SAP Business One?

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.

Which interfaces does Orcha use to connect to SAP?

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.

Can Orcha connect through SAP Integration Suite or MuleSoft?

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.

Does Orcha post directly in SAP?

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.

Does Orcha handle credit notes?

Yes. Orcha captures, checks and codes supplier credit notes like invoices and hands them to SAP the same way, with the original document.

Does Orcha detect duplicate invoices and changed bank details?

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.

Do approvers need SAP access?

No. Approvals run in Orcha, in the browser, in Slack, in Microsoft Teams or by email.

Our purchase orders are not in SAP. Does that work?

Yes. Orcha matches invoices against purchase orders and goods receipts from your other system and hands them to SAP as FI vendor invoices.

We use an invoice cockpit inside SAP today. Can Orcha replace it?

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.