Questions practitioners ask about commodity trading and risk management systems for crude, refined products, and renewable fuels. Each answer points to the chapters, exhibits, vignettes, and glossary terms that take it further.
BasicsUnderstanding CTRM Systems
A CTRM (commodity trading and risk management) system is purpose-built software that manages the lifecycle of commodity transactions, from deal capture through risk management, scheduling and logistics, inventory, and settlement, and serves as the system of record for that activity. It consolidates transactions that would otherwise sit in spreadsheets, email, and disconnected systems into one platform, with consistent valuation, workflows that can be audited, and the position data risk management requires. In bulk liquids, four kinds of business rely on it: refiners, midstream operators, wholesale marketers and traders, and fuel distributors. Each needs a different mix of capabilities and integrations, from margin visibility for a refiner to custody tracking for a terminal or pipeline operator and rack pricing for a marketer, so the type of business is the first input to any CTRM decision.
From the bookChapter 1, CTRM in Context: Who Uses It, for What, and Where
See alsoFAQ: How does the type of bulk liquids business change what it needs from a CTRM? · Exhibit 1.1: CTRM participant profiles: what the system is and which capabilities matter most · Glossary: CTRM, System of record
ETRM (energy trading and risk management) and CTRM (commodity trading and risk management) describe the same category of software, and the difference between them is more historical than functional. ETRM grew out of power and natural gas trading, where financial instruments, capacity scheduling, and regulatory reporting under frameworks such as FERC's drove system requirements. CTRM grew out of physical commodity trading, where managing barrels, volumes, custody transfers, and quality attributes came first. As firms expanded across commodity classes, the terms blurred, and vendors and practitioners now use them inconsistently. The origin still matters when choosing a system, because platforms tend to keep the strengths of the market they were first built for. CTRM for Bulk Liquids uses CTRM as the umbrella term, and the core capabilities it describes apply to both CTRM and ETRM implementations, with distinctions drawn only where they matter functionally.
From the bookChapter 1, CTRM in Context: Who Uses It, for What, and Where
See alsoFAQ: Why do bulk liquids need a different CTRM approach? · Glossary: CTRM, ETRM
A CTRM covers five functional domains across the transaction lifecycle: trade capture, risk management, scheduling and logistics, inventory management, and settlement. Trade capture records physical deals, exchanges, swaps, futures, options, and transportation and storage contracts, with the validation and audit trail every later step depends on. Risk management values positions and measures flat price, basis, and inventory risk, and advanced deployments add Value-at-Risk, stress testing, and hedge effectiveness tracking under ASC 815. Scheduling and logistics connect the commercial book to physical movements through pipeline nominations, truck and rail allocation, terminal storage, and in-transit tracking. Inventory management follows barrels across tanks, pipelines, railcars, trucks, and vessels, including blending, quality adjustments, and losses. Settlement produces invoices and accruals and reconciles them to the general ledger at month-end. Data quality problems anywhere earlier in the lifecycle surface at settlement, so each domain is only as reliable as the one before it.
From the bookChapter 1, CTRM in Context: Who Uses It, for What, and Where
See alsoExhibit 1.2: The CTRM transaction lifecycle · Glossary: Deal capture, Scheduling, Inventory valuation, Settlement, Mark-to-market (MTM)
A CTRM and an ERP are complementary systems: the CTRM manages commercial activity, and the ERP keeps the financial records that activity feeds. The CTRM handles trade capture, position keeping, risk reporting, scheduling, and settlement calculations, none of which an ERP is designed to perform for physical commodities. The ERP handles the general ledger, accounts payable and receivable, and financial reporting. ERP-native commodity modules suit organizations whose commodity activity is mainly financial or procurement-oriented; for operators whose business runs on physical scheduling, terminal inventory, rack pricing, and excise tax, they are usually a partial solution that needs complementary systems. Where one system ends and the other begins is a deliberate design choice and one of the most consequential architectural decisions in a CTRM program. The book sets out three natural break points for that boundary, each with different consequences for interfaces, corrections, and financial reporting.
From the bookChapter 1, CTRM in Context: Who Uses It, for What, and Where · Chapter 6, Understanding the Vendor Landscape · Chapter 8, Integration with External Systems
See alsoFAQ: Where should the boundary between the CTRM and the ERP sit for a physical oil or fuels business? · Chapter 6, Vignette 1: The ERP-native path and the rack · Exhibit 8.1: The three ERP integration boundary options on the transaction lifecycle · Glossary: ERP, System of record
Bulk liquids need a different CTRM approach because their physical, regulatory, and logistics complexity does not map cleanly onto platforms built for power, natural gas, or financial derivatives. Physically, crude grades carry quality attributes that affect value, products are blended and regraded, and terminal inventory must reconcile against meter tickets and operator reports. On the regulatory side, RINs under the federal Renewable Fuel Standard, Low Carbon Fuel Standard credits, and federal and state motor fuel excise taxes create compliance workflows that most CTRM vendors treat as edge cases. In logistics, pipelines, terminals, rail, truck, barge, and vessels each require integrations with more operational consequence than in most other commodity segments. Pricing adds another layer, since a wholesale marketer may manage thousands of daily rack price points across a terminal network. Platforms keep the strengths of the commodity they were first built for, so a product without proven physical liquids deployments is rarely the right starting point.
From the bookPreface · Chapter 1, CTRM in Context: Who Uses It, for What, and Where · Chapter 16, Renewable Fuels as a Trading and Compliance Domain · Chapter 17, Fuel and Excise Tax Compliance
See alsoFAQ: How can a crude or refined products company narrow a long list of CTRM vendors to the ones worth evaluating? · Exhibit 6.1: Key functional categories and the deployed vs capability risk · Glossary: RIN, LCFS, Excise tax, Rack, Blending
On-premises, hosted, and true SaaS are three different CTRM deployment models, and vendors use the word cloud loosely enough to cover more than one of them. On-premises means the organization licenses the software, runs it on its own infrastructure, and controls upgrades, hosting, and security, while carrying the infrastructure cost, administration, and disaster recovery. Hosted means the vendor or a partner runs a dedicated instance in its data center. The client no longer manages infrastructure, but the architecture is still monolithic, so upgrades remain projects that need significant testing and may involve downtime. Most legacy platforms offered in cloud configurations fall into this category. True SaaS is multi-tenant software built to run as a shared service, with each client's data logically isolated and upgrades deployed continuously, so every client stays on the current version. The model affects IT governance, security posture, upgrade cadence, and total cost of ownership, so buyers should verify it during due diligence and not rely on marketing language.
From the bookChapter 5, Evaluating IT Strategy and Execution Capabilities · Chapter 6, Understanding the Vendor Landscape · Chapter 9, Cybersecurity and Risk in System Architecture
See alsoFAQ: How should a company plan for a CTRM outage or cyberattack, and what recovery targets should it set? · Exhibit 10.5: Cumulative cost of ownership for two deployment models, illustrative · Glossary: On-premises, SaaS, Multi-tenant
A full CTRM implementation for a bulk liquids business typically runs nine to eighteen months, depending on scope and scale. The range reflects how much must work on the first production day: these businesses cannot operate in a partial state, so trading, scheduling, inventory, and accounting generally go live together, with some scope such as derivatives or additional business units phased afterward. The work around the implementation adds time. A capability assessment typically takes four to six weeks, and a well-run vendor evaluation takes 10 to 18 weeks between RFP issuance and the selection decision. After go-live, a hypercare period follows while each user group stabilizes. Multi-tenant SaaS platforms with preconfigured transaction lifecycles can shorten deployment for mid-sized organizations, but their functional depth should be tested against the buyer's own scenarios. When schedules slip, the cause is more often governance gaps, unavailable subject matter experts, scope growth, or integration complexity than the software itself.
From the bookChapter 4, Assessing Business Capabilities and Organizational Readiness · Chapter 10, RFP and Evaluation Framework · Chapter 11, Project Governance and Delivery Models
See alsoFAQ: Why do CTRM implementations fail even when the selected software is capable? · Exhibit 10.1: Evaluation process timeline and key outputs by stage · Glossary: Go-live, Hypercare, Cutover
CTRM implementation cost depends on trading sophistication, scope, and deployment model, and the most reliable estimate is the buyer's own five-year total cost of ownership model; a license quote covers only part of it. Investment rises with each of the book's four levels of trading sophistication, and at Level 3, where trading optimizes margin across assets, it becomes a substantial capital commitment that grows with geographic and functional scope. A complete model covers nine cost categories: license or subscription fees, implementation services, internal staff time, infrastructure and hosting, integration build and maintenance, annual support, upgrades, training and change management, and data migration. Integration is the most consistently underestimated line and can equal or exceed the license cost over five years. Internal staff time is routinely left out of vendor-prepared estimates, and independent integrator estimates for complex projects typically run well above vendor estimates. Because cost structures differ by deployment model, a year-one comparison and a year-five comparison can favor different platforms.
From the bookChapter 2, Strategy First: Commercial Objectives · Chapter 10, RFP and Evaluation Framework
See alsoExhibit 2.2: Reporting, control, and investment requirements by sophistication level · Exhibit 10.4: TCO model component framework · Exhibit 10.5: Cumulative cost of ownership for two deployment models, illustrative · Glossary: TCO, Systems integrator (SI)
Part IStrategic Alignment in Bulk Liquids Trading
Substantially. Every CTRM user in bulk liquids needs commercial activity made visible, manageable, and defensible, but refiners, midstream operators, wholesale marketers, and distributors each depend on a different mix of capabilities and integrations. A refiner uses the system largely to see refining margin: crude slate economics, inventory valuation, and hedge performance. A midstream operator uses it to track custody, manage nominations, and reconcile movements. A wholesale marketer needs daily netbacks by terminal and customer, rack pricing across thousands of daily price points, and correct tax treatment in many jurisdictions; a distributor adds dispatch, truck ticketing, and delivery confirmation. A configuration built around one model serves another poorly: a system configured for a fuel marketer and repurposed for an asset-backed trading refiner will serve neither well. Selection should start from an honest view of which commercial domain the system must serve first and most completely. Companies that select from generic checklists tend to find users back in spreadsheets within months of go-live.
From the bookChapter 1, CTRM in Context: Who Uses It, for What, and Where
See alsoExhibit 1.1: CTRM participant profiles: what the system is and which capabilities matter most · Glossary: Asset-backed trading, Netback
Further readingWhy Should Energy Asset Owners Consider an ETRM System (Podcast, E2B: Energy to Business, 2021; with Mark Smith)
Both, in different ways. Choose the platform for where the business intends to operate over the life of the system, and configure it for where the business operates today. A company running Level 2 operations that plans to reach Level 3 within three years should not buy a platform adequate only for Level 2, nor switch on every Level 3 feature at go-live and take on complexity it cannot yet absorb. The sound course is a platform with a credible path to Level 3 and a phased configuration plan built on a solid Level 2 foundation. Each level of trading sophistication raises reporting, controls, staffing, and investment: Level 2 needs a centralized CTRM for daily mark-to-market and portfolio limits, and Level 3 adds Value-at-Risk and trade surveillance, with a substantially larger CTRM investment. Each step is an organizational commitment as well as a software purchase, and investing in a system without investing equally in people leads to implementation failure.
From the bookChapter 2, Strategy First: Commercial Objectives
See alsoChapter 2, Vignette 2: Swapping barrels between pipelines · Chapter 2, Vignette 3: Storage plays in contango · Exhibit 2.1: The four levels of trading sophistication · Exhibit 2.2: Reporting, control, and investment requirements by sophistication level · Glossary: Middle office
Further readingWhat you Need to Know Before Starting an ETRM System Implementation Process (Article, Energies Media, 2019)
Settle risk appetite before configuration, because it determines valuation logic, control workflows, limit enforcement, and reporting. Trading shops that take managed exposure for profit need detailed position reporting and flexible valuation; refiners and midstream operators that treat exposure as a cost to minimize need strong hedging workflows and strict limit enforcement. Either posture works when it is deliberate. The resulting decisions are concrete. Accepting flat price exposure on inventory but not on purchases requires separate valuation and hedging logic for each; material basis risk requires location-based price curves; credit appetite decides whether limits block a trade at entry or flag it for review. Inventory valuation is a risk-appetite decision too. A Gulf Coast marketer that valued all inventory at weighted-average cost saw a sharp price drop reach its accounting statements only the following month, and spent several months revaluing in spreadsheets while the system was reconfigured.
From the bookChapter 3, Risk Appetite and Regulatory Exposure
See alsoChapter 3, Vignette 1: A loss the books saw a month late · Glossary: Risk appetite, Inventory valuation, Delegation of authority (DOA)
A formal capability assessment before system selection is the most reliable test. Software cannot supply a missing middle office, an undocumented scheduling process, or an unresolved inventory valuation method, and a new system often makes such problems worse. A useful assessment covers five pillars of commercial readiness (trading strategy and commercial mandate; risk governance and controls; people and organization; process and workflow; finance, credit, and compliance) and places each capability on a Follower-to-Leader spectrum drawn from comparable organizations. Because a gap can have an organizational, process, or system cause, a system purchase fixes only the last. What to fix first follows from dependencies: risk governance before limit logic, inventory valuation before daily mark-to-market, and trade capture discipline before position reports. Risk governance is perhaps the most common gap, and an organization stronger in logistics than in risk should build that foundation first and then introduce the CTRM.
From the bookChapter 4, Assessing Business Capabilities and Organizational Readiness
See alsoChapter 4, Vignette 1: The assessment that reframed the business case · Exhibit 4.1: The five pillars of commercial readiness and their CTRM design implications · Exhibit 4.2: An illustrative capability profile on the Follower-to-Leader spectrum · Glossary: Middle office
IT capability should set the limits of the program design. Which deployment models, integration approaches, and delivery plans are realistic depends on what IT can deliver and sustain today, and companies that skip an honest assessment discover the constraints mid-implementation, when changing course costs most. The starting condition is business-IT alignment: an IT function left out of the commercial strategy work tends to treat a CTRM as an infrastructure deployment. One refiner moving toward Level 2 and beyond received an IT proposal (on-premises hosting, SAP integration at deal capture, a custom scheduling interface) that amounted to a Level 1 architecture. Beyond alignment, assess integration capability, the principle governing the CTRM boundary and custom code, cloud readiness, SDLC maturity, master data management, and the ability to direct an outside support provider. A weakness should change the plan: a marketer that phased cloud governance and master data work ahead of go-live went live on schedule and on budget.
From the bookChapter 5, Evaluating IT Strategy and Execution Capabilities
See alsoChapter 5, Vignette 1: A Level 1 architecture for a Level 3 ambition · Chapter 5, Vignette 2: Two assessments, one program design · Exhibit 5.1: IT capability dimensions, assessment questions, and CTRM program implications · Glossary: Master data
Part IISystem Selection and Technical Architecture
Start by removing products never built for physical liquids. The market is much smaller than vendor directories suggest, and most platforms keep the strengths and limits of the commodity and business model they were first built for. Then apply three filters. The first is the HC Liquids column of each product's functional capability matrix in references such as Commodity Technology Advisory's CTRM and Risk Management Sourcebook. The second is the difference between functionality deployed in production at a client site and functionality the vendor says it could provide; that gap is widest in rack marketing, quality and sampling, pipeline scheduling, blending and inventory, and taxation, so credit those claims only after seeing a production deployment at a comparable reference site. The third is the buyer's own size and commercial model. ERP-native commodity modules are a partial solution for physical operators, and a "cloud" offering may be a hosted legacy platform with a traditional upgrade cycle.
From the bookChapter 6, Understanding the Vendor Landscape
See alsoChapter 6, Vignette 1: The ERP-native path and the rack · Exhibit 6.1: Key functional categories and the deployed vs capability risk · Exhibit 6.2: Vendor landscape orientation by buyer profile and primary fit · Glossary: Multi-tenant, SaaS
Further readingCTRM & RM Sourcebook of Software Suppliers and Products (Report, Commodity Technology Advisory, 2025; free with registration) · ETRM & CTRM Software Selection in the Digital Era (Article, Energies Media, 2021)
Weight requirements by the buyer's commercial model, tag them by commodity, and test them with end-to-end scenarios drawn from the buyer's own transactions. Requirements documents fail in two directions: padded with everything anyone could want, often lifted from another company's RFP, or describing the company the buyer hopes to become. A rack marketer needs depth in scheduling, nominations, terminal integration, rack pricing, and excise tax; Monte Carlo VaR marked Critical means the template was never checked against the business. A commodity applicability flag on each requirement exposes vendors whose crude and products deployments do not extend to ethanol, RINs, or leased crude. Scenarios test whether the system can run a real sequence, from a pipeline purchase on a specific cycle through pricing, delivery, tax, settlement, and the ERP invoice. Eight to twelve well-chosen scenarios from the current system's transaction history yield more signal than twenty that repeat the same patterns.
From the bookChapter 7, Requirements Definition for Bulk Liquids and Renewables
See alsoChapter 7, Vignette 1: The commodity matrix exposes the gap · Chapter 7, Vignette 2: The transmix scenario changed the selection · Exhibit 7.1: Requirements category priority by commercial profile for this buyer type · Exhibit 7.2: Business scenario taxonomy for CTRM evaluation
Choose the boundary before integration design begins, from three natural break points in the transaction lifecycle: after deal capture, after actualization, or after invoicing. Everything before the break runs in the CTRM and everything after it in the ERP, so the choice sets the system of record for each stage and shapes every other interface. Breaking after deal capture is simplest but leaves the CTRM blind to physical execution. Breaking after actualization often suits operators at Levels 2 and 3 of commercial sophistication: the CTRM holds a real-time position through scheduling and ticketing, and only settled data passes to the ERP, at the cost of more complex interfaces and limited forward credit visibility. Breaking after invoicing gives the simplest corrections and suits an acquired entity with a mature CTRM. Left open until the implementation partner asks, the decision gets made under time pressure. Whatever the boundary, counterparty, product, and location master data must match across both systems.
From the bookChapter 8, Integration with External Systems
See alsoChapter 8, Vignette 3: Eleven counterparty names · Exhibit 8.1: The three ERP integration boundary options on the transaction lifecycle · Exhibit 8.3: ERP integration scenario comparison · Glossary: ERP, Actualization, System of record, Master data
Further readingLeading Practices for Integrating ETRM & ERP Systems (Article, LinkedIn, 2017) · Integrating ETRM and ERP Systems (Presentation, Best Practices for Oil & Gas, 2013; with Yael Urman)
Plan for the commercial consequences first: when a business cannot trust the positions, nominations, and settlement data in its CTRM, it cannot safely trade, schedule, or pay. Colonial Pipeline shut down for six days in 2021 as a precaution, because after a ransomware attack it could not determine whether its operational systems had been affected. For a well-architected on-premises trading system, a recovery time objective (RTO) of four hours or less during trading hours and a recovery point objective (RPO) of 15 to 30 minutes are reasonable commitments. A long RPO is the more insidious failure, because missing transactions must be rebuilt from counterparty records and manual logs. Ransomware specifically targets backup infrastructure, so backups stored alongside production are not a DR plan, and a backup proves itself only when it has been restored to an isolated environment. For hosted and SaaS platforms, negotiate application-level SLAs and annual evidence of failover. The breach plan must also settle whether positions and nominations from the breach window can be trusted.
From the bookChapter 9, Cybersecurity and Risk in System Architecture
See alsoExhibit 9.2: RTO and RPO on a failure timeline · Exhibit 9.3: RTO, RPO, and availability targets for CTRM deployments · Glossary: Recovery time objective (RTO), Recovery point objective (RPO), Disaster recovery (DR)
Further readingThe Cybersecurity Risk Posed By Your Outdated ETRM System (Article, JD Supra, 2021)
The version support policy and any restriction on who may implement, upgrade, or customize the platform. Both usually sit in standard boilerplate, and private equity concentration among vendors makes both more consequential. Agreements that support only the current and preceding release turn the vendor's release cycle into a permanent upgrade program, and a major upgrade of a heavily integrated CTRM can take three to six months. One midstream operator, pushed outside support two years after go-live, found that only the vendor's own team could perform the upgrade and that it was booked 18 weeks out; the operator ran unsupported for two months before an $800,000 upgrade its business case had never modeled. Negotiate support windows long enough for a responsible upgrade, unrestricted third-party rights or a genuinely competitive approved partner group, and written roadmap commitments with remediation if they slip. A buyer who accepts the standard form accepts the vendor's most favorable terms.
From the bookChapter 10, RFP and Evaluation Framework
See alsoChapter 10, Vignette 3: One version behind support · Exhibit 10.6: Contract terms checklist · Exhibit 10.4: TCO model component framework · Glossary: Systems integrator (SI), TCO
Part IIIImplementation and Operationalization
One of the most persistent causes lies in governance and internal ownership: decisions are not made at the right level by people with the authority to make them, and the client lets leadership of its own program drift to the implementation partner. A delivery team with real authority should make 60% to 80% of program decisions, the program management office 10% to 20%, and the steering committee fewer than 5%; each question that travels up the hierarchy and back costs two to four weeks. When one rack marketer's supply sponsor seat sat empty for six weeks, deferred decisions forced rework and moved the derivatives go-live by a month. Internal ownership also means allocating the subject matter experts who know where the exceptions are. A refiner that gave its senior back-office expert a quarter of her time found a misconfigured posting rule only in testing, and the six-week slip cost more than the time saved. The integrator answers for delivery; only the client can answer for its decisions and readiness.
From the bookChapter 11, Project Governance and Delivery Models
See alsoChapter 11, Vignette 1: Six weeks without a business sponsor · Chapter 11, Vignette 2: A quarter of the expert's time · Exhibit 11.2: Accountability lane model for SI and vendor · Glossary: Systems integrator (SI), Subject matter expert (SME), Project management office (PMO)
Ask four questions in order and stop at the first that resolves the gap. Is the gap real, or has the team not yet found the configuration that covers it? Is it a platform problem or a process problem the business sponsor could change? Would a purpose-built tool beside the CTRM, integrated by API, serve better than code inside it? Only then: what will the customization cost over its life? A 40-hour build may need 20 hours of assessment, remediation, and retesting at every major upgrade over a ten-year lifecycle. Configuration travels through upgrades; customization is code the organization owns and the vendor cannot support, and every custom object must be reassessed at each upgrade. Organizations that let custom objects accumulate defer upgrades until an upgrade rivals the original implementation in cost. Some customization is justified. The aim is an honest inventory of items that were logged, approved in writing, and documented.
From the bookChapter 12, Configuration vs Customization
See alsoChapter 12, Vignette 1: Two hundred forty custom objects · Chapter 12, Vignette 2: A methodology nobody needed anymore · Exhibit 12.1: The four-question customization decision framework · Glossary: Configuration, Customization, RICEFW
Further readingThe (Technical) Debt Harvest in an ETRM Upgrade (Article, LinkedIn, 2026) · Postmodern ETRM: Why Technology Should Impact Your Investment Decisions in Trading Systems (Article, Opportune Insights, 2020; with Stephen Bell and Steven Bradford)
When a gap is real and a process change cannot close it, a purpose-built complementary tool integrated with the CTRM is usually the sounder answer, provided it is governed as a system in its own right. Deferring the gap is also a decision, and the one most organizations reach for: the business fills it with shadow spreadsheets that have data models, users, and a release schedule set by one person's availability. Custom code inside the CTRM can fail quietly. One custom approval workflow kept running after an upgrade but stopped routing a new deal subtype, and an audit later found 17 deals executed without desk head approval. A complementary tool works under three conditions: it connects to the CTRM through a supported mechanism such as an API, the CTRM remains the system of record, and each tool has named business and IT owners, change control, and an entry in a registry reviewed before every CTRM upgrade.
From the bookChapter 13, Bridging the Gaps: When Core CTRM Isn’t Enough
See alsoChapter 13, Vignette 1: The custom workflow that failed silently · Chapter 13, Vignette 2: The payables spreadsheet only one person understood · Exhibit 13.1: Recurring gaps at the CTRM boundary: default workarounds, purpose-built solutions, and integration patterns · Exhibit 13.2: The governed complementary tool ecosystem · Glossary: Shadow spreadsheet, Limit of authority (LOA), System of record
Further readingFrom Monolith to Marketplace: Why Enterprise Energy Software Solutions Need an App Store Ecosystem (Article, LinkedIn, 2025)
Classify every in-flight transaction category by its state at go-live and assign it one explicit handling rule before the cutover window opens. Completed transactions are not migrated. Transactions begun in the legacy system with obligations running past go-live are completed there, and only the resulting balance loads into the new system. Transactions in mid-execution are split, finishing in each system and joined by an opening inventory balance. New transactions run entirely in the new system. The split rule concentrates the risk: a barge loaded before go-live and discharged after it is in-transit inventory whose opening balance must match the legacy record, or the discharge becomes an inventory discrepancy that flows into positions and financial reporting. Term and evergreen deals must be in production before cutover, interfaces need a planned activation order, and the sequence should be rehearsed in at least two mock cutovers. An unreconciled opening balance should be a no-go condition.
From the bookChapter 14, Data Management, Testing, and Cutover
See alsoChapter 14, Vignette 2: Twelve thousand barrels and a no-go · Exhibit 14.1: The four transaction cutover rules at the go-live boundary · Exhibit 14.2: Transaction cutover decision framework · Glossary: Cutover, In-transit, Mock cutover
Further readingLeading Practices for ETRM System Conversion, Cutover & Go-Live (Article, Energies Media, 2021; with Jason Wilton)
Measure the timeliness and completeness of operational data against metrics defined before go-live. Users who log in daily can still be operationally absent: nominations confirmed days late, invoice approvals batched to month-end, and payables left unmatched produce wrong positions and unreliable accruals while adoption looks healthy. Define what good looks like for each user group, such as movement tickets booked within a set window of the physical movement, documents matched within a set period, and daily position reconciliation within tolerance, and set specific baselines, such as 90% of tickets booked within 24 hours. When a metric slips, the super-user for that group works out the cause with the people involved. The same metrics should decide when hypercare ends, group by group. At one refiner, schedulers confirmed nominations when invoices arrived, three to seven days late, and the resulting phantom positions surfaced only in the sixth week as month-end P&L swings.
From the bookChapter 15, Change Management and User Adoption
See alsoChapter 15, Vignette 2: Phantom positions from late confirmations · Exhibit 15.2: Operational health metrics by user group: what good looks like and the indicators of adoption failure · Glossary: Hypercare, Super-user
Part IVBeyond the Core—Risk, Compliance, and Optimization
A CTRM can carry compliance for a refiner or blender subject to the federal Renewable Fuel Standard and a single state Low Carbon Fuel Standard: tracking the RIN lifecycle, connecting to the EPA's EMTS, and producing the reports. A separate compliance application becomes necessary as the number of programs grows, as their rules change faster, and when the business must optimize across programs. Each program has its own obligation logic, and a refiner exposed to six LCFS programs, six greenhouse gas programs, and the RFS runs 13 or more rule sets at once. The deciding factor is the rate of rule change: a stable program can live in CTRM configuration, while one still being shaped by rulemaking belongs where business users maintain obligation rules as configuration tables. One refiner's custom application needed a four- to six-month development cycle for each new program, longer than the lead time the programs allowed. The CTRM remains the commercial system of record throughout.
From the bookChapter 16, Renewable Fuels as a Trading and Compliance Domain
See alsoChapter 16, Vignette 2: A compliance application outgrown by the rules · Exhibit 16.3: The compliance application architecture · Glossary: RIN, LCFS, Renewable Fuel Standard (RFS), System of record
Three functions that a CTRM does not perform natively at multi-state complexity: tax determination at invoice time, return preparation and filing, and license and exemption certificate management. The CTRM supplies the transaction data and the ERP posts liabilities and remittances. States differ in rate, taxable event, and product classification, and state and local jurisdictions routinely produce hundreds of rate changes in a single year, some on as little as 30 days' notice. A manually maintained rate table applies the wrong rate to every gallon between a change's effective date and the update; one distributor operating in eight states absorbed just under $400,000 after missing rate changes in three jurisdictions. Moving to an automated tax engine is a risk-management decision. Filings should draw from one authoritative source, because mismatches between tax invoiced and tax reported are the main trigger for state audits. Exemption certificates produce the most audit findings: an exempt sale is protected only by a valid certificate on file at the time of sale.
From the bookChapter 17, Fuel and Excise Tax Compliance
See alsoChapter 17, Vignette 1: Missed rate changes in eight states · Chapter 17, Vignette 2: Expired certificates and an audit · Exhibit 17.3: Three-function fuel tax compliance architecture and CTRM data flows · Glossary: Excise tax, Rack
Either the data and configuration beneath the VaR are incomplete, or its readers treat a quantile statistic as the worst case. Risk reporting is a stack (position, exposure, valuation, P&L, risk metrics), and each layer inherits the integrity of the one below it. One products marketer lost roughly four times its reported one-day VaR after about 30% of in-transit inventory was missing from the position system, a five-day pricing window had been configured as a month average, and a regional differential curve had gone stale. None of these were model failures; the VaR was precisely calculated from imprecise inputs. Even with clean inputs, a 95% one-day VaR says nothing about the size of losses on the other five days in 100, and a 60-day historical window can lag a new volatility regime. Stress testing and Conditional VaR supply the tail view, and VaR belongs only after exposure and mark-to-market are trustworthy.
From the bookChapter 18, Risk Management and Analytics
See alsoChapter 18, Vignette 1: A precise VaR from imprecise inputs · Chapter 18, Vignette 3: The stress scenario the model could not see · Exhibit 18.1: The risk reporting stack · Exhibit 18.5: What VaR sees and what it does not · Glossary: Value at Risk (VaR), CVaR, Basis risk, Mark-to-market (MTM)
Four conditions: clean CTRM data, an investment sequence that does not skip maturity phases, users who can evaluate what a tool recommends, and governance proportionate to what each tool can affect. Tolerance for data problems is lower for AI than for human reporting, because a model trained on flawed data learns the wrong patterns. One marketer's demand forecasting model learned from data in which movements were recorded after delivery, and it treated the recording lag as demand behavior; value arrived after 22 months against a six-month plan. An organization that cannot produce a clean daily position report without analyst intervention is not ready for optimization or agentic automation. Governance starts with whether a tool reads from the system of record or writes to it: a reading tool's worst failure is a wrong answer, and a writing tool's is a wrong action in positions or settlements. Any automated action affecting a reportable position, a deal record, or a regulatory filing needs human approval.
From the bookChapter 19, Leveraging Emerging Technologies
See alsoChapter 19, Vignette 2: Forecasting a recording lag · Exhibit 19.1: The four AI maturity phases · Glossary: Machine learning (ML), Agentic automation, System of record
Further readingWho Approved It? AI Governance for Bulk Liquids Operators (Article, LinkedIn, 2026)
Most mature organizations use a blend, decided by the depth of internal domain expertise, the cost structure the organization can sustain, and the system's commercial criticality; cost alone is a poor guide. Internal support brings proximity to the business, the knowledge that resolves an unexpected risk report within 30 minutes before a board meeting. Managed services supply after-hours coverage, specialized configuration skills, upgrade capacity, and cross-client pattern recognition. A common split keeps risk reporting logic, compliance configuration, and commercial analytics internal and outsources interface monitoring, ticket triage, and release management. Every function needs a named owner and every interface a named monitor, and a provider needs business context: one marketer's escalations fell once the provider's lead analyst joined weekly commercial calls. Internal teams are typically understaffed for the first 6 to 12 months; at one refiner, a three-person team shrank to one within 60 days, and the commercial team rebuilt a spreadsheet the system was meant to replace.
From the bookChapter 20, The Evolving CTRM Operating Model
See alsoChapter 20, Vignette 1: Three people, then one · Chapter 20, Vignette 2: Managed services without business context · Glossary: Managed services, RICEFW
Further readingKey Considerations For Supporting Your ETRM System (Article, SHALE Magazine, 2021)
AboutThe Book and This Site
CTRM for Bulk Liquids: A Practitioner's Guide to Strategy, Selection, Implementation, and Operation is a book about commodity trading and risk management systems for refiners, marketers, midstream operators, and distributors of crude oil, refined products, and renewable fuels. It was written by Kent B. Landrum, a Partner at Opportune LLP and former Chief Information Officer of CPS Energy, and published by Thin Leaf Press in 2026. It covers the full CTRM lifecycle in four parts: strategic alignment, system selection and technical architecture, implementation and operationalization, and topics beyond the core such as renewable fuels compliance, excise tax, risk analytics, emerging technologies, and the long-term operating model. It has twenty chapters and an epilogue, a glossary, exhibits, and 45 composite vignettes. The book is written for commercial and operations leaders, IT architects, project sponsors, and the consultants who advise them. It assumes readers know the business, though not that they have run a CTRM program before, and suggests a reading path for each role.
From the bookPreface · How to Use This Book · About the Author
See alsoAbout the Author · Reading paths by role · Exhibits · Glossary
The CTRM Readiness Diagnostic is an online self-assessment on this site that scores an organization against the five pillars of commercial readiness from Chapter 4 and shows where it sits on the four levels of trading sophistication from Chapter 2. The five pillars are trading strategy and commercial mandate; risk governance and controls; people and organization; process and workflow; and finance, credit, and compliance. Each capability is placed on a Follower-to-Leader spectrum. The diagnostic takes about ten minutes and returns a readiness profile with the chapters to read next. Users enter their name, work email, and role once, and access then lasts up to 90 days from the same browser without creating an account. Details, answers, and results are shared with Opportune LLP, and a copy of the results is emailed to the user. The diagnostic is a starting point; the full capability assessment described in the book typically takes four to six weeks.
From the bookChapter 2, Strategy First: Commercial Objectives · Chapter 4, Assessing Business Capabilities and Organizational Readiness
See alsoReadiness Diagnostic · FAQ: How can a trading organization tell whether it is ready for a CTRM, and what should it fix first? · Exhibit 2.1: The four levels of trading sophistication · Exhibit 4.1: The five pillars of commercial readiness and their CTRM design implications