Your Swansea books balance in Xero and still can't survive a Welsh Government grant audit without a spreadsheet
Custom accounting software, or more often a custom layer over Xero or QuickBooks, for a Swansea business runs £30,000 to £85,000 over 3 to 6 months. QuickBooks, Xero, and FreshBooks handle the GL, VAT, and Making Tax Digital well, and they have no real concept of fund accounting: which grant funded which cost, what's eligible, when the claim period closes, and whether a clawback looms. For South Wales businesses living on City Deal, SMART Cymru, and Innovate UK money, that gap is exactly what an audit tests, so the grant view ends up in a spreadsheet.
Your books are clean in Xero. VAT files through Making Tax Digital, the month closes, the accountant is happy. Then a Welsh Government or Innovate UK auditor asks you to show every cost charged to a specific grant, prove each was eligible, and reconcile it to the claim you submitted, and none of that lives in Xero, because Xero accounts for a business, not for a fund. So your finance lead rebuilds the grant view by hand from the GL, the emails, and the claim spreadsheets, every single time.
This is the gap between commercial accounting and fund accounting. Off-the-shelf tools track money by account and tax code; grant funders track it by award, eligible category, and reporting period, with rules about what counts and clawback if it doesn't. Mapping one onto the other is manual, error-prone, and exactly where audits find problems. The books being correct is necessary and nowhere near sufficient when a third of your funding comes with a fund accountant's expectations.
Why the usual tools struggle in Swansea
- Xero accounts for the business, not the fund, so grant-eligible spend is reconstructed by hand for every audit
- Claim periods, eligible categories, and clawback rules have no home in commercial accounting software
- Reconciling submitted grant claims to the GL is a manual, error-prone spreadsheet exercise
- Bilingual Welsh and English financial reporting for public-sector contracts isn't supported
What a custom accounting build changes
You go custom when fund accounting sits on top of commercial accounting and the two don't meet. A Swansea build adds a grant-and-fund layer over Xero or QuickBooks: it tags costs to awards and eligible categories, tracks claim periods and clawback risk, reconciles claims to the GL automatically, and reports bilingually. The custom case is efficient because you keep the tool that already does VAT and the ledger, and build only the fund-accounting intelligence that the off-the-shelf product was never designed to hold.
- A meaningful share of your funding comes from grants with eligibility and clawback rules
- Every audit means rebuilding the grant view by hand from the GL and spreadsheets
- You need bilingual financial reporting for public-sector contracts
- Claim-to-GL reconciliation is a recurring, error-prone manual task
- Your finances are purely commercial with no grant fund accounting
- Xero or QuickBooks plus your accountant already covers everything
- Grants are small enough that a spreadsheet is genuinely sufficient
- You have no bilingual or funder-reporting requirement
- A fund-accounting layer that tags every cost to its grant, eligible category, and claim period
- Automatic reconciliation of submitted claims to the general ledger, ending the spreadsheet rebuild
- Clawback-risk flagging before a cost becomes an audit problem
- Bilingual Welsh and English financial reporting for public-sector and funder requirements
- Keeps Xero or QuickBooks for VAT and the GL, so you build only the grant intelligence you lack
- You're building a layer, not a full ledger, so it depends on Xero or QuickBooks staying in place
- Grant rules change each funding round, so the eligibility logic needs ongoing maintenance
- Your accountant must understand both the commercial books and the fund layer, which is a coordination cost
- If grants are a tiny part of your finances, a spreadsheet is honestly cheaper than a build
The features that matter for Swansea
Swansea accounting: the full scope
Everything an accounting build here can cover: QuickBooks integration, Xero integration, invoicing software, bookkeeping software, financial reporting, accounts payable automation and accounts receivable.
Accounting pricing in Swansea: the real numbers
| Project scope | Typical cost | Timeline |
|---|---|---|
| Grant-and-fund accounting layer over Xero or QuickBooks | £30k to £55k | 3 to 4 months |
| Full fund-accounting platform with bilingual reporting | £60k to £85k | 4 to 6 months |
| Claim-to-GL reconciliation and audit-export module | £25k to £45k | 2 to 4 months |
From kickoff to launch: the schedule
Exactly what you get
The fund-accounting intelligence Xero and QuickBooks don't have, built over the ledger you keep. Concretely: cost tagging to grants, eligible categories, and claim periods, automatic claim-to-GL reconciliation, clawback-risk flagging, bilingual Welsh and English reporting, and an audit-ready export bundling evidence by funder. You keep your accounting tool for VAT and the GL. The grant data ties directly into your ERP, the funded hours from your HR software, and the project view in your project management software, so one funded-cost picture spans the business.
How to choose a developer in Swansea
Find a team that understands fund accounting, not just bookkeeping, because tagging a cost to an award with eligibility and clawback rules is a different discipline from closing a month. Ask how they reconcile a submitted claim to the GL and how bilingual statements are produced. A good partner keeps your Xero or QuickBooks and builds only the fund layer, the same way an honest ERP or internal tools team integrates what works rather than replacing it. Replacing your ledger should be a hard sell to you.
- !They propose replacing Xero entirely; ask why you'd rebuild VAT and the GL you already have
- !No grasp of fund accounting; ask how they tag a cost to an award and an eligible category
- !They skip claim-to-GL reconciliation; ask how submitted claims match actual spend
- !No bilingual reporting plan; ask how Welsh and English statements are produced
- !They quote without seeing a funding agreement; ask how they model eligibility and clawback
Teams investing in accounting in Swansea usually scope it next to warehouse management, field service management, erp, since these systems share data and budgets.
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
Can't our accountant just handle grants in Xero?
They can record the transactions, but Xero has no native concept of a fund, an eligible category, a claim period, or clawback risk, so the grant view gets rebuilt by hand each audit. A custom layer over Xero encodes those rules so the reconciliation and audit export are automatic. Your accountant still runs the commercial books; the layer handles the fund accounting Xero can't.
Should we replace Xero or build on top of it?
Build on top, almost always. Xero and QuickBooks do VAT, Making Tax Digital, and the GL well and cheaply, and rebuilding that is wasted money. The right shape is a grant-and-fund layer that reads from your existing ledger and adds the eligibility, reconciliation, and reporting intelligence. A developer pushing a full ledger replacement for grant reasons is usually overselling.
How does claim-to-GL reconciliation actually help?
It matches what you submitted to a funder against what you actually spent in the ledger, flagging mismatches before an auditor finds them. Today that's a manual spreadsheet exercise prone to error, and errors mean disallowed costs and clawback. Automating it protects the funding and saves the recurring finance time, which is often the clearest single payback on the build.
Do we need bilingual financial reporting?
If you hold public-sector contracts or report to Welsh Government bodies, bilingual statements can be expected or required, and building them in avoids manual translation. For a purely commercial business with no public-sector exposure it's optional and gets scoped out. As with the rest of the build, it's decided in discovery so you only pay where it genuinely applies.