The operating problem
A payment event is not always a paid invoice. A reliable process asks whether the money belongs to this entity, this client, this invoice, and this period, then re-reads the remaining balance.
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. Authenticate the event
Verify the source signature using provider guidance and preserve the event ID for deduplication.
2. Resolve the invoice
Use accounting IDs and the correct company/tenant. Reject a payment with an ambiguous reference.
3. Fetch current state
Read the latest invoice and payment record. A late callback must not overwrite a subsequent refund or credit.
4. Classify the balance
Separate unpaid, partial, paid, refunded, and disputed states. Only the approved business rule can unlock delivery.
5. Reconcile and alert
Store a restricted reconciliation reference. Create a staff task for currency, amount, or matching exceptions and periodically reconcile missed events.
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 |
|---|---|---|
| event_id | dedupe_key | Provider event ID |
| company_id | tenant_reference | Check company boundary |
| invoice_id | record_reference | Never rely only on invoice display number |
| balance_due | payment_state | Allow partial and reversed states |
| updated_at | source_version | Ignore obsolete callbacks |
Acceptance checks
- A partial payment stays partial.
- A refunded payment cannot keep delivery unlocked.
- A duplicate event creates no duplicate receipt.
- An event for a different company is rejected.
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.