Foreign branch Corppass access, administrators and recovery

Foreign branch Corppass access should be assigned to named people, tested against Bizfile and supported by a recovery record. A Corppass Admin account alone does not prove that the user can make ACRA transactions. ACRA’s guidance, updated on 9 September 2026, says users should check their assigned e-services and whether default access covers the service they need.

The branch should avoid a single-person dependency. Record who can approve administrators, who administers users, which people may file and who can recover access when a user leaves or cannot log in.

Distinguish the registered officer from the administrator

The Corppass administrator application page describes a Registered Officer as a person officially registered to the entity and an Admin as a person appointed to manage Corppass for it. Those functions may involve different people.

For a foreign company branch, start with the current ACRA record and the parent’s appointment authorities. Identify the authorised representative, any other registered officer recognised by the service, the intended Corppass administrators and the business users who need access.

Do not assume that a corporate service provider automatically owns the client’s administrator role. Record whether the provider is an Admin, Sub-Admin or user, and which internal person can approve, review or end that access.

Wait for the new UEN to become available

ACRA’s foreign-company after-registration page says the branch can register for Corppass after the entity is available, generally one day after registration. Keep the UEN and verified business profile ready.

Before applying, confirm that the registered officers shown by ACRA are current. A mismatch can delay approval or leave the wrong person controlling access. If the parent has changed its appointment between filing and activation, resolve the corporate record first.

Save the application reference, applicant, date and approval status. Do not store passwords or Singpass details in the corporate file.

Check Bizfile authority after login

The ACRA Corppass access guide warns that an Admin may still receive a not-authorised message. It tells users to inspect their profile and assigned e-services, including customised access and default access.

Test with a low-risk read action before a filing deadline. Confirm that the user can select the correct UEN, reach Bizfile and see the intended transaction class. A successful Corppass login is only the first check.

Record the digital service, role, parameter or transaction scope where applicable. A finance user may need tax services but not ACRA changes. A filing user may need Bizfile without broad access to every government service.

Use least access and separate duties

Give each person the access required for their work. Keep administrator authority narrower than a general convenience role where the business can do so. Review whether one person can both create a user and complete a sensitive filing without independent approval.

For company-secretarial work, identify the preparer, reviewer and authorised submitter. The parent should know which filings the external provider can make and which require fresh instructions. Keep engagement terms separate from the technical Corppass assignment.

Use individual accounts. Shared accounts make it difficult to identify who acted and are harder to revoke safely.

Create a branch access register

Prepare for ordinary access failures

List the first checks for a not-authorised error: correct UEN, active user, assigned e-service, role parameters and any recent change that has not taken effect. Capture the error text and time without recording credentials.

For an account activation or identity problem, use the official Corppass support route. For a Bizfile service assignment problem, follow ACRA’s profile checks. Do not repeatedly reset unrelated accounts or create duplicate administrators without understanding the cause.

Keep current contact details for the registered officer and administrators. A recovery process that sends approval to an old employee’s email address is not a working process.

Remove access during handovers

When staff or providers change, set an effective date and preserve the filings or acknowledgements they were handling. Assign and test the replacement before removing the departing person’s access where continuity permits.

After removal, review other connected services, saved browser sessions and provider permissions. Corppass termination does not automatically settle access in the branch’s bank, tax software or document systems.

Run a quarterly review and another review before major filings. Ask each role owner to confirm that the access remains necessary and that the person can still reach the intended service.

Keep evidence of the review date, users checked, access removed and unresolved items. If a user retains access for a short handover, set an expiry and a named person to confirm removal. This makes the review an operating control instead of an undated list of accounts.

Keep the parent company in control

The parent board or authorised management should receive a concise report of administrators, critical users, backup arrangements and exceptions. This is especially important where the branch relies on an external provider for local filings.

The foreign company entry options guide is the pillar cornerstone. The post-registration checklist covers the wider first month. The authorised representative guide explains the local appointment. The Market Entry and Domiciliation hub connects the library.

Reliable access is visible before a deadline. The branch should be able to name its administrators, show their authority, prove that Bizfile access works and recover control without asking a departed employee or an unknown provider account.