Receipts at the bottom of a backpack, an envelope on the accountant's desk on the first of the month, a spreadsheet with mileage rates calculated by hand. In most Polish SMEs the "travel expense system" is still an envelope and a sales rep's good memory. There's a better way — one that doesn't require deploying a corporate juggernaut over six months.
Business trips look like a detail until you add them up. Ten field employees, each with an average of five expenses a month, each spending half an hour filling out forms — that's sixty person-hours a year on the sales side alone. Add the accountant: one or two hours a month tidying up, entering and verifying. And at the end of every quarter someone usually ends up hunting down a missing taxi receipt from Poznań.
Automating this is not AI magic. It's mostly a simple mobile app, OCR on receipts, and ERP integration. But the order matters — and there are a few places where it's easy to trip.
Where the time actually goes
Before you automate anything, it's worth writing the process out step by step. In most SMEs it looks like this:
- Employee gets back from a trip and throws receipts into an envelope (or a backpack, in the worse scenario).
- At month-end they fill out the trip form — by hand, in Word or Excel, calculating per diems and mileage.
- They bring the envelope to the accountant.
- The accountant checks receipts for VAT deductibility, enters items into the ERP (Comarch Optima, enova365, Subiekt), books the reimbursement.
- The reimbursement goes on payroll or a separate transfer.
Three steps are automation candidates: 1 (collecting receipts at the moment they're created), 2 (per diem and mileage calculations), and 4 (re-typing data into the ERP). Step 5 is already automated in every payroll system.
At one of our clients — a 22-person construction supervision firm in western Poland with nine engineers in the field — step 4 alone took the accountant an average of 5 hours a month. After deploying the setup described below, it dropped to under an hour. On the engineers' side: 25 minutes a month per person, down from 40. Total: roughly 45 hours reclaimed per year.
The mobile app that does the work
The heart of the solution is a phone app. The choice is wide and it doesn't have to be expensive — from off-the-shelf tools like Emplocja, Fakturownia Wydatki or Expensify, all the way to native modules in Polish payroll systems (enova365 has a decent trip module, Comarch ERP XL and Optima have add-ons).
The minimum set of features that actually matters:
- A photo of the receipt on the phone right after purchase. Not at month-end. A thermal-paper fiscal receipt fades within three weeks — after two months the paper is simply blank.
- OCR that extracts date, amount and VAT from the receipt. You don't need 100% accuracy — 80% is enough, the employee fixes the rest in two seconds.
- Mileage from geolocation — the phone measures the route, not a thumb on Google Maps.
- Expense category picked from a short list (fuel, hotel, meals, taxi, other). This drives how it posts in the ERP.
- A simple approval workflow — the manager approves from their phone with one tap, without logging into three systems.
What's not worth over-engineering: full structured OCR of VAT invoices. In business travel, 90% of documents are ordinary fiscal receipts without a tax ID — there's nothing to deduct VAT from, so full invoice OCR is wasted effort. Cost invoices are a separate topic we cover in our invoice OCR post.
ERP integration — the whole game
Without integration into the payroll system or the ERP, everything above saves the sales reps some time but the accountant is still re-typing everything. The whole difference is here.
Integrations look different in practice depending on the system:
- Comarch Optima — usually an XML/API import into the Cashbook and Trips modules. Deviations from standard per-diem rates need to be mapped explicitly.
- enova365 — the native trip module can consume data from an external app via SOAP. A separate conversation is how it posts to cost accounts (415-* in most SMEs).
- Subiekt GT / Nexo — the API is limited, in practice we usually go through the EPP file format and cleverly map "expense reimbursement" documents (ZK).
- Microsoft Dynamics 365 Business Central — modern REST API, integration is straightforward, but remember Polish tax localisation.
A rule that holds up: integrate one way. The mobile app collects and pushes into the ERP. Reverse sync (like reimbursement status) is rarely worth its price — the employee just needs a "processed" notification from the app.
Traps nobody mentions at the demo
A few things that only surface during rollout:
- Domestic vs foreign trips — foreign per-diem rates vary by country and change with a Ministry of Finance regulation. Your app must have a current table and a way to swap it in.
- Flat-rate lodging vs invoice — if the employee has no hotel invoice, they get a flat rate. The app has to handle these as mutually exclusive; otherwise the accountant checks everything by hand anyway.
- Foreign currency — a hotel in Berlin paid by card in euros. NBP exchange rate from the day before, conversion to PLN, VAT only on the deductible portion. This is the step where errors show up most often.
- Advances — the employee took a 2,000 PLN advance and spent 1,700. The app has to settle the 300 PLN owed back, not simply pay 1,700 again.
- Private car vs company car — mileage rate applies only to the private one. For the company car we reimburse actual fuel receipts. One employee with both cases (it happens) breaks naive logic.
- A reimbursement request for something that wasn't bought — we see it twice a day in practice. An app that photographs receipts at purchase time reduces this to near zero.
None of these are showstoppers. But every one of them has to be addressed deliberately before go-live — otherwise a month in the accountant is back in Excel because "this app can't do it".
What it actually costs
For a Polish SME with 10-30 field staff, realistic cost is:
- Mobile app licence — 15-40 PLN per user per month (Emplocja, Fakturownia Wydatki, Rydoo fall in this range).
- ERP integration — a one-off 5,000-20,000 PLN depending on the system and depth. Comarch Optima and enova365 are cheaper, Subiekt harder, Dynamics usually the simplest.
- Rollout and team training — 2-5 days of a consultant plus an hour of user training. Mobile apps are fairly obvious, the whole job is on the ERP side.
For the 22-person firm above, annual running cost is around 6,000-7,000 PLN, and payback comes in 10-12 months from accountant and sales time alone — without counting savings from "lost" receipts or reimbursement errors.
What's next
Travel expense reporting is one of the least glamorous processes in a company, which is exactly why it's such a good automation candidate — nobody is attached to "we've always done it this way". Return on investment is measurable, rollout fits in a quarter, and the team itself is happy not to carry envelopes of receipts around any more.
If you're wondering how this would look at your company — with your specific ERP and how your team actually works — let's talk. First call is half an hour and it's free.
Business trips look like a detail until you add up sixty person-hours a year of filling out forms.