Avoid a moving target
A batch should refer to a defined input snapshot, not “whatever is in the database now.” Record the source system, export time, selection rule and row count. Use a neutral batch identifier without personal information. Keep ongoing changes in the source system separate until reconciliation.
Declare exclusions
Exclude records that do not belong to the authorised purpose before preparing an upload. Preserve the reason outside the vendor file where possible. Do not remove suppression history merely because the active batch omits those records. A smaller input file is not evidence that the master list is now clean.
Synthetic boundary
Batch A contains the membership newsletter segment as of Monday noon, not every contact the organisation has ever collected. Tuesday’s new signups remain outside A. The reviewer can now explain why the result count differs from Tuesday’s live total without treating the difference as data loss.
Put it into practice
Use a batch cover sheet with a neutral ID such as Cedar-01, a source-system name, an export timestamp, a selection description and an expected count. Add the rule for records changed after the cutoff. Do not name the batch after a sensitive customer segment if the filename will travel outside its authorised audience. In a fictional workflow, 1,200 source rows are eligible for review, but 100 are held outside the verification input for an independently documented reason. The cover sheet should explain both counts rather than calling 1,100 the entire database. When results return, compare them with the defined input, not with the live system's later total. A volunteer can then understand the arithmetic without reconstructing the original operator's intentions. Close the batch explicitly before creating another; reusing an identifier makes stale results and duplicate processing much harder to spot.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Bouncer API introduction — Merchant documentation · docs.usebouncer.com · Merchant-controlled · checked 2026-09-27