The operating problem
Start with an authoritative payment-system event for an engagement. A successful handoff produces a reviewed payment status and onboarding task. Define the accountable owner before connecting systems. The workflow does not determine trust treatment, transfer funds, or reconcile a client trust ledger by itself. 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. Verify the payment event
Authenticate the provider and preserve the event ID for durable deduplication.
2. Resolve client and engagement
Use approved mappings and the correct entity rather than matching names loosely.
3. Read current payment state
Distinguish pending, settled, refunded, disputed, and partial outcomes.
4. Request accounting review
The authorized person confirms treatment and any conditions for opening work.
5. Record the approved handoff
Link the reviewed status to onboarding and keep reversals visible.
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 |
|---|---|---|
| payment_event_id | payment_event_id | Resolve the stable source reference in the correct client, entity, and engagement. |
| engagement_id | engagement_id | Resolve the stable source reference in the correct client, entity, and engagement. |
| current_payment_state | current_payment_state | Resolve the stable source reference in the correct client, entity, and engagement. |
| accounting_approval | accounting_approval | Use the authorized owner or reviewed decision; unknown values stop the handoff. |
Acceptance checks
- A disputed payment cannot remain silently cleared.
- A pending event does not count as settled funds.
- 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.