Verify Indonesian Company Documents Before Payment: AHU, OSS, Tax, and Bank Checks
No logo, QR image, seal, signature, PDF, screenshot, or public search result proves the entire company, license, authority, tax, and bank story by itself.
To spot fake or misleading Indonesian company documents, verify the issuer, current official record, legal entity, document identifier, date, status, scope, signatory or submitting authority, and relationship to other records. A genuine document can still be expired, superseded, altered after issuance, used for the wrong company, or presented as proof of a license or bank status it does not establish. Verification should therefore test the record chain, not visual appearance alone.
Before paying an agent, acquiring shares, signing a contract, funding capital, or relying on a claimed PT PMA, collect the relevant documents and independently verify the issuer, legal entity, identifier, current status, scope, authority, and consistency across AHU, OSS, tax, and bank records. Use the fake NIB and registration risk checks to identify common warning signs, then reconcile exceptions, escalate unresolved discrepancies, and preserve the verification evidence before proceeding.
Key takeaways
- Start from official domains reached independently, not from links or QR codes inside the document.
- Match entity, number, date, status, scope, location, authority, and version across records.
- Distinguish genuine, current, applicable, complete, and sufficient as separate conclusions.
- Stop payment or reliance when a material mismatch cannot be independently resolved.
Check a company document pack
Inventory each record, claim, issuer, identifier, version, authority, official source, and mismatch before reliance.
In this article
Inventory the documents and claims
List every document received and the claim it is supposed to prove. Typical items include deed, ministerial approval or notification, AHU company profile, shareholder and director data, beneficial ownership data, NIB, standard certificate, license, sector permit, NPWP or tax status, registered address, capital evidence, bank letter or statement, invoice, power of attorney, and identity documents. Record filename, page count, language, issuer, number, date, entity, version, source, and custodian.
The claim column is essential. An AHU company record may support legal-entity data; an NIB supports selected OSS registration data; a standard certificate may have a verification status; a bank statement may show a transaction but not the legal classification of capital. Do not let one authentic-looking PDF expand into claims it was never designed to prove. The company evidence for banks guide explains this proof-boundary principle in banking.
Create risk flags for inconsistent legal names, numbers, dates, addresses, shareholders, directors, capital, KBLI, locations, status words, fonts or page layouts, missing pages, cropped screenshots, broken or non-official links, editable file layers, unverifiable QR codes, personal payment accounts, unexplained translations, and documents obtained only through the seller. Visual anomalies trigger checking; they do not by themselves establish fraud.
| Document | Claim it can help test | Claim it does not prove alone |
|---|---|---|
| AHU company profile | Entity and selected corporate record data | Current licenses, tax compliance, bank access, or all ownership facts |
| NIB or OSS record | Selected business identity and licensing data | Every sector condition is active or the business is operational |
| NPWP or tax record | Taxpayer identity or status shown by issuer | All returns are filed or no tax debt exists |
| Bank evidence | Account or transaction facts within its scope | Capital classification, ownership, license, or source legitimacy |
Verify AHU and ownership records
Navigate independently to the official AHU domain and search the limited-company profile using the legal name or available identifier. Compare the returned legal name, entity type, establishment or change information, address, management, and other available data with the documents. Where a paid official extract or notary confirmation is required, obtain it through a controlled route. Record the search date, query, result, and limitations.
AHU's official limited-company profile search states that its PT data refers to Law 40 of 2007. AHU also provides a beneficial ownership search and explains that data may be submitted by authorities, corporations, notaries, or authorized corporate contacts. Treat public data as an official-source check, while verifying timeliness and reconciling it with deeds, registers, ownership charts, and identity evidence.
Confirm document authority and sequence. Identify the notary, meeting or shareholder approval, execution date, AHU submission, acceptance or notification, effective date, and subsequent amendments. Ask the issuing notary or qualified Indonesian counsel to verify questionable documents through independently sourced contact details. Do not call a phone number printed only on the disputed document or supplied by the seller.
Entity check
Match legal name, entity type, number, address, formation and amendments to official AHU data and current extracts.
Authority check
Trace shareholder or board approval, signers, notary, submission, acceptance, effective date, and later changes.
Ownership check
Reconcile deeds, shareholder register, AHU or beneficial ownership data, ownership chart, UBO identities, and control rights.
Verify before payment
Confirm entity, authority, scope, payee, bank details, milestone, deliverables, receipts, and remedies independently.
Verify OSS, licenses, tax, and bank claims
Use the official OSS portal's NIB search and current records to compare entity name, NIB, activities, locations, risk level, and displayed licensing status. Then identify any standard certificate, license, PB UMKU, sector approval, verification, technical requirement, premises condition, or operating limitation outside the NIB itself. A real NIB can be misrepresented as permission for an activity, site, or stage not covered by the record.
OSS is the official risk-based licensing portal and currently provides public NIB search on its official site . Use the current portal reached directly and preserve the result date. For tax claims, ask the company to obtain current evidence through DGT-controlled channels and reconcile it with returns and receipts; do not rely on a picture of an NPWP card to conclude that filings, PKP status, balances, or compliance are current.
For bank claims, verify the document directly with the institution through independently sourced contact information and lawful authorization. Match bank name, branch or channel, account holder, partial account identifier, date, currency, transaction, signatory or digital verification, and purpose. Never ask the bank to disclose protected data without authority. A legitimate remittance does not by itself prove that money is paid-up capital, that a license is active, or that the payer controls the company.
OSS scope
NIB, KBLI, project, location, risk, certificate or license, verification, PB UMKU, sector and operating conditions.
Tax scope
Taxpayer identity, registration and PKP status, filings, receipts, payments, account balance, notices, and period.
Bank scope
Institution, account holder, authority, transaction, date, amount, currency, purpose evidence, and confirmation limits.
Score mismatches and control payment
Classify each result as verified and consistent, verified with a limitation, stale or superseded, incomplete, unverifiable, inconsistent, or suspected alteration. Record the source, search or callback route, date, reviewer, evidence, discrepancy, response, and next action. Do not label a party fraudulent solely because a public search is unavailable or data is delayed; escalate material anomalies to the issuer, notary, authority, bank, and Indonesian counsel.
Use payment gates tied to verified claims. Before a service deposit, verify the contracting entity, payee, bank details, scope, authority, and milestone. Before a share acquisition or capital payment, verify the company, ownership, approvals, transaction documents, bank route, and conditions. Before signing an operating contract, verify entity authority, KBLI and license status, premises, tax invoice readiness, and the specific signatory. The registration payment safety checklist provides a companion milestone structure.
If alteration or fraud is reasonably suspected, stop new payment and reliance, preserve original files and metadata, communications, payment instructions, domains, account details, official searches, callbacks, and provider responses. Contact the bank or payment provider promptly about available protective steps and seek local legal advice on safe reporting. Do not modify the evidence, publicly accuse individuals without basis, or confront a suspected actor in a way that creates safety or recovery risk.
Mismatch log
Claim, document, official source, result, limitation, materiality, explanation, evidence, owner, and deadline.
Payment gate
Verified party, authority, payee, bank details, scope, milestone, deliverable, invoice, receipt, and remedies.
Incident file
Original files, hashes or metadata where available, messages, domains, accounts, payments, searches, callbacks, advice, and reports.
Official references and review basis
The following primary sources were checked on August 1, 2026. They establish the regulatory or service boundary used in this article; bank, tax office, OSS, AHU, and immigration decisions can still depend on the current record and the facts of a particular application.
- AHU — Limited-company profile search — Official source for selected limited-company profile data.
- AHU — Beneficial ownership search — Official source describing submitted beneficial ownership data and its contributors.
- AHU — Online guide index — Official guide index for corporate and beneficial ownership data searches and downloads.
- OSS — Official portal and NIB search — Official risk-based licensing portal with public NIB search and current licensing context.
The reliance test for Indonesian company documents
Rely on a document only within the claim it can support and only after confirming the issuer, entity, number, date, status, scope, authority, and current version through independently reached official or issuer channels. Reconcile AHU, ownership, OSS, licensing, tax, bank, corporate, and payment records; preserve limitations and unresolved differences rather than turning a public search into a blanket authenticity guarantee.
Stop payment or operational reliance when a material mismatch remains unexplained. Obtain Indonesian legal, notarial, tax, licensing, or bank confirmation for the specific risk. If the records support a legitimate new setup, compare the complete evidence chain with the Indonesia company registration framework before treating the entity as ready to transact.
Resolve a suspicious mismatch
Preserve evidence, stop new reliance, contact issuers through official channels, and obtain local advice.
Frequently asked questions
