In short
- The PIB (Pemberitahuan Impor Barang) is the electronic import declaration — BC 2.0 — filed through the customs system by a licensed PPJK.
- Its key fields are not clerical: identity, classification, value, preference and permits are the five decisions of the import.
- The filing carries an identity: whose NPWP/NITKU it is filed under owns the tax record it creates.
- Most rejections trace to a short list of causes — digit errors, description drift, value queries, missing permits — all preventable before sailing.
What the PIB is
The declaration that converts a physical arrival into a legal import — and a tax event.
- Electronic, standardized: the BC 2.0 form through the customs system; data-driven, so consistency across documents is machine-checkable.
- Filed by a licensed PPJK on behalf of the importer of record — legal representation, not data entry. See Customs Clearance Service.
- Binding: the values, codes and claims on it become the position of the importer — including in a future audit. See Customs Audit.
- Gating: assessment, payment, risk channel and release (SPPB) all flow from the filed data.
The key fields and why each matters
Five field groups decide the file. Everything else is supporting detail.
- Container and B/L data bind the declaration to the physical cargo — a mismatch there is a whole other category of delay. See Cargo Tracking.
| Field group | What it sets | What goes wrong when sloppy |
|---|---|---|
| Importer identity | NPWP, NITKU, API — who owns the declaration and the tax record | Rejection on digit mismatch; filing under the wrong establishment |
| Goods and classification | Description and HS code per line — duty, PPN treatment, Lartas | Wrong duty; permit gaps; examiners query the mismatch |
| Customs value | CIF in currency, converted at the prevailing NDPBM | Valuation queries; the audit history begins here |
| Preference and claims | FORM E reference when ACFTA rates are claimed | Missed claims pay full MFN; inconsistent claims bounce |
| Permits and references | Lartas approvals the declaration references | Rejected filing until the permit exists |
The timeline of a clean file
Illustrative timeline for a prepared, consistent file. Every step shortens when the preparation was done at sea.
| When | What happens | Who acts |
|---|---|---|
| Before sailing | HS verified on INSW/BTKI; permits screened; identity digits checked; PIB drafted | PPJK with importer input |
| Arrival data lands | Filing submitted; registration number issued | PPJK |
| Day 1–2 | Assessment computed; duties paid through the official channel | PPJK coordinates; importer funds |
| Day 2–3 | Risk channel resolves (or examination is scheduled) | System — quality decides |
| Day 3–5 | SPPB released; D/O settled; delivery dispatched | PPJK and trucking |
The compressed version: A file prepared before sailing clears in days. The same file prepared after arrival clears in the same number of steps and a multiple of the days — because every step now waits on the previous one. See Transit Times.
Whose name owns the tax record
The most consequential line on the PIB is the identity block — and it is a business decision, not a formality.
- Filed under your NPWP/NITKU and API: the PPh 22, the PPN trail and the audit history are yours — creditable, auditable, bankable.
- Filed under a third party (undername): the tax record belongs to that party. Your goods moved; your company built nothing. See Undername Import Risks.
- The audit trail follows the identity: future queries address the filer identity, not the buyer. A stranger in your disputes is a structural cost.
- Decide deliberately: own-name whenever you hold the trio; undername only as a documented interim choice. See NPWP, NIB & API.
Common rejection reasons, and their fixes
The list that accounts for most bounced files. Every fix is a pre-filing step.
| Rejection reason | Typical root cause | Fix, and when |
|---|---|---|
| NITKU/NPWP digit mismatch | Retyped identifiers, stale location data | First-16 check against NPWP — before filing |
| HS code inconsistent with description | Supplier wording carried over unexamined | Verified classification and one consistent description — before sailing |
| Valuation query | Invoice value below plausible band for the goods | True values and complete cost build-up — always |
| Missing permit reference | Lartas cargo filed without its approval | Permit before goods — before booking |
| FORM E data mismatch | Certificate, invoice and B/L disagree | Consistency pass on the certificate — before sailing |
| Container/B/L data mismatch | Copy-paste between shipments | Reconcile against the actual transport documents — at filing |
After release: the declaration lives on
The PIB is not a ticket that expires at the gate — it is the beginning of a record.
- Keep the file: PIB, assessments, payment proofs, certificates. Records are the currency of any future query or audit.
- Reconcile: the assessed values, codes and rates against what was estimated — discrepancies are checkable and we check them.
- Learn per lane: each completed file sharpens the next — recurring codes, recurring permit paths, stable identity data.
- The relationship: a clean declaration history is an asset that compounds; a messy one is a tax on every future shipment. See Common Mistakes.
Related pages
This page summarizes field practice and publicly available Indonesian import rules for general business reference only—it is not legal, customs, or pricing advice. Customs provisions, tariff rates, and licensing requirements keep changing, so the rules in force at the time and the official processing result always prevail. Wuhan Freedom International Logistics Co., Ltd. · Licensed PPJK in Indonesia · Jakarta / Semarang / Wuhan.