Validate each row independently
Confirm the service identifier, required target type, quantity limits, and billing basis for every line. A batch can contain valid and invalid requests at the same time. One successful sample row does not establish that the rest of the file is ready.
Check batch-level consistency
Look for accidental duplicates, missing campaign references, and total spending above the approved budget. Distinguish intentional repeated purchases from duplicate entries. Calculate the expected charge using current rates before submitting the prepared set.
Keep a result per row
After submission, record accepted order identifiers or errors against the original row references. Do not mark the entire file successful merely because the upload or request completed. Retry only unresolved rows after understanding whether they were accepted.
Decision checklist
| Decision | What to check |
|---|---|
| Row | Service target quantity |
| Batch | Budget and duplicate review |
| Result | Identifier or explained error |
Worked example
A hypothetical 20-row file contains 18 eligible requests, one missing target, and one quantity below minimum. A preflight review can pause the two exceptions while preserving the original references for the other 18 approved rows.
Example figures explain the decision; they are not current prices or promised results.