Error with customer data (TIN and BRN )
Introduction:
This article is to assist for errors that details problems with Customer TIN and BRN
Troubleshoot steps:
Check the Related Lists table on the document.
In Zoho Books > the document that is failed to pushed > scroll down to the related lists table.
Check the customer's profile
In Zoho Books > the document that is failed to pushed > click on the company name link > customer page > edit,

Verify Customer TIN and BRN (make sure it is correct and matching the latest official values from LHDN)
please ensure you are using the latest BRN of your customer, and not the old BRN format
(you may need to look this up or get it directly from your customer)

Fill in registration numbers and MSIC codes where applicable, and if none are provided, fill the fields with "NA" as shown :

Double check that all values do not have any spaces inside, before, or after the data as this will also trigger an error.
To investigate TIN numbers and BRN numbers on your own:
ensure the BRN number is valid and correct from your customer
Proceed to the customer details widget
key in the registration number in the appropriate field, and then click "search taxpayer's TIN".
the TIN should autofill based on the correct value from LHDN if the BRN is correct or registered
- an error will appear otherwise
- you may now save the values
Alternate possibility: address fields
In the back end, should any address field dropdowns not be using the present dropdown selection options, it will also trigger this error.
Navigate to your customer's address fields, and select all corresponding options for the dropdowns,
DO NOT manually type in these fields, as this will cause errors if not exactly following the prefilled dropdown data.
example below:
Final step: applying new details and testing
- Address (confirm that the address stored in the profile is correct and updated)
- Take note of all the address fields and make sure they are
filled in following the format below
with the correct information (street address,city, state,country, zip code).

- Double check that TIN and BRN
- is the latest up to date values
- does not have any spaces before or after,
- they can be verified by the TIN search widget
- Check the customer's address on the document (on the document edit page).
make sure updated address selected in document

- Save the document
- attempt to push.
Please do not hesitate to contact us through our support email if you have any questions or require any further assistance.
Related Articles
Error with Customer TIN and BRN when previously valid and pushable (error as of April 2026)
Introduction: This article is to assist for when the plugin cannot find the TIN and BRN of a customer (either cannot push or cannot find via widget) but the data is valid, and the document can be manually submitted without issue. Troubleshoot steps: ...
Error - ( for foreign buyer ) message detailing about buyer TIN / BRN
Introduction: It would appear that you are experiencing issues with a foreign buyer TIN or Registration number, Solution: Do check on your customer's TIN, as this is a foreign customer, you are to use TIN EI00000000020 in accordance with LHDN general ...
Error with customer data (address, phone number)
The error may look like what is below: Troubleshoot steps: Check the Related Lists table on the document. In Zoho Books > the document that is failed to pushed > scroll down to the related lists table. Check the customer's profile In Zoho Books > the ...
"error in line _ _ , invalid JSON format string" (Checking the plugin's config data )
Introduction This article is to troubleshoot the following: The uncommon TIN/BRN mismatch error if you have the correct BRN and TIN for your organization's plugin setup, if you have the correct TIN and BRN entered into the plugin. One such error that ...
Customer details widget error
Introduction The error in question is when the customer details side widget either comes with an error, or refuses to load : This issue is usually due to the locations module not being enabled, as Zoho recently changed the back end and now has tied ...