AI automation that asks for review when it is unsure.

Agents that read invoices, emails and documents, act in your systems and ask you whenever a case calls for it.

Projects from €6,000Reply within one business day

Paper stops going through the keyboard.

Every invoice is read on arrival: supplier, amounts, VAT and GL account.

Every field, with its confidence.

What is certain is posted. What does not add up lands in your inbox.

Your team reviews. It no longer transcribes.

Projects from €6,000. Reply within one business day.

Let's talk about your automation

Reads the invoice the way your team would

Supplier, tax ID, amounts, VAT and GL account come straight from the PDF as it arrives, scanned or not. Every field carries its confidence level.

  • Different invoice layouts
  • Checked against orders and suppliers
  • No template per supplier
Extracted data 7/8
Supplier EmpresaD S.L.
Tax ID B-55667788 98%
Invoice no. RM-26-0744 98%
Date 14 Oct 2026 96%
Taxable base €1,800.00 97%
VAT 21% €396.00 Check
Total €2,196.00 97%
  • High confidence The value is used as is, with nobody re-checking it.
  • Does not add up VAT is not 21% of the base, so the invoice goes to review.

And asks when it is not sure

If a figure does not add up or the invoice is over the agreed amount, it stops and asks you, with what you need to decide.

Review request Check VAT

Post the invoice with this VAT?

The VAT charged is not 21% of the taxable base.

Supplier
EmpresaD S.L.
VAT charged
€396.00
VAT expected (21%)
€378.00

And keeps a record of every step

What came in, what was extracted, which rule applied and who approved it. You can check it whenever you want.

Activity RM-26-0744
10:41 Received by email Inbox
10:41 7 of 8 fields extracted Read
10:41 Rule: VAT ≠ 21% of the base Review
10:52 Approved by Laura M., with a note Approved
10:52 Posted to the ERP · entry 2026/0418 ERP

One invoice, from email to ERP

A supplier invoice arrives. The system reads the PDF, checks the data, asks for approval because it is over the threshold and posts it to the ERP.

  1. The invoice arrives by email and shows up in the inbox on its own.
  2. Supplier, tax ID, amounts, VAT and GL account are extracted, each with its confidence level.
  3. It is over €5,000, so the rule asks Laura from Finance to approve it.
  4. Once approved, it is posted to the ERP with its journal entry.

Something like this for your company?

Let's talk about your automation

What changes day to day

Today

  • Rule-based automation breaks on every exception
  • Tasks that need judgement still depend on people
  • Your team spends hours reading, copying and sorting information
  • Transcription errors are caught late and are costly to fix

Once it is running

  • Workflows that cope with real documents, even incomplete ones or in an unexpected format
  • Your team only reviews the doubtful cases, with the context already gathered
  • Every decision is logged and can be checked later
  • Fewer hours a week spent copying data from one place to another

What is included

Judgement where rules fall short

Classic automations stop at the first unexpected case. An AI agent reads the context and can handle common variations (a different format, a missing field, an ambiguous request) without anyone rewriting rules; what it is unsure about, it asks.

Understands plain language

A process can start with an email, a message or an attached PDF, with no forms to fill in. The agent works out what is being asked and carries it out in your systems.

Tasks with several steps

The agent looks things up, checks them and completes the task across several systems: find the order, validate the amount, register the invoice. Each step is recorded.

Knows when to ask

When a case is unusual or exceeds an amount or risk threshold, the agent stops and hands it to the right person, with all the context ready for a quick decision.

Learns from corrections

Every correction your team makes is recorded and used to refine instructions, examples and thresholds. With use, the share of cases that need a person tends to shrink.

Traceable and under control

Every decision is logged: what came in, what the agent decided and why. High-impact actions require human approval before they run.

Typical uses

  • Finance and admin

    Supplier invoice registration

    The agent reads PDF or scanned invoices, extracts supplier, amounts, VAT and line items, matches them against purchase orders and registers them in the ERP. Anything that does not match, or exceeds an amount, goes to approval.

  • Customer service

    Email triage and replies

    Every incoming email is classified by intent and urgency, linked to the right customer or order, and arrives with a draft reply ready to review and send.

  • Operations and legal

    Data extraction from documents

    The agent reads contracts, delivery notes, forms and reports, extracts the key data, validates it and files it in the right place. Nobody has to retype it.

  • Management

    Regular reports for management

    The agent gathers data from your systems, highlights the variations that matter and delivers a ready-to-read summary on the schedule you choose.

How we keep risk under control

The AI works within clear limits and a person reviews the sensitive steps. You save time and quality stays under your control.

  • Confidence threshold

    The agent only acts on its own when its confidence is above the agreed threshold. Below it, the case stops and waits for review.

  • Human review where it matters

    High amounts, new suppliers or inconsistent data are routed to the person responsible, with the information prepared to approve or correct.

  • A log of every decision

    A record of what came in, what was extracted, what was decided and who approved it. You can audit it at any time.

  • Data and GDPR

    We use providers with data processing agreements, EU hosting options and no training on your data. Only what is strictly needed is sent.

How we work

The timeline depends on scope and is set in writing in the proposal.

  1. Pick the right tasks

    We review your day-to-day operations and look for tasks that are repetitive but variable, which rules handle badly. We rank them by volume, impact and risk.

  2. Design the flow and its limits

    We define how the agent reads each input, what it may do in your systems, which thresholds trigger human review and what gets logged. All in writing before any code.

  3. Build and validate on real cases

    We build the agent and test it on real examples from your company, hard cases included. You see how it behaves and approve it before it goes into production.

  4. Roll out and monitor

    We deploy gradually and monitor quality, cost and escalated cases, tuning thresholds and instructions with the data from the first weeks.

From €6,000

Indicative price for a typical project, VAT not included. Fixed written quote after the first call.

What a typical project includes

  • Process analysis and use-case definition
  • Agent connected to your systems (ERP, email, CRM)
  • Confidence thresholds and an approval flow
  • Decision log and a monitoring dashboard
  • Production rollout, documentation and training

Usual stack: OpenAI, Anthropic Claude, Google Gemini, LangChain, Python, Node.js, TypeScript, PostgreSQL, Redis, Docker, AWS, REST APIs.

Frequently asked questions

How is AI automation different from traditional automation?

Traditional automation follows exact rules: if an input does not fit the expected pattern, it fails. An AI agent interprets context. It can work with real documents and messages, even when they come in different formats or with data missing, and passes to a person whatever it is unsure about.

What if the AI gets something wrong?

We design for that case. The agent works with a confidence threshold: if it is sure, it acts; if not, it stops and asks for review. High-impact actions require human approval, and every decision is logged so it can be reviewed or corrected.

What happens to our data? Is it GDPR-compliant?

We work with AI providers that offer data processing agreements (DPAs), EU processing options and a commitment not to train their models on your data. We send only the information each task needs and, where the case requires it, we can use models hosted on your own infrastructure.

Which tasks suit AI automation best?

High-volume, repetitive tasks that require interpreting something: invoices, emails, documents, customer queries, reports. If today they depend on a person reading and deciding, they are usually good candidates: the agent prepares the work and a person reviews what is unclear.

How long does it take to get running?

It depends on the scope and the systems involved; the timeline is set in the written proposal, with milestones. We start with a well-defined case, prove it works on your data and expand from there.

Do we need to change our ERP or tools?

No. The agent connects to what you already use (ERP, email, CRM, shared folders) through their APIs or, where there are none, through custom integrations.

Which task would you take off your team’s plate?

Tell us which process eats the most hours or causes the most errors. We will explain in writing how an AI agent would handle it, which controls it would have and what it would cost.

  • Fixed written quote
  • One person accountable
  • Milestone-based payments
What do you need?
Please choose what you need.
Please tell us your name.
Please enter a valid email address.
Two sentences are enough
Please add a short note about what you want to achieve.
Help us prepare the call

Optional. A little context makes the first call more useful.

Please accept the privacy policy to continue.

Received.

We'll write back within one business day with two time slots for the call.

Let's talk about your project