Skip to Content

Odoo 19 Point of Sale: cash in and cash out on the right account, no reclassifying

November 16, 2026 by
Odoo 19 Point of Sale: cash in and cash out on the right account, no reclassifying

A waiter takes €40 out of the till for tips, the owner deposits €500 at the bank, someone buys lemons at the shop across the street. In the Odoo 19 Point of Sale, all three moves end up in the same place: the suspense account of the cash journal. Here is why, what the standard really allows, and the free module I wrote so that each reason lands directly on its own account.

1. The problem: everything lands on the suspense account

The question comes up regularly on the Odoo forum, asked by Odoo 19 Online users: “cash in and cash out in the Point of Sale debit a suspense account, and I can’t find anywhere to say which expense account to use for which reason”. The result: either the accountant fixes the entries one by one, or someone builds an automated action that reads the label and changes the account, and breaks as soon as a cashier types “tip” instead of “Tips”.

I checked the Odoo 19 code (point_of_sale/models/pos_session.py, methods try_cash_in_out and _prepare_account_bank_statement_line_vals): the cash line is created without a counterpart account, and the reason is only free text pasted into the label. With no account, Odoo uses the journal’s suspense account. It is not a regression: Odoo 18 did exactly the same.

💡 Key takeaway

The reason typed at the register has no accounting meaning in Odoo: it is a label. The account is always the same one, the suspense account.

2. What the standard offers (and its limits)

The usual workaround uses accounting reconciliation models: a rule spots “Tips” in the label and suggests the right account. It works, but the reconciliation screen that applies them is an Enterprise feature, the rule depends on what the cashier typed, and the entry stays wrong until someone reconciles it.

The most frustrating part is that Odoo already knows how to do it. Cash differences found when a session is closed go straight to the journal’s loss or profit account, account taxes included. The mechanism exists; it simply isn’t wired to cash in and cash out.

💡 Key takeaway

A reconciliation model fixes things afterwards. The right reflex is for the entry to be born correct, at the moment the money leaves the drawer.

3. The solution: predefined reasons, each with its own account

The POS Cash In/Out Reasons module adds a list of reasons under Point of Sale › Configuration. For each one: a name, a direction (in, out or both) and an account. Optionally: taxes (the amount typed is then tax included) and an analytic distribution. A reason can be limited to some registers: the terrace does not necessarily need the same ones as the counter.

At the register, habits don’t change: open Cash In/Out, type the amount, and the reasons show up as large buttons, filtered by the chosen direction. One tap is enough; the text box is still there for a detail (“Anna and Tom”). The entry is posted directly to the reason’s account. A free text reason, with no button, keeps the standard behaviour.

For a Belgian brasserie or shop, this covers everyday cases: tips paid back to staff, bank deposits (internal transfer account), change fund, a small purchase at the corner shop with its deductible VAT.

💡 Key takeaway

The cashier picks a reason, the accountant has nothing left to reclassify. And a misspelt reason no longer exists: there is nothing left to type.

4. What is checked, and what it costs

The chosen reason reaches the server as an identifier: it is checked again on every move. It must be active, belong to the company of the register, be allowed for this register and match the direction of the move. Otherwise nothing is created. Access rights stay Odoo’s: only those who could already make a cash in or out can do so.

I measured the cost: 4 more SQL queries per move (51 instead of 47), and that figure does not change whether you have 1 reason or 50. The entry reuses the method Odoo already uses for closing differences: nothing reinvented on the accounting side.

The trade-off to know: reasons are loaded when the register opens. A reason added during service appears after a page reload. And like any module, it cannot be installed on Odoo Online: you need Odoo.sh or your own hosting.

💡 Key takeaway

Checked on the server, fixed cost, and the accounting follows the path Odoo already takes for cash differences.

⚔️ The Match: standard Odoo 19 vs POS Cash In/Out Reasons

Criterion Standard Odoo 19 With the module
Counterpart account Suspense account, always The reason’s account
Entering the reason Free text One button, plus a note if needed
VAT and analytic Fixed by hand Set per reason
Reasons per register No Yes
Edition Reconciliation screen: Enterprise Community and Enterprise, free

Behaviour checked in the Odoo 18 and 19 Community source code, module tested on Odoo 19 Community and Enterprise.

The Verdict: the entry should be born right, not fixed

The module is free, under the LGPL-3 licence: POS Cash In/Out Reasons.

Does your Odoo register leave other entries to reclassify every month? I review your setup as part of an Odoo audit.

Request a Free Audit
Odoo 19 removed the expense report: how to group your expenses again