> For the complete documentation index, see [llms.txt](https://amast-einvoice.gitbook.io/amast-einvoice-sass/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://amast-einvoice.gitbook.io/amast-einvoice-sass/appendix/acronym-term.md).

# Acronym / Term

You may find these term across our platform. This guide help you to understand common term used.

| Acronym / term | Meaning     | API / code value                               |
| -------------- | ----------- | ---------------------------------------------- |
| IV             | Invoice     | `documentType`: `invoice` (LHDN type `01`)     |
| CN             | Credit note | `documentType`: `credit_note` (LHDN type `02`) |
| DN             | Debit note  | `documentType`: `debit_note` (LHDN type `03`)  |

***

Platforms & systems

| Acronym  | Meaning                                                                                          |
| -------- | ------------------------------------------------------------------------------------------------ |
| SaaS     | This platform (software service you integrate with)                                              |
| LHDN     | Lembaga Hasil Dalam Negeri — Malaysia tax authority                                              |
| MyInvois | LHDN e-Invoice system / API                                                                      |
| IRB      | Inland Revenue Board (same ecosystem as LHDN; “IRB UUID” = LHDN document UUID)                   |
| AMS      | Your upstream billing/source system (field names like `subtotal`, `grand_total` aligned in docs) |
| ERP      | Enterprise resource planning (e.g. client system)                                                |
| POS      | Point of sale                                                                                    |
| UBL      | Universal Business Language — XML/JSON invoice format sent to LHDN                               |

***

API & IDs

| Acronym / field  | Meaning                                                            |
| ---------------- | ------------------------------------------------------------------ |
| API              | HTTP integration (`X-API-Key`, `/api/v1/...`)                      |
| Batch ID         | `submissionBatchId` — one submit request (1–100 docs)              |
| Doc ID           | `documentId` — platform document record (per `referenceId` + type) |
| Txn ID           | `transactionId` — one API attempt row per document                 |
| lhdnSubmissionID | LHDN submission UID (whole batch submit on MyInvois)               |
| lhdnUUID         | LHDN per-document UUID (IRB document id)                           |
| ref ID           | `referenceId` — your invoice/CN/DN number                          |

***

Submission modes

| Term             | Meaning                                                                 |
| ---------------- | ----------------------------------------------------------------------- |
| Consolidated     | `submission_type`: `consolidated` — buyer = General Public on LHDN      |
| Non-consolidated | `submission_type`: `non-consolidated` — real buyer `recipient` required |
| GP               | General Public — fixed consolidated buyer (TIN `EI00000000010` in docs) |

***

Taxpayer / buyer identity

| Acronym | Meaning                                                                |
| ------- | ---------------------------------------------------------------------- |
| TIN     | Tax identification number                                              |
| BRN     | Business registration number (company)                                 |
| NRIC    | National ID (individual); used in `identification_no`                  |
| ID      | Identification number (generic; validate-TIN API `idType` + `idValue`) |

***

Status dimensions (two columns in UI)

| Field       | Meaning                                                                                       |
| ----------- | --------------------------------------------------------------------------------------------- |
| SaaS status | `submissionStatus` / batch `status` — `Queued` → `Processing` → `Submitted` \| `SubmitFailed` |
| LHDN status | `lhdnStatus` — `Submitted`, `Valid`, `Rejected`, `Invalid`, `Cancelled`                       |

| SaaS / pipeline | Meaning                              |
| --------------- | ------------------------------------ |
| Queued          | Saved; waiting for worker            |
| Processing      | Worker building UBL / calling LHDN   |
| Submitted       | Submit call finished (platform side) |
| SubmitFailed    | Platform could not submit to LHDN    |

| LHDN      | Meaning                                      |
| --------- | -------------------------------------------- |
| Valid     | LHDN validated document                      |
| Invalid   | Failed validation after accept (sync)        |
| Rejected  | Rejected in submit response (same HTTP call) |
| Cancelled | Cancelled on LHDN                            |

***

Other terms in docs/code

| Acronym                | Meaning                                                            |
| ---------------------- | ------------------------------------------------------------------ |
| CN parent / related IV | `relatedInvoice` on credit note → original invoice                 |
| Idempotency key        | Header `idempotency-key` — safe retries                            |
| XAdES                  | XML advanced electronic signature (UBL v1.1 signed path)           |
| HITS                   | LHDN host system (mentioned in validation errors, e.g. NRIC check) |
| ERR###                 | LHDN validation error codes (e.g. `ERR406`, `ERR206`)              |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://amast-einvoice.gitbook.io/amast-einvoice-sass/appendix/acronym-term.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.