Idempotency
Also called Idempotency key · Duplicate protection
TL;DRProcessing the same row twice produces one event, not two.
Usage arrives in files that get re-exported, re-sent, and overlap by a day. Without a rule for what makes a row the same row, every re-upload double-bills.
A template names the columns that together identify a row; the key built from them is stored with the event, and a matching key on a later upload is skipped. It is a product feature, not a plumbing detail — the operator picks the columns.
Where it happens in Sonic
Next
See it on your contracts
A walkthrough on the agreements and files you actually bill from — not a slide deck.