Agenthub

Solutions / Finance & accounting

The match is the easy part. The exceptions are the job.

A price variance on line four. A supplier who changed their IBAN by email. Agenthub puts agents on the exception queue — coding, matching, chasing, reconciling — and stops them at the payment, the dunning letter and the new vendor.

Exception queue

Exceptions get worked, not just flagged.

Anything can flag a variance. An agent pulls the PO and the goods receipt, and proposes the fix with the evidence attached.

DSO

Cash lands sooner, without chasing the wrong people.

Invoices reach each customer's portal in the format that portal wants. Reminders go out only after the agent has checked for an unapplied payment.

Days to close

The close stops being a sprint.

Reconciliations run through the month instead of in one week. Accruals, tie-outs and the first draft of the variance commentary are waiting for you.

Three days before close.

This is the board when agents hold the ledger work — and where they stop.

The work we take on.

Not a category. The specific jobs that fill a finance team's week — where the judgment shows up in the exceptions.

  1. Invoice intake, coding and the three-way match

    Invoices arrive three ways at once: PDFs, structured XML, a supplier portal. The agent codes them the way your team codes, matches to PO and goods receipt, and brings each variance back.

    Data connectors · AI-powered indexing

  2. Payment runs that stop at the money

    The agent builds the run from what is approved and due, and flags every supplier whose bank details changed. Then it waits. Releasing money is a human decision — one tap in Slack.

    Approval gates · “Who did this?”

  3. Vendor onboarding and screening

    New supplier: validate the VAT number, screen against the EU consolidated list, confirm the bank account belongs to the company on the invoice. A fuzzy match goes to a person.

    Company-wide guardrails · Audit log

  4. Collections that read the account first

    Before a reminder goes anywhere, the agent checks whether the money is already in the bank behind an unreadable remittance. And no email reaches a customer without a human yes.

    AI supervisors · Slack-native

  5. Customer AP portals, worked like a person works them

    Your largest customers pay through portals — Coupa here, Ariba there, each with its own silent rejection queue. Agents operate them in a real browser, and catch the rejection the day it happens.

    Browser agents · Operations board

  6. Reconciliations and the chase before close

    Bank and balance-sheet reconciliations run through the month, not in one week. The agent also chases the three people who still owe you numbers.

    Success tracking · Version history

What matters in finance work.

Four constraints run this department. Each has a mechanism behind it, not a promise.

Two sets of eyes on anything irreversible

A wrong journal entry is fixable. A wrong payment is a phone call to a bank. Money leaving, messages to customers and vendor-master changes sit behind approval gates.

It has to hold up in the audit

“Show me the support” is the question this work is built around. Every agent action and every human change is in the audit log — what was decided and on whose authority.

The invoicing rules keep moving

Belgium is live, France lands this September, and plenty of your suppliers still send a PDF. When an agent's intake rules change, simulate it against last month's real invoices.

Ledger data doesn't leave Europe

Customer data is hosted in the EU, and open models run on our own EU infrastructure, so inference can stay in Europe too. Subprocessors are on the security page.

“Nothing leaves the building without a name on it.” That's not bureaucracy. That's the control.

First agent in a month.

  1. Day 1We sit down with you

    We map how invoices actually reach you, then pick the highest-volume, lowest-risk job: coding and matching supplier invoices. Nothing in it moves money.

  2. Day 7Platform installed

    Connected to your ERP — SAP, NetSuite, Fortnox, whatever you run — plus the bank feed. Where there's no API, agents use a browser.

  3. Day 14First agents at work

    Agents code and match on real invoices. Payment release, any external email and any change to bank details wait for a named human in Slack.

  4. Day 30Live in production

    A month of verified success rates. Scope widens to collections drafts — and the approval list gets shorter only where the record earned it.

Bring last month's exception queue. We'll work it.

Thirty minutes, your invoices, your ERP. Watch the exceptions get cleared — and watch the agent stop before the payment.