Hi Anna, invoice INV-25-018472 from Meiermetal is blocked in SAP.
Reason: price deviation +7.4% from the PO.
Can you confirm whether the deviation should be approved?
kontori reads every incoming invoice, matches it against purchase orders and goods receipts, gathers missing information across email, Teams and supplier portals, and turns it into a fully coded, documented booking in your ERP.
Most accounting work is gathering context: an approval here, a cost center there, a corrected invoice from the supplier. kontori asks for exactly what is missing, in the tool your team already uses, and completes the booking as soon as the answer arrives.
kontori captures invoices from mailboxes and portals, understands them, matches line items against orders and goods receipts, prepares coding and cost centers, and posts the finished booking to your ERP. Documented at every step.
From invoice capture to period-end close. These are the daily tasks kontori handles end-to-end.
kontori posts bookings automatically when confidence and policy allow. Below your threshold, the case lands with your team: full context, a drafted resolution, an audit trail. Your team reviews every draft at the start. With every correct case, you raise the threshold and kontori takes over more.
You set the Confidence Threshold. kontori handles everything above it. Anything below it lands on your desk, 80% prepared.
The ERP is the system of record. Email is the system of work. kontori connects the two.
Connect your systems, set policies, and kontori starts processing invoices immediately. Your team keeps full control, and every step lands in the audit trail.
kontori is hosted in Germany, isolated per tenant, and GDPR-compliant. Every action is logged and exportable for audits.
kontori automates the path from incoming invoice to finished booking. It captures invoices from mailboxes and portals, matches them against purchase orders and goods receipts, prepares coding and cost centers, gathers missing information from colleagues and suppliers, and posts the documented booking to your ERP.
kontori handles the blocked cases an ERP routinely pushes back to humans: three-way-match deviations, missing PO documents, supplier disputes, intercompany reconciliations, and cut-off issues at month-end. The agent reads context across email, Teams, Slack and PDFs, gathers the missing data, and writes the resolved case back to the ERP with a full audit trail.
kontori connects to enterprise ERP systems through standard APIs. Common platforms include SAP, Microsoft Dynamics and Oracle NetSuite. The agent reads blocked invoices and exceptions, gathers context from connected systems (Outlook, Teams, Slack, SharePoint, supplier portals, PDFs), and writes the resolved case back into the ERP as a posting or document update. If your ERP is not on the list, ask us. We build new connectors together with early customers.
Faster than you might expect: we can take a customer live within an hour. We connect the ERP, set your approval policies, and kontori starts working. Most customers begin with a single exception type, for example price deviations on AP invoices, and expand the scope as confidence grows.
When a case can't be resolved automatically, kontori messages the responsible person directly in the tool they already use, such as Microsoft Teams, Slack or email. The message includes the full case context and inline quick-actions like Approve or Forward. The clarification happens in seconds and the resolution is written straight back to the ERP.
The case is routed to the assigned person with full context, a suggested resolution, and a clear approval path. Nothing is posted to the ERP without a decision authorized by a person or by a rule you set. Every escalation step is logged so auditors can trace exactly how a case was resolved.
No. kontori takes over the legwork around a blocked case: gathering documents, following up with colleagues and suppliers, preparing the resolution. Every decision and every approval stays with your team. Accountants get time back for the work that actually needs their judgment.
kontori is built for audits. Every action, prompt and result is logged and traceable. The platform is hosted in Germany, tenant-isolated, and GDPR-compliant. A per-case audit trail provides GoBD-relevant evidence directly in your ERP.
All customer data is processed and stored in Germany on tenant-isolated infrastructure. Data sovereignty stays in the EU. Customers can revoke access and request full deletion at any time, with no lock-in.
kontori uses large language models to read cases, documents and messages. The models run in inference mode only and follow the same data rules as the rest of the platform: customer data stays inside the customer tenant and processing is GDPR-compliant.
No. Customer data is never used to train kontori's models or any third-party models. Prompts and outputs are stored inside the customer tenant for audit purposes only.
Pricing depends on your case volume and the number of connected systems. Most customers start with a pilot for a single exception type. Book a short call and we will put together a concrete quote for your setup.
Connect your ERP, your inbox, and your supplier portals. In 30 minutes we'll show you 3 live invoices going from inbox to posted booking, on your data and with your policies.