Tax Applicable is the switch, and most items have it off — transcript

Play this as a presentation — one slide per step, with the same narration. Every word of every step is on this page.

This lesson is for whoever at GadgetSphere owns the item master and has been asked why an invoice came out with no tax line. In about thirteen minutes you will know which single tick decides that, which document types honour it, and why a tenant can be full of correctly configured tax codes that nothing uses.

Step 1 — Find the tick that gates everything else

After this step you will know what you are actually looking at on the item’s Tax tab. The tab holds a country and four sets of three fields — a code, a type and a rate — for input tax, output tax, output withholding and input withholding. Above all of them sits a single tick labelled Tax Applicable. It is not a label or a hint. It is a gate. With it off, none of the twelve fields below it is copied onto any document line, however carefully they are filled in. The screen does not say so and does not grey anything out.

Reference: Doc Item Maintenance — Tax tab

Step 2 — Weigh how many items have it off

After this step you will know this is the normal state rather than an oversight. Across every tenant on the platform, most active items have the tick off — roughly seven hundred thousand of them, against about four hundred and thirty thousand with it on. That is not a misconfiguration. Plenty of what a retailer sells is genuinely untaxed, and plenty of item records exist for stock movement rather than for selling. But it does mean that when somebody says the tax codes are set up, the honest question back is how many items are actually inside the gate.

Reference: Doc Item Maintenance — Tax tab

Step 3 — Spot the item that shows a code it will never use

After this step you will know a specific trap. About fourteen hundred items across five tenants carry an output tax code with the tick off. Somebody chose that code. It is visible on the screen. It is in the exports. And it does nothing, because the gate above it is shut. This is the one configuration that is genuinely misleading rather than merely quiet: an auditor checking that items carry tax codes would pass every one of them. Checking the tick is a different query from checking the code, and only the first one tells you anything.

Reference: Doc Item Maintenance — Tax tab

Step 4 — Learn which documents take the item’s tax at all

After this step you will stop expecting tax defaults everywhere. Which of the item’s triples applies is decided by the document’s type. A type whose name contains sales takes the output triple. A type containing purchase takes the input one. Everything else takes neither — no code, no type, no rate from the item at all. That covers a long list: delivery orders, stock transfers, consignments, jobsheets, packing orders, payment and receipt vouchers. Most of them should not carry tax, so the rule is right. It is worth knowing because it is silent, and because a custom document type that names neither word inherits the same silence.

Reference: Doc Item Maintenance — Tax tab

Step 5 — Notice what the drop-down will and will not offer

After this step you will know why a code you created does not appear. The line-level tax drop-down filters the list by the tax type string. On a sales document it keeps only the three Malaysian output types. On anything that is not a sales document it keeps codes whose type contains the words input or purchase. A blank entry is added at the top so a line can be deliberately left untaxed. One consequence is worth naming: a VAT sales code for Singapore, Thailand or Indonesia matches neither filter on a sales invoice, so it never appears there, while its purchase twin does.

Reference: Tax Configuration — Lifecycle and effects

Step 6 — Connect the tick to what the regulator is told

After this step you will see why a screen about stock affects a tax filing. An item inside the gate, on a sales document, with a rated code, produces a tax amount. An item outside it produces nothing, and a line with no tax amount is submitted to the regulator as tax not applicable. So the tick is not only about whether an invoice prints a tax line — it decides, through the amount, what kind of tax the regulator is told applies. Before any of it can post, the company’s default output and input tax account links must exist with a subledger, or the tax line is dropped and the document fails to balance.

Reference: Tax Configuration — Lifecycle and effects

How the steps fit together

    flowchart TD
  s1["Step 1 — Find the tick that gates everything else"]
  s2["Step 2 — Weigh how many items have it off"]
  s3["Step 3 — Spot the item that shows a code it will never use"]
  s4["Step 4 — Learn which documents take the item's tax at all"]
  s5["Step 5 — Notice what the drop-down will and will not offer"]
  s6["Step 6 — Connect the tick to what the regulator is told"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  

Check yourself

Three to five questions on what you just heard. Every correct answer links to the page that makes it correct, so you can check the source, not just the mark.

Next: Six rows in Tax Configuration that are not tax codes · Back to the series · Play this as a presentation