Prices including tax: when the POS and Business Central disagree

Setup & tax · 8 min read

A shelf price in retail is the price the customer pays — tax in. Business Central, left to its defaults, treats prices as tax-out. When one side of an LS Central setup assumes tax-inclusive prices and the other side assumes tax-exclusive, every sale still rings up, statements still post, and the books are quietly wrong by exactly the tax rate. This guide shows what that looks like on posted sales, where the setting lives on each side, and how to fix the wrong side once.

What the mismatch looks like on posted sales

Work the arithmetic on a single item before touching any setup. An item priced at $100.00 tax-in, at a 13% HST rate, is really $88.50 of net sales plus $11.50 of tax (100.00 ÷ 1.13 = 88.50, rounded). Now post that same $100.00 through a setup that treats it as tax-exclusive:

The signatures are distinctive. In the mismatch row, the register total is higher than the shelf price — customers notice that one first. In the reverse row, the register total looks right, but posted net sales and tax are both understated: the store collects $100.00, owes tax calculated on a $100.00 net sale, and remits tax calculated on $88.50 instead. Either way, the error is never random. Every affected transaction is off by the same percentage, which is what makes this diagnosable: pull one posted sale, divide the tax by the net, and if the result is not your tax rate, an inclusion setting is wrong somewhere.

Where the setting lives on the Business Central side

Business Central decides price inclusion in two places, and Microsoft Learn documents exactly how they combine. On a sales document, the Prices Including VAT checkbox controls whether the Unit Price and Line Amount fields include VAT; by default they do not. That checkbox gets its default from the Prices Including VAT field on the Customer card. On the item side, prices can be set up to include or exclude VAT — and, per Learn, prices on the Item Card typically exclude VAT. The four combinations resolve like this:

Two practical consequences. First, there is no single "system" switch — the item flag and the document/customer default are independent, and a change to one without the other flips the result. Second, the conversion in the third row depends on the VAT percentage in the VAT Posting Setup for that business × product posting group combination. Business Central calculates VAT from those combinations — each one carries the VAT percent, calculation type, and the G/L accounts VAT posts to — so a wrong rate there produces the same symptoms as a wrong inclusion flag. Check both before concluding anything.

Where the setting lives on the LS Central side

Retail items are priced tax-in by design. The LS Retail item setup procedure has the user fill in the item's Cost and Unit Price Including VAT on the Retail Item Card, with the posting groups (Gen. Prod., VAT Prod., Inventory) defaulted from the retail product group. Receipts follow the same convention: fiscal receipt content includes the unit price for each item with VAT, plus total VAT for the transaction and for each VAT group.

Where exactly the field sits depends on your price experience. In LS Central 21.3, with Business Central's new sales price experience enabled, the Unit Price with VAT field left the Retail Item Card — it now lives under the item's Prices & Discounts / Sales Prices — and the old Retail Price Including VAT field on the Retail Item Card was removed. So a procedure written against an older version ("just edit the field on the item card") will send you hunting for a field that is no longer there. Confirm which price experience is enabled before following any screenshot-based instructions, including your partner's.

The Canada wrinkle: no inclusive-pricing switch to flip

Canadian stores get an extra constraint. Per a Dynamics Community answer on the Canadian localization, Business Central's North American tax engine calculates sales tax (GST/HST/PST) on top of net prices and does not support Prices Including VAT — the field is locked by design, and forcing inclusive values in through configuration packages can display inclusive totals while posting then fails. The supported approach in that localization is net prices in Business Central with tax calculated on top.

That shapes the LS Central design rather than breaking it: the customer-facing price stays tax-in at the shelf and on the POS, and the conversion to a net amount has to happen in the retail layer, using the tax posting setup — which is exactly why the VAT percent in the posting setup and the retail customer's defaults matter so much, and why the verification sale below is not optional. If your tenant is a VAT localization instead, the document-side switches in the table above are live and the fix is a settings change; in a Canadian tenant, treat any "just turn on Prices Including VAT" advice as a red flag.

Which side do you change?

• Shelf and POS prices are tax-in, posted totals are higher than the shelf price: the Business Central side is interpreting inclusive prices as exclusive. Fix the BC-side interpretation (item price flags, retail customer default, posting setup rate) — never re-price the store to match the error.
• Shelf prices are tax-in, totals are right, but net sales and tax post low: a net price was loaded into a tax-in field somewhere. Fix the price data or the flag on the side that was loaded wrong; the register total is not evidence that the posting is right.
• Only one tax rate is wrong: suspect the VAT Posting Setup percent (or the item's VAT Prod. Posting Group) for that rate before touching any inclusion flag. Inclusion errors hit every rate at once.
• Only new items are wrong: suspect the item template or product group defaults the items inherited — the same class of setup error covered in our posting troubleshooting checklist.

Fix procedure

1. Prove it on one transaction. Pick a posted sale for a single item at a known shelf price. Divide posted tax by posted net. If the result is not the tax rate, continue; if it is, the problem is elsewhere (start with posting groups).
2. Write down the intended truth. One sentence: "Shelf prices include HST" (the normal retail case). Every setting below gets checked against that sentence, not against each other.
3. Audit a sample of items. For 10–15 items across tax rates, compare the shelf price against the retail price (Unit Price Including VAT, or the Sales Prices entry under Prices & Discounts on newer versions). Note whether the stored price is the tax-in figure or the net figure.
4. Check the item flags and the retail customer default. On the BC side, confirm the Item Card price-inclusion flag matches how the stored price was loaded, and check the Prices Including VAT default on the customer record your retail sales post against.
5. Verify the rate. In VAT Posting Setup, confirm the VAT percent for each VAT business × product posting group combination your retail sales use. A correct inclusion setup with a wrong percent still posts wrong tax.
6. Change the wrong side only. Correct the flag, the default, the rate, or the loaded price — whichever step 2's sentence convicts. Do not edit posted history to make it agree.
7. Redistribute and wait. Retail item data reaches the terminals when it is exported/distributed to the POS. Make the change, let distribution run, and confirm a terminal shows the corrected price before selling on it.
8. Run one verification sale per tax rate. Sell one item at each rate, then check the resulting transaction and, after calculation, the statement tax lines (see the end-of-day routine) against hand arithmetic: net = shelf ÷ (1 + rate), tax = shelf − net.

What success looks like

The register total for a single item equals its shelf price to the cent. The posted transaction splits that total into net and tax that match the hand calculation for its rate, for every rate you sell at. Statement tax lines agree with the sum of the transactions, and dividing tax by net on any line returns the configured rate. If all three hold for a full day of trading, the mismatch is fixed — not just moved.

Tax configuration decides what you collect and remit. This article is general information about system setup, not professional tax advice — confirm rate and remittance questions with your accountant.