IRAS Errors

Refer to this section to resolve common CPF errors.

 

UNB Grp 0. UNB Segment not found, error is 06200.

 

Explanation:

The text file was not prepared according to IRAS Interface File Specification of PAT system. Instead, the text file was prepared according to the file specification of IRAS e-Submission system.

 

NAD Grp 0. Invalid Employer ID, Type is 8 error is T07CM1732G.

 

Explanation:

The payer id type declared in RFF AWM is incorrect. In this example, the payer ID type is declared as '8' (for UEN - Local Company), but the payer ID declared is of type UEN - Others.

Please find the acceptable format for each payer ID type below.

 

7 = UEN - Business (ROB) - Standard entity identification number issued to Businesses registered with ACRA

8 = UEN - Local Company (ROC) - Standard entity identification number issued to Local Companies registered with ACRA

U = UEN - Others - Standard entity identification number issued to all other entities which are not a business or local company

A = ASGD - Tax reference number assigned by IRAS

I = ITR - Income tax reference number assigned by IRAS

C = CRN - Central Registration number issued by Trade & Industries

M = MCST - Management Corporation Strata Titles number issued by Building and Construction Authority

G = GSTN - Goods & Services Tax number issued by IRAS

 

Format:

UEN - Business (ROB) - NNNNNNNNC (9 chars)

UEN - Local Company (ROC) - YYYYNNNNNC - for Local Companies (10 chars)

F000NNNNNC or FNNNNNC - for Foreign Companies

UEN - Others - SYYPQNNNNC or TYYPQNNNNC (10 chars)

ASGD - ANNNNNNNC (9 chars)

ITR - 4NNNNNNNNC (10 chars)

CRN - NNNNNNNNNNNC (12 chars)

MCST - MCSTNNNN (8 chars)

GSTN - MCNNNNNNNC (10 chars)

Where:

is a space

C is a check digit

N is numeric

YYYY is a year

TYY and SYY are the year of issuance, where T represents '20'and S represent '19’

PQ is the entity type, e.g. 'LL' represents 'Limited Liability Partnership’

ID No cannot be blank and must not have preceding space(s). Those highlighted in bold are fixed prefixes.

 

LIN Grp 1 (LIN=2). NAD Grp 1. Invalid Employee ID, type is 2, error is 610929135501

 

Explanation:

The employee id type declared in RFF AWM is incorrect. In this example, the employee ID type is declared as '2'(for FIN No), but the employee ID declared is not of type FIN No. A FIN No should always start with 'F'or 'G’.

Please find the acceptable format for each employee ID type below.

 

1 = NRIC - This is for Singaporean or Permanent Residents. The format of the ID number must be with prefix 'S' or 'T'(for NRIC issued from Year 2000 onwards)

2 = FIN - This is for Foreigners holding Work Permit or Employment pass. The format of the ID must be with prefix 'F'or 'G'(for FIN issued with effect from Year 2000 onwards).

3 = Immigration File Ref No - This is the immigration file reference number issued by immigration

authorities. The format is NNNNNNNC (8 chars)

4 = WP No - Work Permit No. Format is N NNNNNNNC (10 chars) with a space after the first N

5 = Malaysian I/C - It can be used to declare for non-resident director only. Format is it consists of 7 or 8 alphanumeric or consists of 12 numerics

6 = Passport No - It can be used to declare for non-resident director only.

 

LIN Grp 1 (LIN=80). 1st RFF Grp 1. Payee ID Type should in the range 1-6, Qualifier=AWM error is 0

 

Explanation:

Invalid employee ID type 0 has been declared in the text file. Please refer to the IRAS error no 3 for the list of acceptable values for employee ID type.

 

1 LIN Grp 1 LIN=73. NAD PE Segment not found

2 LIN Grp 1 LIN=73. MOA 128 Segment not found

3 LIN Grp 1 LIN=73. MOA 367 Segment not found

4 LIN Grp 1 LIN=73. MOA 368 Segment not found

5 LIN Grp 1 LIN=73. MOA 67 Segment not found

6 LIN Grp 1 LIN=73. MOA 776 Segment not found

7 LIN Grp 1 LIN=73. MOA 369 Segment not found

8 LIN Grp 1 LIN=73. MOA 340 Segment not found

9 LIN Grp 1 LIN=73. MOA 275 Segment not found

10 LIN Grp 1 LIN=73. MOA 265 Segment not found

… and so on

 

Explanation:

If you see a list of consecutive errors saying some segments not found, it means there are some mandatory segment missing or not properly declared in the text file. In order to identify which part of file causing the error, you should see the first segment that is reported as "not found". In this example, you should check the NAD PE segment of employee no 73.

 

This kind of error can also be caused by a blank line in your text file. Similar to the above explanation, you should see the first segment that is reported as "not found" to identify the position of the blank line. In this example, the blank line would be exactly before the NAD PE segment of employee no 73.

 

LIN Grp 1 LIN=45. …

LIN Grp 1 (LIN=256). …

I have so many employees in the file, how do I know the error is caused by which employee’s data?

 

Explanation:

If the error is caused by some employee specific data, the error message will contain "LIN=XX" phrase, which means the error happens while reading data belonging to employee no XX in the text file. In this example, the error messages refer to employee no 45 and 256, respectively.

 

To locate certain employee in your text file, you can open your text file with an editor that has searching feature, e.g. notepad, wordpad, etc. You can type "LIN  XX" (notice that there should be 2 spaces between then character N and the first digit of employee number) as the search keyword. For example, you can type "LIN  45" to search the beginning of data declaration belonging to employee no 45.