Trust / YMYL

Methodology and Data Sources

How KBLI, OSS, KLU, BTKI, and UMP data is collected and verified. Source tiers: official, derived, fallback. Editorial policy and review process.

2 pages in this section 2026 reference Official Indonesian source cross-check required

Pages in this section

Published: 2026-08-13 Reviewed: 2026-08-13 Authority: Official Indonesian source cross-check required

How the methodology works

This site is a reference layer, not a substitute for the official decision maker. We first collect raw data, then normalize it, and only after that publish a public page. Every step keeps enough source trace to make the page auditable later.

Workflow

  1. Pull primary material from official portals, regulations, or authoritative documents.
  2. Normalize the data so labels, codes, and hierarchy remain consistent.
  3. Compare against support sources when structure or terminology needs clarification.
  4. Mark anything incomplete, unstable, or still awaiting verification.
  5. Publish only the claims that are strong enough for public reference use.

Source tiers

TierMeaningHow it is used
officialA primary source that can be checked again laterUsed for core claims, definitions, and structure
derivedA normalized structure built from official dataUsed for navigation, crosswalks, and hierarchy
fallbackA support source used when the official file is awkward to use directlyUsed only to fill gaps, never to replace the main claim
needs-verificationThe signal is strong, but manual checking is still neededHeld back until a stronger check is available
pending-importThe target dataset is not in the publish pipeline yetNot used for final public claims

What we verify

  • titles and codes must match the source
  • parent/child relationships must stay consistent
  • effective dates and version notes must be clear when available
  • internal links must point to the correct pages
  • schema and metadata must reflect the visible content

When a page is held back

We hold a page when the primary source is missing, when a conflict is still unresolved, or when the page would look complete even though the data coverage is still thin. For YMYL topics such as licensing, tax, regions, or business classification, being clear is more important than being fast.

How conflicts are resolved

If two sources disagree, we do not pick the easier one. The first priority is the most specific and most recent official source that can still be verified. If the conflict remains open, the page is downgraded to needs-verification or fallback until the evidence improves.

Review cadence

Every page has its own review date. That date changes when metadata, source references, or internal links are updated. Faster-moving datasets, such as minimum wages, are reviewed more often than more stable classification layers. Regulatory datasets are reviewed when there is evidence of rule changes or editorial corrections.

See also

Contact us

If you spot a data issue, send the page URL, the disputed section, and the primary source you want us to compare it against.

Reports that include an official source link and a short explanation of the issue are usually the fastest to review.

Changelog

  • 2026-08-13 - The reference page was published with the initial source layer, structure, and coverage note.
  • 2026-08-13 - Metadata, internal linking, FAQs, and source-verification notes were updated.

This portal is informational. Confirm the final obligation and competent authority before filing, licensing, payroll, tax, or investment decisions. Read methodology.