Manual expense reports, blurry receipts, approvals stuck in a manager’s inbox while they’re on annual leave, and a finance team re-keying every figure into Xero by hand. If that sounds like your month-end, you already know the off-the-shelf tools haven’t fixed it. Most generic apps ask you to bend your process around their software, and the per-user fee keeps climbing every time you hire, whether you use half the features or not.
Companies usually start looking for something better at a recognisable moment: spreadsheets stopped coping, an audit flagged weak approval evidence, the per-user bill jumped after a round of hiring, or a corporate card rollout left card statements and expense claims that won’t reconcile. Whatever the trigger, the underlying problem is the same. The software’s assumptions don’t match how your business actually spends and signs off money.
We build expense tracking software to fit how your business runs. Our team is UK-based, the software connects to the systems you already use, and you own it outright when we’re done. No per-user pricing, no multi-year contract, no annual renewal surprise. This page covers where generic tools fall short, what we build instead, how a project runs, and roughly what it costs.
Where off-the-shelf expense tools fall short
For a small team with simple sign-off, the mainstream apps are fine, and we’ll say so. The trouble starts as a business grows past that. Generic expense software is built for the average company, which means it isn’t built for yours. The recurring complaints we hear:
- Per-user pricing has a cliff. A monthly fee per head looks cheap at 30 staff and uncomfortable at 200. SaaS expense tools commonly run £4 to £15 per user per month, so headcount growth quietly turns into a five-figure annual line item with no extra value attached.
- The features you actually need sit behind a higher tier. Cost-centre hierarchies, budget tracking and proper approval rules are often locked into a “premium” plan, and enterprise tools can add several thousand pounds in setup and onboarding fees on top of the headline price.
- Approval routing is too rigid. Most platforms handle “manager, then finance” well and struggle with anything past it: conditional thresholds, matrix sign-off, delegation when an approver is away, or rules that stop a salesperson approving their own travel.
- OCR isn’t as clean as the demo. Receipt scanning is excellent on a flat, well-lit receipt and noticeably worse on a crumpled or faded one, so someone still corrects merchant, date and VAT by hand.
- It doesn’t talk to your other systems. If the link to your accounting, payroll or ERP system isn’t there, expenses get re-keyed and the categories rarely map cleanly to your GL codes.
- UK rules are an afterthought. Many of the best-known platforms are US-built, store data in the US, and treat HMRC mileage rates, VAT handling and Making Tax Digital as configuration rather than design.
- Enterprise contracts lock you in. The heavyweight option typically wants a two-to-three year commitment. If a new compliance requirement lands mid-contract, you’re stuck.
The result is workarounds, reimbursements that drag on for weeks, and month-end reports nobody fully trusts. Staff reconcile figures by hand and finance chases an audit trail that should already exist. The subscription is rarely the biggest cost. The lost time and the errors are.
What we build instead
We build the software around your business rather than handing you a box to squeeze into.
Built around your process
We map your approval hierarchies, spending policies, cost-centre structure and reporting needs before anyone writes code. Conditional routing, matrix sign-off, delegation cover for absent approvers, escalation when nothing is approved within a set window: the workflow matches your org chart, not the other way round.
Pay for it once
No per-user fee. You buy it, you own the source code and the data. Your headcount grows; your software cost doesn’t follow it up.
Connects to what you already run
Native links to Xero, QuickBooks Online and Sage so approved claims post to the right GL codes without re-keying, plus connections to payroll and HR for employee and cost-centre data. We can also handle corporate card feeds for transaction matching, and legacy ERP or finance systems that no SaaS connector touches.
UK rules handled by design
Statutory HMRC mileage rates, VAT identification and split receipts, Making Tax Digital and an immutable audit trail, all built in from the start rather than bolted on. UK data residency where you need it.
Only the screens you use
No feature bloat. Claimants see the few fields that matter for their workflow, which is usually what drives adoption in the first place.
Room to grow
Need per-diem rules, project allocation or a new integration next year? We add them. No migration, no re-platforming, no waiting on a vendor roadmap.
Support from people here
From rollout onwards, our UK team is around during UK working hours when you need them.
Features and modules
Every project is a bit different, but these are the parts that usually go in:
- Mobile receipt capture. Staff photograph a receipt and submit the claim from their phone, iOS or Android, or email it in. Nothing piles up in a shoebox until month-end.
- Receipt OCR. Merchant, date, amount and VAT pulled off the image automatically, with a confidence score so finance knows which scans to double-check rather than reviewing every one.
- Policy checks. Submissions that break your spending rules, a missing receipt, an over-limit meal, a missing project tag, get flagged at the point of entry rather than discovered weeks later.
- Approval workflows. Routing by amount, department, cost centre or project code, with conditional thresholds, delegation cover and escalation built around how your sign-off actually works.
- Accounting sync. Connection to Xero, QuickBooks Online and Sage, with your expense categories mapped properly to GL accounts so the posting is correct, not approximate.
- Mileage tracking. Distance calculated at HMRC statutory rates (45p per mile for the first 10,000 business miles, 25p after), with optional GPS logging and consent recorded at onboarding.
- Corporate card reconciliation. Card transaction feeds matched automatically against submitted claims, with unmatched items flagged for follow-up.
- Cost-centre and project allocation. Spend tracked against budgets, including splitting a single claim across more than one project or cost centre where the work calls for it.
- Reporting and dashboards. Spend by department, project, person or supplier, budget versus actual, and approval cycle times, with drill-down to the individual receipt.
- Reimbursement processing. Batch-approve claims and trigger payment, with clear status for each employee on what’s submitted, approved and paid.
- Multi-currency. Conversion and reporting for expenses incurred abroad, with rates handled so the figures reconcile.
- Audit trail and access control. An immutable log of who submitted, approved, returned and paid each claim, role-based permissions, encryption in transit and at rest, and UK data residency where required.
How a project runs
We build in phases so you get something working early rather than waiting months for everything at once.
Discovery and planning (2-3 weeks)
Workshops with your finance team, approvers and a few claimants to document your expense policy, your approval hierarchy, your cost-centre and GL structure, and the things that currently annoy everyone. We also pin down what has to integrate, since that’s usually the part that drives timeline and cost.
First release (8-12 weeks)
The core that earns its keep on day one: receipt capture and OCR, the approval workflow, accounting posting, reimbursement and basic reporting. We run progress reviews along the way, and a pilot with one team or department before a wider rollout so issues surface at small scale.
Later phases (typically 6-10 weeks)
The pieces that aren’t needed on launch day: mileage tracking, corporate card reconciliation, advanced approval rules, budget alerts, custom dashboards and any further integrations. Splitting these out keeps the first release on schedule and lets you spread the spend.
Testing, deployment and migration
User acceptance testing, then go-live. Data migration is usually light, the employee and cost-centre master and current GL mapping, though moving historical claims off a legacy system takes longer. We keep your old process running until the new one is proven, rather than switching it off on day one.
Training and support (ongoing)
Separate sessions for claimants, approvers and finance, since each needs something different, plus documentation and UK support after launch.
A focused first release runs around 8-12 weeks; a full build with mileage, card reconciliation and reporting is roughly 4-7 months depending on integration complexity. You get a progress update every week.
Cost and ownership
Custom development is a larger cost upfront than a subscription, and a much smaller one after that. A few things to weigh up honestly:
- A custom build is a one-off project cost plus modest ongoing hosting and optional support. SaaS is a per-user fee that rises every time you hire, before any setup fees, premium-tier upgrades or per-integration charges are added on.
- The crossover point depends on headcount and feature scope. Below roughly 50 staff with simple sign-off, SaaS is usually the cheaper and more sensible choice. For larger teams, or where you need complex approvals, project allocation or legacy integration, custom tends to come out ahead over a three-to-five year horizon.
- You own the source code and the data, so there’s no vendor lock-in, no two-or-three year contract, and no surprise renewal price hike. If you ever want to take the work in-house or to another developer, you can.
- The project has a scope and a price agreed at the start, instead of a bill that creeps up with every new hire.
We won’t pretend a custom build is right for everyone. We’ll model it against your headcount and your current SaaS spend in a free consultation, and tell you plainly if subscription software is the better answer for where you are now.
Sector use cases
The data entities are similar everywhere, employees, expenses, receipts, approvals, cost centres, mileage logs, an audit trail, but the workflow on top of them changes a lot by sector. A few examples:
- Construction. Field teams submit material, fuel and plant costs from multiple job sites. Each claim is tagged to a job-site code, allocated to the project cost centre, checked against the purchase order, and posted to the project GL, so site managers see budget versus actual without waiting for month-end.
- Healthcare. Mobile clinicians travel between patient sites and need mileage logged at HMRC rates with the audit-ready trail an NHS trust or CQC inspection expects. Per-diem rules vary by location and overnight stays, and approval can route through a clinical lead.
- Legal and accountancy practices. Billable expenses are matched to a client and matter code, checked for billability, and flow through to the billing module for the client invoice, removing the manual hop between time-tracking, expenses and billing.
- Manufacturing and supply chain. Procurement spend, freight, supplier visits and trade shows is matched against purchase orders, with three-way matching of PO, receipt and invoice, and spend analysed by supplier and product category.
- Charities and nonprofits. Spend is allocated to grant and restricted-fund codes, approvers confirm grant-rule compliance, and donor-reporting comes straight out of the system rather than being assembled by hand.
- Professional services and consulting. Project-level expense tracking tied to client recharges and timesheets, so what gets billed back to the client is accurate and traceable.
- Field services. Mobile-first capture for technicians, including reliable submission when they’re working somewhere with poor signal.
Whatever the sector, the compliance rules, the terminology and the workflow get built in from the start rather than worked around afterwards.
Common Questions About Custom Expense Tracking Software
When does a custom build make more sense than Expensify, Zoho or Concur?
Per-user SaaS works well below roughly 50 staff with a single currency and a simple manager-then-finance sign-off. A custom build earns its place when the per-user fee starts to scale painfully, when your approval routing is genuinely complex (cost-centre sign-off, conditional thresholds, delegation), when you need to allocate spend to projects or grants, or when you have to integrate with a legacy ERP or HR system that no SaaS connector covers. We will tell you honestly if SaaS is the better call for you.
How does custom development cost compare to SaaS?
A custom build is a larger cost upfront and a small one after that, typically modest hosting plus optional support, while SaaS is a per-user fee that rises every time you hire. The crossover point depends on headcount and feature scope, but for larger teams or feature-heavy requirements custom usually wins over a three-to-five year horizon. We will model both against your numbers before you commit, rather than promise a fixed payback.
What's the typical development timeline?
A focused first release covering receipt capture, approvals and accounting posting usually takes around 8-12 weeks. Adding mileage, corporate card reconciliation, advanced approval rules and reporting takes the full project to roughly 4-7 months. We give you a detailed schedule once requirements are agreed and a progress update every week.
Can you integrate with our accounting and HR systems?
Yes. We build native integrations with Xero, QuickBooks Online and Sage so approved expenses post to the correct GL codes without re-keying, and we connect to HR or payroll systems for employee, cost-centre and manager data. We can also integrate corporate card feeds for transaction matching, and legacy ERP or finance systems that sit outside the usual connector lists.
Will it handle HMRC and UK compliance?
It is built for UK finance teams. That means statutory mileage rates (45p per mile for the first 10,000 business miles, 25p after), VAT identification and split receipts so VAT returns reconcile, and an immutable audit trail that records who submitted, approved and paid every claim. Receipt images and approval records can be retained for the six years HMRC expects, with GDPR-compliant handling and UK data residency.
How do you handle updates and changes?
You own the source code, so there is no vendor lock-in and no forced upgrade. We offer optional support packages for changes and new features, but you are also free to make changes in-house or bring in another developer. A new policy rule, expense category or integration is usually a small piece of work, not a six-month wait on someone else's roadmap.
Do you provide training for our team?
Yes. We train each group separately, since their needs differ: claimants need around an hour on capturing and submitting receipts, approvers need a couple of hours on routing and policy checks, and the finance team needs longer on administration, GL posting and month-end. Documentation and post-launch UK support are included.