Does this work with our accounting system?

The pattern needs an authorized way to read invoices and payments from your system of record and to write back what the role maintains. The audit confirms whether your setup exposes that, and which fields are in scope.

Is this the same as automating AR follow-up?

Follow-up is one workflow, with its own page. This role holds follow-up, payment tracking and reporting under one gate structure, so the readiness question applies to all three at once. The readiness checklist is where to start.

The AR clerk as an AI Employee

Receivables is one role on paper and three interruptions in practice

Today

Follow-up runs on whoever remembers

Follow-up runs on whoever remembers, so the invoices that go quiet are the ones nobody had on their list that week.
Payments land in the bank without the invoice being marked, and the person who could match them is doing something else.
The receivables report gets rebuilt from a spreadsheet the night before someone needs it.
On paper those are one role; in practice they are three interruptions spread across people who were hired for other work.

With agents

The ledger is the trigger and one gate holds the seam

Follow-up stops depending on who remembers.
The report is a view rather than a project.
Your time goes to the accounts that need a person.

How an agent runs it

The receivables job is three cadences that rarely stay with one person for long, and the seam between them is where invoices go quiet. This role holds the seam, with one gate on anything that leaves the business.

01

Monitors

Watches open invoices against the terms on each one, so the work starts from the ledger rather than from a reminder.

02

Drafts

Prepares follow-up from your templates and your tone rules, with the invoice and the history attached. Follow-up as a workflow has its own page; here it is one duty of the role.

03

Tracks

Matches incoming payments to open invoices and records the ones it cannot match, rather than guessing.

04

Reconciles

Compares the receivables view to the system of record on the cadence you set, and lists the differences.

05

Human gate

Routes any message beyond the first reminder tier, any change to an account's standing, and any write-off or dispute to the finance owner for a decision, because those are the actions that leave the business or change what a customer owes.

06

Assembles

Builds the receivables report in your existing format, with the exceptions it held listed at the top.

07

Flags

Names the accounts whose pattern changed, with what changed shown, so the person deciding sees the reason rather than the alert.

Results

What changes when the ledger does the reminding

Chased because it is due

The ledger is the trigger and the cadence is written down, so an invoice gets chased because it is due rather than because someone noticed.

A view, not a project

Assembly runs on the cadence from records the role already maintains, so nobody rebuilds it the night before.

Your time on the accounts that need you

The gate routes exactly those, with the reason attached, and the rest keeps moving inside the rules you set.

Where this fits

AI Employee

Tier 2 through the AI Employee door: a full role of known-process work handed to one governed agent, rather than a single task. The proof step is one workflow on its own, such as AR follow-up; this role is the scale step, holding follow-up, payment tracking and reporting under one gate. Its boundary is receivables: it does not take on payables, the close, or credit decisions. From here the pattern can extend toward an agent-run finance back office, as a direction it could take rather than a state it promises. How It Works describes how the gates and authorizations are built.

Tier 2 / Scale

How It Works

Questions, answered

The first reminder tier can run inside the rules you write. Everything past it, and any change to an account's standing, is gated by default and opens only on your decision. The ledger and the templates are yours and stay in your systems, so the work can be run by hand at any point without the agent.