Courses / Commodity Trading Operations & ERP
One trade, many records — the deal lifecycle
A single trade lives as a recap, a contract, an order, a shipment, an invoice and a journal. Most defects sit in the hand-offs between them.
Lesson 1 · free to read
The records a trade becomes, and where they break
A trader agrees a deal on the phone or by email. By the time the money has moved, that one deal has been written down several times, often in different systems:
- The recap. The trader's summary of what was agreed.
- The contract. The legal document, with its general terms, quality terms and payment terms.
- The ERP orders. A purchase order (PO) and a sales order (SO).
- The shipment or ticket. What physically moved: a vessel, a container, a truck on a scale.
- The invoices. A bill from the supplier (accounts payable, AP) and an invoice to the customer (accounts receivable, AR).
- The journal. The entries in the general ledger (GL) that finance reports from.
Most defects do not sit inside any one of these records. They sit in the hand-off between two of them. The contract says 4 decimal places and the order screen keeps 2. The recap says one shipment and the email trail ended at two. The shipment arrived but the invoice never learned the bill of lading date. When a customer reports a problem, ask first which hand-off it crossed.
A trade is not finished when it is invoiced. Prices can be fixed after delivery, quality is known only after inspection, and money settles weeks after the goods move. The system has to allow an invoice and later corrections to it (module 4).
The journal is not the last record. It is listed sixth, but it should not be written last. Every event above (the contract's committed value, the receipt, the bill, the shipment, the valuation of open positions) should post as it happens, as an accrual, an actual or a revaluation. Month-end then closes what is already in the books instead of reconstructing it.
Back-to-back trades. Many merchants buy and sell the same cargo and match the two legs. The margin is the gap between the legs, so the comparison between them is internal: neither counterparty should ever see the other leg's price. An Asian agricultural trader we worked with runs its book this way: create the purchase contract and the sales contract, allocate one to the other, and confirm each. Confirming generates the PO and the SO automatically.
Drop-shipment. Much physical trade never touches the trader's warehouse: goods go straight from supplier to customer. In an ERP such as Acumatica this is set per order line (the line is marked for a purchase order of type drop-ship, with the customer as ship-to), not by a special order type. There is no warehouse shipment; the purchase receipt stands in for it. A food sourcing group we worked with runs almost every transaction this way, one sales order to one drop-ship purchase order.
The rest of this module
- From estimate to actual — the costing chainA trade is priced on estimated costs and judged on actual ones. The system has to carry both.
- Three ways a lifecycle fails quietlySilent matches, invisible screens, and features that exist only in a summary.
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: Contracts in practice — pricing, terms, lines and splits