Most of your team never opens a finance tool. With Orcha connected to Slack, approvers get each supplier invoice as a direct message with the PDF, the coding and the warnings Orcha found, and decide with one click. Orcha records who decided, when and on which version. We set up the connection with you during onboarding.
Approvers decide where they already are. Capture, checks, coding and routing run in Orcha.
A conceptual view of the approval message: everything an approver needs, the PDF in the thread and a confirmation before the decision counts.
Illustration, not a screenshot: names, amounts and the layout are examples. Slack is a trademark of its owner; Orcha is not affiliated with Slack.
Orcha asks the approver in Slack and takes the decision back.
When it is an approver's turn, Orcha sends a direct message with supplier, amount, dates, up to eight line items with coding, the warnings and the PDF.
The approver approves or rejects, with a confirmation step. Reminders arrive on weekdays in the same conversation.
Orcha records who decided, when and on which version of the invoice. If the invoice changes afterwards, a new approval is requested.
| Object | Direction | Interface |
|---|---|---|
| Approval request | Orcha to Slack | Direct message with buttons |
| Decision | Slack to Orcha | Approve or reject, with confirmation |
| Invoice summary and PDF | Orcha to Slack | In the message and its thread |
| Reminders | Orcha to Slack | Weekdays, same conversation |
| User link | Orcha and Slack | Work email, with confirmed manual links |
The people who approve invoices are rarely in the finance tool. The Slack message is built so they can decide without opening it.
Both buttons are in the message, with a confirmation step before the decision counts.
Supplier, amount, dates, service period, order and goods-receipt references, up to eight lines with account, cost dimensions and tax rate, and the warnings Orcha raised.
If the saved amounts do not add up, Approve is refused until they are confirmed in Orcha. Reject always works.
We send a one-time install link, valid for seven days, to someone who can add apps to your Slack workspace.
Orcha links Slack members to Orcha users when their work email matches. For anyone else we propose a link, and the person confirms it in Slack.
Per entity, approvers get requests in Slack, by email or both.
One request per invoice type, end to end.
Approvals run in Slack from then on.
Each Slack member is linked to their Orcha user; people who are not linked keep receiving email.
Installed in your workspace, one workspace per Orcha organisation.
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 demoEvery approver needs an Orcha user, because Slack members are linked to Orcha users by work email. After that they decide in Slack; anyone who is not linked keeps getting requests by email.
Yes. Orcha records who approved or rejected, when, through Slack, and which version of the invoice they saw. If the invoice changes after the request went out, a new approval is requested.
One Slack workspace per Orcha organisation.
Not today. Slack is used for approval requests, reminders and link confirmations. Other notifications go by email and Microsoft Teams, and invoices come in by email, upload or API.
Anyone allowed to add apps to your Slack workspace. We send them a one-time install link during onboarding.
Finance alerts in your Teams channels, set up during onboarding.
Orcha × Microsoft TeamsPre-coded invoices straight into DATEV Unternehmen Online.
Orcha × DATEVInvoices 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 365