Receivables Assistant for confirmed unpaid invoices only
Reminders are prepared only for invoices confirmed unpaid, with exact amounts; paid or disputed items are blocked, and nothing is sent until a person approves it.
The problem it answers
Reminders go out late, twice, or to customers who already paid, and iSystematic's Receivables Assistant prepares them only for invoices confirmed unpaid.
What it does
It prepares reminders for confirmed unpaid invoices only, with the exact amounts from your ledger; disputed or paid items are blocked.
Each amount is checked against the ledger before a reminder is drafted. Its access to accounting is read-only, and sending is a separate operation that a person approves.
It never moves money or changes an invoice. A conflicting status blocks the reminder, and a repeated run does not repeat a send.
A duplicate or wrong reminder is treated as an incident: the queue pauses while the cause is found.
Built from
It is built from one catalogue workflow and three catalogue patterns.
| Id | Name | What it brings |
|---|---|---|
| W16 | Invoice Reminder Preparation | Verifies due date and status, drafts a polite reminder, and waits for the owner's approval |
| P04 | Approval Before Commitment | Sending, disputes, credits and refunds wait for approval |
| P07 | Deduplicate Before Acting | The invoice identifier is checked, so a reminder is never sent twice |
| P11 | Keep a Workflow Receipt | Each reminder records its inputs, approval and result |
What it is built on
Four parts of the framework corpus decide which reminders may exist, and each leaves a record the client keeps.
| Framework | In this solution | Client keeps |
|---|---|---|
| Boundary Invariant | Reminders only for invoices confirmed unpaid, with exact amounts; disputed or paid items blocked | BOE Declaration per reminder rule |
| PEVG | The verifier checks each amount against the ledger before a reminder is drafted | Reminder queue with verification |
| Capability Contract (AP-5) | Read-only access to accounting; sending is a separate operation that needs approval | Capability contracts |
| AI Incident Response Protocol (AIRP)™ | A duplicate or wrong reminder is a signal; containment pauses the queue | Incident record; derived test |
Five parts apply to every build and are not repeated here: decision rights, the five gate records, a BOE Declaration per control, a vendor assessment for every vendor, and incident response. How we build sets out all of them.
The evidence it leaves behind
Every reminder run leaves records the client keeps.
- A reminder queue with approvals
- A BOE Declaration for each reminder rule
- The ledger check behind each reminder
- Capability contracts
- Incident records and the tests derived from them
- The five gate records, as for every build
Typical buyer
The typical buyer is a finance team.
Status
Proposed, as of 9 October 2026. A solution becomes Piloting or Released only after a documented pilot, and no result is shown for it before then.
How to start
Most organisations start with the Automation Assessment. When reminders are already the clear first task, a six-week Pilot runs them for one team, with the baseline measured first.
Where to go next
Operations leaders
For COOs: iSystematic's two-week Automation Assessment scores ten candidate tasks, recommends three solutions and sets a baseline before anything is built.
Read more →Intake to Onboarding
Intake to Onboarding extracts each new request, lists what is missing, prepares the onboarding pack and opens tasks only after a person approves them.
Read more →Meeting-to-Action Operations
Meeting-to-Action Operations turns consented recordings or notes into decisions, owners and dates, and creates tasks only after a person approves them.
Read more →Board and Committee Pack Preparation
Board and Committee Pack Preparation collects approved inputs, checks them against the agenda and drafts a cover summary with a source map for every paper.
Read more →How we build
How iSystematic builds: every solution uses the same deposited frameworks. See what each part decides, what the client keeps, and each specification's DOI.
Read more →Conformance is self-declared; no regulator endorses this work.
Start with the Automation Assessment
Two weeks, a fixed fee shared on a short call, ten candidate tasks scored and three solutions recommended.