Orcha captures, codes and routes your vendor bills, then creates them in NetSuite through SuiteTalk REST, with your subsidiaries, departments, classes and locations. We set up the connection with you during onboarding.
Everything before the vendor bill runs in Orcha. Your subsidiaries, ledgers and payments stay in NetSuite.
Orcha reads the master data it needs from NetSuite and creates each approved vendor bill there.
Supplier invoices arrive by email or upload, as PDF or as XRechnung and ZUGFeRD e-invoices.
Agents read each invoice, propose account and segments, and route it for approval.
The approved bill is created in NetSuite with its lines, segments and the PDF.
| Object | Direction | Interface |
|---|---|---|
| Vendors, accounts, subsidiaries | NetSuite to Orcha | SuiteQL |
| Departments, classes, locations | NetSuite to Orcha | SuiteQL |
| Vendor bill | Orcha to NetSuite | SuiteTalk REST |
| Original document (PDF) | Orcha to NetSuite | Script in your account |
NetSuite runs many international groups with several subsidiaries. Orcha's integration is built for that from the start.
Each bill is created in the right subsidiary, with that subsidiary's accounts.
Coding includes your NetSuite segments, not just the account.
A small script in your account lets Orcha attach the original invoice to the vendor bill.
We go through your NetSuite setup and invoice volume.
Your admin creates an integration record for Orcha.
So PDFs can be attached to vendor bills.
So Orcha codes the way your team does.
Every bill type once, end to end.
Orcha connects with an integration record and a role you control.
SuiteTalk REST and SuiteQL, 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 vendor bills in NetSuite and reads your master data. We set up the connection with you during onboarding.
Through SuiteTalk REST for vendor bills and SuiteQL to read master data, with token-based authentication.
Yes. A small script in your NetSuite account lets Orcha attach the PDF, because NetSuite's REST API cannot attach files on its own.
No. Approvals run in Orcha, in the browser, in Slack, in Microsoft Teams or by email.
Invoices ready to book, without an add-on in the SAP core.
Orcha × SAPApproved invoices posted and vendor master data kept current, every change approved in Orcha.
Orcha × Dynamics 365Approved bills and sales invoices straight into Xero.
Orcha × XeroCoded supplier invoices for Sage, set up per Sage product.
Orcha × Sage