Custom app for receipts and invoice approval on the go
As long as VAT returns are filed quarterly, a receipt can sit in a dashboard compartment for a month. With per-transaction reporting, that is too late: the counterparty has already reported the transaction and your side is still missing. Capturing therefore shifts from the month-end close to the moment itself, and that moment is almost never at the office.
Why the purchasing side hurts first
The ViDA package, adopted by the Council in March 2025, introduces e-invoicing in line with EN 16931 and digital reporting per transaction. In the Dutch timeline, domestic e-invoicing starts on 1 January 2030 and domestic digital reporting on 1 January 2032. For intra-Community transactions, the date is 1 July 2030.
Attention almost always goes to the outgoing invoice, because that one is yours. The purchasing side is harder, because someone else decides when something arrives and in what form. Once both parties report per transaction, a comparison emerges: your report next to your supplier's. Discrepancies that are now smoothed out within a quarter will then become visible.
That is exactly where the practical problem lies. Part of your purchasing flow does not originate in a system but in a hand: a receipt from the wholesaler, a proof of delivery on the building site, a fuel card, a parking ticket. Those documents travel along in a van and surface weeks later. That worked as long as the closing cycle set the rhythm.
How we build this
The document is the unit here, and the moment of capture is where you gain. If a receipt comes in on the same day, the rest is just administration.
We look at who receives which receipt and what currently happens to it. At most companies that means three or four places, each with its own habits.
Take a photo, link it to an order or project, done. Every extra step costs usage, and an app nobody uses doesn't move the problem, it doubles it.
Amount, supplier and date are suggested and confirmed by a person. Processing automatically without confirmation produces errors that later have to be reported openly.
The app is an input channel, not a second set of books. What is captured flows through to the system that your tax return and reporting come from.
What the app actually does
The app does little, and that little has to fit into a single action. Which components you need depends on how your purchasing flow arises.
Capturing a receipt on the spot
A photo with timestamp and location, linked directly to an order, project or cost centre. A receipt that arrives the same day is an administrative task; a four-week-old receipt is a search.
Recognition with confirmation
Amount, date, supplier and VAT are suggested and confirmed by the user. Suggesting works; booking automatically without checking produces exactly the errors that will soon have to be reported openly.
Approving on the move
A manager sees what needs reviewing and approves or rejects with a reason. As long as approval is tied to a desk, one person's diary determines your turnaround time.
Working fully offline
Capture continues without a connection and syncs later, with each document showing whether that succeeded. In a car park or on a building site, that is the normal situation.
Missing documents made visible
An order without a receipt, a receipt without an order, an amount that differs from the purchase order. The system shows the gap while there is still something you can do about it.
Passing data to your accounting
What is captured goes to your ERP or accounting system via integrations. The reporting side itself is covered on ViDA software.
Who we build for
Where documents originate differs greatly from company to company. Four situations.
Construction and installation
Materials are delivered to the building site and the receipt goes to the site manager. Linking it to the right project matters more here than the receipt itself, because without a project, post-calculation is a guess.
Service companies with van stock
Technicians buy from the wholesaler on the road. The receipt travels in the van and surfaces at the next clean-out, usually after the close. See also the field service app, which this component fits into.
Transport and distribution
Fuel receipts, toll receipts and ferry tickets arise on the road and across borders. For cross-border traffic, it also matters that the counterparty reports in another member state.
Offices with lots of small expenses
Travel expenses, subscriptions and one-off purchases are small individually and large in total. What goes wrong here is not the amount but the missing proof of purchase.
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
The app is an input channel for your accounting, not a standalone system. What it captures ends up in the source from which your tax return and reporting are built.
Why Appfront
The month-end close loses its purpose
With reporting per transaction, collecting documents after the fact is too late. We move capture to the moment the document is created.
Documents are created where there is no signal
Car parks, building sites, warehouses. That is why offline is the starting point rather than the emergency scenario.
Recognition proposes, it doesn't decide
We have a person confirm. An error that is posted automatically and reported afterwards costs more than the second it takes to confirm.
No second set of records
The app writes through to your existing package via integrations. Two places holding the same receipt are guaranteed to drift apart.
Security and privacy
A device holding purchase documents contains more than it seems: supplier names, prices, project names and sometimes customer details on a delivery note. These devices go out on site and are shared between crews. That is why we tie permissions to the user rather than the device, store offline only what has not yet been processed, and make sure a lost device can be disconnected remotely.
On the administrative side, a requirement applies that becomes stricter with ViDA. The original image of a receipt is your supporting evidence and must be retained unaltered alongside the data extracted from it, for the retention period set by the tax authority. That is why we store the image exactly as captured and record who confirmed or changed which value. A system that only knows the final booking cannot show where it came from during an audit. How we handle security ourselves is set out in our information security policy; reports from outside go through our CVD policy.
Frequently asked questions about the receipts and approval app
ViDA moves VAT information from a periodic return to a report per transaction. That removes the room in which missing documents are filled in later. A receipt that only surfaces at period close is then too late, and at most companies a share of these documents originates outside the office.
Recognition proposes the amount, date, supplier and VAT, and this works well on clean receipts. We have a person confirm rather than posting automatically, because an error that has been reported once has to be visibly corrected. Confirming takes a second and prevents that.
Yes, that is the starting point. Photo, integration and confirmation all happen locally and sync as soon as there is a connection, with each document showing whether it succeeded. Without this, you would miss precisely the places where most loose receipts arise.
Usually, yes, and that is preferable to a second app on the same device. A field service app already has the login, the projects and the offline capability; document capture is added as one more component.
No, and that is deliberate. The app is an input channel; bookkeeping, returns and reporting stay in your existing package. What we build is the bridge between the moment a document is created and the system where it belongs.
They are precisely the reason to start early. Different VAT rates, different notations and a counterparty reporting in another member state. We capture the original image and have the user confirm it, so that the finance team can later determine how the transaction should be treated.
This app is about the incoming side and about documents created outside the office. The ViDA software is about the outgoing invoice under EN 16931 and about reporting per transaction. They share the same accounts but not the same users.
That depends on the number of document types, whether approval is involved and which package it is integrated with. Capture with a photo and an integration is usually usable quickly; recognition and the approval flow cost more. We give a substantiated estimate after the discovery phase.
Receipts arriving too late?
Check how many purchase documents were more than two weeks old when they were processed in your last close. That number is about to become your problem. We build this as a standalone app and as part of a broader custom app or custom software project.