Regalkes, OSS-RBA and e-suka: Indonesia Online Licensing Systems

1. Key takeaways

Indonesia runs its device and PKRT licensing through three connected online systems, and most operational failures come not from the regulations but from inconsistent entity data and missed deadlines inside these systems. Knowing what each portal does, and keeping the data aligned across all three, prevents the majority of avoidable account and submission problems.

• Regalkes (regalkes.kemkes.go.id) is the registration submission and search portal for devices and PKRT.
• OSS-RBA (oss.go.id) is the entry point for corporate business licensing (NIB, IDAK, CDAKB compliance status) and for some notification-regime applications.
• e-suka (esuka.binfar.kemkes.go.id) is used to apply for various confirmation letters, including SKI, SAS, raw material and spare part imports, and advertising approvals.
• The three systems are connected through a single sign-on (SSO) mechanism.
• The most common sticking point is inconsistent entity information. The company name, address and email must be completely identical across Regalkes, OSS and KFA. The email is the critical field: the KFA system expressly requires the licence holder to update the KFA email to match Regalkes and to match the OSS registration email. Otherwise, accounts can be locked and electronic procurement transactions cannot be completed.
• Operational details: the systems are fully electronic and no longer accept paper applications; electronic certificates require no stamp duty seal or wet signature and can be printed by the holder through INSW or Regalkes; declaration-type submissions must bear the required stamp duty; uploaded files follow strict format and naming rules, commonly PDF with a size limit per file.
• System downtime does not excuse missed deadlines. Industry reporting indicates that the Regalkes system was shut down for an upgrade from 15 December 2025 to 9 January 2026, and NIEs expiring during that period were deemed invalid from 1 January 2026. This downtime information is industry reporting, pending verification against official announcements.
• The practical reading of the episode is simple: deadlines are absolute even when the infrastructure is not available, so every deadline-driven action must be scheduled with a buffer large enough to absorb an outage of the kind described.
• Because the three systems are linked through single sign-on, an error in one system’s entity data can propagate into login and transaction failures in the others, which is why data consistency is an operational requirement rather than a cosmetic preference.

2. Legal basis

The operational foundation consists of the three portals themselves and the circulars that govern them. The Regalkes portal (regalkes.kemkes.go.id) hosts the registration and search functions; OSS RBA (oss.go.id), together with its panduan guidance pages, hosts the business licensing functions; and e-suka (esuka.binfar.kemkes.go.id) handles the confirmation letter applications. The requirements on KFA email synchronisation are set out in Kemenkes circulars, with the circular reference to be taken from the current issue in force. The treatment of electronic certificates, which require no stamp duty seal or wet signature and can be self-printed through INSW or Regalkes, reflects the fully electronic administration of the regime, while declaration-type submissions remain subject to the stamp duty requirement. The downtime episode is documented here as industry reporting pending verification against official announcements, and it demonstrates the operative principle that a system outage does not constitute an excuse: obligations continue to run even when the portal cannot receive filings. Taken together, the operational rules of this section are not treaty-level law but portal-level administration, and they change more often than the regulations do; the checklist below should therefore be re-verified against the current portal pages and circulars at each renewal cycle rather than treated as fixed.

3. Expert insights

Build a system calendar. Submit renewals as soon as the window opens 9 months before expiry, and never wait until the last 60 days. The downtime episode shows why: an NIE that expires during a period when the system cannot accept filings is treated as invalid from its expiry date, and the outage itself provides no relief. A renewal filed months early would have been unaffected; a renewal filed in the final weeks had nowhere to go. Beyond timing, unify the KFA, OSS and Regalkes email addresses on a company domain mailbox and designate a specific person to receive notifications, because account lockouts and missed deficiency notices most often trace back to a mailbox nobody monitors. These are small administrative disciplines, but they govern whether the entire regulatory investment in a certificate remains usable, and they cost almost nothing to implement compared with the losses they prevent.

4. Practical recommendations

• Operate a system calendar for every certificate: file the renewal as soon as the 9-month pre-expiry window opens, never in the last 60 days.
• Audit entity data across Regalkes, OSS and KFA so that the company name, address and email are completely identical in all three systems, and re-verify after any corporate name or address change.
• Unify the KFA, OSS and Regalkes email addresses on a company domain mailbox, and assign a named person to receive and act on system notifications.
• Treat the downtime episode as a planning lesson rather than an exceptional event: this information is industry reporting pending verification against official announcements, but the underlying principle that system unavailability does not excuse an expiry should be built into every renewal plan.
• Prepare uploads to the current format and naming rules, commonly PDF within the per-file size limit, before starting a submission, so that file rejections do not consume evaluation days.
• Confirm where each transaction belongs before filing: registrations and searches in Regalkes, corporate licensing and certain notifications in OSS RBA, and confirmation letters such as SKI, SAS, raw material and spare part imports and advertising approvals in e-suka.

5. Verification checklist

• □ Regalkes portal (regalkes.kemkes.go.id).
• □ OSS RBA (oss.go.id) and its panduan guidance pages.
• □ e-suka (esuka.binfar.kemkes.go.id).
• □ Kemenkes circular on KFA email synchronisation (circular reference as currently in force).
• □ Downtime information is industry reporting, marked pending verification against official announcements.

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, authorised representative and local testing support across Southeast Asia, including Indonesia. Our team prepares dossiers to ASEAN CSDT structure, manages AKL/AKL-I submissions with Kemenkes, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com