Wholesale Power Settlements Software: Build vs Buy for Shadow Settlement
Buy the calculation library. Maintaining charge code formulas against tariff amendments across markets is genuinely hard work and a vendor already does it.
On this page
Buy the calculation library. Maintaining charge code formulas against tariff amendments across markets is genuinely hard work and a vendor already does it. With one resource in one market and no joint owners, a specialist product plus one competent analyst costs less than anything you would build. Build the input assembly, the deadline clock and the internal allocation, because no vendor will ever fit those to your ownership structure.
What the off-the-shelf products actually do well
Take the honest position first. If you have a single resource in one independent system operator market, no joint owners and a simple contract structure, do not build anything. A specialist vendor plus one analyst who can read a business practice manual will cost less and cover you better.
PCI Energy Solutions is deep and well established, and for an asset owner who also wants bidding, scheduling and generation management in one place it is a coherent choice rather than a compromise. Power Settlements is focused specifically on this problem and well regarded for it, and the thing you are actually buying is their calculation library across markets. Maintaining that library against tariff amendments and business practice manual revisions is relentless, unglamorous work, and paying someone else to do it is usually correct. OATI covers scheduling and settlement functions for a wide range of participants. Yes Energy is excellent at market data and is often the right source layer underneath any settlement process, though it is not a settlement engine and treating it as one leaves the recalculation and dispute workflow unaddressed.
What all of them absorb on your behalf is change. When a market revises a formula, restructures a charge code or alters a file format, the vendor absorbs it inside your licence. Own that yourself and every tariff amendment becomes a small project with your name on it. That is the single strongest argument for buying and it deserves more weight than it usually gets in these conversations.
Where they stop: the settled amount has to reach an internal home
Getting the market's number right is only half the job.
The settled amount then has to be allocated to a specific generating asset, split between joint owners under an operating agreement, attributed to a bilateral contract or a retail book, matched against the hedge that was supposed to cover it, and posted to the general ledger with the correct treatment. That is almost always the largest spreadsheet in the department and the one nobody wants to own. It is also the part no product will ever fit, because your operating agreement was negotiated rather than standardised.
The second stopping point is input assembly. Recalculation is arithmetic once the data sits in one place, and getting it there is the actual project. One charge might need settlement quality meter data from your meter data agent, day ahead and real time market results, your own submitted offers and bids, ancillary service awards, outage records and resource registration data. Those arrive on different schedules from different systems, and some of them are restated afterwards. Meter data corrections in particular flow through quietly and change the basis of a calculation you already ran. A settlement engine that does not track the vintage of every input produces recalculations that disagree with themselves between runs, and analysts stop trusting it within a month.
The third is the calendar. Markets do not settle once. ERCOT publishes initial, final and true-up statements with the true-up landing months after the operating day, and other markets run their own resettlement cycles. Each publication opens its own dispute window measured in days rather than months. A rarely triggered uplift charge that looks plausible inside a heavy bill can sit unexamined for three weeks, and by the time an analyst notices the allocation basis was wrong the window closed nine days earlier. The money is gone quietly, and nobody did anything wrong. The process simply cannot find an error faster than the calendar closes.
The arithmetic: markets, resources and the cost to build
The crossover in this category is not volume. It is markets.
Vendor pricing here generally combines an annual figure per market with a figure per settled resource. Take a first release at $145,000, add year two at 18 percent, and you are near $171,000 over two years, or roughly $7,150 a month. Against a licence at $45,000 per market per year plus $6,000 per resource, that breaks even at about seven resources inside one market. In practice the second market decides it long before the seventh resource does, because a second market roughly doubles the vendor line while adding perhaps 40 percent to a build whose input layer, deadline engine and allocation rules already exist.
There is also a per-transaction dial nobody tells you about, and it is the cheapest analysis in this whole article. Rank the last twelve months of statements by absolute dollars per charge code and count how many codes it takes to reach 90 percent of your total. That list is almost always shorter than anyone expects, and it is your first release scope. You are not recalculating several hundred charge codes. You are recalculating the few dozen that carry the money.
On the other side of the ledger, put a figure against the errors you currently cannot find. Not a fabricated recovery rate, because nobody can honestly supply one. Just the charges you queried late last year and the amounts involved. Most desks have two or three examples and have never added them up.
What a custom build actually costs
Bands from Digital Heroes delivery experience across reconciliation and financial control systems.
- First release. One market, the charge codes carrying most of your dollars, automated input assembly with versioned observations, variance detection against the statement, deadline tracking and a dispute pack generator. $90,000 to $200,000 in 12 to 20 weeks.
- Full platform. Adds additional markets, allocation to assets, contracts, joint owners and hedges, accrual estimation for month end close, and true-up tracking across restatements. $250,000 to $650,000 over 9 to 18 months.
Data migration runs 10 to 25 percent of the build, and it is unusual here because you are loading history rather than replacing a system. You need twelve to twenty-four months of statements, meter data and market results to prove the engine reproduces known outcomes before anyone will trust it against a live statement. That backload is the acceptance test, not a preliminary.
Year two and after runs 15 to 20 percent of build cost annually, and in settlements that number is not padding. It is tariff amendments changing formulas you implemented, file format revisions on a calendar you do not control, and new charge codes appearing after a market design change. If you build, you have signed up to track the business practice manuals. Budget the analyst time as well as the developer time.
The four situations where building wins
Two together is a real case. One is not.
- Regulatory fit. You file Electric Quarterly Reports with the Federal Energy Regulatory Commission and need the transaction detail to reconcile to what you settled. Add controls over financial reporting if you are publicly held, where an auditable path from a general ledger balance back to a charge code and its inputs is a control rather than a convenience.
- Scale economics. You settle in two or more markets and your team maintains parallel spreadsheets per market, which is the crossover from the section above expressed as headcount.
- A workflow that is your competitive advantage. Allocation to joint owners, contracts and hedges. An asset with several owners and a non-trivial operating agreement is a rules engine on its own, and getting it right is a commercial relationship rather than a back office task.
- Integration sprawl across three or more systems. A meter data agent, the market portals, an energy trading and risk management system, a hedge book and the general ledger. When five sources must agree before a number posts, the agreement layer is the product and nobody sells it.
How to decide in a week, then buy a written specification
One week, one analyst, no procurement.
Monday, run the charge code ranking described above and write down how many codes reach 90 percent. Tuesday, take the largest of them and try to recalculate one operating day from the business practice manual and your own inputs. Record how long assembling the inputs took compared with the arithmetic. Wednesday, list every dispute window that opened in the last quarter and how many days each stayed open before anyone looked. Thursday, ask your controller how the current month's accrual estimate is produced and whether it is a calculation or a judgement. Friday, count the spreadsheets that carry allocation to owners and contracts.
If Tuesday took an afternoon, Wednesday shows every window reviewed and Friday finds one spreadsheet with an owner, buy a specialist product and staff an analyst. That is a functioning settlements desk.
If the week says build, the next step is a paid discovery phase rather than a proposal. Digital Heroes runs discovery to a signed product requirements document covering the versioned input model, the deadline objects, the recalculation scope and acceptance criteria, and you keep it whichever firm builds from it. We contract through an India LLP, a US LLC or a UK LTD so intellectual property assigns under your own law, we run our own products including Section Vault, and you meet the named engineers before signing. Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S are all checkable.
We are the wrong firm if nobody in your organisation can read a business practice manual and explain a charge code formula. Software does not create that capability, it amplifies it, and an engine configured by people who do not understand the tariff produces confident wrong answers faster than a spreadsheet does.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- A study (led by Prof. Pak-Lok Poon, published in Frontiers of Computer Science, 2024) reviewing decades of spreadsheet-quality research found that about 94% of spreadsheets used in business decision-making contain errors, illustrating the hidden risk of manual spreadsheet workarounds that custom software is built to replace. Source: Central Queensland University / phys.org (Prof. Pak-Lok Poon et al.) (2024) →
- Independent reporting of Gartner's 2025 survey confirms 59% of finance leaders use AI, up from 37% in 2023, with error and anomaly detection (34%) and accounts payable automation (37%) among the leading use cases. Source: CPA Practice Advisor (reporting Gartner) (2025) →
- In the Flexera 2025 State of ITAM report, respondents reported roughly 33% of SaaS spend is wasted, underscoring how paying for off-the-shelf seats and tiers that go unused erodes the supposed cost advantage of generic SaaS. Source: Flexera (2025) →
- A later Nucleus Research review of analytics software ROI case studies found customers received $9.01 in benefits for every dollar spent on analytics technology, showing returns vary with deployment factors but remain strongly positive. Source: Nucleus Research (2019) →
Frequently asked questions
How long before a shadow settlement engine starts finding real variances?
Twelve to twenty weeks to a first release, but the useful signal usually arrives earlier. Once the input assembly works and two or three high dollar charge codes recalculate, you can run them against the last six months of statements before the rest of the build finishes. Historic backloading is the acceptance test in this category, so treat it as part of the schedule rather than a preliminary.
Who owns the calculation logic and the settlement history if an agency builds it?
You should own the repository, the infrastructure accounts, the calculation configuration and the full history in an open format, agreed in writing before kickoff. Settlement records support dispute positions and financial reporting and may be examined years later. Digital Heroes assigns ownership at the first commit and contracts through an India LLP, US LLC or UK LTD entity so the assignment holds under your own law.
What data do we need before independent recalculation is possible?
Settlement quality meter data from your meter data agent, day ahead and real time market results and prices, your own submitted offers and bids, ancillary service awards, outage records and resource registration data. Store every one as a dated, versioned observation and record which version each calculation consumed. Without that vintage tracking your recalculations will disagree with themselves and your analysts will stop opening the tool.
What happens when meter data is restated after we already recalculated?
You re-run the period, and you must be able to re-run it either way. The system should reproduce the original result against the original inputs and the new result against the current inputs, then show the difference. That distinction between what you knew then and what you know now is what makes a dispute conversation defensible. A design that overwrites inputs cannot do it at all.
Can settlement data support a month end accrual estimate?
Yes, and for many finance teams that is the strongest single reason to build. Once the engine recalculates from inputs, estimating a charge before the statement arrives becomes a forecast on a known formula rather than a controller writing down a judgement. It adds a forecasting path to the build and it changes the close from an explanation exercise into a variance report.
What is the difference between shadow settlement and invoice validation?
Invoice validation compares this month's charge code totals against last month's and investigates what moved. It is a smoke detector. Shadow settlement recalculates the charge from the tariff formula and your own inputs, then compares line by line at statement granularity. Only the second finds allocation errors and wrong resource attribution, because those produce numbers that look entirely reasonable at the total level.
Should we replace an existing vendor or build around it?
Build around it, in most cases. The hybrid we see working at mid-sized firms is to licence the charge code calculation capability where a vendor maintains it well, then build the input assembly, exception workflow, deadline management and internal allocation around it. The vendor keeps pace with the tariff. You keep control of the part shaped by your own asset structure and ownership agreements.
How should joint owner allocation be represented in software?
As dated configuration with an audit trail rather than as a formula copied down a spreadsheet column. Ownership percentages, effective dates, contract designations and hedge links each become records that can change over time, so a settled amount from an operating day two years ago allocates by the rules in force then. Reconstructing that from a current spreadsheet is exactly the work you are trying to remove.
How much does it cost to keep a settlements build current each year?
Fifteen to twenty percent of build cost annually, and unusually for software, a meaningful share of that is analyst time rather than developer time. Somebody has to read the business practice manual revisions and decide what changed. If you build, you have taken on the tariff tracking that a vendor was doing inside your licence, and pretending otherwise is how these systems quietly go stale.
What should we ask a developer before signing a settlements contract?
Ask them to walk one charge code from your own market end to end using the business practice manual. You are testing whether they will engage with the tariff or expect your team to hand them arithmetic, and both models work as long as you know which you bought. Then ask what a dispute pack looks like, and expect the market's number, your number, the inputs behind each and the tariff reference.
Should I hire a freelancer or an agency to build my accounting software?
A strong freelancer is fine for a reporting dashboard or one integration; anything that holds your books needs a team. Ledger software requires backend, frontend, QA, and accounting domain knowledge, and one person rarely covers all four while staying available for the 5 to 10 year life of the system. The most common rescue job Digital Heroes takes on is a solo-built ledger with no tests and no documentation after the freelancer moved on.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
What can custom accounting software do that QuickBooks, Xero, and FreshBooks can't?
It encodes your actual business rules: progress billing tied to project milestones, revenue recognition for your specific contract types, landed cost tracking, or approval chains that match your org chart. Off-the-shelf tools handle generic bookkeeping well but force every business into the same chart of accounts and workflow. FreshBooks, for example, is built around freelancer-style invoicing, so inventory or multi-entity accounting means leaving the product entirely.
How small can the first version of my software be and still be worth building?
One workflow, end to end, for one type of user: the single process that currently burns the most hours or loses the most money. In Digital Heroes delivery experience, first versions scoped to 6 to 10 weeks of build time ship, get used, and generate the feedback that makes version two obviously right, while 9-month first versions routinely launch with features nobody touches. Everything you cut from v1 gets cheaper to build later, because real usage reorders the roadmap for you.
How much does custom accounting software cost for a small business?
Most small business accounting builds land between $25,000 and $75,000 for a working first version, while a full double-entry platform with invoicing, payroll, and reporting runs $100,000 to $250,000. Across 2,000+ projects at Digital Heroes, the biggest cost driver is how many external systems the software must connect to, not the accounting logic itself. A tool that automates a single painful workflow, like reconciliation or job costing, can come in under $20,000.
How do I migrate years of QuickBooks data into a custom system?
Use a staged migration: export full history through the QuickBooks API or backup files, load it into the new system, then run both systems in parallel for at least one full closing cycle before cutting over. Expect cleanup work, because books older than three years almost always contain miscategorized transactions that surface during import. Digital Heroes schedules migration as its own project phase with its own sign-off, never as a launch-week task.
I'm outgrowing FreshBooks. Is custom software the logical next step?
Usually not directly, because FreshBooks is an invoicing tool more than a full accounting platform, and the natural next step is QuickBooks or Xero for proper double-entry books. Custom development makes sense when those do not fit either, typically because of a billing model none of them handle, like usage-based or milestone billing. In that case a custom billing engine that feeds a standard ledger is often smarter than replacing everything.
Who can build a custom accounting software system?
Digital Heroes builds custom accounting software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other accounting software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Aaradhya.
Senior Backend Engineer · Python · Delhi · 4 posts on the site
Published · Last updated .
