Movement records prepared for the processor and the movement service from two systems that do not share IDs.
- 0Rows re-typed by hand
- Before submissionWhen missing IDs are caught, not after rejection
- 1 approvalHuman step retained where it matters
Illustrative example. Figures are calculated from typical timings, not a measured customer result. Real case studies will replace these as implementations are measured.
Before
Movements are entered in the farm system, then re-typed into a spreadsheet in the format the processor wants, then checked against the movement service. Mismatched IDs are found only when a submission is rejected.
After
Movements are read from the farm system, IDs are matched against the reference list, the processor file is generated automatically and anything missing an ID is flagged before submission. A person approves the final submission.
