Data in. Actions out.

Claridy connects to your ERP, your bank and your mailbox. It turns data into clean tables and runs workflows that act on them. Nothing syncs back until it's verified. Here's the whole machine.

Everything else we read
GmailGmail
OutlookOutlook
Google SheetsGoogle Sheets
ExcelExcel
SalesforceSalesforce
NmbrsNmbrs
ABN AMROBank · CAMT
PSP filesPSP files
Claridy workflow engineIdle
Structured tables
Invoices176
8 awaiting review
Transactions2410
96% reconciled
POs148
line level
Customers312
limits tracked
Workflows on top
Match every invoice to its PO at
Reading your description142 runs today
Deterministic code, written by AI from your plain-language description.
Read · write back
The ERP you run onUntouched
NetSuite
Microsoft Dynamics
Exact
Untouched. No migration, no configuration changes. Every booking lands back here.

Your sources are connected. Here is what happens next.

01

Your data, structured

Invoices, transactions, POs, receipts and customers from every source become clean, structured tables — one model, deduplicated, currency- and entity-aware.

Differences between source systems get resolved here, not passed downstream. No workflow ever reads a mailbox or a PDF directly; it reads verified tables.

SourcesStructured
Mail · PDFfactuur_heeren_apr.pdf
Bank · CAMTSEPA-0912 · EUR -24580
Sheet · rowPO-2026-114 · 3 lines
One verified row
Heeren Bouwgroep BVEUR 245803 sources
Deduplicated · currency- and entity-aware · source refs kept
02

The workflow, written

You describe the job in plain language — with your tolerances, your exceptions, your names.

Claridy's AI writes the deterministic code that runs it. The code is inspectable, and it does exactly what you said — nothing more.

Your description
Generated workflowGenerating
match invoice.lines to po.lines
  tolerance 2%
if diff > 2% → assign "Sanne" with diff
else → book and log
Inspectable · nothing more than you saidDeterministic
03

The output, tested

Before a workflow runs on its own, you run it supervised — every action proposed, you approve. You see where it agrees with your team and where it does not, with the reason attached.

You set the confidence threshold, and then you let go. No leap of faith on your own data.

Supervised · 2026-05-0496% agreement
Workflow proposed
4310 · CC-204 · EUR 24580
Your team booked
4310 · CC-204 · EUR 24580
142 of 149 actions agreedApproved
7 disagreements · with reasonsYour call
Threshold90%
04

It runs, reliably

Live means boring, on purpose. The same input produces the same output every run — no model drift, because there is no model in the execution path.

Every action lands with a confidence score and a log line: what it read, what it decided, what it did. Above the threshold it executes; below, it escalates with the difference already worked out.

Run log · liveRunning
11:42INV-2026-0428 matched · booked 431098%
11:43BNK-0912 reconciled · EUR 2458097%
11:44Reply sent to Heeren Bouwgroep96%
11:44INV-2026-0434 · no PO → your team61%
No model in the execution path · same input, same output

Control over your workflows

Per workflow, per entity. Start with approvals on everything and loosen it when the numbers earn your trust.

Confidence scores

The workflow knows when it doesn't know. A low score means a human decides, not a guess that gets booked.

Threshold 90% · below → your team

Approvals where you want them

Fully automatic, approve per action, or approve per batch. Your dial, set per workflow.

Coding · auto · Payments · per batch

Audit trail per step

What it read, what it decided, what it did — with the source document attached. Auditor-ready.

Exportable · per invoice · per run
GDPR compliant·EU data residency·Your data stays in your systems·Read-only where possible·No model drift: deterministic executionMore on security ↗

Connect everything, use everything

One connection per system, built by us and authorized by you. The ERP is the anchor; everything else feeds it.

ERP · the anchor
NetSuite
Microsoft Dynamics
Exact
Read · write back
Mail · documents · sheets
Gmail
Outlook
Google Sheets
Excel
Read-only
CRM · banks · PSP files
Salesforce
Stripe
ABN AMRO · CAMT
File-based where the provider requires it
Browse all integrations ↗

Live in weeks

Week 1

Connect and configure

Your ERP, mailbox and bank connected, read-only first. Your tables mapped to the Claridy model.

Week 2

First workflow live

Running on real data with approvals on everything, so you watch it work before you loosen the dial.

Day 30

Measured

Match rate, time saved and exception count. Expand when it has proven itself, not before.

See it on your own data

Thirty minutes, your ERP, one workflow. You will see the log before you see a contract.