Organization Admin

Configure the workspace and run every operating module, control, integration, and business lifecycle.

Organization AdminConnections22 min read

Onboard Singapore government services

Prepare Corppass authority and connect ACRA, IRAS, CPF EZPay, and GovTech APEX without confusing agency approval with platform configuration.

Who can do this

Organization Admin plus the entity’s authorized Corppass roles

Primary route

/settings/organization/api-services

Last verified

4 August 2026

What you need
Have these ready before you start.
  • An active Singapore entity and UEN
  • A Corppass Admin or Sub-Admin
  • A documented service purpose and authorized employee
  • Agency approval or subscription where required

01

Separate authorization from configuration

The organization applies to the agency, accepts its terms, assigns authorized people, and remains responsible for submissions. The platform stores approved connection details and supports the workflow; it does not grant government authority.

02

Assign Corppass access

A Corppass Admin or Sub-Admin assigns the relevant digital service and any agency roles, parameters, or Sub-UENs.

  1. Identify the exact agency digital service required by the workflow.
  2. In Corppass, create or select the authorized user.
  3. Assign the service and its required agency role or parameter.
  4. Complete any additional agency check outside Corppass.
  5. Retain approval evidence, authorized person, and effective date.

“Access to all e-Services” does not bypass additional agency roles, parameters, Sub-UENs, or separate onboarding.

03

Subscribe through ACRA API Marketplace

ACRA API Marketplace manages subscriptions, applications, and usage for official entity information services. Corppass users under the same entity share the business account.

  1. Sign in to the ACRA API Marketplace with the authorized Corppass identity.
  2. Choose the required service: Entity Information Query, Financial Information Query, or trustBar Verification Query.
  3. Use the mock API before production where available.
  4. Create the application and obtain the Client ID, Client Secret, or API Key shown for the subscription.
  5. In API Overrides choose ACRA Bizfile API Marketplace and enter the marketplace URL, official source URL, and issued credentials.
ACRA API Marketplace connection form and credential fields
The ACRA connection records the official marketplace and source URL separately from secret credentials.

04

Register the IRAS application

Use the IRAS API Developer Portal to select a plan, register an application, inspect operations, and test APIs. AIS flows may also require APEX OAuth details and signing material.

  1. Browse the API or plan in the IRAS Developer Portal and confirm eligibility.
  2. Register an application and subscribe it to the required product plan.
  3. Test the operation in the portal using sandbox credentials.
  4. For AIS/APEX OAuth, register the exact redirect URI and public JWKS; keep the ES256 private key only in the platform vault.
  5. In API Overrides choose IRAS API Marketplace and complete environment, base URL, client credentials, API key, signing key ID, organization name, and private key fields that apply.

05

Prepare CPF EZPay

CPF EZPay requires Singpass and a CPF Submission Number. First-time UEN entities assign the CPF EZPay e-Service to authorized officers in Corppass.

  1. Apply for or confirm the organization’s CPF Submission Number.
  2. Assign CPF EZPay in Corppass to the authorized officer.
  3. Choose the submission method: CPF EZPay, Electronic Standing Instruction, or FTP based on the payroll workflow.
  4. Configure Direct Debit early or plan PayNow QR payment.
  5. In API Overrides choose CPF EZPay and record the official portal, submission mode, CSN, and FTP credentials only when FTP is used.

Expected result: The payroll team can prepare a contribution file or submission, while an authorized person still verifies and completes payment in the official channel.

06

Complete the production control check

Government sandbox success is not production authorization.

  1. Confirm the platform organization, UEN, agency account, and reporting period all match.
  2. Verify the authorized submitter and approver are current.
  3. Test retrieval or validation before attempting a live filing.
  4. Save the agency acknowledgement and platform audit evidence after submission.

Troubleshooting

  • No agency application is visible: check the Corppass entity and the user’s assigned service.
  • Sandbox works but production fails: confirm production approval, endpoints, keys, and registered redirect/JWKS.
  • CPF submission is not complete: verify payment status in CPF EZPay; file preparation alone is not payment.

Official sources