Solutions · Finance

Operational superintelligence for finance teams.

AI workers that post every invoice, reconcile every transaction and chase every overdue payment. They operate on your ERP and your banks, with the permissions you set, and your team approves anything that moves money.

See the platform

Cycle

The close starts with every invoice that comes in.

From the invoice received to the monthly report, every stage has an AI worker assigned and a person on your team who approves.

From invoice to close

  1. 01 · Accounts payable

    Invoice received

    Reads every invoice that reaches the supplier inbox.

    Payables

  2. 02 · Accounts payable

    Posting

    Proposes the account, cost centre and VAT and posts it to your ERP.

    Payables

  3. 03 · Accounts payable

    Approval

    Matches it to the purchase order and delivery note and routes it to the approver.

    Finance Ops

  4. 04 · Reconciliation and treasury

    Payment

    Prepares the week’s payment run for your approval.

    Treasury

  5. 05 · Collections

    Collection

    Chases overdue invoices in the tone and on the channel you set.

    Collections

  6. 06 · Reconciliation and treasury

    Reconciliation

    Matches every bank transaction to invoices and receipts.

    Reconciliation

  7. 07 · Close and reporting

    Close

    Prepares the close and the monthly report for review.

    Reporting

Org chart

An AI workforce with the departments of your finance function.

AI workers grouped by department, each with a role, its permissions and a person on your team who answers for it.

8

AI workers · 4 departments

Close and reporting

Chief of Staff

Prepare the finance director’s daily brief.

WhatsApp · Slack

Accounts payable

2

  • Payables

    Post every invoice the day it arrives.

  • Finance Ops

    Take every invoice through approval and payment.

Collections

2

  • Collections

    Collect every invoice on time.

  • Client Care

    Answer customers’ questions about their invoices.

Reconciliation and treasury

2

  • Reconciliation

    Reconcile every bank transaction.

  • Treasury

    Anticipate each week’s cash position.

Close and reporting

1

  • Reporting

    Prepare the close and the monthly report.

01 / 03 · Accounts payable

Every invoice in the inbox, posted the same day.

Every invoice that arrives is read, matched to its purchase order and posted to the right account and cost centre. Anything that does not match is held and queried.

  • PayablesAccounts payable
  • Finance OpsAccounts payable

Invoice FV-2026-1187

Haulier P-0318

received at 08:04

  • Haulier P-0318
  • September freight, 38 shipments
  • €2,000.00
  • €420.00
  • €2,420.00
  • 30 October
PayablesExtracted
Supplier
Haulier P-0318
Description
September freight, 38 shipments
Net amount
€2,000.00
VAT 21%
€420.00
Total
€2,420.00
Due date
30 October
  1. 01

    Invoice capture

    Supplier, net amount, VAT, withholdings and due date extracted from every PDF that reaches the inbox.

  2. 02

    Posting to your ERP

    Expense account, cost centre and VAT proposed from that supplier’s history.

  3. 03

    Purchase order and delivery note match

    If the amount or quantities do not match, the invoice is held and the supplier is asked.

  4. 04

    Payment runs

    The week’s payment run, prepared with due dates and balances, ready for finance to approve.

02 / 03 · Collections and reporting

Every overdue invoice, chased the next day.

Reminders before the due date, escalated notices after it and payment promises with follow-up. With what has been collected and what is outstanding, the monthly report is prepared for your team to review.

  • CollectionsCollections
  • ReportingClose and reporting
Collections · today
  1. 08:00

    Collections

    Reminder to 14 customers with invoices due this week

    Done
  2. 08:05

    Collections

    Second reminder to customer C-1042: €18,634.00, 7 days overdue

    Done
  3. 10:20

    Collections

    Customer C-2210 promises to pay on Friday: date logged

    Done
  4. 11:00

    Collections

    Customer C-0877, 30 days overdue: call proposed, awaiting approval

    Approval
  5. 17:30

    Reporting

    Receivables ageing updated: €64,210 overdue, 12% less than in August

    Done
  6. 18:00

    Reporting

    Weekly cash report sent to management

    Handoff
  1. 01

    Payment reminders

    Escalated by days overdue, by email, WhatsApp or phone call, in the tone you set for each customer.

  2. 02

    Payment promises

    Logs the promised date and writes again if the payment does not arrive.

  3. 03

    Month-end close

    Close checklist, accruals and provisions prepared for review.

  4. 04

    Reporting

    Cash position, receivables ageing and the month’s P&L for management on the first working day.

03 / 03 · Reconciliation

Reconciling is explaining the lines that do not match.

Every morning, transactions from all your banks are matched to invoices, payment runs and receipts. Almost all of them match, and each difference arrives with its reason and a proposed entry.

  • ReconciliationReconciliation and treasury
  • TreasuryReconciliation and treasury

212 / 219

reconciled

€486,320.55

Amount reconciled

ERP · invoices, payment runs and receipts

  1. FV-2026-1071€3,120.00
  2. FV-2026-1084€4,235.50
  3. FV-2026-1090€2,904.50
  4. FV-2026-1102€2,220.00
Sum€12,480.00

Bank · September statement

Transfer · Customer C-2210

€12,480.00

It matches: four invoices, one transfer

Exceptions

  1. Bank fee

    €38.40

    International transfer: entry proposed to account 626.

  2. Grouped payment

    €12,480.00

    Customer C-2210 pays four invoices in a single transfer: split and matched.

  3. Partial payment

    €1,815.00

    Half of invoice FV-2026-1110 received: the rest stays open and collections is notified.

  4. No reference

    €290.00

    Transfer without a description: the customer has been asked by email.

  1. 01

    Daily matching

    Bank transactions matched every morning to invoices, payment runs and receipts.

  2. 02

    Differences explained

    Bank fees, grouped payments and partial payments: each difference with its reason and a proposed entry.

  3. 03

    Payment gateways and card terminals

    Each settlement broken down into sales, fees and refunds, and matched to its orders.

  4. 04

    Several banks and entities

    Every account of every entity in the same matching run, under the same rules.

Exception

A €484 mismatch, explained the same day.

Late on the last day of the month, a payment comes in that does not match. Three AI workers find the cause, confirm it with the customer and propose the entry, and the controller approves it.

Trigger

17:20

A payment does not match at month end

  • Message
  • Action
  • Approval
  • Handoff

  1. 17:20Reconciliation· Message

    30 September. Customer C-1042 transfers €18,150.00 against an invoice for €18,634.00. €484.00 is missing.

  2. 17:22Reconciliation· Action

    €484.00 is €400.00 plus VAT. There is a credit note for that amount, issued in August, that was never applied.

  3. 17:25Collections· Message

    Writes to the customer to confirm they deducted credit note A-2026-031. At 17:48 they reply yes.

  4. 17:50Reconciliation· Action

    Proposes the entry: apply the credit note and close the invoice.

  5. 18:05Núria · Controller· Approval

    The controller checks the entry against the source document and approves it.

    Approved by Núria

  6. 18:10Reporting· Action

    The customer’s account is back to zero and the close stays on schedule.

  7. 18:30Reporting· Handoff

    The close note explains the difference, with links to the credit note and the customer’s email.

Reach

The close depends on what is left to explain.

What changes when every invoice, every transaction and every overdue payment has someone following it.

97%

of transactions reconciled without intervention

The rest arrive with their reason and a proposed entry.

  • 4 min

    from inbox to posted invoice

    With account, cost centre, VAT and due date proposed.

  • 2.5×

    faster month-end close

    Reconciliation is done before the 30th.

  • 34%

    less overdue balance

    Every overdue invoice is chased the next day.

Enterprise

Every action, in view. Every decision, with a reason.

Every step an AI worker takes is logged. Your team sees what they do, why they do it and with which permissions, and can change it at any time.

01

Visible

Every message, call and change goes into a log with author, time and outcome.

02

Explainable

Every decision carries its reason: which data the worker read and which rule it applied.

03

Isolated data

Data in the EU, isolated per client and encrypted. Access with two-step verification.

Security
04

Governable

You decide, channel by channel, what each worker does on its own, what needs approval and what it never touches.

Governance

Questions

What finance teams ask before they start.

If your question is not here, we will answer it in the demo.

Which ERP do they work with?
The one you already use. They operate through direct connections or the browser, with the permissions you set, and post to your ERP the way your team would.
Can they move money?
Only with your approval. They prepare payment runs, entries and credit notes, a person on your team approves them, and you set limits by amount and by type of transaction.
Who is accountable for an entry?
Your team. Every proposed entry carries the source document, the reason and the time, and the log records who approved it.
What about auditors?
Every action is logged with an author, a timestamp and a reason, and linked to its source document. The audit trail exists from day one.

Other sectors

One system, shaped to each sector.

The processes change from one sector to the next. The operating system underneath stays the same.