Orcha connects to Microsoft Teams through a bot and posts the events that need action to the channel you choose: approval requests and decisions, failed DATEV exports, documents Orcha could not read, contract deadlines and more. We set up the connection with you during onboarding.
Your team sees what needs action in the channel it already reads. Capture, checks and decisions stay in Orcha.
A conceptual view of the cards Orcha posts to a Teams channel. Your team notices what needs action and opens it in Orcha.
Illustration, not a screenshot: names, amounts and the layout are examples. Approvals are decided in Orcha, in Slack or by email. Microsoft Teams is a trademark of its owner; Orcha is not affiliated with Microsoft.
Orcha posts to the channel you pick for each entity.
An approval is requested or decided, a DATEV export fails, a document cannot be read, a contract deadline comes up or a bank allocation fails.
Orcha's bot posts an adaptive card with the key facts to the channel you chose.
Your team opens the item in Orcha and resolves it there.
| Object | Direction | Interface |
|---|---|---|
| Approval requested, approved, rejected | Orcha to Teams | Adaptive card in the channel |
| DATEV export failed | Orcha to Teams | Adaptive card in the channel |
| Ingestion failed, document unreadable | Orcha to Teams | Adaptive card in the channel |
| Contract deadlines | Orcha to Teams | Adaptive card in the channel |
| Bank allocation failed | Orcha to Teams | Adaptive card in the channel |
The connection uses Microsoft's bot framework, so your Microsoft 365 admin stays in control of what is installed.
Each alert is an adaptive card with the key facts, not a wall of text.
Pick the Teams channel for each entity, so every team sees only its own alerts.
A Microsoft 365 admin gives consent once and installs the bot.
Orcha switches on Teams notifications for your organisation.
A Microsoft 365 admin gives consent for the Orcha app once and installs it in Teams.
Pick the channel per entity and the events you want in Orcha's notification settings.
Trigger one alert of each kind and check it in the channel.
Alerts arrive in Teams from then on.
Your Microsoft 365 admin decides what Orcha's bot can do in your tenant.
A standard Teams app and bot, no changes to your tenant beyond the installed app.
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 posts adaptive cards to your Teams channels for events such as approval requests and decisions, failed DATEV exports, documents that could not be read, contract deadlines and failed bank allocations. We set up the connection with you during onboarding.
Not inside Teams today. Teams shows the approval events, and approvers decide in Orcha, in Slack or by email.
Not today. Invoices come in by email, upload or API.
A Microsoft 365 admin gives consent once and installs the bot. We guide you through it during onboarding.
Approve supplier invoices in a Slack message, set up during onboarding.
Orcha × SlackPre-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