> 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/faq.md). # FAQ ## Why use this SaaS instead of direct LHDN? Direct submission often requires costly digital signature certificates and intermediary compliance. We handle expensive and complicated signing and LHDN-facing steps; you integrate with simplified JSON. ## When are credits deducted? Credits are checked and deducted when submit (or cancel) is **accepted** into the queue — one credit per document on submit, one per cancel. Exact refund rules on failure: see product UI / billing terms. ## Bearer or X-API-Key? Either works. Pick one style per integration. ## Where do I create API keys? Dashboard → **API Keys** (after sign-in). ## Can I call the API from a browser? No. Server-side only. ## Consolidated vs non-consolidated? See [Core concepts](/amast-einvoice-sass/core-concepts.md). Consolidated uses General Public buyer on LHDN; you keep underlying sales records for audit. ## Will submit block duplicate invoice numbers? Only for prior submits **on this platform** for your tenant (`documentType` + `referenceId`). Not across MyInvois or other integrators. ## Credit note for invoice not sent via this SaaS? Yes. Provide `relatedInvoice.referenceId` and `lhdnUuid` from LHDN/MyTax Portal. ## Does status polling hit LHDN every time? No. It reads stored state updated by our workers and sync jobs. ## Webhooks? Not supported. Poll the status endpoint. ## How often should I poll? A few seconds initially, then back off. Stop when batch status is terminal. --- # 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/faq.md?ask=&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.