QuickBooks closes the month, then your finance team rebuilds project margin in a spreadsheet
When a Reading services firm uses QuickBooks or Xero for the ledger but rebuilds project revenue and margin in spreadsheets every month, custom accounting tooling closes the gap. Expect £45k to £110k over 3 to 6 months, with automated project recognition live in about 10 weeks.
QuickBooks, Xero and FreshBooks are excellent general ledgers and poor project-accounting engines. A Thames Valley consultancy billing a mix of fixed-fee, T&M and retainer work can't get accurate revenue recognition or per-project margin out of them, so finance exports everything into a spreadsheet and rebuilds the numbers by hand each month.
Across multiple entities it gets worse: consolidation is manual, intercompany entries are error-prone, and the management accounts the board sees are a finance contractor's three-day reconstruction. The accounting software does the statutory job and leaves the management-accounting job to a spreadsheet.
Where the off-the-shelf tools fall short
- Project revenue recognition is rebuilt in a spreadsheet every month
- Per-project margin isn't available without manual reconstruction
- Multi-entity consolidation and intercompany entries are manual and error-prone
- Board management accounts depend on a contractor's three-day rebuild
Custom accounting: what Reading teams actually get
Custom accounting tooling sits beside Xero or QuickBooks and automates exactly what they can't: project revenue recognition across contract types, per-project margin, and multi-entity consolidation. Statutory filing stays with the proven ledger; the management-accounting layer becomes a system instead of a spreadsheet, so the board sees real numbers in days.
Feature priorities for Reading teams
What we build under accounting in Reading
Digital Heroes builds the full accounting stack for Reading teams. Typical engagements cover accounts receivable, general ledger, expense management, custom accounting software, QuickBooks integration and Xero integration.
- Finance rebuilds project revenue in spreadsheets monthly
- Per-project margin needs manual reconstruction
- Multi-entity consolidation is manual and error-prone
- Board accounts depend on a multi-day rebuild
- You're a single entity with simple, product-style revenue
- Xero or QuickBooks meets your real needs
- You don't have complex project recognition
- You can't keep an accountant involved in a build
The honest cost picture for Reading
| Project scope | Typical cost | Timeline |
|---|---|---|
| Project-recognition layer over Xero or QuickBooks | £45k to £75k | 3 to 4 months |
| Full management-accounting and consolidation system | £80k to £110k | 4 to 6 months |
| Multi-entity consolidation only | £35k to £60k | 2 to 4 months |
Timeline: what happens, and when
Exactly what you get
A management-accounting layer that automates what Xero and QuickBooks can't: project revenue recognition across your contract mix, real per-project margin, and multi-entity consolidation. Your statutory ledger stays put and trusted; the spreadsheet that finance rebuilds every month retires; and the board gets reliable numbers in days, not a contractor's three-day reconstruction.
How to choose a developer in Reading
Insist on a team with an accountant in the room, because recognition logic that fails an audit is worse than a spreadsheet. Ask to see a recognition engine they shipped and how it handled a year-end. Keep Xero or QuickBooks as the statutory ledger and integrate tightly rather than replacing it, and budget for ongoing maintenance as tax rules shift. This work overlaps heavily with ERP (Enterprise Resource Planning) and BI (Business Intelligence), so check they understand both.
- Automated project revenue recognition across contract types
- Real per-project and per-pod margin without manual rebuilds
- Multi-entity consolidation and intercompany handled automatically
- Faster, more reliable management accounts for the board
- Statutory filing kept with your trusted ledger, integrated cleanly
- You own the recognition logic and its audit defensibility
- Integration with the ledger must be rock-solid to avoid drift
- An accountant must stay involved through the build
- Tax-rule changes mean ongoing maintenance
- !No accountant on their team, ask who validates the recognition logic
- !They want to replace Xero, ask why not keep it for statutory filing
- !No audit trail, ask how a recognition journal is traced and reversed
- !They ignore intercompany, ask how multi-entity consolidation works
- !They quote before discovery, ask what contract mix they're assuming
Most Reading teams pricing accounting end up comparing notes on warehouse management, field service management, erp too; the systems share one data spine.
Rohan advises mid-market and enterprise teams on ERP, CRM and custom software, and has led delivery on dozens of business-software builds.
Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
Should we replace Xero or QuickBooks?
Usually no. Keep it as the statutory ledger it's good at and build a project-accounting layer on top for recognition, margin and consolidation. Replacing a proven ledger adds compliance risk for little gain, whereas the management-accounting layer is where the real pain lives.
How is this different from custom ERP?
It overlaps. A custom ERP includes accounting plus operations; an accounting-software build focuses narrowly on the recognition, margin and consolidation layer over your existing ledger. For many Reading firms the accounting layer is the right first step, expandable into full ERP later.
Will the recognition logic survive an audit?
Yes, if it's built with an accountant and keeps a full audit trail. The engine applies methods you and your auditor agree, posts journals automatically, and records every adjustment, so the numbers are defensible rather than a manual estimate.