Skip to main content

Dev Station Technology

Finance teams

Finance software with the audit trail built in

Approvals, payments records and reporting where every change has a name and a time on it. Our own finance runs on a customised Odoo ERP we built.

1 Sep 2025Date the failure to prevent fraud offence took effect
250Employees: one of three size tests for a large organisation
6Principles in the Home Office guidance
40%Efficiency gain in three months on our own Odoo build
What this is

The control is only as good as the record of it

A reasonable procedure that nobody can evidence does not help when it is tested. Finance software has to show who approved what, on which data, and what happened when something looked wrong.

Where we have proof

our own customised Odoo ERP, which unified sales, projects, invoicing, HR and expenses (an internal Dev Station build)

Where we have not yet

We have no published finance case. We say so on the first call and show the closest work.

Services

What we build for finance teams

Approval workflows

Spend, payments and journals routed to the right person, with the decision recorded.

Audit trail

Who changed what and when, held where nobody can quietly edit it.

Invoicing and billing

Generated from the work recorded, so the invoice matches what was done.

Management reporting

Live figures from the ledger, ready before month end.

ERP and bank integration

The record has to reach the ledger and the bank, in both directions.

Role and access models

Separation of duties built into who can raise, approve and release.

Rules

What the failure to prevent fraud offence asks of an organisation

These come from the Home Office guidance on the offence, published on gov.uk.

In force from 1 September 2025An organisation can be liable if an associated person commits a fraud intending to benefit it. Source: Home Office, failure to prevent fraud guidance, gov.uk.
Large organisations onlyAn organisation is large if it meets two of three tests: more than 250 employees, more than £36 million turnover, more than £18 million total assets. Source: same guidance.
Six principlesTop level commitment, risk assessment, proportionate risk-based prevention procedures, due diligence, communication including training, and monitoring and review. Source: same guidance.
The organisation has to show itThe defence is that the organisation had reasonable prevention procedures in place, so the evidence of those procedures matters. Source: same guidance.
Case study

Our own ERP, built and run in house

Customized Odoo ERP built by Dev Station for its own operations
Internal build, Dev Station

Streamlined operations with a customised Odoo ERP

We replaced disconnected spreadsheets with a self-hosted Odoo ERP covering sales, projects, invoicing, HR and expenses. The case page records a 40 percent gain in operating efficiency within three months.

40%Operating efficiency gain in three months
Technologies in the build abovePostgreSQLDocker
Who we build for

The teams who call us

Finance directors at growing companies

Teams whose controls grew out of spreadsheets and email.

Controllers and shared service centres

Where approvals pass through many hands and the trail has to survive.

Software firms with a finance product

Teams adding approvals or reporting to what they ship.

Compliance and internal audit teams

Teams who need the evidence of a control when an auditor asks.

Related reading: accounting software, banking software, financial services software and business software.

FAQs

What buyers ask first

Do you have a finance case?

Not yet published. We say so on the first call and show the closest work, which is our own Odoo ERP, which is an internal build.

Do you give advice on fraud prevention procedures?

No. That advice comes from your lawyers and compliance team. We build the approvals and records they specify.

Can you extend Odoo or build beside it?

Both. We customised our own Odoo and can also build a service next to it when the module is the wrong tool.

Who owns the code and the cloud accounts?

You do, from the first commit. Repositories and cloud accounts stay in your name.

Send us one approval path

Thirty minutes with the engineers on how a payment gets approved today and what the record shows afterwards.

Let's Talk