Historical version and sandbox purpose
This six-page guide is Version 2.0 dated 31 May 2023, headed YA2022 API Sandbox Testing. Its disclaimer separately states information correct as at 16 August 2021. Preserve those dates when using its basis-year 2021 scenarios; they are not instructions to submit that year’s test records as current production data. The sandbox mimics production so developers can test integration before sending actual commission records. Use the API and authentication specifications for field definitions beyond these scenarios.
Create the account and API subscription
Register in the Sandbox Portal and subscribe to Submission of Commission Records (Corppass). Register the software callback URL using the registration form. Enter the registrant’s actual first and last names in the account fields, then edit My organisation to follow Name of Organisation_Tax reference No of organisation. The source refers to section 2 of the Commission API (CP) specifications and the Corppass Authentication API specifications for setup detail.
Use the published test organisation
The published sandbox Singpass login is S9991256A with test password Spcp1111. API calls use organisation ID type UEN-Local Business and organisation ID 98706710M; payloads encode organisationIDType as 7. These are public sandbox credentials and fictitious test values from the guide, not production credentials. Set A must use the stated values except authorisedPersonIDNo and idNumber, which require valid IDs. A different organisationIDNo will prevent API submission.
Set A scenario 1: original records
Set validateOnly=false, BasisYear=2021, organisationIDType=7, organisationIDNo=98706710M, authorisedPersonIDtype=1 and a valid authorised-person NRIC. The authorised person is TESTER 1, MANAGER; organisationName is TEST 1 PTE. LTD.; telephone 61234567; email TESTER1@TEST1.COM; batchIndicator O; numOfRecords 2; totalGrossCommission 49856. Record 1 uses idType 1 and a valid earner NRIC, name EARNER 1, nationality 301, sex M, designation 3, birth date 19810320, grossCommission 5396. Record 2 uses idType 8 and a valid earner UEN, name EARNER 2 and grossCommission 44460. The two amounts reconcile to 49856. Expected output includes an acknowledgementCode in the ES17DDMMYYCOMMNNNNNN pattern, empty fieldInfoList and returnCode 10.
Set A scenario 2: a negative amendment
Use validateOnly=false, basisYear=2021, organisationIDType=7 and the same organisation number. The authorised-person ID type is 1 with valid NRIC; name TESTER 2; designation IT SUPPORT; organisationName TEST 2 S’PORE BRANCH; telephone 91234567; email TESTER2@TEST2.COM. batchIndicator is A, numOfRecords is 1 and totalGrossCommission is -4256. The one earner record has recordID 1, idType 1 and valid NRIC, EARNER 1, nationality 301, sex M, designation 3, birth date 19810320 and grossCommission -4256. The expected response again has an acknowledgement code, no field errors and returnCode 10. Preserve the negative sign and amendment indicator; this is not another original positive submission.
Set A scenario 3: duplicate-record validation
Use validateOnly=true and the scenario-1 organisation and authorised-person fields, with batchIndicator O, two records and totalGrossCommission 69520. Both records use the same valid NRIC for EARNER 1 and the same nationality 301, sex M, designation 3 and birth date 19810320; their recordIDs are 1 and 2 and gross commissions are 25985 and 43535. Expected output is returnCode 30, message Arguments Error and messageCode 850301. fieldInfoList identifies commissionEarnerDtl, says Duplicate record exists and identifies recordID 2. This validation-only scenario deliberately tests a duplicate even though the monetary total reconciles.
Set B and submission of test results
Generate 10–20 fictitious records, preferably combining individual and business earners, with organisationIDType 7 and organisationIDNo 98706710M. A successful actual sandbox submission returns an acknowledgement code. Email results to data_mgmt@iras.gov.sg using the source template: acknowledgement codes for Set A serial numbers 1 and 2; for Set B, number of records and total gross commission. Scenario 3 is the validation error case and is not listed as a successful acknowledgement row. IRAS states it will respond with the testing outcome within 10 working days. This is the historical guide’s testing procedure, not permission to substitute fictional data in production.
Official source
This article independently explains the substantive contents of the official PDF, including the relevant conditions, procedures and annexes. The linked document remains the authoritative source for its original wording, and later changes should be checked separately.
Read the official PDF ↗