Should you build or buy Government Tax & Revenue Collection?

Government tax and revenue collection software runs property and other tax assessment, billing, payment processing, and delinquent-collection workflows for counties, cities, and state agencies. Local governments buy or build it to bill taxpayers accurately, post payments to the general ledger, and pursue collections against statutes specific to their jurisdiction.

Buy, unless you are already one of the jurisdictions with a standing development team and a system that fits your statutes better than any package does. The proven builds are real but they are decade-long commitments, and collecting tax correctly earns you nothing beyond compliance. Spend negotiating effort on configuration rights, payment-processor flexibility and exit terms.

Build it, buy it, or bridge?

⚒ Build it
✓ Buy it
➔ Bridge
Cost shape
A handful of counties run homegrown systems, but Cook County's Tyler property tax contract, capped at $30 million in 2015, has needed contract amendments to stay on track.
Vendor systems like GenTax or RevQ run into seven or eight figures depending on jurisdiction size.
Buy the collections core; reserve custom work for assessment and data layers where local rules diverge.
Time to value
Homegrown systems at long-tenured jurisdictions took years to reach their current state, not a single project.
A configured vendor system typically runs a multi-year implementation timeline for this category.
Buy the payment and posting core now; extend assessment logic over a longer internal timeline.
Differentiation captured
Local assessment and data layers can reflect a jurisdiction's specific statutes more precisely than a package.
Collecting tax correctly earns a jurisdiction compliance, not a competitive edge over any other government.
The vendor owns payment processing and posting; the jurisdiction owns assessment logic on top.
AI feasibility today
AI can help with document classification and data entry, but no jurisdiction has built its collections core on AI.
Vendors are adding AI-assisted data entry and anomaly detection to configured tax systems, not replacing them.
Layer AI-assisted intake on a bought collections core; the statutory posting logic stays configured, not built.
Who it fits
Jurisdictions with a standing development team and decades of accumulated statute-specific tooling already in place.
Any county, city, or state agency billing and collecting tax without an existing homegrown system.
Jurisdictions wanting configuration on assessment specifics while buying payment processing and posting.

When building makes sense

A small number of jurisdictions have proven a government can build and run its own tax collections stack, and that record is worth taking seriously rather than dismissing. A survey of 398 governments by the Lincoln Institute and GFOA found homegrown collection systems running at 45 percent of mid-size counties and 43 percent of large counties, alongside warnings about the age of that code and the staffing needed to keep it running. The build case depends entirely on having that staffing already in place: a standing IT development team, decades of institutional knowledge about local statutes, and the budget to maintain a system for as long as the jurisdiction exists. What building does not offer is a competitive advantage. Collecting tax correctly is compliance, not differentiation, and a jurisdiction without an existing team and codebase is a poor candidate to start one now, however proven the pattern is elsewhere.

When buying makes sense

Buying is the safer default because the failure cases in this category are severe and well documented. Cook County's property tax contract with Tyler Technologies, capped at $30 million when it was signed in 2015, has needed contract amendments to stay on track, and that kind of overrun is not unique to one jurisdiction. Vendor pricing runs into seven or eight figures depending on jurisdiction size, a real cost but a bounded and comparable one against a custom build that can run for a decade before it is finished, if it finishes at all. The category is specific enough to each jurisdiction's statutes that a package alone rarely covers everything, so the practical approach is to buy a configured system for payment processing and posting, and negotiate hard on configuration rights and exit terms so local assessment rules can be layered on without being locked to one vendor's roadmap.

The desk read

Build-versus-buy analysis for Government Tax & Revenue Collection is being written. In the meantime, the framework that drives every B4 call is on the B4 Index page.

Representative vendors Avenu RevQGenTaxTyler CashieringAvenu RevQ. Jurisdiction sizeexisting ERP posting requirementsstatutory complexity tend to drive the choice more than feature lists

Frequently asked

Do any local governments actually run their own tax collection software?

Yes, more than the vendor pitch usually admits. A national survey of 398 governments found homegrown collection systems in use at 43 to 45 percent of mid-size and large counties, though the same survey flagged aging code and staffing pressure as ongoing risks at those jurisdictions.

Why do government tax system projects run over budget so often?

Because tax statutes are specific enough that configuration and integration work commonly exceeds what an initial contract scoped, and that gap tends to show up after a contract is signed. New Hampshire's FAST Enterprises GenTax contract, originally capped at $29.55 million in 2018, was later amended to a higher ceiling, and Cook County's Tyler Technologies contract shows the same pattern. The overrun risk is built into the work, not one jurisdiction's mistake.

What determines whether a jurisdiction should build instead of buy?

Whether it already has a standing development team and years of accumulated statute-specific code. Building without that foundation in place is a multi-year, multi-million-dollar commitment with no documented shortcut, and the payoff is compliance, not competitive advantage.

What are the main government tax and revenue collection vendors?

Representative vendors include Avenu RevQ, GenTax, Tyler Cashiering, Avenu RevQ. Jurisdiction size, existing ERP posting requirements, statutory complexity tend to drive the choice more than feature lists. B4 Pro includes the category score and the full vendor list.

The B4 Index scores every software category on two axes, strategic differentiation and AI feasibility, to classify it Build, Buy, Bridge, or Beware. See the full methodology.

More in Property Assessment & Tax Administration