Build vs Buy Hedge Accounting and FX Exposure Software
Buy if you hedge one currency pair out of one ERP under one reporting standard. Packaged platforms carry the accounting logic and the standard updates cheaply.
On this page
Buy if you hedge one currency pair out of one ERP (Enterprise Resource Planning) under one reporting standard. Packaged platforms carry the accounting logic and the standard updates cheaply. Build when exposure assembly is the bottleneck: several ERPs, dual reporting, or a designation you cannot reproduce two years later. Most groups end up buying the accounting and building the exposure layer feeding it.
Buy first if your programme fits the shape vendors assumed
Chatham Financial's ChathamDirect, Kyriba, ION Reval and Hedgebook were built by people who understand ASC 815 and IFRS 9 properly. They carry the accounting logic, absorb standard amendments, and produce disclosure tables your auditor already recognises. If your hedging programme sits inside the shape those products assume, buying is the cheaper and calmer answer, and a build would be an expensive route to the same destination.
That shape is narrower than most treasurers realise. One reporting standard rather than dual reporting. One hedge type, usually foreign exchange cash flow hedges of forecast purchases or sales. Exposure emerging from a single ERP instance with a consistent entity hierarchy. A treasury team small enough that entering instruments by hand is not itself a job. Critical terms that match between instrument and hedged item, so ongoing effectiveness can be assessed qualitatively rather than through regression against a hypothetical derivative.
If that describes you, buy the licence. Spend the difference on a designation memo template your auditor has reviewed in advance and on a quarterly control signed by someone other than the preparer. A group running a dozen forwards against one forecast exposure can hold a defensible programme on a controlled workbook. We have told prospective clients precisely that and walked away from the project.
The condition that pushes a treasury team into building
The build case never begins with accounting. It begins with exposure. Every packaged product is strong at producing accounting from designations you make against exposures you hand it. None can go and fetch the exposure, because exposure is a function of your entity structure, your functional currency assignments, your intercompany netting conventions, your forecast horizon and the specific document types and ledger accounts that constitute exposure in your business. That is yours, and no vendor can ship it.
So groups buy the platform and keep feeding it from a workbook one person maintains. The reproducibility problem, which is the actual audit problem, survives the purchase completely intact.
Here is the specific failure. Your designation on 3 March referenced an exposure report run that morning. Eighteen months later the auditor asks what that exposure looked like on 3 March. You rerun the report. It returns a different number, because the ledger has been posted to, restated, revalued and reorganised since. Nothing is wrong with your controls in any ordinary sense, but you cannot reproduce the figure that supported an elected accounting treatment, and that is a finding.
Build when two or more of these hold: you run more than one ERP instance because of acquisitions, you report under both US GAAP and IFRS, you hedge more than one risk type across cash flow, fair value and net investment hedges, your forecast genuinely moves inside the quarter so hedge ratios drift, or you have already taken an audit comment on designation documentation or dedesignation timing.
What each path costs, with the reasoning attached
Packaged platforms rarely publish pricing, and the reason matters. Hedge accounting modules are commonly priced against entity count, currency pairs and instrument volume rather than named users. That pricing behaviour is the one buyers get caught by: acquire two subsidiaries in a new currency and your renewal steps up materially, even though your hedging activity barely changed. Ask any vendor to write down in the contract which variable drives the fee and cap the annual uplift before you sign, not at renewal when you have no alternative.
Realistic annual licence spend for a mid-sized group sits in the tens of thousands, rising into six figures for complex multi-entity programmes, plus implementation. Advisory-bundled offerings cost more and are often worth it, because you are buying accounting judgement alongside software.
On the build side, a first release covering automated exposure extraction across entities and currencies, netting under your own conventions, certified exposure snapshots, instrument capture with full terms and structured designation documentation runs $70,000 to $160,000 over 10 to 16 weeks in our delivery experience. A full platform adding effectiveness testing with retained results, journal generation into the general ledger, dedesignation workflow and an audit evidence pack runs $180,000 to $450,000 phased across 6 to 12 months.
The dominant cost driver is ERP condition, not accounting complexity. Extracting open purchase orders from a customised SAP instance is a different project from reading ledger balances out of NetSuite, and a group with three ERPs is buying three integrations. Dual reporting adds meaningfully. Independent valuation, if you want your own curve data and pricing library rather than accepting counterparty marks, adds again.
The costs nobody quotes you
First, the annual standard-change tax. If you build the accounting engine as well as the exposure layer, you now own the obligation to absorb amendments to ASC 815 and IFRS 9 forever. That is precisely the work a vendor spreads across hundreds of customers. It is the strongest argument for the hybrid: buy the accounting, build the exposure engine, and let the vendor keep the standard.
Second, forecast provenance. Exposure includes forecast transactions owned by commercial teams in their own models. Getting a defensible forecast feed usually means a governance conversation with sales and procurement about who certifies a number and how often. Budget weeks for that, not days, and start it before the build.
Third, the treasury management system does not always give the data back cleanly. Extracting full instrument terms, not just notional and rate, from a system you already pay for is often a paid professional services engagement with your incumbent vendor. Confirm the export path in writing during procurement.
Fourth, on the buy side, the exception queue. A platform that cannot ingest your exposure will happily accept a manual upload, and within a year somebody's full-time job is preparing that upload. That salary belongs in the buy column.
Fifth, and this one catches almost everybody, the internal staffing draw. A build needs your technical accounting owner for roughly a day a week throughout, your group reporting manager for the designation and journal design sessions, and an IT contact who can obtain ERP credentials without a three-month approval queue. Projects in this category stall on access far more often than on requirements. Name that IT contact before kickoff rather than discovering the gap in week four, and treat their time as a real line in the budget rather than as goodwill absorbed by an already busy close calendar.
Sixth, implementation on the buy side is routinely quoted at a fraction of what it consumes. Configuring entity hierarchies, currency pairs, accounting rules and disclosure templates in a packaged platform is several weeks of your own team's time regardless of what the statement of work says, because only your team knows the answers. Buying does not remove that work. It relocates it.
The test that settles it in one afternoon
Pick one live hedge relationship designated at least four quarters ago. Give a colleague ninety minutes and ask for four things: the exposure position as it stood on the designation date, the designation documentation as it existed on that date, every effectiveness assessment performed since, and the journal entries that flowed to other comprehensive income with a trace back to the calculation.
If all four arrive inside ninety minutes and the exposure figure reconciles exactly, buy a licence and stop. Your controls are stronger than your instincts suggest. If the exposure has to be reconstructed, or if the designation memo cannot be tied to a specific instrument and a specific exposure, you have found the build. Note carefully that neither outcome is about the accounting arithmetic. It is about whether your evidence chain exists as records or as recollection.
Run a second check on the hedge ratio. Take one relationship and ask what the coverage percentage was at each month end since inception. If nobody can answer without rebuilding it, your dedesignation risk is live right now, and that is the finding that turns into a restatement rather than a comment.
What to do next
Write the exposure definition down first, before you speak to any vendor or developer. One page per entity: which ledger accounts, which document types, which forecast source, which intercompany positions net and which do not. Most groups discover during this exercise that two people hold different definitions, and settling that on paper is worth more than any software decision you will make this year.
Then run a competitive process on the accounting layer and a separate scoping conversation on the exposure layer. Ask any developer how they would store an exposure position so it can be reproduced in three years. If the answer is a report you can rerun, they have missed the point of the entire project.
Digital Heroes builds the exposure and evidence layer for finance teams, and we start with a written product requirements document before any code, which for a system that is ultimately audit evidence is not a formality but the deliverable that survives staff turnover. The team is 50-plus people across 2,000-plus delivered projects, with entities in India, the United States and the United Kingdom so contracting and IP assignment happen under your own law rather than someone else's. If you want to see how the team communicates before committing budget, the Digital Marketing Heroes channel carries 2.5 million subscribers and a long public record of the same explanations. Send the exposure definition, your ERP list and one designation memo, and the scoping conversation gets specific quickly.
If you want that decision made properly rather than quickly, Digital Heroes writes a product requirements document before any code exists, so the scope is fixed and priced rather than discovered later at a day rate. You keep the specification either way.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Gartner estimates RPA can eliminate up to 25,000 hours of avoidable rework caused by human errors in the finance function each year, equating to savings of roughly $878,000 for an organization with 40 full-time accounting staff (based on interviews with more than 150 corporate controllers and chief accounting officers). Source: Gartner (2019) →
- Deloitte reports that modern ERP implementations aim to deliver reduced manual effort, greater transparency, a single source of truth, and increased productivity, but many organizations do not capture the full expected benefits (a significantly lower ROI) without disciplined strategy, change management, and data readiness. Source: Deloitte (2024) →
- 88% of organizations are concerned about employee retention, and providing learning opportunities is respondents' #1 retention strategy; career progress is cited as people's top motivation to learn, yet only 36% of organizations qualify as 'career development champions.'. Source: LinkedIn Learning (2025) →
- Technology 'Leaders' grow revenue at more than twice the rate of 'Laggards'; laggards surrendered 15% in foregone annual revenue in 2018 and stood to miss out on as much as 46% in revenue gains by 2023 if they did not change their enterprise technology approach. Based on a survey of more than 8,300 organizations across 20 industries and 20 countries. Source: Accenture (2019) →
Frequently asked questions
How much does custom hedge accounting software cost?
A first release covering exposure extraction across entities and currencies, netting, certified snapshots, instrument capture and structured designation documentation runs roughly $70,000 to $160,000 over 10 to 16 weeks. Adding effectiveness testing, journal generation, dedesignation workflow and a full audit evidence pack takes it to $180,000 to $450,000 across 6 to 12 months. ERP count and condition drive that range far more than accounting complexity does.
How long before a build is actually usable in a close?
Ten to sixteen weeks to a first release, then one full quarter running parallel with your existing workbook before you rely on it. The schedule risk is almost never the accounting logic. It is ERP integration, particularly in groups carrying several instances inherited through acquisitions, where pulling open purchase orders is a separate problem from pulling ledger balances and needs separate scoping.
Can we migrate historical hedge relationships into a new system?
Yes, and you should migrate designations, instrument terms and effectiveness results, but be honest that historical exposure snapshots usually cannot be recreated because the data no longer exists in reproducible form. The practical approach is to import what is documented, mark the pre-migration period as evidenced by the legacy files, and start certified snapshots from go-live forward. Agree that boundary with your auditor before migration, not after.
Which integrations tend to cause trouble on these projects?
SAP instances with customised tables are the usual culprit, followed by treasury management systems that export instrument summaries but not full terms. Bank platforms vary widely in how they release trade confirmations. Get written confirmation of the export path from your incumbent treasury vendor during procurement, because retrieving your own instrument data is sometimes a chargeable professional services engagement rather than a menu option.
Does building put our hedge accounting election at risk?
Not if the evidence chain is stronger than what you have now, which is usually the point of building. The risk sits in the opposite direction: designations that cannot be tied to a reproducible exposure position are already the most common source of findings. Involve your audit partner in the design review before development starts, and have them confirm the evidence pack format they would accept.
Who actually builds this kind of finance system?
Specialist custom software firms rather than treasury vendors, since the work is integration and evidence design rather than accounting standard maintenance. Digital Heroes fits this category for finance teams because every engagement starts with a written product requirements document before any code, which matters when the deliverable is ultimately audit evidence, and because the firm contracts through Indian, United States and United Kingdom entities so IP assignment happens under the buyer's own jurisdiction.
What separates Digital Heroes from a generic development shop here?
The insistence that an exposure position is stored as an immutable certified snapshot rather than a rerunnable report. That single design decision is what makes a designation defensible three years later, and generic teams almost always propose a query instead. Digital Heroes also ships products of its own, including ShopScore, HeroCheckout and Section Vault, so the engineering discipline is applied to systems the firm has to maintain itself.
How do we verify a development partner before paying anything?
Check the company holds a D-U-N-S registration, which confirms a verified business entity rather than a trading name. Read the Clutch profile for reviews tied to named client contacts and project values, and check Trustpilot for the pattern of complaints rather than the average score. Then ask for the contracting entity in your own jurisdiction and confirm the IP assignment clause names it before any money moves.
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.
Will an app built for 10 users survive growing to 500?
Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
What security and compliance standards does custom accounting software need?
At minimum: encryption at rest and in transit, role-based access control, and immutable audit logs recording every change to the ledger. If outside parties rely on your numbers you will want SOC 2 style controls, and storing card data pulls you into PCI DSS, which most builds avoid by tokenizing payments through Stripe or a similar processor. Your industry adds its own rules, so compliance requirements belong in the written spec, not in a post-launch retrofit.
What does it cost to maintain custom accounting software each year?
Budget 15 to 20 percent of the build cost annually, so a $100,000 system needs $15,000 to $20,000 a year for hosting, security patches, dependency updates, and small fixes. Accounting software carries one extra obligation most software does not: keeping tax rates, filing formats, and bank feed connections current as banks and tax authorities change their systems. Skipping maintenance for two years usually costs more to repair than the maintenance would have cost.
How long does it take to build custom accounting software?
A focused first version takes 10 to 16 weeks, and a complete QuickBooks-class replacement takes 6 to 9 months. In Digital Heroes delivery data, schedules slip most often during data migration and bank feed integration, so we budget those two phases at double the first estimate. Treat any promise of a full accounting system in under two months as a warning sign.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
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 Zoe.
Senior Brand Designer · New-york · 8 posts on the site
Published · Last updated .
