Define one batch before exporting records
Read the guide →Guide preview
Give the batch a purpose, cutoff and owner so the result can be interpreted later.
Define identity, exclusions and return rules before processing.
Define identity, exclusions and return rules before processing.
New to the topic? Begin with the first guide. Otherwise, go straight to the question you need to answer.
Give the batch a purpose, cutoff and owner so the result can be interpreted later.
Never let a verification label rewrite whether a particular message is permitted.
An external verification result must not silently override existing exclusions.
Minimise the vendor file; retain the richer business record in its authorised source system.
Use an explicit reconciliation key; spreadsheet position alone is a fragile identity system.
A duplicate technical address may still be linked to different business records; preserve the distinction.
Validate headers, row counts and field boundaries before blaming a verifier for an unusable return.
Start with the route whose scope and write-back behaviour you can explain.
A batch is ready only when input, authority, destination and return ownership are clear.