Registry entry

Indonesia OSS Individual/UMK Business Identification Number (NIB) Registration

Register a new Business Identification Number (Nomor Induk Berusaha, NIB) for an individual Micro or Small Business (Usaha Mikro dan Kecil, UMK) actor through Indonesia's Online Single Submission Risk-Based Approach system (OSS RBA, oss.go.id), operated by the Ministry of Investment and Downstream Industry / Investment Coordinating Board (BKPM) under Government Regulation No. 5 of 2021 and Law No. 11 of 2020 on Job Creation. Opens Indonesia as the registry's 18th jurisdiction and its Business Formation vertical, the closest Indonesian analogue to us/irs/employer-identification-number-ss4, ph/bir/tin-application-corporations-partnerships, and sg/acra/sole-proprietorship-registration: the NIB is simultaneously a business identification number, an importer identification number, and (for eligible low-risk activities) the business license itself. Covers the full individual-applicant pathway end to end: OSS mobile-number account registration, KTP (electronic ID card)-based applicant profile data, business-actor tax/social-security identifiers, KBLI (Klasifikasi Baku Lapangan Usaha Indonesia, the 2020 Indonesian Standard Industrial Classification) business-field selection, land-area/capital data that feeds OSS's own automated risk-and-scale validation engine, business detail, business-location data, product/service listing (including halal and SNI/Indonesian National Standard certification status), and the mandatory self-declaration (Pernyataan Mandiri) of compliance with spatial-planning (KKPR), safety/health/environmental (K3L), and environmental-management (SPPL) commitments. Scoped to a single natural-person (orang perseorangan) applicant registering under the UMK (Usaha Mikro dan Kecil, capital up to Rp5 billion excluding land/buildings) pathway with exactly one KBLI business-activity code and one product/service line; does not model account password/OTP verification screens, the login (Masuk) screen, the Non-UMK/business-entity (PT/CV/Yayasan) pathway, adding a second or subsequent KBLI code or product/service line via the wizard's own 'Tambah Bidang Usaha'/'Tambah Produk / Jasa' repeat actions, downstream sectoral/PB-UMKU permits, or the read-only NIB certificate output — see VERIFICATION.md. This document does not submit the registration; the live OSS RBA system (oss.go.id) and BKPM are always authoritative.

Registry entry

id/bkpm/oss-nib-registration-individual-umk

Jurisdiction
Indonesia · national
Version
1.0.0
Verification
draft
Authority
Ministry of Investment and Downstream Industry / Investment Coordinating Board (BKPM)

Authoritative source OSS RBA official user guide, 'Individual UMK Licensing through OSS Indonesia Application' (English-language, 20-step screenshot walkthrough of the OSS Indonesia mobile app), published at oss.go.id/en/panduan/635970086345c7d71a814499

Machine access

Schema document
registry/id/bkpm/oss-nib-registration-individual-umk/1.0.0/schema.jsonapplication/schema+json
Verification record
registry/id/bkpm/oss-nib-registration-individual-umk/1.0.0/VERIFICATION.mdtext/markdown
Registry catalog
registry/index.jsonone record per schema id

Field reference

39 fields across 9 steps, read from the published schema.json, with names, types, requiredness, and validation as the document states them. The live government form remains the authoritative source.

OSS Account Registration

  • mobileNumber string required

    Active Indonesian mobile number, never previously used in the OSS system, prefixed with the country code (+62). Verified via a one-time WhatsApp code before the applicant profile step can continue; the verification code itself is not modelled (ephemeral, not durable application data).

    patternclassification: pii

Applicant Profile (KTP Data)

  • nik string required

    The applicant's 16-digit National Identity Number (Nomor Induk Kependudukan), as printed on their electronic KTP (Kartu Tanda Penduduk). Forms the basis of both the OSS account profile and the later NIK carried onto the Business Actor Data screen.

    patternclassification: sensitive-pii
  • fullName string required

    Full legal name exactly as printed on the applicant's electronic KTP.

    length: 0–100classification: pii
  • dateOfBirth date required

    Date of birth as printed on the electronic KTP. The source app's own input format is DD-MM-YYYY (worked example: '19-01-1992').

    classification: pii
  • gender string required

    Dropdown; only the selected value ('Laki-Laki', male) is visible in the guide's worked-example screenshot, not the full option list, so no enum is asserted.

    length: 0–20
  • address string required

    Residential address as printed on the electronic KTP.

    length: 0–200classification: pii
  • province string required

    Residential province. Dropdown; only the selected value ('Jawa Barat') is visible in the worked example, not the full 38-province option list, so no enum is asserted.

    length: 0–100
  • regency string required

    Residential regency or city (kabupaten/kota), cascading from the selected province. Worked example: 'Kab. Bekasi'.

    length: 0–100
  • district string required

    Residential district (kecamatan), cascading from the selected regency/city. Worked example: 'Cikarang Utara', confirmed on the same profile screen just below the fold shown in Step 8's own screenshot.

    length: 0–100
  • village string required

    Residential village or sub-district ward (desa/kelurahan), cascading from the selected district. The field's label is visible on the same profile screen as district, but its worked-example value is covered by a 'successful registration' confirmation dialog in the source screenshot and is not independently confirmed — see VERIFICATION.md.

    length: 0–100

Business Actor Data

  • email string optional

    Email address shown on the Business Actor Data screen alongside the applicant's carried-over NIK, name, gender, and phone number. The worked-example screenshot shows this row with no visible value (only a small expand marker), so whether it is a locked/pre-filled field (matching the pattern of the other carried-over fields on this screen) or a genuinely blank optional input could not be confirmed from this source — modelled as optional pending live-app confirmation.

    length: 0–254classification: pii
  • npwp string optional

    Taxpayer Identification Number (Nomor Pokok Wajib Pajak), if the applicant already has one. The guide explicitly instructs: 'Fill in NPWP, BPJS Ketenagakerjaan, dan BPJS Kesehatan if you already have them' — all three are optional at this step.

    length: 0–20classification: sensitive-pii
  • bpjsKetenagakerjaanNumber string optional

    Employment social security (BPJS Ketenagakerjaan) membership number, if the applicant already has one.

    length: 0–20classification: sensitive-pii
  • bpjsKesehatanNumber string optional

    Health insurance (BPJS Kesehatan) membership number, if the applicant already has one.

    length: 0–20classification: sensitive-pii

Business Classification (KBLI)

  • businessActivityType string required

    Dropdown; only the selected value ('Utama', i.e. primary/main business activity) is visible in the worked example, not the full option list (which by analogy to standard KBLI classification convention elsewhere likely includes a 'Penunjang'/supporting-activity option, not itself confirmed here), so no enum is asserted.

    length: 0–50
  • kbliCode string required

    The 5-digit 2020 KBLI (Klasifikasi Baku Lapangan Usaha Indonesia, the Indonesian Standard Industrial Classification) code identifying the business's field of activity, selected via a keyword search against OSS's own built-in KBLI catalog (e.g. searching 'food stalls', 'fishing', or 'street vendors' surfaces matching codes). Each NIB is allowed to consist of one or more KBLI codes; this document models exactly one. Worked example: '56102'.

    pattern
  • kbliDescription string required

    The KBLI code's own catalog description, auto-populated alongside the code once selected. Worked example: 'Rumah/Warung Makan' (eating house/food stall), with an OSS-supplied explanatory note that the classification covers food-and-beverage service businesses operating from a fixed (non-mobile) premises.

    length: 0–300
  • businessActivityScope string required

    Scope of the business activity. Dropdown; only the selected value ('Seluruh', i.e. entire/all) is visible in the worked example, not the full option list, so no enum is asserted.

    length: 0–50

Business Scale Data

  • businessLandArea number required

    Total land area or floor space occupied by the business, in the unit selected by businessLandAreaUnit. Feeds OSS's own automated risk/scale validation engine (triggered by the 'Validasi Risiko' button) alongside businessCapital. Worked example: 50.

    range: 0–∞
  • businessLandAreaUnit string required

    Unit of the land-area value. Dropdown; only the selected value ('m²') is visible in the worked example, not the full option list, so no enum is asserted.

    length: 0–20
  • businessCapital number required

    Total business capital in Indonesian Rupiah (IDR), excluding land and buildings. Together with businessLandArea, this value is submitted to OSS's own automated engine that computes the business's scale (Mikro/Kecil/Menengah/Besar) and risk level (Rendah/Menengah/Menengah Tinggi/Tinggi) — a source-computed, read-only output not itself modelled as an applicant-input field (see VERIFICATION.md). Worked example: Rp 200,000,000.

    range: 0–∞classification: financial

Business Detail

  • businessAlreadyOperating boolean required

    Whether the business activity has already commenced operating. Source is a two-option radio button: 'Belum' (Not yet, modelled as false) or 'Sudah' (Already, modelled as true, the worked example's selected value).

  • businessName string required

    Name of the business or activity. Source shows a placeholder example ('Contoh: Pabrik Sepatu', i.e. Shoe Factory) and a worked-example value 'Warung Makan' (food stall).

    length: 0–200
  • businessActivityDescription string required

    Description of the business activity. Flagged, not silently corrected: the worked-example screenshot shows this field's own input box displaying the placeholder text 'Kabupaten/Kota' (the same label used for the unrelated regency/city selector elsewhere in this same wizard) rather than a description-shaped placeholder, and carries a dropdown affordance rather than a free-text one — apparently either a reused UI component or a genuine app-side rendering artifact in the source screenshot. This document models the field under its own section header (the only clearly legible label present) but its true purpose/shape is not independently confirmed — see VERIFICATION.md.

    length: 0–300
  • indonesianWorkerCount integer required

    Number of Indonesian workers employed by the business. Worked example: 4.

    range: 0–∞

Business Location

  • businessAddressSameAsPrevious boolean required

    Whether the business-location address is the same as the applicant's residential address or a previously-registered business activity's address. Source is a two-option radio button: 'Tidak' (No, modelled as false) or 'Ya' (Yes, modelled as true, the worked example's selected value). The guide's own screenshot shows the address and cascading region fields pre-filled and editable regardless of this toggle's value; the 'Tidak' branch's own resulting form shape was not independently observed in this source.

  • businessAddress string required

    The business's operating address.

    length: 0–200
  • businessProvince string required

    Business-location province. Worked example: 'Jawa Barat'.

    length: 0–100
  • businessRegency string required

    Business-location regency or city. Worked example: 'Kab. Bekasi'.

    length: 0–100
  • businessDistrict string required

    Business-location district. Worked example: 'Cikarang Utara'.

    length: 0–100
  • businessVillage string required

    Business-location village or sub-district ward. Worked example: 'Mekarmukti'.

    length: 0–100
  • businessPostalCode string required

    Business-location postal code. Worked example: '11772'.

    pattern

Products/Services

  • productServiceCategory string required

    Product/service category. Dropdown; only the selected value ('Lainnya', Other) is visible in the worked example, not the full option list, so no enum is asserted.

    length: 0–100
  • productServiceName string required

    Specific product or service name, entered as free text below the category dropdown. The source screenshot re-uses the identical section header 'Jenis Produk/Jasa' for both this field and productServiceCategory rather than giving this one its own distinct label — modelled here by its position and free-text input shape, not a separately-confirmed label; see VERIFICATION.md. Worked example: 'Nasi Rames' (a mixed-rice dish).

    length: 0–200
  • productionCapacity number required

    Annual production/service capacity, in the unit selected by productionCapacityUnit. The source's own capacity field carries a fixed '/ Tahun' (per year) suffix. Worked example: 20,000.

    range: 0–∞
  • productionCapacityUnit string required

    Unit of the production-capacity value. Dropdown; only the selected value ('Kursi', seats) is visible in the worked example, not the full option list, so no enum is asserted.

    length: 0–50
  • hasSniCertificate boolean required

    Whether the applicant already holds an SNI (Indonesian National Standard) certificate for the listed product/service, only asked when the product/service category requires one. Source is a two-option radio button: 'Tidak' (No, modelled as false, the worked example's selected value) or 'Ya' (Yes, modelled as true).

  • hasHalalCertificate boolean required

    Whether the applicant already holds a halal certificate for the listed product/service, only asked when the product/service category requires one. Source is a two-option radio button: 'Tidak' (No, modelled as false, the worked example's selected value) or 'Ya' (Yes, modelled as true).

Self-Declaration (Pernyataan Mandiri)

  • selfDeclarationAgreed boolean required

    Self-declaration checkbox, required under Law No. 11 of 2020 on Job Creation, by which the UMK applicant agrees to five published commitments: maintaining safety, security, health, and environmental-function preservation (K3L); willingness to fulfil obligations; willingness to undergo the halal-certification process; a Micro/Small Business statement of spatial-planning (KKPR) compliance; and a statement of willingness to manage and monitor the environment (SPPL). Must be checked before the application can be saved/submitted.

Verification record

This file is the source-review record for this document version, per the manual-source-review-v1 practice. It documents the provenance of the published fields and flow and states the current verification claim honestly.

Current claim

  • status: draft
  • verification.method: manual-source-review-v1
  • verification.lastVerifiedAt: 2026-07-07

The document was derived from a directly-read primary source: BKPM's own official OSS RBA user guide PDF, "Individual UMK Licensing through OSS Indonesia Application" — a genuine, 20-step, screenshot-driven walkthrough of the OSS Indonesia mobile app, in English, retrieved directly from oss.go.id's own CDN (s3.oss.go.id) with no login/CAPTCHA/WAF gate. It remains draft, not verified, pending live-app execution testing, per this registry's structural-reference maturity convention.

Why this document exists

This is a standing GovSchema Standard Research cycle (GOV-1546). Before picking this candidate, this cycle first re-screened the National ID & Civic Documents items the task brief itself named as targets (DE Steuer-ID, SG NRIC loss/damage/re-registration, NZ RealMe) and found all three already published: de/finanzamt/tax-identification-number, sg/ica/identity-card-reregistration (and sg/ica/identity-card-replacement), and nz/dia/realme-verified-identity respectively — not open gaps. It then re-checked the UAE Passport gap (CATALOG.md's own top open Passport candidate): both the ICP Smart App user manual (the same source already used for ae/icp/emirates-id-replacement) and the live icp.gov.ae "Issue New Passport"/"Renewal Passport" service pages remain checklist-level only (5 generic steps, 1 document, fee lines) with no field-level wizard screenshot — reconfirming the prior GOV-1474 finding unchanged; not re-attempted without new sourcing.

This cycle instead opened Indonesia as an 18th jurisdiction, a candidate CATALOG.md's own "Known Gaps" section had explicitly flagged as worth scouting ("Indonesia (OSS/NIB business registration, not screened in detail this cycle)"). OSS RBA's own panduan (guidelines) portal at oss.go.id/en/panduan publishes several genuine PDF guides; three were examined before this one was selected:

  • Panduan-Pembuatan-NIB.pdf (Indonesian-language, 17 pages) — a real screenshot walkthrough, but scoped only to adding a business field ("Tambah Bidang Usaha") to an NIB an account already holds, not first-time registration; a weaker starting point than a true end-to-end guide.
  • v2_EN_Pendaftaran-Hak-Akses-OSS-RBA.pdf (English, 4 pages) — covers only the initial OSS account/access-rights registration (NIK, email, password), not the NIB business-registration wizard itself; too thin on its own.
  • "Individual UMK Licensing through OSS Indonesia Application" (English, 20 pages) — selected. Genuinely covers the full pathway end to end, from mobile-app account registration through KTP-based profile data, business actor data, KBLI classification, land/capital data, automated risk validation, business detail, business location, products/services, the mandatory self-declaration, and NIB issuance — the strongest single source found this cycle, and richer than either of the other two guides alone.

Source examined

Access constraint and how it was worked around

The PDF is a plain, directly downloadable file from oss.go.id's own CDN — no login, no CAPTCHA. Its 20 pages carry only sparse instructional-caption text in the extractable text layer (e.g. "Fill in the form according to your Electronic KTP"); the actual in-app field labels only exist inside each page's embedded screenshot image. Every field in this schema was read directly off those rendered screenshots — each page rendered at 2.5x scale via pdfjs-dist + node-canvas (not the sparse text layer) and read with Claude's own vision capability, the same discipline already used for the AE ICP Smart App manuals in this registry.

What was confirmed directly (verbatim, from the rendered screenshots)

  • Step 3 (p.3): Nomor Telepon Seluler (mobile number), +62 country code prefix, "Kirim kode verifikasi melalui WhatsApp" button.
  • Step 7 (p.7): Password / Konfirmasi Password, with the source's own stated rule ("minimum 8 characters, combination of capital letters, lowercase letters, numbers, and special characters (!@#$%^&*_-)") — this screen's fields are not modelled (account credentials, not licensing data; consistent with how no other document in this registry models account-login credentials).
  • Step 8 (p.8): the KTP-based profile form — Nomor Induk Kependudukan, Nama Lengkap, Tanggal Lahir (format DD-MM-YYYY, worked example "19-01-1992"), Jenis Kelamin ("Laki-Laki" selected, no expanded list), Alamat, Provinsi ("Jawa Barat" selected), Kabupaten/Kota (label visible, cut off before a value).
  • Step 9 (p.9): confirms the same profile screen continues to Kecamatan ("Cikarang Utara") and a Desa/Kelurahan field whose label is visible but whose value is covered by a "Terima kasih sudah mendaftar di OSS" (registration-success) confirmation dialog overlaid on the same screenshot — the field's existence and position are confirmed, its worked value is not. Modelled as village, required (consistent with the other, fully-visible members of the same address cascade).
  • Step 11 (p.11): the "Data Pelaku Usaha" (Business Actor Data) card — NIK, Nama, Jenis Kelamin, Nomor Telepon shown as read-only/carried-over from the profile above; Email shown with no visible value; then editable NPWP, BPJS Ketenagakerjaan, BPJS Kesehatan inputs, each confirmed optional by the guide's own caption text ("if you already have them").
  • Step 12 (p.12): the KBLI classification card — Jenis Kegiatan Usaha ("Utama" selected), Bidang Usaha (a combined search field showing "56102 - Rumah/Warung Makan" plus an OSS-supplied explanatory note text), Ruang Lingkup Kegiatan ("Seluruh" selected).
  • Step 13 (p.13): Luas Lahan Usaha (worked example 50) + Satuan ("m²" selected), Modal Usaha (worked example Rp 200,000,000), "Validasi Risiko" button.
  • Step 14 (p.14): a read-only green result badge ("Skala usaha: Mikro" / "Risiko usaha: Rendah") — not modelled as a field (source-computed output, the same convention this registry uses for computed fee totals and risk/scale determinations elsewhere) — followed by the Business Detail card: Kegiatan usaha ini sudah berjalan? ("Sudah"/Already selected), Nama Usaha/Kegiatan (placeholder "Contoh: Pabrik Sepatu", worked value "Warung Makan"), a dropdown-styled input under the header "Deskripsi Kegiatan Usaha" whose own visible placeholder/value reads "Kabupaten/Kota" (see Judgment call 1 below), and Jumlah Tenaga Kerja Indonesia (worked value 4).
  • Step 15 (p.15): the Business Location card — Gunakan alamat yang sama dengan domisili atau kegiatan usaha sebelumnya? ("Ya"/Yes selected), Alamat Usaha (pre-filled/blurred in the worked example), Provinsi ("Jawa Barat"), Kabupaten/Kota ("Kab. Bekasi"), Kecamatan ("Cikarang Utara"), Desa/Kelurahan ("Mekarmukti"), Kode Pos ("11772") — all six address-cascade fields fully visible and unobstructed on this screen, unlike the profile screen's own partially-obscured equivalent.
  • Step 16 (p.16): the Products/Services card — Jenis Produk/Jasa (a category dropdown, "Lainnya"/Other selected) immediately followed by a second field sharing the identical section header "Jenis Produk/Jasa" but rendered as a free-text box (worked value "Nasi Rames") — see Judgment call 2 below — then Kapasitas (worked value 20,000, fixed "/ Tahun" suffix) and Satuan Kapasitas ("Kursi"/seats selected), followed by two Yes/No (Tidak/Ya) questions: "Apakah Anda sudah memiliki sertifikat Standar Nasional Indonesia (SNI)?" and "Apakah Anda sudah memiliki sertifikat halal?", both shown answered "Tidak" (No) in the worked example.
  • Step 17 (p.17): "Pernyataan Mandiri" (Self-Declaration) — a single checkbox "Saya sudah membaca dan menyetujui" (I have read and agree) gating five listed commitments (K3L safety/health/environment; willingness to fulfil obligations; willingness to undergo halal certification; a Micro/Small Business spatial-planning statement; and an SPPL environmental-management statement), with a "Simpan" (Save) button.
  • Step 18 (p.18): "Daftar Produk / Jasa" recap card with a "+ Tambah Produk / Jasa" (add another product/service) action — confirms the products/services list is genuinely repeatable, not modelled (single product/service instance only, pending GSP-0009 composite/repeating values, the same discipline used throughout this registry — see Judgment call 3).
  • Step 20 (p.20): the final "Cetak NIB" (Print NIB) certificate — a read-only government-issued output document, not modelled as an applicant-input field.
  • Steps 1-2, 4-6, 10, 19 (pp.1-2, 4-6, 10, 19): app install/navigation, WhatsApp OTP-code display, the post-registration "Masuk" (login) screen, and the "select KBLI for which the business license will be processed" navigation screen — none show applicant-input fields beyond what is already modelled elsewhere in this schema; not modelled as separate steps.

Judgment calls / scope cuts (read before reviewing)

  1. businessActivityDescription's visible content does not match its own section header — flagged, not fixed. The Business Detail screen's second input (p.14) sits under the header "Deskripsi Kegiatan Usaha" (Business Activity Description) but its own input box displays the text "Kabupaten/Kota" (Regency/City — the exact label used for the unrelated address-cascade field elsewhere in this same wizard) and carries a dropdown affordance rather than a free-text one. This could be a reused UI component bug in the live OSS app itself, or a stale/mismatched screenshot in the guide. Rather than silently modelling a clean "description" text field or silently dropping it, this document keeps the field (named by its own section header, the only clearly legible label) and states the discrepancy explicitly in its own description. A future reviewer with live-app access should confirm the field's true label and input shape.
  2. productServiceName's label is inferred from position, not confirmed text. The Products/Services screen (p.16) shows two consecutive input groups both headed "Jenis Produk/Jasa" — the first a dropdown (category: "Lainnya"), the second a free-text box (worked value "Nasi Rames"). The second field's own distinct label (something like "Nama Produk/Jasa", Product/Service Name) is never shown; this document infers it from the field's position and free-text shape, not from directly-read text. A future reviewer with live-app access should confirm the true label.
  3. No array/repeating-field type (GSP-0009). The wizard's own "Tambah Bidang Usaha" (add another KBLI) and "+ Tambah Produk / Jasa" (add another product/service) actions (pp.18-19) confirm a single NIB may carry multiple KBLI codes and multiple product/service lines. This document models exactly one of each — the worked example's own scope — the same discipline already used throughout this registry pending GSP-0009.
  4. Account-credential and navigation screens excluded. Password/ Konfirmasi Password (p.7), the WhatsApp OTP verification code itself (pp.4-6), and the post-registration "Masuk" login screen (p.10) are excluded — no other document in this registry models account-login credentials or ephemeral verification codes as durable application fields.
  5. Risk/scale validation output excluded. The "Skala usaha"/"Risiko usaha" result badge (p.14) is a source-computed output of businessLandArea and businessCapital, not itself applicant input — the same convention this registry uses for computed fee totals elsewhere (e.g. ae/icp/emirates-id-replacement's excluded fee-summary screen).
  6. Undocumented dropdown option lists. gender, province, businessActivityType, businessActivityScope, businessLandAreaUnit, productServiceCategory, and productionCapacityUnit each show only their selected value in the worked example's screenshot — no full option list is ever expanded on-screen. Per the discipline already established throughout this registry (e.g. ae/icp/emirates-id-replacement's preferredLanguage/passportType/deliveryMethod), none of these are modelled as enum; each is type: "string" with a description stating only the confirmed selected value. province in particular is not modelled as an enum despite Indonesia's ~38 provinces being a fixed list, because (unlike the UAE's 7-emirate precedent this registry has reused by analogy elsewhere) a 38-member list is not "small" enough to safely reproduce from memory rather than from the source itself.
  7. village's worked-example value is unconfirmed; its existence and label are. See "What was confirmed directly" above (Step 9) — the success-dialog overlay in the source screenshot covers this one value, not the field itself.
  8. email modelled as optional, not confirmed either way. See "What was confirmed directly" above (Step 11) — the Business Actor Data screen's Email row shows no visible value, so this document cannot confirm whether it is genuinely a blank optional input or a locked/pre-filled field like its NIK/Name/Gender/Phone neighbours on the same card.
  9. Scoped to Individual/UMK, not Non-UMK/business-entity registration. This guide's own title and its opening screen ("Pendaftaran hanya untuk pelaku usaha Mikro dan Kecil (UMK) orang perseorangan. Bagi jenis pelaku usaha lainnya, silakan mendaftar melalui situs oss.go.id") confirms it is scoped to natural-person Micro/Small Business applicants only; a Non-UMK/legal-entity (PT/CV/Yayasan) NIB registration pathway exists on the full oss.go.id web portal but is a distinct, unscreened flow — see "Known gaps" in CATALOG.md's own update for this cycle.

Path to a verified claim (next step)

  1. Independently re-fetch the same PDF and re-render/re-read each cited page, confirming every field sourceRef against the actual screenshot.
  2. Confirm OSS RBA has not since published a newer guide revision superseding this one, and that the guide's own URL (oss.go.id/en/panduan/635970086345c7d71a814499) still resolves to it.
  3. Obtain access to the live OSS RBA system (requires a real Indonesian NIK and WhatsApp-verifiable mobile number) to: confirm or replace the string-typed dropdown fields with real enum option lists; resolve the businessActivityDescription label/shape discrepancy (judgment call 1); confirm productServiceName's true label (judgment call 2); confirm village's worked value and email's true requiredness/lock state (judgment calls 7-8).
  4. Per this registry's structural-reference maturity convention, advancing maturity.criteria.verifiedSchema/agentReadySchema beyond a second reviewer's field-by-field pass requires live-app execution testing, not just source re-verification.

Re-verification

Per the practice's Cadence, nextReviewBy is set to 2027-01-01 (~6 months). Re-check the source, and confirm no newer guide revision has been published, on or before that date and on any source.url change.

View the raw record (VERIFICATION.md)

Version history

  • 1.0.0 draft latest this page has verification record schema.json

Independent and non-affiliated

GovSchema is an independent, open-source project. This reference is not produced, reviewed, or endorsed by Ministry of Investment and Downstream Industry / Investment Coordinating Board (BKPM) or any government. The authoritative source is always the live government form and its official instructions.