Skip to content

Changelog 2026-10-07

Products now store their purchase price both excluding and including tax, with the VAT between them, and every product field says which side of the price it belongs to.

A product has always had a purchase price excluding tax. It now also stores the price including tax and the VAT applied to it, just as it does for the sale price:

  • taxExcludedPurchasePrice — the purchase price excluding tax
  • taxIncludedPurchasePrice — the purchase price including tax
  • purchaseVat — the VAT between them

Send whichever purchase price you have. The one you send is kept, and the other is derived from it at purchaseVat: send taxIncludedPurchasePrice: 120 with a 20 % purchaseVat, and the product stores 100 excluding tax. If you send both, taxExcludedPurchasePrice is kept. On update, a product keeps both prices and its VAT unless you send one of them.

margin, markupRate and marginRate are always computed on the purchase price excluding tax, whichever one you send. A company that charges VAT recovers it on its purchases, so it is not part of the cost. A company outside VAT has no purchase VAT, so both prices are the same amount: what it actually paid.

Existing products were filled in for you:

  • For a company that charges VAT, purchaseVat is the product’s sales VAT when that is a real rate, and 20 % otherwise. taxIncludedPurchasePrice is derived from the price excluding tax you already had.
  • For a company outside VAT, purchaseVat is empty and taxIncludedPurchasePrice equals taxExcludedPurchasePrice.

No price excluding tax, margin or rate changed.

Product fields now say which side of the price they belong to, so the sale and purchase prices read as pairs. Each old name is deprecated and carries the same value as its replacement:

Deprecated Use instead
taxExcludedPrice taxExcludedSalesPrice
taxIncludedPrice taxIncludedSalesPrice
purchasePrice taxExcludedPurchasePrice
vat salesVat

Nothing changes if you do nothing. The old names are still returned, with the same values, and still accepted on create and update. When a request sends both names, the new one is used.

taxExcludedPrice and taxIncludedPrice only arrived in the 2026-09-14 changelog. If you have just moved to them from unitPrice, your code keeps working: move to the new names at your next change, not before.

The same renaming applies to the product embedded in a document line (lines[].product). The lines’ own fields are unchanged: a line’s purchasePrice is its cost excluding tax, and keeps its name.

When a company changes VAT regime, Altoviz now offers to update its product prices:

  • Starting to charge VAT: add the VAT on top of the sale prices or include it, and turn the purchase prices it entered, which included its suppliers’ VAT, into a price including tax with the cost excluding tax derived from it. Only products still without VAT are changed.
  • Returning to the franchise: keep either what customers paid or the price excluding tax as the single price, with no salesVat; and make the purchase price including tax the cost, with no purchaseVat, since that VAT can no longer be recovered. Only products still carrying VAT are changed.

If you sync products into Altoviz, expect their salesVat, prices and purchaseVat to change on that day, and read them back rather than assuming your copy is current.

Documents are not changed: drafts, open quotes and recurring invoices keep the regime they were created under, and an invoice created from a quote inherits the quote’s. If you create invoices through the API from a quote or a recurring invoice, check liableToVat on the result after a company changes regime.