Executive summary
An energy trading organisation is traditionally divided into three functions: the front office that trades, the middle office that manages risk and control, and the back office that handles settlement and operations. Understanding how these functions divide responsibility, and how they must work together, is fundamental to understanding how a trading business runs, and how an ETRM platform should support it.
The classic division exists for good reasons, separation of duties, specialisation, control, but it also creates a coordination challenge: a trade flows through all three functions, and if they operate on disconnected systems, the hand-offs between them become sources of delay, error, and reconciliation. A modern ETRM’s job is to preserve the separation of responsibilities while unifying the data they all work on.
This article covers the structure of the energy trading organisation, what front, middle, and back office each do, the complete trade lifecycle across them, the information flow between teams, and the modern ETRM workflow that ties them together. It builds on the modern ETRM guide and connects to trade capture and settlements.
Understanding the energy trading organisation
The three-way division of a trading organisation reflects a fundamental principle: those who take risk should be separated from those who control it and those who settle it. This separation of duties is a cornerstone of sound trading governance, preventing the concentration of authority that leads to error and abuse.
At the same time, the three functions are not independent, they are stages in one continuous process. A trade originates in the front office, is controlled and risk-managed by the middle office, and is settled and operationally fulfilled by the back office, and each depends on the others. Understanding both the separation (why the functions are distinct) and the integration (how they must work together) is the key to understanding how a trading business operates, and it frames what a modern ETRM must achieve: distinct responsibilities on unified data.
What is the front office?
The front office is where trading happens. It comprises the traders and originators who take positions, execute trades, and manage the trading book to generate profit within the risk mandate. The front office is the revenue-generating function, closest to the market and the source of the trades everything else processes.
Front-office activities include forming market views, executing trades, managing positions, and pursuing trading strategy. Its defining needs from an ETRM are fast, accurate trade capture, live position management, and the market data and analytics that inform decisions. The front office generates the trades that flow through the rest of the organisation, which is why capturing them accurately and once, on the canonical model, matters so much: everything downstream depends on the front office’s trades being recorded faithfully.
What is the middle office?
The middle office is the risk and control function. It sits between the front office that takes risk and the back office that settles, and its job is to measure, monitor, and control risk, ensure trades are valid and within limits, and provide the independent oversight that sound governance requires.
Middle-office activities include risk measurement (VaR, exposures, sensitivities), limit monitoring, valuation control, scenario analysis, and credit risk. Its independence is essential, the middle office must be able to check the front office objectively, which is why it needs its own view of risk built on the same authoritative data. A modern ETRM serves this by giving the middle office independent, governed risk analytics on the same canonical model the front office trades on, so oversight is both independent and consistent with reality, rather than based on a separately-reconciled set of numbers.
What is the back office?
The back office handles settlement, confirmation, and operations, everything required to turn an executed trade into a completed, settled transaction. It confirms trades with counterparties, manages settlement and invoicing, handles physical operations where relevant, and feeds finance and accounting.
Back-office activities include trade confirmation and settlement, invoicing and payment, reconciliation, and, for physical trading, scheduling and operations. The back office is where trading meets money and physical delivery, and its accuracy is essential because errors here have direct financial consequences. A modern ETRM serves the back office by deriving settlement and operations from the same canonical trade record the front office captured, so what is settled matches what was traded, and the reconciliation between trading and settlement that plagues fragmented operations largely disappears.
The complete trade lifecycle
Seeing how a single trade moves through all three functions makes the division concrete.
| Stage | Function | Activity |
|---|---|---|
| Origination & execution | Front | Form a view, execute, capture the trade |
| Risk & control | Middle | Value, risk-manage, check limits, validate |
| Confirmation | Back | Confirm the trade with the counterparty |
| Settlement | Back | Invoice, settle, reconcile |
| Operations | Back | Schedule and deliver (physical) |
| Finance | Back | Feed accounting and reporting |
The trade is one entity moving through the organisation, and the quality of the whole process depends on the hand-offs being clean. On fragmented systems, each hand-off is a re-keying between the front office’s system, the middle office’s, and the back office’s, and every re-keying is a chance for error and a reconciliation to perform. On a modern ETRM, the trade is captured once and each function reads and enriches the same record, so the lifecycle flows without the friction of moving a trade between disconnected systems.
Information flow between teams
The three functions depend on a constant flow of information between them, and the quality of that flow largely determines how well the organisation runs. The front office’s trades inform the middle office’s risk; the middle office’s limits constrain the front office; the back office’s settlement depends on both; and all three depend on shared reference and market data.
The critical question is whether this information flows through one shared model or through hand-offs between separate systems. When each function has its own system, information flow means data transfer and reconciliation, the middle office’s risk may be based on a slightly different version of the book than the front office holds, and the back office may settle against yet another. When all three work on one canonical model, information flow is automatic, each function sees the same authoritative trade, so risk, control, and settlement are consistent by construction. This is the core value a unified ETRM brings to the three-office structure.
The modern ETRM workflow
A modern ETRM preserves the separation of front, middle, and back office while unifying the data they work on. Each function has its own capabilities, tailored to its role, front-office trading, middle-office risk, back-office settlement, but all operate on one canonical model with appropriate controls and segregation of duties.
This is the resolution of the tension between separation and integration. The separation of duties that sound governance requires is preserved through role-based access and controls, the front office cannot approve its own limits, the middle office provides independent oversight, the back office settles independently, while the data fragmentation that separation traditionally caused is eliminated by putting all three on one model. The result is an organisation with proper controls and no reconciliation tax, which is exactly what the three-office structure needs to run well in a modern trading business.
Why the Gravitas workflow platform is different
Gravitas unifies front, middle, and back office on one canonical model with proper separation of duties.
| Capability | Gravitas |
|---|---|
| Front office | Fast capture, live positions, analytics |
| Middle office | Independent risk on the same model |
| Back office | Settlement derived from the trade |
| One canonical model | All three functions share it |
| Separation of duties | Role-based controls preserved |
| Clean hand-offs | No re-keying between functions |
| Consistent information | Same authoritative trade |
| Reconciliation | Minimal, exception-only |
| Cloud-native | Yes |
| Audit-ready | Yes |
Because all three functions work on one model with proper controls, the organisation has both sound separation of duties and no reconciliation tax, which is what lets the trade lifecycle flow cleanly. And it is delivered at economics that suit desks the incumbents priced out. See the platform, who Gravitas is for, or request a demo.
Implementation best practices
Supporting the three-office structure well rests on a few principles. Preserve the separation of duties through role-based access and controls, the front office takes risk, the middle office controls it independently, the back office settles independently. Unify the data all three work on so information flows through one canonical model rather than hand-offs between systems. Give each function capabilities tailored to its role on that shared model. And eliminate re-keying between functions so the trade lifecycle flows cleanly.
The through-line is that the three-office division is about separating responsibilities, not fragmenting data. A modern ETRM preserves the governance-critical separation of duties while unifying the data, giving the organisation both proper controls and the consistency that comes from every function working on the same authoritative trade. That combination is what the traditional structure needs to work well today.
Workflow KPIs
A trading workflow across the three offices can be measured across flow, consistency, and control.
| KPI | Target |
|---|---|
| Trade lifecycle flow | Clean, no re-keying |
| Front-to-middle consistency | Same book |
| Middle-to-back consistency | Same trade |
| Separation of duties | Enforced |
| Reconciliation effort | Minimal |
| Straight-through processing | High |
| Hand-off errors | Low |
Lifecycle flow and straight-through processing measure how cleanly the trade moves; consistency across functions measures whether they share one book; separation of duties measures control. Together they describe a trading organisation with sound governance and no reconciliation tax.
Frequently asked questions
What are front, middle, and back office in trading?
The front office trades, taking positions and executing to generate profit; the middle office manages risk and control independently; the back office handles settlement, confirmation, and operations. The division separates those who take risk from those who control and settle it.
What does the front office do?
The front office is where trading happens, traders and originators form market views, execute trades, and manage the book to generate profit within the risk mandate. It is the revenue-generating function and the source of the trades everything else processes.
What does the middle office do?
The middle office is the risk and control function: it measures, monitors, and controls risk (VaR, exposures, limits), performs valuation control and scenario analysis, and provides independent oversight of the front office, which requires its own governed view of risk.
What does the back office do?
The back office handles settlement, confirmation, and operations, everything to turn an executed trade into a completed, settled transaction: confirming trades, invoicing and settlement, reconciliation, physical operations, and feeding finance. Its accuracy has direct financial consequences.
Why are the three functions separated?
For separation of duties: those who take risk should be separate from those who control and settle it, which prevents the concentration of authority that leads to error and abuse. It is a cornerstone of sound trading governance.
How does a trade flow through the three offices?
It originates and is executed in the front office, is valued, risk-managed, and validated by the middle office, then confirmed, settled, operationally fulfilled, and fed to finance by the back office. It is one entity moving through the whole organisation.
Why do hand-offs between offices cause problems?
On fragmented systems, each hand-off is a re-keying between separate systems, introducing error and requiring reconciliation, and the middle office’s risk or the back office’s settlement may be based on a different version of the book than the front office holds.
How does a modern ETRM support the three offices?
By preserving the separation of duties through role-based controls while unifying the data all three work on. Each function has tailored capabilities, but all operate on one canonical model, so information flows automatically and consistently.
How is separation of duties preserved on one platform?
Through role-based access and controls: the front office cannot approve its own limits, the middle office provides independent oversight, and the back office settles independently, all enforced by the platform even though they share one data model.
What is the benefit of unifying the three offices on one model?
Information flows automatically and consistently, each function sees the same authoritative trade, so risk, control, and settlement are consistent by construction, and the reconciliation tax of moving trades between disconnected systems disappears.
What is straight-through processing?
Straight-through processing is when a trade flows through the lifecycle, capture, control, confirmation, settlement, without manual re-keying between functions. A unified canonical model enables it by letting each function read and enrich the same trade record.
Does unifying the offices weaken control?
No. Proper separation of duties is preserved through role-based controls; only the data fragmentation is eliminated. The result is an organisation with sound governance and no reconciliation tax, which is what the three-office structure needs to run well.
How does the middle office stay independent on a shared model?
It has its own governed risk analytics and oversight capabilities, and independence is enforced through controls, but it works on the same authoritative data as the front office. This makes its oversight both independent and consistent with the actual book.
What are common workflow implementation challenges?
Keeping the front, middle, and back office consistent, eliminating re-keying, preserving separation of duties, and achieving straight-through processing. Unifying the three functions on one canonical model with role-based controls addresses these.
Download this article as a PDF
Get a clean, branded PDF of this article to read offline or share with your team. Enter your name and corporate email and we’ll send the download link to your inbox.
Where should we send it?
Enter your details and we’ll email you the PDF download link. We use a corporate email to keep this list professional.
Check your inbox
We’ve emailed the PDF download link to your email. It should arrive in a moment. If you don’t see it, check your spam folder.