CTRM and ETRM software development and integration, around the package your desk already runs.
We build and integrate trading software for commodity and energy desks around your CTRM or ETRM package.
Extend the package where it fits, build bespoke workflows, or modernize your in-house system.
- 150+Projects delivered across 12 countries since 2012
- 100+Senior in-house engineers, six countries
- 2 to 4 weeksTypical time from signature to start
- ISTQBISTQB-certified QA engineers
- ISO 27001Certified security practice, audited by Quay Audit UK
01Overview
Scope the workflow and the package boundary
We scope CTRM and ETRM integration around one desk workflow, the package's existing coverage and the records that must return to the authoritative book. The first decision is whether configuration, a supported extension or a custom module provides the required contract, settlement or reporting behaviour.
- Capture and confirmThe deal recorded as agreed, then confirmed with the counterparty.
- Deal and trade capture
- Bespoke contract structures
- Confirmations
- Position and riskWhat the book is worth right now, and how much its value can change before someone needs to be notified.
- Position keeping
- Mark-to-market and P&L
- Exposure and limits
- Move and settlePhysical delivery, invoices and cash connected to the systems that hold the financial record.
- Scheduling and logistics
- Invoicing and settlement
- ERP and bank integration
- Commodity-trading deliveryIn a 2022 review, one commodity trader described a 14-person development team for its internal CRM and B2B marketplace.
02Compare
Build, buy, or build around the package you already have
A supported package, an extension and a custom build serve different trading requirements. We choose the route against your trade types, settlement rules and existing interfaces, keeping one authoritative book.
| Your package and workflow | The engineering requirement | The route that fits |
|---|---|---|
| “It models our trade types end to end.” | Retain the trade model and assess the surrounding data flow | Keep or configure the package where it fits. Scope feeds or reporting separately if the middle office needs them.Get a second opinion firstOr book a meeting |
| “A contract structure it has no field for.” | Represent the contract and retain one book | Assess a supported module or extension, then build the bespoke contract model where needed. Reconcile positions through the package interfaces agreed for the work.How we build custom systemsOr book a meeting |
| “A settlement rule our counterparties insist on.” | Match the deal, delivery, invoice and cash | A confirmation and settlement layer connected to the package, ERP and bank through supported interfaces, with reconciliation breaks raised for review.Platform development and integrationOr book a meeting |
| “A risk view the vendor refreshes monthly.” | Provide the position view on the desk’s required cadence | A reporting layer using agreed position and market data inputs, with refresh schedules assessed against the source interfaces.Data and reporting engineeringOr book a meeting |
| “It is in-house, a decade old, and nobody will touch it.” | Establish a tested boundary for each replacement | Modernize module by module, starting with interfaces and a test harness. Agree reconciliation and cutover criteria against the existing book.Legacy software modernizationOr book a meeting |
03Solutions
Commodity and energy trading software we build
Scope a trading capability beside the package, from contract capture to the feeds and reporting that support the desk's decisions.
A capture interface for bespoke contract structures, embedded optionality and physical legs. We agree how those records and positions reconcile with the package's authoritative book.
- Right when
- The package has no field for it
Mark-to-market, realised and unrealised P&L, and exposure against limits for desk and board reporting. We agree valuation inputs, calculation rules and refresh needs with your risk and middle-office owners.
- Right when
- The desk needs a different position view
Confirmations, invoices matched to deals and deliveries, and cash reconciled against the ledger, with breaks raised for the settlement team to review.
- Right when
- Settlement needs a connected workflow
Curves, forwards, FX and reference data from your licensed market data feeds, versioned and supplied to agreed consumers through a shared ingestion path.
- Right when
- Several systems consume the same feed
Extracts built from retained deal versions and reporting inputs. Formats, retention and acceptance criteria follow the requirements agreed with your compliance and audit owners.
- Right when
- An audit trail is required
Interfaces and a test harness establish the replacement boundary. We modernize modules in phases, with reconciliation and cutover criteria agreed for each release.
- Right when
- A trading module needs replacement
04Obligations
Trading requirements and our company credentials
We scope reporting, audit and valuation requirements against your instruments and markets. Company credentials and build-access controls support the agreed delivery scope.
Trade reporting with a deadline
Your compliance owner confirms which EMIR, REMIT or Dodd-Frank duties apply to the entity, instrument and jurisdiction. We scope the required formats, channels and deadlines for reportable records.
- In a build
- Applicable formats and reporting deadlines
A version history for each deal
Retain the deal as reported, its later changes and the inputs used. The access and retention model follows the audit questions your desk needs to answer.
- In a build
- Retained deal versions and change history
Valuations you can reproduce
To reproduce a valuation, retain the curves, pricing inputs and calculation rules used for that run. Agree comparison and tolerance criteria with the risk owner.
- In a build
- Versioned curves and calculation inputs
ISO 27001:2022 and ISO 9001:2015
Our information-security and quality-management systems are certified across our full operation. The certifications were renewed through a multi-stage audit with Quay Audit UK.
- What it gives you
- A document trail that already exists
ISTQB-certified QA engineers
unicrew has ISTQB-certified QA engineers. We agree test scope for the contract, position or settlement workflow and its integration with the book.
- What it gives you
- QA expertise for the agreed workflow
Least-privilege access, agreed first
On build engagements, least-privilege access is agreed with your technical contact, read-only wherever the work allows. Discovery has no production write access.
- What it gives you
- No production write during discovery
Your compliance owner sets the applicable requirements
Discovery records the reporting, retention and access requirements for your desk. We use that agreed scope to design the history and extracts each consumer needs.
Where a package covers your trade types, we build around it. We add what it does not model, such as a bespoke contract structure or a settlement rule your counterparties insist on. Positions go back into the package, so the desk keeps one book.
Oleksandr TrofimovCTO & Co-Founder, unicrew05Delivery
How a CTRM or ETRM engagement runs
- Draw the boundaryWe review the workflow with the desk, middle office and package owner. We record what the package covers, what can be configured and what needs an extension or custom module.You getWhat stays in the package, and what does not, in writing
- Prove the interface before the featureWe assess the supported API, export or connector and the permissions it allows. We test the required data movement with agreed sample trades and positions before fixing the dependent feature scope.You getA tested supported interface and agreed data flow
- Test one workflow against the bookWe build the priority workflow using agreed trade data, then review it with the people who book, manage or settle those trades. Record ownership and reconciliation criteria are part of acceptance.You getOne workflow in front of the desk, reconciled
- Reconcile, then hand overWe compare positions, P&L and settlement against the agreed acceptance criteria, then document the interfaces and hand over to the team responsible for operations. Ongoing development can continue through team extension.You getReconciliation results, documentation and operating handover
06Proof
Trading delivery and adjacent financial systems
Our commodity-trading CRM and marketplace show direct sector work. Adjacent financial-system extension and modernization projects demonstrate the ownership and integration work behind this offer.
- A commodity-trading platform, built from a PRDWe built an internal CRM, then a B2B marketplace from a Milan commodity trader's PRD, with Ethereum smart contracts. In his anonymous 7 April 2022 Clutch review, the co-founder and CEO writes: "Artelogic's development team was composed of 14 people, including backend and frontend software developers and QA specialists". The CRM "took them 3–4 months to complete"; the marketplace "was more complicated and took them around nine months to complete". The work ran under our former Artelogic brand.14people on the team, in the client's own count
- Financial-system extension from an existing codebaseWe took over and extended a bookkeeping platform for a London financial-advisory firm in ASP.NET MVC, C# and MySQL, including encryption and account security. In a review of 15 August 2017, their head of product writes: "I was grateful to find a team that not only picked up an unfinished piece of software but also turned it around and improved it."2017the year we took over an unfinished build
- A recommendation based on your trading requirementsWe assess package coverage before recommending custom work. ION's Allegro, RightAngle and Openlink, alongside Molecule, Enuit and AEGIS, are options to evaluate against your instruments, workflows and interfaces. Where a package fits, retain or configure it and scope any needed data feeds, reporting or bespoke workflow alongside it.
07Client voices
What trading and finance clients say
I was very satisfied with Artelogic’s project management. They were very good at organizing all the different parts of the project, and our communication was easy; they were always available and proactive. Towards the end of the project, they went the extra mile and worked longer than expected without charging for the extra time, showing a lot of commitment.
Even though Artelogic didn’t have a background in this area, they learned quickly and repurposed technologies they’d used before in order to solve the business problem. I was very impressed with this ability, as most of the people we contacted before implied that they’d need to spend a lot of time of trying to understand our business logic.
08Case studies
Trading, financial extension and platform modernization
Explore the trading marketplace, bookkeeping extension and adjacent .NET Core migration behind these delivery examples.
See all case studies
TradingTrading software with smart contractsOur client, an experienced commodities trader, came to unicrew with a detailed PRD (Product Requirements Document) to develop the trading platform.
FintechAccounting Software Integration & Automation for a Financial Advisory CompanyBookkeeping reconciliation automated in an application unicrew took over, with no issues reported as transaction sizes grew in testing.- ModernizationRewriting and migrating a legacy platform onto .NET Core (Global On Media)unicrew rewrote Global On Media's codebase using .NET Core, React and Stencil.js and migrated its servers in the same engagement.
09Questions
Questions about CTRM and ETRM software
CTRM means Commodity Trading and Risk Management and covers commodities broadly. ETRM means Energy Trading and Risk Management and focuses on energy trading.
Feature coverage varies by product. We assess the instruments, physical scheduling, valuation, settlement and reporting requirements your desk needs, then check the package's actual coverage. The name alone does not establish whether a product supports a particular trade or market.
Choose based on the package's coverage of your trade types, workflows and interfaces.
Retain or configure a supported package where it fits. Assess a vendor module or supported extension for additional coverage. A custom contract, settlement or reporting module fits where the required behaviour needs bespoke development. We define how that module exchanges data with the package and which system owns the book.
We assess the platform's supported interfaces and access permissions before confirming the CTRM or ETRM integration scope.
The design establishes which system owns trades and positions, what data moves and which writes the package permits. We test the agreed interface and reconciliation with your data. ERP, bank and market data connections follow the same assessment. For a package without an API, we review the export and connector options its owner supports.
We quote CTRM and ETRM work against the desk workflow, package interfaces and agreed delivery scope.
- Time and materials: billed hourly, quoted per project.
- Fixed price: quoted per project against an agreed outcome.
- Team extension: billed monthly per team member, with no recruitment or placement fee.
We recommend the model after discovery. Fixed-scope work carries a post-launch warranty, with its length agreed in the contract.
Most engagements start within two to four weeks of signature. Delivery duration depends on the agreed workflow and integration scope.
We estimate the schedule against the trade or settlement workflow, supported package interfaces and agreed reconciliation and acceptance criteria. Those requirements establish the delivery plan for your project.
We scope the trading system's security and reporting requirements with your technical and compliance owners.
On build engagements, access is least-privilege and agreed with your technical contact, read-only wherever the work allows, with no production write access during discovery.
unicrew holds ISO 27001:2022 and ISO 9001:2015 management-system certifications, audited by Quay Audit UK, and has ISTQB-certified QA engineers. Your compliance owner confirms applicable EMIR, REMIT or Dodd-Frank duties; we scope the history, extracts and testing against those requirements.
Yes. We build commodity and energy trading software, from contract capture to the feeds and reporting that support the desk's decisions. Our direct sector work includes a private B2B commodity-trading marketplace and integrated CRM, built on Ethereum smart contracts and a Node.js microservices architecture, which the client's verified Clutch review of 7 April 2022 describes. Adjacent financial work includes extending a London advisory firm's bookkeeping platform in ASP.NET MVC, C# and MySQL.
Plan the next capability around your trading package
Discuss the workflow you want to add and the package you want to retain. We review the boundary, supported interfaces and route to an agreed development scope.
What happens after you contact us
- We reply within one business dayTell us what you trade, which package you run and the workflow you want to add.
- A call about the deskWe discuss package coverage, record ownership and the interfaces available to the work.
- Route and engagement model, in writingAgree the development route and a time and materials, fixed price, or team extension model.
- NDA, then discoveryMost engagements start within two to four weeks of signature.
