Development Agency
Contact Sign in Get a project quote

Service

Expense tracking software development

For owners of small businesses, bookkeeping services and operators of several small entities who need transactions categorised their way, receipts captured on the spot, statements imported and matched by rules, and a clean export to their accountant, designed around how the money actually moves through the business.

Get a project quote See the software package

The problem

What goes wrong today

Where it usually starts

A bookkeeping service looks after thirty-two small clients: cafés, a few tradespeople, two consultancies and a landlord with six flats.

  • Each client sends receipts in their own way: a shoebox once a quarter, photographs in a messaging app, forwarded emails, and one who writes them on the back of the bank statement.
  • The bookkeeper downloads statements from four different banks in four different layouts and pastes them into a spreadsheet per client, then categorises every line by hand, applying rules she keeps in her head: this supermarket is stock for the café but personal for the landlord.

Where it gets harder

Mileage arrives as a text message with a town name.

  • Recurring items such as rent, software subscriptions and loan repayments are retyped every month and occasionally mistyped.
  • At quarter end the accountant asks for a summary by category and a list of anything unusual; producing it means a day of filtering per client.
  • Nobody can tell the café owner, in the middle of the month, how much he has spent on stock against what he planned, because the answer only exists once the quarter is closed.
  • The business of recording has swallowed the business of advising.

Scope of the service

What the build covers

A custom income and expense tracking build normally covers the transaction record and the ways money gets into it. Income and expense entries carry a date, an account, a category from a list you define, an amount, a counterparty and attachments, with a receipt photographed on a phone at the point of spending. Statement import reads files from each bank in the layouts you receive, with rule-based categorisation that learns the counterparty-to-category mapping per business and leaves the uncertain lines for review. Multiple accounts and currencies are supported through configuration, with each entity keeping its own account list and categories. Recurring entries create the expected rent, subscriptions and repayments on schedule and match them when the statement line arrives. Periodic summaries and category reports show income, spending and the difference by week, month and quarter, with drill-down to the entries and their receipts. A mileage log records journeys with purpose and distance against a rate the business enters. Export produces a spreadsheet and an accountant pack of the period’s entries, attachments and unresolved items. Simple budgets per category raise alerts when spending approaches the limit the owner set.

We work through the business with you first: whether it is one entity or many, which banks and file layouts are involved, who enters what and who reviews, which categories matter and whether they must map to the accountant’s chart, what the accountant wants at period end and whether any entries need approval before they count. Each becomes a named workflow stage in the scope document.

Deliberately out of scope

  • Double-entry accounting, which stays with the accounting platform the business or its accountant uses and receives data through integration
  • Any tax calculation, return or submission
  • Financial advice of any kind. The system records what the business spent and received and labels it the way the business asked
  • The figures and what is done with them remain the responsibility of the business and its accountant

When the scope grows

Scoping scenario

A bookkeeping service wants one login across thirty-two client businesses, a per-client rule set, a review queue where the bookkeeper approves uncertain lines before they appear in the client’s own view, and a quarter-end pack per client sent to three different accountants in their own layouts. The multi-entity review queue and per-accountant export layouts make this a custom build, and the scope document says so plainly.

Deliverables

What you receive

  • Discovery notes from mapping how money is recorded, reviewed and handed to the accountant today
  • A written scope document naming each stage from capture to export, the category list, the import rules, the review step and what is left out
  • Designs of the capture screen, the review queue, the statement import and the period report on phone and desktop
  • The build, deployed to your hosting or ours, with categories and rules configured from your real data
  • Migration of transaction history, categories and attachments from your spreadsheets and apps where worth keeping
  • Training for the owner or bookkeeper and a short guide for anyone who only captures receipts
  • Handover material and full ownership of the source code and your data

Process

How a project runs

Each stage maps onto the project view in your client panel. Durations are set in your proposal, never on this page.

  1. Onboarding

    Access to a sample of your statements in each bank layout, your current spreadsheets, your category list and the format your accountant asks for.

    Project stage: Onboarding

  2. Planning

    Discovery with the owner or bookkeeper and, where possible, the accountant; entities, accounts, categories, import rules, review steps and the export pack are written into the scope document.

    Project stage: Planning

  3. Design

    Receipt capture and mileage designed for a phone in a van or a kitchen; import, review and reports designed for a desk.

    Project stage: Design

  4. Development

    Built in layers: entries, categories and attachments first, then statement import and rules, then recurring entries and budgets, then reports and export.

    Project stage: Development

  5. Client review

    One full period of real statements and receipts is run through the system alongside the old method and the two are compared line by line.

    Project stage: Client review

  6. Revisions

    Changes from the review are made and re-checked against the scope document.

    Project stage: Revisions

  7. Ready for launch

    History migrated and opening positions checked by the bookkeeper, the accountant pack verified against a real quarter, alerts tested, launch checklist signed off.

    Project stage: Ready for launch

  8. Delivered

    The business records, reviews and exports on the new system; hosting and maintenance continue under their own agreement if taken.

    Project stage: Delivered

Integrations

Commonly integrated

Systems this kind of business usually asks us to connect. Each integration is confirmed during discovery; none is assumed.

  • Accounting platforms, receiving categorised entries and attachments for the period
  • Bank feed providers as an integration opportunity where the business holds the necessary access, with file import as the baseline
  • Receipt and document capture services for text extraction from photographs
  • Cloud storage for attachments so receipts sit in the business’s own files
  • Card payment and point-of-sale providers for income settlement files
  • Email providers for forwarded receipts and period summaries
  • Mapping services for mileage distance between recorded places

How we would approach it

Worked example

Concept demo

A bookkeeping service with thirty-two clients and three accountants

In this scoping scenario, a bookkeeping service wants a single login across thirty-two client businesses, each with its own accounts, categories and import rules; a review queue where statement lines the rules could not place wait for the bookkeeper before they appear in the client’s own view; receipt capture by each client from a phone; and a quarter-end pack per client sent to one of three accountants, each of whom wants a different layout. The scope we would propose: an entity model with per-entity configuration and a bookkeeper role spanning all of them, rule sets that learn per entity, a review state on every imported line with a queue sorted by client and age, client logins limited to their own entity, and export templates per accountant selected on the client record.

The custom route is needed because a review workflow across many entities and per-accountant export layouts go beyond the single-business, single-export structure of the package.

Concept demo: a scoping scenario written to show how we would approach the work. It is not a delivered client project.

Pricing

What affects the price

Every proposal is priced on scope. These are the factors that move it most for this kind of build.

  • Number of entities, accounts and currencies to configure
  • Banks and file layouts to import, and whether a bank feed provider is in scope
  • Depth of the categorisation rules and whether a review or approval step is required
  • Receipt capture needs, including text extraction from photographs
  • Reports and budgets required, and how many export layouts the accountants need
  • Accounting platforms and storage services to connect
  • Volume and condition of transaction history and attachments to migrate
  • Hosting choice: your own hosting or ours

Start from a package

Income expense tracker package

Categorised income and expense entries with receipt photos, bank statement import with learning rules, recurring entries, budgets with alerts, mileage log, period reports and an accountant export for sole traders and small businesses.

Custom build
View the package

FAQ

Frequently asked questions

How do you decide whether we need a custom build or the package?

During discovery we compare how your business records and reviews money against the income and expense tracker package. If one business, file-based import, a single category list and one accountant export cover you, we quote for the package. Many entities under one bookkeeper, review queues before entries count, or export layouts per accountant point to the custom route.

Does the system do our accounts or tax?

No. It records income and expenses with categories and receipts and produces summaries and exports. Double-entry accounting, tax calculation and any return or submission stay with your accounting platform and your accountant, and the figures are your responsibility and theirs.

Can it connect directly to our bank?

Statement file import is the baseline in every build. A live bank feed through a feed provider is an integration opportunity we scope separately, because it depends on the provider, the bank and the access the business holds.

What happens to a statement line the rules cannot categorise?

It is held for review with the closest matches suggested. Once someone chooses a category the rule can be saved, so the same counterparty is placed automatically next time. Nothing is reported until it has a category.

Who owns the system afterwards?

You do. The source code and your data are handed over at delivery. Hosting and maintenance are optional and separately agreed, and you can move the system to another provider.

Get a project quote for income and expense tracking software

Answer a few questions about your business, your current systems and what should change. We reply with a clear, competitive proposal.

Get a project quote Discuss a partnership
Get a project quote

Cookies on this site. Strictly necessary cookies keep the site working. Allow first-party analytics so we can see which pages lead to enquiries. No advertising, no third-party trackers, no personal data; you can change this at any time on the cookies page.

Manage preferences