Skip to content
Document type 02

Credit note — reduces what the customer owes against a previously-approved invoice.

A credit note (type 02) is how you correct an over-charge, apply a discount after the fact, or accept a return. LHDN tracks every credit note against the UUID of the original invoice it modifies — the parent reference is mandatory, not optional. Once the credit note is approved, the customer's net balance is the original invoice total minus the credit.

When to issue

Four common scenarios.

  1. 01Post-issue discount — you offered a price reduction after the invoice was already approved by LHDN.
  2. 02Returned goods — the customer sent items back; you reduce their liability for the returned quantity.
  3. 03Billing error correction — you over-charged on a line item and need to credit back the difference.
  4. 04Volume rebate — end-of-period rebate applied retroactively against earlier invoices.
Required LHDN fields

What this document type carries that a generic invoice doesn't.

  • Original invoice reference — LHDN UUID of the parent type-01 document.
  • Reason code — LHDN expects a structured reason for the credit, not free text.
  • Credit amount — line-item or full-document credit, with the right sign convention.
  • Same supplier + customer parties as the parent invoice (no party flip).
How Bridge handles it

Same pipeline as every other type.

The bridge stores the LHDN UUID of every approved invoice. When you issue a credit note in the dashboard, the parent reference is filled in automatically from the catalog. CSV uploads carry the parent UUID as a column; the bridge validates the link exists before submitting so LHDN doesn't reject for a dangling reference.

Last updated · May 2026

Independent reference. MyInvois is operated by LHDN. We are not affiliated with LHDN.