Government Fund Accounting Software: Build the Layer or Buy Tyler Munis
The line is federal award count, not agency size. Below roughly eight active federal awards and a single digit fund count, buy: Caselle, Springbrook or BS&A will serve you properly and a build is a liability rather than an asset.
On this page
The line is federal award count, not agency size. Below roughly eight active federal awards and a single digit fund count, buy: Caselle, Springbrook or BS&A will serve you properly and a build is a liability rather than an asset. Above that, and particularly once capital projects span several funding sources and years, the answer is still not a new ledger. It is a $90,000 to $180,000 layer built on the ledger you already run. Almost every agency that arrives asking to replace Tyler Munis needs a wrapper instead, and saying so costs us revenue.
When is off the shelf genuinely the right call here?
The packaged market in local government finance is mature and mostly competent at the thing it was built for. Tyler Munis and BS&A run the ledgers of a very large share of American cities and counties. Caselle and Springbrook serve small entities properly and at a price a four person finance office can defend. OpenGov is a reasonable choice when reporting and transparency are your actual pain and your ledger needs are ordinary.
These products exist because a commercial general ledger cannot answer the question a governmental one has to. A business ledger asks whether money was spent and what it cost. Yours has to answer whether the money was legally available, out of which fund, against which appropriation, in which budget year. Appropriation control, encumbrance accounting at the purchase order stage, interfund transfers and eliminations, and dual statement reporting under Governmental Accounting Standards Board Statement 34 are structural rather than configurable, and the packaged vendors got them right.
Buy if most of these are true:
- Fund count in single digits, with no internal service or enterprise funds carrying interfund billing.
- Fewer than eight active federal awards, all on one indirect cost rate or the de minimis rate.
- Capital projects that are few, small and funded from one source at a time.
- A finance office of three or four people whose close is manual but manageable.
- No state mandated filing in a layout your product cannot produce.
There is also a situation where the answer is not now regardless of size. If you are twelve months into a signed enterprise system replacement, adding a custom layer starts a data ownership argument you will lose. Finish the replacement, then decide what it does badly and build against that.
When does a custom build actually pay off?
The build case in this sector is almost never the ledger. It is the layer the vendor priced as a module you did not buy or cannot get changed quickly.
- Grant volume with rate complexity. Five awards on one indirect cost rate is a week of work. Twenty two awards across three rate agreements, two with cost sharing and one where the rate changed mid year, is six weeks, because every historic rate has to stay replayable when an auditor asks how a prior year draw was calculated.
- An audit finding on grant expenditure reporting. Most of these come from an indirect cost calculation done once in a workbook and never revisited, and from labor distribution that never made it from payroll into the grant record. Both are fixable one level above the ledger.
- Encumbrance visibility. Every packaged system does encumbrance accounting. Almost none of them put a current available balance in front of the person about to sign a contract, so the department head asks finance, the report is a day old, and the requisition was already approved.
- Multi year capital across funding sources. A single invoice splitting across a bond fund, a state grant and a federal award with different eligibility rules is where packaged project accounting falls over.
- An annual close that depends on one person's spreadsheets. The conversion worksheet encodes decisions specific to your entity, and it gets rebuilt from last year's file by whoever is still there.
Building a whole ledger is justified in narrow cases only: a special district, utility authority or joint powers agency whose accounting does not look like a city at all, or an entity trapped on an unsupported legacy system where the migration is happening anyway. A county with sixty funds, thirty departments and two thousand employees is not getting a replacement ledger inside a sane budget, and no honest firm will pretend otherwise.
How do they compare on the things that matter in this industry?
Available balance in real time. Ask a vendor to show a department head a single number that is appropriation minus expenditures minus open encumbrances minus pending requisitions, per organisation and object code, refreshed on demand. Then ask what surfaces an encumbrance with no activity for twelve months before close rather than during the audit.
Indirect cost rate handling. The correct design versions the rate by agreement period with effective dates, so a rate change in March does not silently rewrite July. Ask how a 2024 draw is recalculated the way it was calculated in 2024. That single question separates people who have done federal grant work from people who have read about it.
Conversion to government wide statements. Capital assets, long term debt, compensated absences, the actuarial pension and other post employment benefit entries, and the lease and subscription schedules under Statements 87 and 96 have to come from somewhere. In most agencies that somewhere is a workbook, which is the pattern that breaks when its author leaves.
Audit trail. Governmental records must be defensible years later: append only journals, no silent edits, and the ability to reproduce a statement as it stood on the day it was issued. Any design that allows a posted entry to be quietly changed is disqualifying in either path.
Data portability. Ask exactly what you get back on exit, including transaction detail and the audit trail rather than a summary export, and get it written into the contract rather than discussed at renewal.
What does total cost of ownership look like at your scale?
Two very different projects hide behind the same request. From Digital Heroes delivery experience, a layer covering grant and project accounting, live encumbrance and available balance visibility, and annual comprehensive financial report schedule assembly runs $90,000 to $180,000 and ships in 14 to 20 weeks. A full fund ledger for a special district or small city, meaning general ledger through purchasing, accounts payable, cash receipting and a payroll interface, runs $250,000 to $600,000 across 9 to 18 months. A county of 240,000 residents with forty one funds and twenty two active federal awards typically lands near $172,000 for the layer, with historic rate replay and a full parallel close being the two items that put it at the top of the band.
The lines nobody quotes. Support and maintenance at $18,000 to $45,000 a year for the layer, more for a ledger, because accounting standards change on a published schedule with hard effective dates. Forty to eighty engineering hours a year for audit season, which is not optional and always lands in the same eight weeks. A few days per cycle on chart of accounts upkeep as each budget adoption adds funds, departments and projects. Hosting at $4,000 to $18,000 a year, driven by in state hosting requirements and retention periods that are usually longer than anyone assumes at kickoff. And a rate agreement load each time a new indirect cost rate is negotiated, which is small work, recurring, and unforgiving if done carelessly.
The single most cut and most regretted line is the parallel close. Running the new system alongside the existing ledger for a full period and proving both agree is around fifteen percent of the project. Cutting it is how a system ships and then quietly stops being used, because the comptroller never signed off.
What does the hybrid look like, and when is it the honest answer?
For most cities and counties the hybrid is not a compromise, it is the correct architecture. Keep the ledger where the county bought it and build the surround.
Three pieces stand on their own and can be funded separately:
- The encumbrance and available balance view. A joined read across the ledger, the purchase order file and the contract register, computing available balance per organisation and object code and aging stale commitments onto a lapse review list before close. This is not sophisticated engineering. It is a view the vendor never exposed, and it is the feature department heads notice first.
- The grant register. Award terms, budget periods, indirect cost rate by grant and by rate period with historic replay, draw request assembly from posted expenditures, and a schedule of expenditures of federal awards that ties to the ledger rather than to a parallel workbook.
- Conversion as versioned rules. Capital asset, debt, lease and subscription subledgers posting their own entries, major fund determination running the size tests against actual balances and showing the arithmetic, and every statement line tracing back to the accounts behind it.
Read from the ledger first and write to it only where a write is genuinely needed. A one way pull covers most of what finance needs daily and removes the riskiest part of the work from the critical path. Never build the general ledger itself: it is solved, audited, cheap, and your auditor already knows it.
Which should you choose, by operator size and stage?
Find your row and act on it.
- Small town, two or three funds, no federal awards. Buy Caselle, Springbrook or BS&A and spend the money elsewhere. A build at that size is a liability with a login screen.
- City or county on Tyler Munis or BS&A with eight or more federal awards. Keep the ledger, build the grant register and the encumbrance view. That is the $90,000 to $180,000 layer and it is where the audit findings live.
- Agency with an open finding on grant expenditure reporting. Build the layer, and put historic rate replay and a parallel close in fixed scope rather than as options. An auditor will not accept a system that cannot show its work for prior periods.
- Agency whose annual close depends on one person's conversion workbook. Build the conversion rules regardless of grant count. You are buying continuity.
- Special district, utility authority or joint powers agency whose accounting is not city shaped. A full ledger build at $250,000 to $600,000 is defensible here and almost nowhere else.
- Mid way through a signed enterprise replacement. Do nothing. Finish it first.
Two conditions apply to every build row. Go live at the start of a fiscal year, never mid year, and away from audit fieldwork, because both otherwise consume the same finance staff you need for acceptance. And ask any candidate to explain encumbrance accounting back to you before you explain it to them. If they describe a purchase order as a document rather than as a claim against appropriation authority, you will discover the difference during your first audit.
If you would rather scope this before committing budget, Digital Heroes starts every engagement with a signed specification covering the data model, permissions and acceptance criteria, which is what keeps a fixed price fixed. Nothing about that commits you to the build.
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) →
- McKinsey found that currently demonstrated technologies can fully automate about 42% of finance activities and mostly automate a further 19%, indicating roughly 60% of finance work is technically automatable. Source: McKinsey & Company (2018) →
- The EY survey of 508 payroll professionals at U.S. companies with 250-10,000 employees quantifies the direct and indirect cost of payroll inaccuracy, reinforcing the ROI case for payroll automation; the study is the original source of the frequently cited $291-per-error figure. Source: BusinessWire / EY (Ernst & Young) (2022) →
- 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) →
Frequently asked questions
What does it cost to move off Tyler Munis or BS and A?
More than any agency expects, which is the main argument for not doing it. Converting a decade of transactions is a project of its own, and the honest approach is usually to convert balances and keep the legacy system readable rather than migrate every record.
Then add the parallel close, which is around fifteen percent of any project in this category. Running both systems for a full period and reconciling them is what gets the comptroller to sign, and it is the phase agencies cut first and regret most.
What happens if our ledger vendor raises prices at renewal?
It changes the arithmetic less than agencies hope, because the ledger is rarely the expensive part of your stack in labour terms. Ask what the fee is tied to, meaning users, funds, modules or transaction volume, and get the exit terms in writing including exactly what data you receive back and in what format.
The more useful pressure point is the change request price list. Ask what a custom report or a new calculation costs and how long it takes. That number, not the licence, is what tells you whether the product still fits.
How long does a fund accounting project take?
A grant, encumbrance and reporting layer ships in 14 to 20 weeks. A full fund ledger for a special district or small city runs 9 to 18 months and is normally phased so the general ledger and purchasing go live before cash receipting and the payroll interface.
Plan the go live at the start of a fiscal year and away from audit fieldwork. Data conversion is the usual schedule risk, and converting balances while keeping the legacy system readable is both faster and safer than moving a decade of transactions.
Is Caselle or Springbrook enough for a small city?
For a small entity with a handful of funds, no federal awards and a finance office of three or four, comfortably yes. Both serve that market properly, they cost a fraction of a build, and the assumptions they make will fit you.
Revisit the decision when grants multiply, when capital projects start spanning funding sources and years, or when your annual close depends on one person's spreadsheets. Those are the three conditions that change the answer, and none of them is fund count.
Do we have to replace the ledger to clear a grant audit finding?
Almost never. Most grant expenditure findings trace to an indirect cost calculation done once in a workbook and never revisited, or to labor distribution that never reached the grant record from payroll. Both are fixable in a layer sitting on your current ledger.
Replacing the ledger to solve a grant reporting finding is an expensive answer to a problem that lives one level above it, and it introduces conversion risk that dwarfs the original finding.
How does the single audit threshold change what we need?
The threshold moved to $1,000,000 in federal expenditures for fiscal years beginning on or after October 1, 2024. Agencies that crossed it need the schedule of expenditures of federal awards generated from ledger data rather than assembled by hand, plus a defensible trail from each line back to the transactions behind it.
If you are near the line, confirm your status with your auditor rather than assuming last year's answer still holds. Pandemic era and infrastructure money has moved several agencies in both directions.
What about the lease and subscription standards?
Most agencies still keep both in a workbook, which is exactly the pattern that fails when its author leaves. In a build they become subledgers: each agreement carries its term, payments, discount rate and modifications, and the amortisation entries post on a schedule rather than being keyed once a year.
The value is not the calculation. It is that the population of agreements stays complete as new ones are signed, which is the part a spreadsheet cannot guarantee.
Who owns the code and the data if we hire a firm?
You should own the repository, the database and the cloud accounts outright, with the unrestricted right to hire another firm to continue the work, written into the contract before kickoff. Public money should never buy a system a public entity cannot take elsewhere.
It matters more here than in most categories because the records support an audited financial statement and have to remain producible for years. A firm that hedges on this question has answered it.
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.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
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.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
How long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
How much do developers charge per hour for accounting software work?
In the competing quotes clients share with Digital Heroes, established US and UK agencies charge $90 to $200 an hour for accounting and fintech work, senior freelancers $60 to $150, and offshore teams $25 to $60. We price accounting builds as fixed-scope milestones instead, because hourly billing on ledger work rewards slow debugging. Compare total quoted cost against your workflow list rather than comparing rates against rates.
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.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
Why do agencies charge for a discovery phase instead of quoting for free?
Because an accurate quote requires real work: mapping your workflows, finding the edge cases, and writing a specification, which typically takes 1 to 3 weeks and costs $2,000 to $10,000 at Digital Heroes depending on system complexity. You leave discovery owning a written spec and a fixed price you can take to any vendor, so the money is not locked into one agency. Free estimates are guesses, and the guess usually becomes your budget overrun six months later.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
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.
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 Ishaan.
Shopify Plus Tech Lead · Delhi · 2 posts on the site
Published · Last updated .
