blog·4 min read

What your till journal knows that your accounting cannot see

Turnover per turnover group, payments per method and VAT per rate with a ledger account, per day and per branch. What sits in a till's financial journal, and what you could build with it.

Our bookkeeper gets a little export from the till every week. Can the till
not tell us itself what came in per day, and where it should go?

In a lot of hospitality and retail businesses the turnover travels to the accounting in a weekly export. A file, a person, and a few days of delay. The till itself knows far more than what is in that file, and it knows it per day.

We read a till's financial journal on our own test till, a developer account with demo data. So: this provably works, but it is not running at a client yet. Here we describe what comes out of it and what you could build with that, and we are clear about which of those is only a possibility. For the clients where we do already work on the accounting side: the client stays anonymous and there are no amounts, prices or margins here.

What is in the journal

The financial journal request gives you three things at once, per day and per branch:

Turnover per turnover group. Not per item, but per group as the business set them up itself. In an off licence that could be wine, beer, spirits and other. That is exactly the level of detail you want in the accounting: four or five lines, not a thousand.

Payments per method, with a ledger account. Cash, card, gift card, an amount per method and the account it belongs on.

VAT per rate, with a ledger account. Per rate the base and the amount, and the account.

That last part is the difference between "a little export" and a journal entry. There is no translation step left. You do not only know the amount, you know where it sits.

An important pitfall: whether those ledger accounts are filled in depends on how the till was set up. On our test till the payment methods and the VAT rates do have an account and the turnover groups do not. So the first thing you check at a new business is not whether the integration works, but whether anyone ever attached the turnover groups to an account.

What else there is

Next to the journal there are a few requests about the same thing, at a different level of detail:

  • Per period, per turnover group. A financial journal over a range of days instead of one day.
  • Turnover per turnover group, per hour. You pass a date and ask for the spread across the day.
  • Turnover per item. For anyone who wants to know exactly what was sold.
  • Receipts per booking date. Per receipt the VAT per rate and the payment methods. Useful when you want to look up something the daily totals cannot show.
  • The cash counts. What was counted, separate from what the till thinks should be in the drawer.

Two things to watch with this kind of till API, and we ran into both while building. Prices come in cents, so as whole numbers. And quantities have their own field saying how many decimals belong to them. Fail to convert that and your turnover is a hundred times too high and your stock is just off. Beyond that, this API works with markers per kind of data, so a next call only fetches what changed since the last one.

What you could build with it

Here we move from what we measured to what is possible. None of this runs at a client now, and frankly we want to keep saying that until we have actually built it.

Pre-filling the cash book. Turnover per group, payments per method and VAT per rate are exactly the lines somebody now types into a cash book or an accounting package by hand. An integration that puts those lines ready per week saves the retyping, and with it the typos.

Seeing cash differences on the day itself. What the till thinks is in the drawer, next to what was counted. Right now that is often a conversation after the fact.

Card payments next to the bank. The till knows what was paid by card. The bank knows what was credited, usually a day later and with the fees deducted. Putting those two side by side finds differences that otherwise vanish into a monthly total.

Turnover per hour. Not for the accounting, but for staffing. A week broken down by hour is a different conversation about shifts than a weekly total.

Pouring losses and margin per product. What was sold against what was bought, per item. This is the heaviest of the five, because it depends entirely on a stock administration that is correct.

Common mistakes

Thinking the weekly export is the same as the journal. The export is a summary somebody chose. The journal is the source, per day, with the accounts attached.

Reading amounts as euros. Cents as whole numbers, and quantities with their own number of decimals. Check that on one day you can count by hand.

Assuming the ledger accounts are filled in. Look at how the till was set up before you build a journal entry that lands on empty accounts.

Fetching everything every time. Use the markers and only fetch what changed. Your till sits in a business and has to take payments there, not fill your report.

Building an integration before the daily totals add up. First put one day next to that day's till receipt, to the cent. If that does not work, you do not have an integration problem but a setup problem.

What a connected till can do is on connecting MplusKASSA. How we deal with the API itself is in what we learned from the MplusKASSA API. If you want something like this for your own business, have a look at custom software.

MK
Maarten Keizer

Founder of Invoker. Over twenty years in hosting, system administration and web development; builds the Claude hosting himself and tests everything on our own servers first.

about maarten