Item Master: Fill In the E-Invoice Tab, and Correct It After a Sale
Step 3 of Maintaining the Item Master: fill in the item’s three e-Invoice fields before the item is ever sold, and know what a correction after the first sale does and does not reach. It follows Step 2, the tax codes.
The running example: GadgetSphere is adding LAP-ULT-1401, a 14-inch ultraportable laptop with a serial number on every unit. GadgetSphere Distribution (GSD) will invoice 20 of them to a corporate buyer, one e-Invoice per invoice, while the retail branches report walk-in sales to LHDN monthly in consolidated e-Invoices.
Get the classification from whoever owns e-Invoice compliance before you open the tab. The tab pre-fills 022 Others on a blank item, and nothing warns you at save or rejects it afterwards.
- Step 3: fill in the three e-Invoice fields.
- When the classification turns out wrong after the first sale: what a correction reaches, and what it does not.
Step 3: Fill in the e-Invoice tab — before the item is ever sold
Item Edit > E-Invoice tab
Three fields, all needed for a Malaysian e-Invoice submission:
- Item Classification — the LHDN classification code, chosen from the Classifications list. That list is not a live copy of LHDN’s: a scheduled clock (where your tenant has it) refreshes the wording of the codes already there, and never adds one — a code LHDN introduces is added by hand on Classifications > Create.
- Taxable Type Code — the LHDN tax type. Set it, but do not rely on it: unless the line ends up with a non-zero tax amount and a code other than
06, what you chose here is replaced at submission by a value worked out from the line’s tax amount. See what LHDN is actually told. - E-Invoice UOM — the LHDN unit-of-measure code, which is not the same vocabulary as your base UOM.
There is no tenant default to fall back on. The tenant settings that look like one were disconnected in November 2025 and are read by nothing — every line that consumed them is commented out, and no backend code has ever read them. A category’s own E-Invoice tab records an intention and carries it to no item. What does reach these fields is an Item Template default and the tab’s own hard-coded 022 Others on a blank classification. Fill them in.
022 Others, and a blank e-Invoice unit as H87 piece, with no warning at save and no rejection afterwards. The tab also pre-fills 022 when you open it on a blank item, so the field being filled is not evidence that anybody chose it. Set it when you create the item.When the classification turns out wrong after the first sale
On Tuesday GSD invoiced 20 units of LAP-ULT-1401 to a corporate buyer, finalised it, and LHDN validated the e-Invoice that afternoon. The branches sold 14 more at the till that week. On Thursday, reading the validated e-Invoice, you see the classification is the code one row above the one your compliance owner chose. You correct it on the item’s E-Invoice tab and save. Here is what that save reaches, and why.
A document line is a snapshot of the item, taken at the time the line was added. Adding the item to a sales invoice copies its classification onto the line, beside its own copies of the code, tax code, GL code, unit and unit ratio. Saving an item writes the item and queues three things — a catalogue webhook, a free-shipping update when that flag changed, and the status push to the inventory twin — and touches no document line. So:
| Where the 34 laptops are | What the correction changes |
|---|---|
| Any line added after you saved | Carries the corrected code |
| A draft invoice raised on Wednesday for another buyer | Nothing. Its line still holds Tuesday’s wrong code. Remove the line and add it again — adding is the moment the line copies the item |
A finalised GSD invoice still waiting to go to LHDN | Nothing. The e-Invoice record is built from the document’s own lines, so it goes with the code the line holds. A line holding no code is the one exception: that blank is filled from the item, as the item reads when the record is built |
| Tuesday’s invoice, already validated by LHDN | Nothing, in BigLedger or at LHDN. Correcting it there is a cancellation inside 72 hours of validation, or a credit note after — see cancelling and correcting a validated e-Invoice |
| The 14 till sales, reported in the month’s consolidated e-Invoice | Nothing to correct. Every line of a consolidated e-Invoice is sent as 004 Consolidated e-Invoice, whatever the item says |
| The journal, the stock ledger and the cost of the 34 laptops | Nothing. The classification is read by the e-Invoice and Peppol paths, document imports and a few printed formats; no journal, stock or costing code reads it |
Two things follow that the screen does not tell you. First, for a retailer like GadgetSphere, the item’s classification reaches LHDN only through e-Invoices submitted one per document — the corporate invoices, and the walk-in buyer who asks for an e-Invoice of their own — so that is where a wrong code shows and where to look for it. Second, the correction is a person’s job in two halves: whoever maintains items fixes the record, and whoever owns e-Invoice compliance decides whether a validated e-Invoice whose amounts are right but whose classification is wrong is worth cancelling or crediting at all. BigLedger does not make that call, and this guide does not either.
To find the documents still on their way with the old code, open the Batch Pool in My E-Invoice Admin: its lines list each document line’s own E-invoice Item Classification, which is what will be sent.
What success looks like for this part
The item’s E-Invoice tab shows the classification your compliance owner chose and the e-Invoice UOM you chose, not 022 Others pre-filled by the tab, and in a draft sales invoice’s item search the E-invoice Item Classification column shows the same code. For the taxable type, submit one line and read it on the submitted record. After a correction: every draft line that held the old code has been removed and added again; you have read the Batch Pool’s classification column, so you know which documents still on their way will go with the old code; and any validated e-Invoice carrying the old code is with your compliance owner. The whole item’s checks are on the front page.
Common mistakes in this part
| What goes wrong | What you see | The fix |
|---|---|---|
| E-Invoice tab left blank | Sales work and submissions succeed — carrying 022 Others and H87 piece, which is worse, because nothing tells you | Set classification, taxable type and e-Invoice UOM when you create the item, or from an Item Template |
| Classification corrected after the first sales | Drafts and documents waiting for LHDN still carry the old code | Re-add the line on drafts; check the Batch Pool’s classification column; take validated e-Invoices to your compliance owner |
The rest are on the front page and on Units, Prices and Retiring.
Related documentation
- Doc Item Maintenance applet — every menu, tab and field, the reference
- Malaysia e-Invoice guide — what the classification feeds
- Cancelling and correcting a validated e-Invoice — when the wrong code has already reached LHDN
- Item Master: Units, Prices and Retiring — Steps 4 to 6, and retiring an item