Courses / Commodity Trading Operations & ERP
Implementing a trading system — requirements, go-live, and life afterwards
How to get real requirements, what go-live actually needs, and the patterns that go wrong once a customer is live.
Lesson 1 · free to read
Getting real requirements
Requirements come from the people who do the work, walked through live on their current system, with real documents: a contract as issued, a ticket, a settlement, an invoice, a discount schedule. Templates filled in the abstract arrive late and wrong.
Ask for ten real rows first. Before a customer fills a 400-row data template, ask for ten real contracts and ten real tickets. You will find the format problems in a day instead of a month.
Own the hand-offs nobody else owns. At a flour mill, the ERP partner's signed business requirements ran to hundreds of control rows. The trading system barely appeared in it. Hedging appeared nowhere. All of its data templates were the ERP partner's (users, customers, vendors, chart of accounts, open payables); the trading templates did not exist. The trading system's real job was a set of hand-offs neither side had written down: a contract reference on every sales order, grading through to settlement, unit conversions. We had to bring our own trading data workbook: counterparties, commodities and grades, grade factors, locations and bins, purchase and sales contracts, tickets, opening position, futures, and hedge links.
Learn the customer's language before you correct it.
- At the mill, "OHRW" meant organic hard red winter wheat, not "ordinary". "B" in a contract number meant basis, not a counterparty's initial.
- An organic wheat purchase at nearly double the conventional price was first flagged as a data error. It was the organic premium.
- Ask before calling a number wrong.
Minutes record capability, not commitment. Write down what the customer said and what the product can do. What will be configured is settled in the signed requirements document. Scope and commercial terms are separate conversations and stay out of requirements minutes.
Configure or customise? Configuration is settings and data in the existing product. Customisation is new code. Mixing them up is the commonest cause of a wrong estimate: something that sounds like a setting may need code, and something that sounds big may be a checkbox.
Screen for risk as well as process. A metals and agricultural trading group's discovery covered know-your-customer (KYC) and pre-trade risk screening:
- KYC in two stages: a basic record, then full KYC with signed documents approved by a central team. It expires annually, with a refresh 30 days before expiry and no permanent exceptions.
- Pre-trade approval rules triggered by commodity and by the countries of origin, loading and destination.
- The tenor of a trade (days from paying the supplier to being paid by the customer) drives the funding cost, and so the projected margin.
The rest of this module
- What go-live actually needsMaster data, open contracts, opening balances, written criteria, and a rehearsal.
- Living with a live customerThe patterns that go wrong after go-live, and the habits that prevent them.
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: Milling under someone else's grain — grind contracts and consumption tickets