Monthly client CSV delivery guide
A file name is not a contract. Match source_id, contract ID, and version one-to-one, then repair only the failed client while leaving successful outputs unchanged.
A requires code as a string and qty as an integer. B requires item_id and a required name. C requires id and a date in YYYY-MM-DD form. Keep the contract ID and version beside the input.
| Contract | Required columns | Version | Boundary |
|---|---|---|---|
| A | code / qty | 2026-09 | unknown columns |
| B | item_id / name | 2026-09 | missing name |
| C | id / date | 2026-09 | date format |
Two files may both be called monthly.csv. Do not rely on similar names: record source_id, contract ID, version, and output name. Preview again when a version changes.
source_id contract version output
A A 2026-09 A-delivery.csv
B B 2026-09 B-delivery.csv
C C 2026-09 C-delivery.csvA has two rows and a quantity total of 5. C has one valid date row. B has only item_id, so it is pending rather than a false overall success. The first pass has three successful records from A and C.
| Contract | Input | Result |
|---|---|---|
| A | A.csv: 2 rows | success |
| B | B-bad.csv: no name | pending |
| C | C.csv: C01 / 2026-10-01 | success |
In this synthetic case, add the known value 部品B to B. Retry B only, then compare A and C logical outputs without recalculating them. The final set has three clients and four records.
retry: B only
B-fixed: B01, 部品B
A quantity total: 5 (unchanged)
C date: 2026-10-01 (unchanged)Do not send the full creator ZIP to one client. Confirm each A, B, and C output with its mapping card, and do not include original files or another client’s data without permission.
All materials are synthetic. This guide does not perform uploads or promise contract inference, unknown-column acceptance, cancelled-row handling, previous-month zero-filling, customer names, or sales outcomes.