The operating problem
Start with an approved aging report refresh. A successful handoff produces a reviewed collection task or neutral payment reminder. Define the accountable owner before connecting systems. Do not send a demand based on stale balances or ignore a dispute. A source event is a request to evaluate the current state; it is not permission to make an irreversible change.
Use your own working copy
The free workbook for this process opens in a browser and works offline after download. It includes editable checks and notes, a text export, and a print view. It is a planning resource: it does not send messages, read account data, or run actions in business systems. No vendor account is needed to use the workbook.
Map the process
1. Read the current aging
Lock company, as-of date, currency, and invoice references from the accounting source.
2. Check current balance
Re-read each candidate invoice for payments, credits, refunds, and disputes before drafting.
3. Apply collection preferences
Use authorized contacts, client agreements, and any pause or relationship restrictions.
4. Prepare the next action
Draft a concise reminder or assign a staff call according to the approved aging policy.
5. Record and reconcile
Save the approved contact outcome and suppress duplicate requests until the next permitted date.
Information to check
These reference fields describe the process. Use invented values while planning. Keep real records in an appropriate private system; the public website does not need them.
| Reference field | Working record | Check before progressing |
|---|---|---|
| invoice_id | invoice_id | Resolve the stable source reference in the correct client, entity, and engagement. |
| as_of_date | as_of_date | Validate the date, timezone, and approved reporting or review period. |
| balance_due | balance_due | Validate the date, timezone, and approved reporting or review period. |
| collection_hold | collection_hold | Resolve the stable source reference in the correct client, entity, and engagement. |
Acceptance checks
- A payment received after the report suppresses the reminder.
- A disputed invoice enters staff review.
- A repeated source event creates only one current review task.
- A changed source version invalidates an earlier approval.
Walk through a successful example, a duplicate, a missing item, an incorrect match, and an interrupted handoff with synthetic records. Record the expected result, observed result, owner, and recovery action. Checklists record your work; checking a box does not establish that an external action happened.
Ownership and review
Name the person responsible for the process and the person who can resolve an exception. Define which decisions require qualified professional review. Use stable references, limit access to private records, and document when work must stop. Educational material does not establish legal, accounting, tax, security, or regulatory compliance.
Run a measured pilot
Choose a small, reversible sample. Measure handling time, waiting time, review, rework, and errors before changing the process. Include the effort of maintaining the new method. Expand only when the observed result meets your acceptance criteria; a longer checklist is not proof of improved performance.
Use the free workflow planner to define your next step, or compare the assumptions in the opportunity calculator.