Case studies

A full financial year in 7 and in 10 hours. Roughly 70 and 50 percent less time than the previous manual bookkeeping.

Two users told us their times. Both imported and posted a complete 2025 financial year in PilotOS. Here are the numbers — and their limits.

Case 1 · financial year 2025

Vita-doerr

Business with ongoing bookkeeping
previously Taxpool – posted by hand

One year of bank transactions
fully imported and posted to the journal
2 hrs
Bookkeeping for 2025
whole year, using the history match
7 hrs
Compared to manual bookkeeping
owner's own estimate, not timed by us
−70 %

3,500 postings in the year, previously entered by hand in Taxpool. Two hours for the bank import, seven for the complete books — at 70 percent less time that implies a baseline of about 23 hours: roughly 150 postings per hour before, 500 now. The baseline is calculated, not measured.

The owner has approved publication of these figures.

Case 2 · financial year 2025

Christine N.

Retail · sole proprietorship
natural person, owner is a certified merchant (Kauffrau) · name abbreviated, permission pending

Whole year 2025
imported and posted, bank to entry
10 hrs
Compared to before
user's estimate, not timed by us
approx. −50 %

4,000 postings, previously Taxpool as well. Ten hours for a full year including import and posting — at about 50 percent less time that implies roughly 20 hours before: 200 postings per hour instead of 400. Also calculated, not measured.

For scale: 4,000 postings a year is roughly 330 a month and about 17 per working day. That is the everyday reality of a retail shop — register, incoming goods and bank run in parallel.

No handover to a second program, because receipts, bank and journal live in the same database.

What these numbers do not say

  • They are self-reported. Both users noted their own times. We did not stopwatch them.
  • The percentages are the users’ own estimates against their previous manual bookkeeping in Taxpool. They imply baselines of roughly 23 and 20 hours — that is arithmetic, not a stopwatch. We show the calculation because it can be checked; we do not sell it as a measurement.
  • The posting volumes are user statements as well. 3,500 and 4,000 postings — we have not counted the journals ourselves.
  • This is not the tax adviser's time. How long the accountant reviews afterwards is not part of it.
  • Two cases are not a statistic. Different document volumes. Foreign currencies or several clients take longer — we will not claim otherwise.
Questions

Questions about the case studies

Who measured these times?

The users themselves. Both noted their own hours; we did not stopwatch them and have no screen recording. That is why the numbers are labelled as self-reported on this page and not presented as a benchmark.

Why only two cases?

Because we publish only what exists. Two real cases with names and figures are worth more than twenty invented ones with stock photos — and anyone who invents one case has no reason to be trusted on the other numbers.

What would make the numbers stronger?

A measured baseline: how long the same work took before, and how many transactions were involved. Both would turn a percentage into a comparison. We are collecting that.

Can I talk to the two users?

Not through us. We do not pass on contact details of customers. The names and the figures are published with permission; the contact stays with them.

How to read a case study like this

Ask three questions, in this order: Who says it? What was the baseline? What was measured, and by whom? The first question is answered by the name on the card, the second by the previous software and the posting volume, the third by the sentence “calculated, not measured”.

A vendor case study normally fails the third question. It reports a percentage without saying whether the clock was running. Ours says so explicitly, which makes the figure weaker and the page stronger: you can check what stands behind it, and you know exactly where your own judgement has to start.

What you cannot see here: whether the result holds for your document volume, your account structure or your industry. Two retail and service businesses are a beginning, not a promise.