Workflow and actors
When an email, PDF, Excel file or EDI message arrives, the workflow extracts header and lines, resolves references, checks catalog, price and stock, and prepares the quote or order; operations receives only the exception queue.
RFQ and order extraction into the ERP, three-way match on delivery notes and invoices, stock monitoring, quote generation and anomaly detection, unattended and wired into your system.
The workflows, examples and figures on this page are illustrative composites and modelled targets, not measured client results. In a real project, we define the baseline, thresholds and human review with your data before rollout.
One customer sends the order by email with an Excel attached, another a scanned PDF from their internal system, a third copy-pastes from a catalogue version that’s two updates old. Someone opens it, finds the reference, checks stock in SAP Business One or Holded, computes the price, enters the line and repeats, for every customer, every day. Meanwhile, delivery notes and invoices pile up waiting for a three-way match.
We design automations that run the moment the document arrives: they read the RFQ or order in any format, map to the catalogue, check stock and price in the ERP, create the quote or order in SAP Business One, Holded, Odoo or Microsoft Dynamics 365 and route edge cases to a review queue. The three-way match and stock monitoring run in parallel, without touching anything that already works.
When an email, PDF, Excel file or EDI message arrives, the workflow extracts header and lines, resolves references, checks catalog, price and stock, and prepares the quote or order; operations receives only the exception queue.
It uses intake documents, customer and SKU masters, commercial terms, inventory and ERP purchase order, delivery note and invoice records, with shared identifiers for reconciliation and traceability.
Low-confidence OCR, unknown SKUs, unusual price or quantity, insufficient stock and unmatched documents stop before any write or payment. Idempotency keys catch duplicate submissions.
Sales approves quotes and out-of-rule terms; operations validates uncertain orders, procurement reviews replenishment and finance resolves discrepancies before authorising payment.
We separate AI-assisted extraction from deterministic validation and idempotent writes. Each step retains its source document, confidence, applied rules and state so it can resume without duplicating orders.
We connect the mailbox or EDI feed to available SAP Business One, Holded, Odoo, Dynamics or other ERP APIs or connectors, starting with reads and drafts before agreed writes are enabled.
Reads orders in email, Excel, PDF or EDI, maps references against the catalogue, validates stock and price in SAP Business One, Holded, Odoo or Microsoft Dynamics 365 and creates the quote or order, non-standard cases route to sales with full context.
Cross-references purchase order, delivery note and supplier invoice, detects discrepancies in quantities, prices and contractual discounts and opens the issue for procurement, only matched documents progress to payment.
Watches stock levels, consumption by customer and rotation by SKU, detects early signals of stockout, proposes replenishment orders and alerts the owner when a pattern breaks the historical baseline.
Turns a sales request into a complete quote with references, volume discounts and customer terms, drops the document into the ERP and sends the draft to sales to review before sending out.
Compares each order against the customer’s historical pattern, detects out-of-range quantities, inconsistent prices or discontinued references and warns before confirming in the ERP.
Baseline assumption: Four people dedicated to keying orders into SAP Business One from email, Excel and heterogeneous PDFs. Average time per order: 9 minutes. Quotes that take half a day. Manual three-way match by accounting with month-end close on day 11. Stockouts spotted late, with commercial cost.
Modelled operating target: 91% of orders land in the ERP in under 2 minutes without intervention. Standard quotes ready in 4 minutes. Unattended three-way match with close on day 4, the team only reviews discrepancies. Stockouts anticipated with 5-10 days of margin. The back office moves to exception handling and new-customer onboarding.
Enterprise CRM with fine-grained permissions, AI workflows that respect the data model.
Enterprise CRM/ERP suite in the Microsoft ecosystem, native fit with 365 and Power Platform.
Reference ERP for mid-market distribution and manufacturing, document extraction and ops orchestration.
Spanish cloud ERP widely adopted by SMBs, invoicing, expenses and reconciliation automation.
Modular open-source ERP, AI agents and workflows on top of sales, inventory and project modules.
Email, calendar and SharePoint as channel and context, triage, drafting and RAG over your inbox and files.
Yes. We connect via API or intermediate connector with SAP Business One, Holded, Odoo, Microsoft Dynamics 365 Business Central and the main ERPs in the Spanish market. If your instance is heavily customised, we map against the real fields in your model rather than the standard ones, we don’t force you to change your business logic.
You do. The automation applies the rules and price lists that live in your ERP or in a table maintained by the sales team. When the order matches the rules, it goes through automatically. When it falls outside the framework (new customer, exceptional discount, non-standard term), it goes to sales review with the rationale. It never invents a price.
The automation measures confidence on every extracted field. Below a configurable threshold, the entire order goes to human review with the original document, detected fields and the issue. Nothing is confirmed in the ERP with dubious data. For recurring customers we also validate against historical patterns to catch unusual differences.
The first useful workflow, usually order extraction into the ERP or the three-way match, is in production in 5-8 weeks, on your real documents and existing integrations, with before/after metrics measured. From there we scale the rest of the catalogue based on proven return.
We design for privacy from the start, human control, traceability, usage limits, permissioning and documentation. For sensitive processes, we help assess risk and applicable obligations under GDPR and the EU AI Act.
Every engagement is led personally by one of the partners. If there's a fit, you get a personal first read of your case within one business day, not a canned demo.