MyInvois e-Invoice Errors: Buyer TIN Invalid, TIN Not Matching and How to Fix Them

MyInvois error lookup table

“MyInvois” means LHDN’s system returned the message; “AutoCount” means AutoCount’s software shows it. Sources checked 9 October 2026.

What does "Buyer TIN is invalid" mean in MyInvois?

The MyInvois error “Buyer TIN is invalid” (code ERR406) means the buyer’s BRN is valid, but no taxpayer TIN matches the Buyer TIN on the e-invoice. The TIN is wrong or wrongly formatted. The fix is to look up the buyer’s correct TIN with the Search TIN function or MyTax Portal, check the BRN, then resubmit.

The full message is Buyer TIN is invalid. Kindly use the Search TIN function to get the correct TIN (MyInvois SDK - Taxpayer Validator Errors). Its twin, Supplier TIN is invalid (ERR401), means your own TIN cannot be matched, possibly a formatting or typo issue.

1. Copy the buyer’s TIN and BRN exactly as your software stores them.
2. Search the TIN with LHDN’s Search TIN function or the MyTax Portal.
3. Confirm the BRN belongs to the buyer you are invoicing.
4. Check the TIN format against LHDN’s FAQ.
5. Correct the TIN in the customer master, not only on this invoice, then resubmit.

LHDN advises validating a buyer’s TIN once, when the buyer is set up, and caching it, rather than calling its MyInvois SDK - Validate Taxpayer's TIN API before every submission, which may be throttled.

If this repeats across many invoices: the customer master is missing TINs or holds unchecked ones, for example from buyers created before e-invoicing or from a second source system.

What does "The authenticated TIN and documents TIN is not matching" mean?

The MyInvois error “The authenticated TIN and documents TIN is not matching” means the issuer TIN in the e-invoice differs from the TIN your system logged in as. With a taxpayer login, the issuer TIN must match the TIN tied to the Client ID and Client Secret. Through an intermediary, it must match the represented taxpayer’s TIN.

The rule is in the MyInvois SDK - FAQ, which adds that sole proprietors can validate TINs starting with “IG” with their BRN once the “Business Owner” role is assigned in MyTax. In AutoCount Cloud Accounting, AutoCount’s support article says the error appears when TIN ownership was validated as an individual and the Tax Entity later changed to Business, such as IG with BRN (AutoCount support: 'authenticated TIN and documents TIN is not matching' (26 Feb 2026)). Its fix:

1. Click the Account Book icon, then Company Profile, then Edit Company Info.
2. In the Tax Entity dropdown, clear the value and save.
3. Edit again, re-select the correct Tax Entity and save.
4. Edit and save the invoice to bring up the TIN Ownership validation link.
5. Open the link, enter the Client ID and Client Secret from your business profile in the MyInvois Portal, and submit.
6. Submit the invoice again.

If this repeats across many invoices: the TIN, tax entity or credentials sit on the wrong profile, or one login submits for more than one company.

What does "TIN ownership is not validated" (E100) mean in AutoCount?

The AutoCount error “TIN ownership is not validated” (code E100) most probably means the MyInvois Portal Client ID and Client Secret have not been entered in AutoCount’s Company Profile. The message comes from AutoCount, not from LHDN. The fix is to enter both under the Company Profile’s e-Invoice tab, then sync again.

In AutoCount POS5/FNB the message reads Submit E-Invoice failed: TIN ownership is not validated, then a validation link and (Code: E100) (AutoCount Resource Center: TIN ownership error, POS5/FNB (2 Sep 2024)). We found no use of the phrase “TIN ownership” in LHDN’s SDK error pages or FAQ (searched 9 October 2026).

1. In the MyInvois Portal, go to Taxpayer Profile > Representatives > ERP > Register ERP to get a Client ID and Client Secret.
2. Under Representatives > Intermediaries, confirm Auto Count Sdn Bhd (TIN C20239710060) is added (AutoCount support: How to Validate TIN Ownership in PalmPOS (30 Apr 2025)).
3. In AutoCount, go to Tools > Company Profile > e-Invoice tab, enter both in the MyInvois Portal box, and click OK.
4. Run the speed sync again.

AutoCount’s PalmPOS guide says the credentials are used only for validation and are not stored on the AIP server.

If this repeats across many invoices: ownership was never validated for this company. Fix the setup once, then resubmit the failed invoices.

What does "Intermediary Login Error" mean in AutoCount?

The AutoCount message “Intermediary Login Error” appears when validating the Client ID and Client Secret in Company Profile. AutoCount gives three causes: the Company Profile TIN differs from the MyInvois Portal TIN, the intermediary was added under an individual login instead of the company login, or its date range or permissions are wrong.

In AutoCount Accounting 2.2 the message reads Intermediary Login Error: TIN "xxx" is incorrect or intermediary is not setup correctly (AutoCount Resource Center: 'Intermediary Login Error' (10 Oct 2024)). An intermediary can do only what the taxpayer granted (MyInvois SDK: Login as Intermediary System).

1. Go to Tax > Tax Entity Maintenance and correct the TIN, or create a tax entity with the right one.
2. Log in to the MyInvois Portal as the company, not as an individual.
3. Add or edit the intermediary there, set the correct representation dates and enable the permissions.
4. In Company Profile, re-select the tax entity and TIN, and click OK.

If this repeats across many invoices or companies: each company needs its own intermediary setup in its own MyInvois profile.

What do "unauthorized_client" and "403 - Forbidden" mean when AutoCount submits?

The AutoCount errors “LHDN login error: unauthorized_client” and “Submit document error: 403 - Forbidden” both point to the MyInvois intermediary setup. AutoCount says unauthorized_client comes from an intermediary added in the individual profile or a wrong representation date range, and 403 Forbidden from intermediary permissions that were never enabled.

Sources: AutoCount’s AutoCount Resource Center: LHDN login error unauthorized_client (31 Oct 2024) and AutoCount Resource Center: Submit document error 403 - Forbidden (9 Oct 2024) articles. LHDN’s API returns a similar IncorrectSubmitter 403 when an intermediary lacks permission (MyInvois SDK: Submit Documents API).

1. Log in to the MyInvois Portal as the company.
2. Go to View Taxpayer Profile > Representatives > Intermediaries. If AutoCount’s intermediary sits only in your individual profile, add it here.
3. Click Edit, then Continue.
4. Correct the Representation From and To dates so the To date has not passed, enable all permissions and save.
5. Wait (AutoCount observed at least 30 minutes; not an LHDN timing), then re-submit.

If this repeats across many invoices: the representation period has expired or permissions were never enabled.

What do "DuplicateSubmission" and DV302 mean in MyInvois?

MyInvois has two duplicate checks. HTTP 422 “DuplicateSubmission” means the same taxpayer sent an identical submission within 10 minutes; wait the Retry-After seconds. Error DV302 means a document matches one processed within 2 hours on type and version, issuance date-time, internal ID and supplier TIN, or buyer TIN for self-billed.

DV302 is on LHDN’s MyInvois SDK - Duplicate Document Validator Errors page; the 422 DuplicateSubmission response is on the MyInvois SDK: Submit Documents API page.

1. Check whether the first copy was accepted with a UUID (MyInvois SDK: Submit Documents API).
2. If it was, mark it as submitted; do not resend it.
3. For a 422, resend the same payload only after the Retry-After wait.
4. If a true duplicate validated, cancel it within 72 hours; after that, changes need a credit, debit or refund note (LHDN e-Invoice Guideline v4.8 (30 Aug 2026)).

If this repeats across many invoices: your software retries without checking what was accepted, or two systems submit the same sales.

What do signature errors DS310, DS311 and DS322 mean?

MyInvois signature errors DS310 and DS311, “Signer of invoice doesn’t match the submitter of document”, mean the signing certificate’s serial number or TIN does not match the submitting taxpayer. The fix is to sign with the certificate that belongs to the submitting organisation. DS322 means the document changed after signing, so re-sign after every edit.

The codes are on LHDN’s MyInvois SDK - Signature Validator Errors page and matter mainly to direct API setups that sign their own documents.

1. Compare the TIN inside the certificate with the taxpayer TIN registered in MyInvois.
2. Sign with the certificate tied to the submitting taxpayer.
3. Make every change first, then sign, then submit.

If this repeats across many invoices: one certificate serves several companies, or a later step edits documents after signing.

What does "Issuance date time value of the document is too old" mean?

The MyInvois error “Issuance date time value of the document is too old and cannot be submitted” means the e-invoice’s issuance date is outside the allowed window. LHDN’s fix is to check the propertyPath in the error and set the issuance date to within 72 hours before submission, then submit again.

The answer is in the MyInvois SDK - FAQ. The opposite, Document issuance date and time is in the future, means the date-time is not in UTC format.

1. Read propertyPath to see which date failed.
2. Set the issuance date-time within 72 hours before submission, in UTC.
3. Submit again.

If this repeats across many invoices: invoices are batched days after they are raised, or the source system sends local time instead of UTC.

When is a repeating MyInvois error a data or integration problem?

A repeating MyInvois error is a data or integration problem when the same message appears on many invoices from one source. A one-off error can be a typing mistake. Repeats can come from missing buyer TINs in the customer master, a second source system without TINs, a login set up on the wrong profile, or retries that resend copies.

If every invoice starts in AutoCount and AIP submits it, the fix is often in the AIP setup; ask whoever supplies your AutoCount licence. When invoices start elsewhere, a bridge we scope is designed to stop repeats at the source:

1. Validate each buyer’s TIN once, when the buyer is created, and cache it (MyInvois SDK - Validate Taxpayer's TIN API).
2. Look up each invoice’s source document ID before sending, so a retry never creates a duplicate.
3. On HTTP 429, wait the Retry-After time (MyInvois SDK: Integration Practices); log in again only when the one-hour token expires (MyInvois SDK - FAQ).
4. Hold failed validations on a list with the exact error text for a person.
5. Store each UUID against the AutoCount document and reconcile on a schedule (daily or monthly, agreed at scoping).

The full design is on our MyInvois e-invoice automation page. On a free 15-minute scoping call we tell you whether your errors are a data, setup or integration problem.

Key terms

TIN

Tax Identification Number. In a consolidated e-invoice the buyer’s TIN is the general public TIN EI00000000010; LHDN publishes other general TINs, such as EI00000000030 for foreign suppliers in self-billed e-invoices.

BRN

Business Registration Number, one of the identity numbers (with NRIC, passport and army number) that MyInvois checks a TIN against.

Client ID and Client Secret

Credentials generated in the MyInvois Portal (Register ERP) that let a system log in as the taxpayer.

Intermediary

A system that logs in to MyInvois with its own credentials and acts for a taxpayer, with only the permissions the taxpayer granted.

UUID

The 26-character document ID MyInvois assigns to each accepted e-invoice.

The general TINs are listed in Appendix 1 of the LHDN e-Invoice Specific Guideline v4.9 (7 Sep 2026).

Related guides

• AutoCount to MyInvois e-invoice automation: when invoices start outside AutoCount.
• Malaysia e-invoice 2026 guide: who must issue e-invoices after the RM3 million exemption.
• AutoCount API integration: connecting a POS, marketplace or ordering system to AutoCount.

Sources

1. MyInvois SDK - Taxpayer Validator Errors, Inland Revenue Board of Malaysia (LHDN). Retrieved 9 October 2026.
2. MyInvois SDK - FAQ, Inland Revenue Board of Malaysia (LHDN). Retrieved 9 October 2026.
3. AutoCount Resource Center: TIN ownership error, POS5/FNB (2 Sep 2024), Auto Count Sdn Bhd. Retrieved 9 October 2026.
4. AutoCount Resource Center: 'Intermediary Login Error' (10 Oct 2024), Auto Count Sdn Bhd. Retrieved 9 October 2026.
5. AutoCount Resource Center: LHDN login error unauthorized_client (31 Oct 2024), Auto Count Sdn Bhd. Retrieved 9 October 2026.
6. AutoCount Resource Center: Submit document error 403 - Forbidden (9 Oct 2024), Auto Count Sdn Bhd. Retrieved 9 October 2026.
7. MyInvois SDK - Duplicate Document Validator Errors, Inland Revenue Board of Malaysia (LHDN). Retrieved 9 October 2026.
8. MyInvois SDK: Submit Documents API, Inland Revenue Board of Malaysia (LHDN). Retrieved 9 October 2026.
9. MyInvois SDK - Signature Validator Errors, Inland Revenue Board of Malaysia (LHDN). Retrieved 9 October 2026.
10. MyInvois SDK - Validate Taxpayer's TIN API, Inland Revenue Board of Malaysia (LHDN). Retrieved 9 October 2026.
11. AutoCount support: 'authenticated TIN and documents TIN is not matching' (26 Feb 2026), Auto Count Sdn Bhd. Retrieved 9 October 2026.
12. AutoCount support: How to Validate TIN Ownership in PalmPOS (30 Apr 2025), Auto Count Sdn Bhd. Retrieved 9 October 2026.
13. MyInvois SDK: Login as Intermediary System, Inland Revenue Board of Malaysia (LHDN). Retrieved 9 October 2026.
14. LHDN e-Invoice Guideline v4.8 (30 Aug 2026), Inland Revenue Board of Malaysia (LHDN). Retrieved 9 October 2026.
15. MyInvois SDK: Integration Practices, Inland Revenue Board of Malaysia (LHDN). Retrieved 9 October 2026.
16. LHDN e-Invoice Specific Guideline v4.9 (7 Sep 2026), Inland Revenue Board of Malaysia (LHDN). Retrieved 9 October 2026.