Rounding differences on statements: where they come from and where they post

Daily operations · 9 min read

Every statement difference gets called "rounding" sooner or later, usually right before someone posts it and stops thinking. That is a mistake, because three different things land on a statement wearing the same small-numbers disguise — and only one of them is actually rounding. Name which one you have before you chase it: they have different causes, different posting destinations, and very different ideas of "small."

Three kinds of rounding land on a statement

Cash penny rounding is the Canadian case. The Government of Canada phased out the penny — the Royal Canadian Mint stopped distributing it on February 4, 2013 — while the cent remains the smallest unit for pricing. Only cash is affected: payments by cheque or electronically settle to the cent exactly. The federal guideline rounds the final cash total, after GST/HST and any fees are calculated, to the nearest five cents: totals ending in 1 or 2 cents round down, 3 or 4 round up, 6 or 7 round down, 8 or 9 round up, and 0 or 5 do not move. The government's own worked example: a $4.92 after-tax total is paid as $4.92 by card, and as $4.90 in cash.

Calculation rounding is Business Central's precision machinery doing arithmetic. Rounding precision is configured, not improvised: for local currency, the General Ledger Setup page carries the invoice rounding precision and type, and currency cards carry amount, unit-amount, and invoice rounding precision for foreign currencies. Microsoft Learn's invoice-rounding documentation uses exactly the retail-relevant example — local custom can require amounts rounded to a value divisible by 0.05 — and notes that when an invoice is rounded, an extra line carries the rounding amount. One caution: that extra-line mechanism belongs to BC sales and purchase invoices. LS statements do not use invoice rounding lines; statement differences travel the tender route described below, and confusing the two sends people hunting for lines that will never exist.

Declaration differences are the impostor. The drawer was counted, the count did not match the transactions, and the gap has nothing to do with rounding rules — a short count, a change error, an unrecorded paid-out. These post through the difference machinery, and they are the ones worth hunting, because unlike rounding they do not cancel out.

Where rounding and difference amounts post

On the statement itself, a difference is the gap between two fields on the statement line. Counted Amount is filled automatically from the tender declaration entries when a declaration was performed on the terminals; for tender types marked Counting Required the counted amount must be entered, and for tenders that do not require counting the field simply takes the Trans. Amount. The maximum gap allowed is a setup decision: the Max. Diff. to Allow Post. field defines the largest difference between counted amount and Trans. Amount a line may carry into posting, and the system warns when a line's counted amount is zero while its Trans. Amount is not. The standing pre-posting check from the statement procedure still applies: before posting, the Difference Amount should be 0.00 on every line and Counted Amount should equal Trans. Amount — a counted amount of 0.00 can be filled with the Trans. Amount manually, which is a declaration shortcut, not a fix.

When a difference does post, its destination is set per tender: the Tender Type Card's Difference G/L Acc. is the account that receives the difference between Counted Amount and Trans. Amount for that tender's statement lines, and card setups copy the tender type's difference account automatically when the card number is filled in. If you have never deliberately chosen those accounts, differences are still posting somewhere — finding out where is step one of the hunt below.

Under Safe Management, declaration differences get a fuller audit trail. When a declaration posts with a shortfall — the documented use case is a cashier whose physical count is $5.00 below the expected total built from the opening float plus the shift's recorded transactions — Safe Management automatically creates a Trans. Difference Entry (table 99001700) recording the transaction and receipt numbers, the signed amount (negative for a short, positive for an overage), the staff ID, the terminal, the date and time, and the statement code. Managers review them on the Trans. Decl. Diff. Entries page (99001876), drill through to the original POS transaction, and then decide: write the difference off to the account in the entry's Diff Account No. field, charge it back to the cashier, or keep it open for investigation. A rounding difference worth its name rarely needs that meeting. A recurring one does.

The rounding ceiling: how big can honest rounding get?

Penny rounding has a hard mathematical ceiling, and computing it takes one minute. Each cash transaction moves by at most 2 cents — that is the largest adjustment in the guideline's table. So a day's total cash rounding can never exceed 2 cents × the number of cash transactions. Three hundred cash sales cap the day's rounding at $6.00 in the absolute worst case — and that worst case requires every single total to land on a maximum-adjustment ending in the same direction. Real days mix endings, the guideline is symmetric (four endings round down, four round up), and the expected net over any busy week is close to zero. Two conclusions follow, and they are the whole decision framework for this problem:

• |Difference| > 2¢ × cash transactions → it is not penny rounding. Full stop. Treat it as a declaration or counting problem.
• Difference within the ceiling but always the same direction, week after week → also not honest rounding. Symmetric rounding does not trend. A steady one-direction drift means something systematic: a tender rounding where it should not, change given against unrounded totals, or a count that is consistently taken wrong.

Hunting a small persistent difference

1. Split the difference before analysing it. Pull a run of statements (two weeks is a good sample) and total the Difference Amount by tender, by terminal, and by day. Rounding lives on the cash tender only — card and other tenders settle to the cent — so a difference sitting on a card tender was never rounding. A difference on one terminal or one staff member's lines is a local habit, not a system setting.
2. Apply the ceiling test. For the cash tender, compare each day's difference against 2 cents × that day's cash transaction count. Over the ceiling even once: reclassify the problem as declaration/counting and go to the difference entries. Under the ceiling but one-directional: keep hunting, with suspicion on procedure rather than setup.
3. Verify every shift actually declared. A Dynamics Community thread on phantom statement differences gives the standing advice: check that a tender declaration was done for all shifts and that the declarations replicated to head office — a missing declaration manufactures a "difference" out of nothing, and posting then sends it to the tender's difference account as if it were real.
4. Read the difference entries, not just the statement. Work the Trans. Decl. Diff. Entries for the period: amounts, signs, staff, terminals, times. Patterns are visible here that statement totals hide — the same terminal every Friday, shorts only on closing shifts, round amounts (a $5.00 short is a count or a float problem; rounding never produces round numbers).
5. Follow the money to the G/L. Review postings into each tender's Difference G/L Acc. over the same period. If the account balance grows steadily in one direction, the difference is a cost of doing business that nobody chose — whatever its cause, it is now large enough to assign to an owner and a fix.
6. Then, and only then, adjust setup. If the pattern convicts a setting — a non-cash tender rounding, a Max. Diff. to Allow Post. so generous that real problems post silently — change it, and note the date. A difference that stops the day a setting changes was the setting.

Fixes by cause

• True penny rounding, within ceiling, directionless: no fix exists because nothing is broken. Leave it visible in the difference account and review the balance monthly; it should hover, not climb.
• Rounding applied to non-cash tenders: remove it. The federal guideline rounds cash only; electronic payments settle to the cent, and rounding them creates differences with no legal basis and no ceiling logic.
• Threshold too loose: set Max. Diff. to Allow Post. to a deliberate small value per tender, so a difference beyond honest rounding stops the posting and gets a human decision — that field exists precisely to be that tripwire.
• Declaration gaps: fix the close routine, not the statement. Every shift declares, declarations replicate before calculation, and counted amounts are entered for Counting Required tenders instead of defaulted — see the end-of-day routine.

What success looks like

Daily cash differences sit comfortably inside the computed ceiling and change sign across days. Card and other non-cash tenders show no differences at all. The difference G/L accounts explain themselves: small, directionless balances that a month-end glance can clear. And when a difference does exceed the ceiling, posting stops at the threshold instead of waving it through — the system surfaces the problem on the day it happens, while the shift, the staff, and the transactions are still identifiable in the difference entries.

General information on system setup and reconciliation practice — not accounting or professional advice. Confirm difference-account treatment with your accountant.