Capture at the receipt Accurate and complete reproduction Works without a connection

Custom app for receipts and documents with a retention obligation

Scanning paper may replace the original, but only if the digital copy is an accurate and complete reproduction. That is not an abstract requirement: it concerns the photo someone takes with a phone of a crumpled receipt on the passenger seat, and whether that photo will still be legible in seven years.

Appfront
Live

Why the moment of capture matters

The statutory tax retention period is seven years, and ten years for data on real estate. If you digitise paper, you may discard the original provided the digital reproduction is accurate and complete. That digital version then falls under the retention period itself and must be retrievable within a reasonable time.

This is where it goes wrong in practice. A receipt that only comes out of a coat pocket at the end of the month has faded, torn or gone missing. A photo taken at an angle and in the dark is not a complete reproduction. And a receipt that ends up as a loose image in a group chat is not a record but a message.

A receipt also contains more than an amount. For VAT, the supplier, the VAT number, the date and the itemised amounts all matter. If you only copy the total, you're left with a figure without the supporting evidence, and that evidence is exactly what gets requested in an audit.

For the people who collect the receipts, all of this is secondary. They're on the road, wearing gloves or standing at a counter. An app that asks for more than a few steps gets skipped, and then paper becomes the administration again.

How we build this

The core is the receipt at the moment it's still in someone's hand. Everything that happens afterwards is just processing what was captured then.

1
Recording in the moment

A photo with a timestamp and location, taken while the receipt is still complete and legible.

2
Checking legibility

The app checks whether the image is sharp and complete, and asks for a new capture if it isn't.

3
Adding the details

Supplier, date, amount and VAT, derived automatically as far as possible and confirmed by the user.

4
Passing it on to the finance team

The capture lands in the system where the retention period is monitored and the entry is booked.

What the app actually does

Capturing the receipt is the foundation. What else you need depends on how many people submit receipts and on your accounting package.

Photographing with checks

Straightening, cropping and judging whether the image is complete, because half a receipt is not a true representation of the original.

Reading data automatically

Supplier, date and amounts are suggested; the user confirms or corrects them.

Works without signal

On the road, in a car park or on a site with no coverage. The app works locally and syncs as soon as there's a connection.

Linking a receipt to a project

So costs end up in the right place straight away rather than being allocated afterwards.

Missing receipts made visible

A payment without a receipt is a gap in the evidence. It should be visible while it can still be resolved.

Evidence stays evidence

The original capture is kept alongside any edits, with the time and the person who made them.

Who we build for

Who submits the receipts differs per company. Four situations.

Fitters and field staff

They buy materials on the road and have the receipt in hand for five minutes before it disappears.

Drivers

Fuel, tolls and parking produce receipts that rarely make it to the office.

International trips and travel

Receipts in another language and currency need to be captured on the spot, because the context is gone later.

Accountants

They receive an envelope at the end of the month and have to turn it into a watertight set of accounts.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

Accounting packages change, cost categories shift and VAT rates are revised. Fields, categories and integrations should be configurable rather than hard-coded in the app.

React Native or native iOS and Android Offline storage with synchronisation Camera with cropping and straightening Automatic reading of receipt text Photo with timestamp and location Integration with your accounting package Cost centre or project on the receipt Roles for submitter, finance and management Retention of the original capture Audit trail on every change

Why Appfront

An incomplete photo is not a true representation

The requirement is a correct and complete representation of the original. We build that check into the app itself, not into a review afterwards.

The receipt is only complete for a moment

What comes out of a coat pocket at the end of the month is often illegible. The right moment is at the till.

Capturing must be faster than keeping

People who stuff the receipt in their pocket do so because it's quicker. The app has to beat that, not just match it.

We don't do your bookkeeping

The booking and the tax judgement stay with you and your accountant. We make sure the evidence is sound.

Security and privacy

Receipts show what your people bought and where, and therefore where they were. That calls for restraint: record what the accounts need and nothing more. We set access by role, show an employee their own submissions and the finance team the whole picture, and log who views what. Anything stored locally on the device is encrypted and can be wiped remotely if a phone is lost.

For this topic, the reliability of the moment is what matters. A capture that has later been swapped for a nicer photo is no longer a faithful reproduction of the original when it comes to an audit. We keep the original capture with its time, place and person, even when synchronisation happens later, and make any correction a visible one. How we handle security ourselves is set out in our information security policy.

Frequently asked questions about digitising receipts

You can, provided the digital version is an accurate and complete reproduction of the original. If you meet the conditions, you do not need to keep the paper. The digital version itself then falls under the retention period of seven years, or ten for real estate.

Because a partial, skewed or blurry capture is not a complete reproduction. In an audit, what counts is what can be read, and it has to remain legible seven years from now. That is why the app checks the image at the moment of capture, rather than someone discovering a problem months later.

Almost always. Receipts are generated at a till, in a car park or on a site with no coverage. The app works locally and synchronises as soon as a connection is available, preserving the original timestamp.

Then there is a gap in your supporting documentation. It should be visible while it can still be fixed, for example by requesting a duplicate. Discovering afterwards that receipts are missing is the most expensive scenario.

Largely, yes. Supplier, date and amounts are suggested based on the text on the receipt, after which the user confirms them. It is not fully automatic, and that is a good thing: the confirmation is the moment an error gets noticed.

In the accounting system, where the retention period is monitored and the entry is booked. We describe that side on our page about software for the tax retention obligation. See also our approach to building an app.

How many receipts never reach your accountant?

For one month, count the payments without a supporting receipt. If there are more than a handful, the gap is not in your accounting but in the route leading to it. We build this as a standalone app and as part of a broader app development project.

Edit content