Look for collisions

Review whether separate teams reuse short invoice numbers such as 001 or 100. A proposed euro collection could arrive with an identifier that appears valid in several places. Design a reference convention that remains understandable when departments, projects or accounting periods overlap, using only information appropriate for the payment record.

Test a human lookup

Give a colleague an illustrative receipt and ask which commercial obligation it belongs to. If they need to search several systems or inspect a customer’s entire profile, the identifier is doing too little work. Tap Tap Go’s planned vIBAN and SEPA routes are coming soon; confirm eventual reference handling before relying on your convention in live instructions.

Imagine this

An illustrative future scenario

Picture two divisions issuing invoice 104 in the same month. During preparation, the business adds a division code to its internal reference map. It can then recognise the intended obligation without pretending that a unique receiving detail necessarily identifies every invoice.

Make it practical.

Use this checklist as you read. Checks are not stored.

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.