Integrations·4 min read

Deposits in MplusKASSA and Exact Online

A deposit belongs in its own turnover group and its own article. What we proved on a test till about automatic deposits, and why your accounting rejects a whole purchase order.

Deposits have to show up separately on the receipt and separately in the
accounting. Set it up properly on the till and see what a purchase order does.

A deposit is not turnover. You hold on to it until someone brings the packaging back, and then you give it away again. As long as it sits in your till and your accounting as just another article, your turnover looks higher than it is and the deposit balance quietly drifts.

We worked this out for a drinks wholesaler with a liquor store: an MplusKASSA till next to Exact Online. The trial ran on our own test till. The client stays anonymous and there are no amounts, prices or margins here.

Below is how to set it up, and the three things that do not work the way you would hope.

How to set it up on the till

A deposit gets its own turnover group. In MplusKASSA a turnover group has a type, and there is a type for refundable deposits. Set your group to that type and the deposit line appears on the receipt and in the daily totals separately from your normal turnover. That is exactly what your accounting needs later, because a deposit belongs on its own ledger account and not on a turnover account.

A deposit gets its own article. One article per type of packaging, with its own rate, inside that turnover group. Not a surcharge inside the product price, because then you can never see it separately or give it back.

Put a button on the till screen. This sounds like a poor substitute for automatic deposits, and it is, but it is what works. Why that is, is in the next section.

What does not work: adding the deposit automatically

The till API has a field for linking articles together, so that ringing up a product automatically brings a deposit article along. That is exactly what you want.

The field is accepted when you create or update a product. You get no error. Ask for the product again afterwards and the link is gone, and no deposit appears on the receipt.

We checked that on the test till: created the product with the link, read the product back, link gone, then rang up two receipts with several units of that product. No deposit line, both times. So the conclusion is not "we did something wrong" but: through the API that link is not stored.

Hence a button of its own on the screen. Whoever is at the till rings up the deposit separately. Less elegant, and it does add up.

What your accounting does: reject the whole order

Now the other side. You want to put an order with your supplier into Exact Online as a purchase order, with the deposit included, because your supplier charges it too.

Exact then rejects not the single line with the deposit article, but the entire purchase order, if that deposit article has no supplier article at that supplier. So you do not get an order with a line missing; you get nothing.

That is hard to spot, because you usually create the deposit article once and use it with several suppliers. With the first supplier you created the supplier article, with the second you did not, and the order that fails is the second one.

The rule we settled on: a deposit article has a supplier article at every supplier whose orders it appears on. Check that before you send the order, not after.

A deposit does not belong in a warehouse transfer

Third point, and the easiest one to get wrong by accident. When you move stock from one warehouse to another, for example from your wholesale stock to the shop, the deposit does not come along.

A deposit is not stock. It is an amount you are holding. Put it in a transfer and you are moving something that is not anywhere, and after that none of your warehouses reconciles with your accounting any more.

Two traps in the till API

The list of turnover groups is replaced wholesale. Send a new turnover group by passing only that group, and the groups you did not pass disappear. We had that once, and afterwards checkout failed on the till itself, because articles pointed at a group that no longer existed. Always send the full list, including the groups you are not changing.

Updating a product means sending the whole product back. If there is a custom field for deposits that you do not send or do not know about, the till refuses the change. Read the product first, change what you want, and send the rest back untouched.

Common mistakes

Hiding the deposit inside the product price. Then it is not a deposit any more, it is turnover, and you cannot give it back.

Setting the turnover group to an ordinary type. Then deposits sit among your turnover and your turnover reporting is wrong.

Assuming an API field works because it does not error. Always read back what was stored, and then ring up one item to see what lands on the receipt.

Using one deposit article with several suppliers without a supplier article per supplier. Then a whole order fails, not one line.

Including deposits in a warehouse transfer. After that your stock no longer reconciles.

Updating a list in the till API with only your own entry. The rest disappears, and you find out at the till.

What an integration on the till can do is on connecting MplusKASSA. More quirks of that API are in what we learned from the MplusKASSA API and in five ways to break your till. If you want this set up for your own shop, 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