TAP TAP GO
Create an invoice-level payment map
Record the agreed invoice amount, each authorised payment method and the reference for every attempt. Ask the supplier how it will acknowledge partial payments before splitting the amount. Keep rejected, pending and completed attempts distinguishable under provider definitions. The invoice remains the anchor: a finance reviewer should be able to see how the whole obligation was addressed without reading disconnected chat messages from several people who paid parts of it.
Agree who confirms completion
Name one person to obtain the supplier's final acknowledgement and reconcile any remaining difference. If a refund is needed, ask which original payment it relates to and how it will be returned. Do not assume the supplier's system will allocate multiple transfers exactly as your team expects. A clear close-out record prevents repeated follow-ups and makes later adjustments easier to investigate when the project team has already moved on to another assignment.
Hypothetical example
A hypothetical event producer pays a venue deposit by transfer and the remaining balance by card. The invoice record links both transactions and the venue's confirmation. When the guest count changes, the producer can identify which payment any adjustment relates to without reconstructing the original agreement.
Make it practical.
Use this checklist as you read. Checks are not stored.References & further reading
Background reading — CFPB: prepaid card comparison resources (US context) ↗Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.
