Six rows in Tax Configuration that are not tax codes — 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 has opened Tax Configuration, found six rows called 01 through 06 with no rate and no type name, and wondered whether they are the answer to the not-applicable problem. In about thirteen minutes you will know what they are, why they are harmless, and how to tell a working list from a stranded one.

Step 1 — Look at the six rows

After this step you will recognise them on sight. Open Tax Configuration in any tenant and among the tax codes you will find six with codes 01, 02, 03, 04, 05 and 06, descriptions reading sales tax, service tax, tourism tax, high-value goods tax, sales tax on low value and not applicable, a country of Malaysia, a rate of zero, status active, and a blank Tax Type Name. They are the tax authority’s list of taxable types, parked in the tax-code table by a platform changeset. Every tenant has exactly six. Nobody has added one and nobody has taken one away.

Reference: Tax Configuration — Lifecycle and effects

Step 2 — Confirm that nothing reads them

After this step you will know they cannot hurt you. Their stored type is the word einvoice, and every place that reads tax codes filters on that word. The sales side of the line drop-down keeps only three output types, and einvoice is not one. The other side keeps anything containing input or purchase, and einvoice contains neither. The withholding drop-down keeps rows with a withholding type, and these have none. The item’s Tax tab offers only the eight Malaysian types. So they appear in this listing and in no other screen on the platform. The only thing that reads them is the listing you are looking at.

Reference: Tax Configuration — Lifecycle and effects

Step 3 — Understand why the blank column is the tell

After this step you will have a rule for spotting a stranded row anywhere on this screen. The listing turns a stored tax type into a friendly name using a fixed map of ten values. A row whose type is not in that map shows a blank name. That is what these six are doing, and two more legacy rows in every tenant do the same. A blank Tax Type Name is the screen quietly telling you that it does not recognise this row. Do not fix it by re-typing the row with a real type — that would put an inert row into the document drop-downs, which is the one way it could start doing harm.

Reference: Tax Configuration — Troubleshooting

Step 4 — Separate the three lists people confuse

After this step you will stop looking for the taxable type in the wrong table. There are three lists with the same six names on this platform. These six inert rows in the tax-code table. A separate six-row list that the item’s E-Invoice tab actually reads, identical in every tenant and never extended. And the derivation at submission, which produces a code without consulting either list. Only the second is a real choice you make, and the third overrules it in almost every case. Editing the first changes nothing anywhere, which is the honest reason it is worth a lesson: it is the most plausible wrong place to look.

Reference: Tax Configuration — Lifecycle and effects

Step 5 — Notice the other things on this screen that do nothing

After this step you will know what else not to rely on. Two boolean columns on a tax code, marking it as input or output, are written by this applet and read by no drop-down — those filter on the type string instead. They are not inert, though: the listing endpoint will filter on them if you ask it to, so a code whose flag was cleared quietly drops out of that search. Two more columns for tariff and industry classification are never written at all. And setting a code to inactive hides it from this listing while leaving it selectable on a new invoice, because the document drop-downs load every code that has not been deleted. So a code you think you retired is still available to whoever raises the next document.

Reference: Tax Configuration — Lifecycle and effects

Step 6 — Find out how much of this surface anyone uses

After this step you will know where the thin ice is. The withholding half of this platform is almost entirely unconfigured. Across every tenant, the withholding type column is empty on essentially every tax code, and codes with one exist in a single tenant. That means the withholding drop-down on a document line is empty nearly everywhere, and the two withholding triples on every item’s Tax tab have nothing to offer. The item screen also fails to reload a saved withholding rate. If you need withholding tax, treat this as unproven ground and test it before you commit to it.

Reference: Doc Item Maintenance — Tax tab

How the steps fit together

    flowchart TD
  s1["Step 1 — Look at the six rows"]
  s2["Step 2 — Confirm that nothing reads them"]
  s3["Step 3 — Understand why the blank column is the tell"]
  s4["Step 4 — Separate the three lists people confuse"]
  s5["Step 5 — Notice the other things on this screen that do nothing"]
  s6["Step 6 — Find out how much of this surface anyone uses"]
  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: Proving a tax setup from the only place that can prove it · Back to the series · Play this as a presentation