Aug 24, 2026
2 min read

Change Behaviour on VAT Prod. Posting Group - Prices Incl. VAT in v28.2

The VAT Product Posting Group on a G/L Account purchase line no longer keeps the Direct Unit Cost, which can lead to vendors being paid the wrong amount.
Share:
On this page
  1. The problem
  2. Old Behaviour
  3. New Behaviour
  4. Root cause
Change Behaviour on VAT Prod. Posting Group - Prices Incl. VAT in v28.2

A customer flagged this issue since v28.2 environment, and it’s worth knowing about if you use “Prices Incl. VAT” on purchase orders or purchase invoices.

The problem

When “Prices Incl. VAT” is set to true, BC has always kept the “Direct Unit Cost” for G/L Account lines when you change the VAT Product Posting Group. The total including VAT stays the same.

Old Behaviour

Old Behaviour

Here’s an example. Start with a G/L Account purchase line, VAT Prod. Posting Group set to VAT15:

  • Total Incl. VAT: 100
  • VAT Amount: 13.04
  • Total Excl. VAT: 86.96

Now change the VAT Prod. Posting Group to NO VAT. This used to give:

  • Total Incl. VAT: 100
  • VAT Amount: 0
  • Total Excl. VAT: 100

That’s the behaviour you’d expect. The total does not move.

New Behaviour

New Behaviour

But from the affected build, the same change now gives:

  • Total Incl. VAT: 86.96
  • VAT Amount: 0
  • Total Excl. VAT: 86.96

Root cause

According to the repo, this started with build w1-28.2.50931.51034. BC changed the condition for when it recalculates the direct unit cost to include G/L Account lines:

ShouldUpdateUnitCost New Behaviour

Before this, G/L Account lines were not part of that unit cost update logic in the same way. Now that they are included, the behaviour that used to hold for these lines breaks.

Why the changes? No idea. If you’re on v28.2 and you use “Prices Incl. VAT” with G/L Account purchase lines, it’s worth to be cautious about this, especially if VAT product posting groups get changed after the line is entered.

Sales Line logic remains the same.

Sales Line Logic

Related Posts