Courses / Commodity Trading Operations & ERP
Milling under someone else's grain — grind contracts and consumption tickets
When a processor draws down a merchant's grain instead of buying loads at the scale, the ticket is what the process consumed, not what a truck delivered — and two systems usually count it independently.
Lesson 1 · free to read
A contract settled by consumption, not receipt
Module 5 covers wheat a mill holds but does not yet own: financed and title-held by a grain merchant until it moves from storage into the mill's process. The mill still needs its own commercial agreement for what it actually grinds from that grain, and that agreement is usually a grind contract: a monthly, flat-priced purchase for a fixed volume of one wheat class, for example 250,000 bushels of soft white wheat delivered as consumed over three months.
Unlike the scale tickets in module 3, a grind ticket is not a truck's weighbridge receipt. It is a reading from the mill's own process-control system: the tonnage of a given wheat class that crossed from the dirty-wheat bins into temper in the last 24 hours, entered once a day (typically half a dozen tickets a day, up to about eight at peak). Each grind ticket is batch-applied to the grind contract it belongs to. Where more than one grind contract could take it — two classes running at once, say — the user designates which. Nothing is final: a ticket can be unlinked and reapplied as often as needed, and a whole month's tickets can be redone, right up to the point the contract is final settled. Final settlement is what raises the accounts payable bill for that month's grind, at the flat price the contract fixed. Only then does correcting a ticket mean reopening a closed bill rather than simply reapplying it.
Because the price is flat and fixed at signing, a mill that carries the physical price risk during the month typically hedges it the same day the grind contract is written: it passes a matching long futures position to its broker for the tonnage the contract commits it to, so the exposure the paper just created is covered before a single bushel is ground.
What a system must therefore do: let a consumption reading, not only a scale ticket, drive settlement; allow tickets to be freely relinked while a contract is open; and treat "final settled" as the one event that both locks the tickets and raises the bill.
The rest of this module
- Two systems, one throughput — reconciling before month-endBoth counterparties measure the same physical event independently. Compare and agree the difference before the bill goes out, not after.
- One site can be both miller and merchantThe same company may only grind at one location and also trade the raw commodity at another. Model the site's role, not the company's.
Carry on with the course
The other lessons and the quiz are in the course itself, where your progress is saved and counts towards the certificate: Commodity Trading Operations & ERP.
Next module: Who funds the goods and who hedges them — the merchant between producer and off-taker