Orcha captures, codes and routes your supplier invoices, then creates them in weclapp as purchase invoices with ledger accounts, taxes, cost centres and the PDF. We set up the connection with you during onboarding.
Everything before the purchase invoice runs in Orcha. Your purchasing, journal and payments stay in weclapp.
Orcha reads the master data it needs from weclapp and creates each approved invoice there as a purchase invoice.
Supplier invoices arrive by email or upload, as PDF or as XRechnung and ZUGFeRD e-invoices.
Agents read each invoice, propose ledger account, tax and cost centre, and route it for approval.
The approved invoice is created in weclapp with its lines, cost centres and the PDF, ready for your team to complete.
| Object | Direction | Interface |
|---|---|---|
| Suppliers, ledger accounts, taxes | weclapp to Orcha | party, ledgerAccount, tax |
| Cost centres and cost types | weclapp to Orcha | costCenter, costType |
| Purchase invoice | Orcha to weclapp | purchaseInvoice |
| Original document (PDF) | Orcha to weclapp | document/upload |
weclapp runs sales, purchasing, warehouse and accounting in one cloud system. Orcha's integration is designed to fit into that, not around it.
Coding includes your weclapp cost centres and cost types per line, split across several cost centres where you need it.
Orcha creates the purchase invoice for your team to complete in weclapp, so the journal entry stays in your hands.
The original invoice is stored on the purchase invoice in weclapp, as PDF or as ZUGFeRD.
We go through your weclapp setup and invoice volume.
Created in weclapp for a user you choose; API access is part of ERP Services and ERP Trade.
So Orcha codes the way your team does.
Set up with you once for your structure.
Every invoice type once, end to end.
Orcha connects with the API token of a weclapp user you choose, and you can revoke it at any time.
The public weclapp REST 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.
Anything else? Talk to the team that builds the integration.
Book a demoYes. Orcha creates purchase invoices in weclapp and reads your master data. We set up the connection with you during onboarding.
Through the weclapp REST API, with an API token. weclapp includes API access in ERP Services and ERP Trade, not in ERP Starter.
No. Orcha creates each purchase invoice with its coding and the PDF. Your team completes it in weclapp, and the journal entry follows from there.
No. Approvals run in Orcha, in the browser, by email link or in Slack.
Coded vendor bills for Odoo, set up during onboarding.
Orcha × OdooCoded vendor bills for NetSuite, set up during onboarding.
Orcha × NetSuiteCoded A/P invoice drafts for SAP Business One, set up during onboarding.
Orcha × SAP Business OnePre-coded invoices straight into DATEV Unternehmen Online.
Orcha × DATEV