What does accounts receivable involve?
Accounts receivable involves two different kinds of work: the mechanical work of matching incoming payments to invoices and tracking what is overdue, and the relationship work of reminding customers, handling disputes, and deciding when to escalate. A Digital FTE suits the first and prepares the second.
Treating the two the same is the common mistake. Automating reminders without a gate damages relationships; failing to automate matching wastes hours that could go to the relationships.
What does the Digital FTE do in receivables?
The Digital FTE matches each incoming payment to its invoice or invoices with the evidence attached, flags partial payments and overpayments with the amounts and the likely reason, and keeps the ageing view current daily. When an invoice crosses a threshold you set, it drafts a reminder for approval.
It also flags disputes: a customer reply that questions an invoice is surfaced with the invoice, the original terms, and the correspondence, so the person handling it starts from the evidence rather than from the inbox.
- Payment matching with evidence, daily
- Ageing tracked and current, thresholds you set
- Reminders drafted for approval at each threshold
- Partial payments, overpayments, and disputes flagged with documents
What can earn autonomy in receivables?
Routine first reminders on small, undisputed invoices to customers outside a protected list are the usual candidate for autonomy, once the approval record shows a long run of unchanged drafts. Even then, the remit can restrict tone, timing, and which customers qualify.
Second and later reminders, anything to a key account, and anything with a dispute attached stay gated. Escalation to a collections process is never automated; it is a business decision with a relationship on the other side.
How does it handle disputes?
The Digital FTE handles disputes by preparing them, not resolving them. It pauses reminders on a disputed invoice automatically, gathers the invoice, the terms, the delivery or service evidence, and the customer's message, and puts the package in Approvals with a suggested next step.
The person who owns the relationship decides. A dispute resolved by a system is a customer lost; a dispute prepared by a system is a customer who gets a fast, informed answer from a person.
What does the finance lead see?
The finance lead sees a receivables view that is current every morning: what came in, what matched, what is overdue by band, which reminders are waiting for approval, and which disputes are open with their packages ready. The morning brief puts what is waiting on them first.
Over time, the diagnostic mission answers questions like why is days-sales-outstanding rising, with ranked hypotheses from your own invoice and payment data, such as a customer segment paying later or a billing change that confused customers, each with evidence attached.
What does a reminder proposal contain, and how is tone controlled?
A reminder proposal in Approvals contains the invoice, its age band, the customer's payment history from the ledger, the reminder text drafted to the tone rule for that band, and the reason it is proposed now: the threshold it crossed. Anything the FTE noticed that argues against sending, such as a partial payment in transit or an open dispute, is flagged on the proposal, and a disputed invoice's reminders are paused automatically rather than proposed.
Tone is controlled in the remit, not per email. The remit sets the register for first reminders, later reminders, and key accounts, names the customers on the protected list who never receive an automated reminder, and states the escalation point past which the FTE stops proposing and a person decides. The manager approves, edits, or sends back with a reason, and repeated edits to tone become a remit rule at the weekly review. Once first reminders on small undisputed invoices to unprotected customers show a long clean record, that class alone can be promoted; every later reminder and every key account stays gated.