Invoice reconciliation that finishes overnight

Reconciliation is not difficult work. It is patient work, it is never finished, and it is the first thing to slip when the month gets busy. Dutta does the matching every night and brings you only the lines that need a person.

The work today

It is four windows and a squint. The invoice, the purchase order, the payment and the contract behind it all live in different places, and confirming they agree means opening all four and comparing them line by line.

The clean matches take the longest. Most lines reconcile without incident, and confirming that is where the hours go. The handful that do not are the ones that matter, and they surface last.

It happens in a batch, so problems age. Nobody can reconcile continuously, so it is done weekly or at the close. A duplicate payment or a rate that does not match the contract sits undiscovered until then.

The reasoning is not written down. Why a line was accepted lives in the head of whoever accepted it. Three months later, at audit, that answer has to be reconstructed.

What Dutta does, in order

OvernightReads the day’s new invoices and payments from your ledger and matches each against its purchase order.
On a clean matchRecords it with the documents it compared attached, so the evidence exists before anyone asks for it.
On a partial matchStops rather than guessing, and holds the line as an exception with the source documents behind it.
07:00Sends the digest: what reconciled cleanly, what did not, and what needs a decision from you.

What it reads and writes

An AI employee holds scoped credentials — read, write or send, per system — and nothing beyond its mandate. Permission is granted per system, and revoking it takes effect immediately. For this job that normally means:

  • Ledger — read, to compare invoices, purchase orders and payments
  • Documents — read, for the contract and any amended terms behind a line
  • Email — draft only, until you grant send

Where a person stays in the loop

Dutta prepares, drafts and flags; a person approves anything with a consequence. You name the checkpoints, and for this job they usually are:

  • Every exception it raises — nothing is accepted or written off on its own
  • Any journal entry, credit note or write-off
  • Anything that reaches a supplier or a customer

Questions

Does it pay anything?

No. It reads your ledger, matches, flags and drafts. Payment and posting stay with a person, and you name the actions that must wait for approval before they happen.

What happens when two records nearly match?

It stops and asks, with both records attached. An employee that guesses is worse than no employee at all in finance, so it is built to escalate rather than resolve.

Can we see why a line was accepted?

Every action is logged with its inputs, sources, reasoning trail and output, and any run can be replayed. Audit logs export to your SIEM.

The role behind this job

This work is what the Finance employee does on shift. Everything else it handles, and the whole shift it works, is on the role page: an AI employee for finance operations.

Put it on shift

Pricing is per AI employee on shift; humans are unlimited on every plan. See pricing or tell us the process that eats your team’s week.

Other jobs Dutta takes