How should Finance/Tax and Company Secretary teams update workflows under PER-10/BC/2026 for customs-controlled goods and barang tidak dikuasai?

PER-10/BC/2026 changes how many businesses must operationalise the handling of customs-controlled goods, including barang tidak dikuasai, in day-to-day workflows—not just in the customs lane, but in inventory, accounting close, and tax positions. For importers, bonded zones/warehouses, and logistics operators, the business problem is predictable: unclear triggers lead to late responses, incomplete document packs, inventory that doesn’t reconcile, and finance teams forced to “guess” whether a write-down or write-off is defensible for Indonesia Accounting & Tax. This guide provides a role-based implementation roadmap (Ops/Customs, Warehouse, Finance/Tax, and Indonesia Company Secretary/Legal) so you can redesign SOPs from trigger → evidence → approvals → accounting entries → tax support → record retention, and stay audit-ready into 2027.

What operational “triggers” should your SOP recognise under PER-10/BC/2026 (so you act early, not after a hold)?

The fastest way to reduce disruption is to define clear triggers—events that force a controlled workflow and a controlled document pack. Under PER-10/BC/2026 the key issue is not memorising definitions; it is recognising when goods move into a customs-controlled state (including barang tidak dikuasai) and ensuring your organisation treats that moment as a formal status change.

Build a trigger register (simple, operational)

Create a one-page “trigger register” that sits inside your SOP and is mirrored in your inventory/warehouse system. Typical trigger categories to include:

• Detention / hold events: any official notice/communication indicating goods are detained, restricted, or placed under a customs control process.
• Non-claimed / uncollected goods risk: goods that remain unclaimed by the entitled party (customer/consignee/importer, depending on scenario) beyond internal thresholds and are at risk of becoming treated as not controlled by the owner.
• Discrepancy events: mismatch between import documentation and physical goods (quantity/spec mismatch), damaged cargo, missing packages, or “over/short” findings that push the goods into a special handling process.
• State-handling pathway events: events indicating goods may be subject to disposal/auction/destruction/other state-directed outcomes.

Map each trigger to a “clock start”

For each trigger, define:

• Clock start: when you treat the case as opened (e.g., date of notice received, date of BA/inspection, date warehouse flags non-claimed status).
• Owner: one accountable function (not a committee).
• First response deadline (internal): not a legal deadline—your internal SLA to avoid last-minute scrambling.

Practical outcome

If your SOP can’t answer “when do we stop treating this as normal inventory and start a controlled case file?”, you will see late escalations, inconsistent accounting treatments, and weak evidence during tax audit or internal audit review.

Who must do what, and when, across Ops/Customs, Warehouse, Finance/Tax, and Company Secretary?

PER-10/BC/2026 is implemented through handoffs. Most execution failures happen at the seams: Ops assumes Finance will ‘handle it later’; Finance assumes Ops has the documents; Legal/Company Secretary is informed only when something goes wrong.

A workable design is a RACI-based case workflow: Responsible, Accountable, Consulted, Informed.

Recommended role-based ownership (adapt as needed)

1) Ops/Customs (including PPJK/customs broker interface)

• Responsible for opening the case file at trigger, logging key dates, and managing correspondence.
• Responsible for obtaining official documents (notices, BA, inspection records, instructions) and ensuring completeness.
• Consulted on operational feasibility of options (return, re-export, rework, disposal route).

2) Warehouse/Bonded facility team (including inventory controller)

• Responsible for physical control: segregation, labeling, location control, and movement logs.
• Responsible for physical evidence: photos, counts, condition reports, and chain-of-custody.
• Consulted for storage cost tracking (for management decision-making).

3) Finance/Tax

• Accountable for accounting position and tax supportability.
• Responsible for creating a consistent accounting entry playbook (reclassification, impairment, provisions, write-off).
• Responsible for compiling audit trail: why the accounting treatment matches facts and evidence.

4) Company Secretary/Legal

• Accountable for internal governance: SOP updates, authority matrix, document retention policy.
• Responsible for ensuring management approvals are documented (minutes/resolutions where required by internal policy).
• Consulted on dispute posture, contractual notifications (customer/vendor), and record integrity.

A practical timeline that works for SMEs

• Day 0–2 (Trigger to Case Open): Ops opens case, Warehouse locks stock, Finance creates a “temporary status” in inventory/ERP.
• Day 3–10 (Evidence Build): document pack assembled; warehouse reconciliation and valuation inputs gathered.
• Day 10–20 (Decision Gate): management chooses pathway (recover, release, re-export, dispose, write-down/write-off), supported by Finance/Tax memo.
• Month-end (Close): accounting entries posted with evidence index; tax implications logged.

The goal is not speed for its own sake; it is preventing uncontrolled decisions made during month-end close without the evidence needed later.

What document pack should you standardise for barang tidak dikuasai and other customs-controlled goods?

Finance and Company Secretary teams need a standard “evidence kit” that can survive three tests: (1) operational reality, (2) customs file integrity, and (3) accounting/tax audit defensibility.

Design a document pack with three layers

Layer A — Authority & status documents (the ‘why’)

• Official notices/letters received and sent (and proof of delivery/receipt)
• BA/inspection reports or other official records evidencing status change
• Any instruction on handling route (e.g., hold, return, further examination, disposal path)

Layer B — Inventory & ownership evidence (the ‘what’)

• SKU-level inventory listing tied to import documents
• Physical count sheets, location map (rack/bin), photos, condition reports
• Movement log (segregation date, transfers, access control)
• Evidence of entitlement/ownership/abandonment context (contracts, Incoterms references in shipment docs where applicable, consignee instructions, non-claim correspondence trail)

Layer C — Outcome evidence (the ‘what happened’)

• Release/return/re-export documents if resolved
• Disposal/auction/destruction outcome documents where applicable (and reconciliation of quantities)
• Settlement documents (if any), third-party confirmations, and internal approvals

Evidence standards that reduce future disputes

• Index everything: one case number, one shared folder, one index sheet.
• Keep a correspondence trail: not just final letters; include emails and call logs summarised into a note.
• Make your inventory evidence “re-performable”: an auditor should be able to re-check quantities from source to outcome.

Implementation tip

Create a template called “Customs-Controlled Goods Case File” and make it mandatory for any trigger. If the case file is incomplete, Finance should not close the case with a write-off decision—only a temporary classification until evidence is complete.

How do you redesign warehouse and bonded-zone controls so inventory stays reconcilable during holds and special handling?

For bonded zones/warehouses and logistics operators, the risk is that physical controls and system status drift apart. Once that happens, Finance cannot support inventory balances, and Ops cannot demonstrate chain-of-custody.

Minimum control set to implement

1) Segregation & labeling

• Physically segregate controlled goods (cage/zone) with restricted access.
• Use clear status labels: “Under Customs Control — Case #___”.

2) System status code aligned to triggers Introduce status codes in WMS/ERP (even if basic):

• Normal
• On Hold (Customs)
• Under Review (Documentation)
• Pending Outcome (Disposal/Return)
• Released/Closed

3) Movement governance

• No movement without a movement ticket tied to the case number.
• Periodic cycle count for hold zone (frequency depends on volume/risk).

4) Cost capture (for decision-making) Track storage and handling costs for the case. This helps management decide whether to pursue release/recovery versus accept disposal/write-off where commercially rational.

Reconciliation workflow that Finance can rely on

At minimum, implement a weekly (or bi-weekly) reconciliation for open cases:

• Opening quantity per WMS
• Additions/removals with references
• Closing quantity per physical count spot-check
• Variances investigated and documented

This is not “extra admin.” It is what allows a defensible accounting position later, particularly if goods become non-recoverable.

What decision gates should management use before approving write-downs, write-offs, or disposal outcomes?

The biggest downstream tax and audit problems come from premature write-offs or inconsistent rationales across cases. PER-10/BC/2026-driven events can feel operational, but they create financial reporting consequences.

Use a 4-gate decision framework

Gate 1 — Control and probability

• Are the goods still under company control or a controlled process with a plausible release route?
• Is recovery probable, uncertain, or unlikely based on evidence (not hope)?

Gate 2 — Ownership and entitlement clarity

• Are you the economic owner of the goods, or are you holding as a logistics operator for another party?
• Do contracts/shipping terms indicate who bears the loss in this scenario?

Gate 3 — Valuation and impairment logic

• Are goods damaged, obsolete, or restricted such that NRV (net realisable value) is lower?
• Are additional costs required to make goods saleable (rework, re-labelling, re-export costs)?

Gate 4 — Evidence sufficiency

• Do you have enough Layer A/B documents to justify the accounting treatment?
• If not, approve only a temporary classification and complete evidence first.

Approval matrix (keep it practical)

• Ops recommends pathway with evidence
• Finance/Tax recommends accounting/tax treatment
• Management approves based on quantified impact (value, costs, timeline)
• Company Secretary/Legal ensures approvals are properly documented and retained

A short internal memo per case (1–2 pages) is usually enough—if it is structured and references the evidence index.

How should Finance record accounting entries for customs-controlled goods without creating audit gaps?

You want consistency, not creativity. Build an “accounting treatment playbook” so month-end does not become a case-by-case debate.

Step 1 — Separate operational status from accounting status

Operationally, goods may be “held.” Accounting-wise, your questions are:

• Is it still inventory?
• Is it impaired?
• Should it be reclassified (e.g., inventory under dispute/other assets)?
• Is a provision needed?

Step 2 — Standardise the journal entry pathways

Common pathways to design (names depend on your chart of accounts):

Pathway A: Reclassification (still recoverable, evidence incomplete)

• Move from normal inventory to “Inventory under customs control/held goods” sub-ledger.
• No P&L impact yet, but improve visibility and governance.

Pathway B: Write-down/impairment (value reduced, outcome uncertain)

• Recognise impairment based on supportable NRV estimates (and document basis).
• Keep the case open with periodic reassessment.

Pathway C: Write-off (non-recoverable with outcome evidence)

• Recognise write-off only when evidence supports loss recognition (e.g., documented disposal/destruction/irrecoverable outcome).
• Link write-off approval to management decision gate and evidence pack.

Pathway D: Third-party goods (logistics operator scenario)

• Ensure you are not recording customer-owned goods as your inventory.
• Focus on revenue recognition for services, and provisions only where contractually exposed.

Step 3 — Close with an audit trail, not just a number

For each open case at month-end, Finance should maintain:

• Case summary (status, expected outcome, next action date)
• Value at risk and accounting treatment
• Evidence index references

This makes 2027 audits and internal control reviews dramatically smoother because you can show disciplined judgment over time.

What Indonesia tax positions (PPN and PPh) should you map early to avoid “non-deductible” surprises later?

Tax risk is rarely triggered by the existence of a hold; it is triggered by weak evidence and inconsistent treatment between commercial reality, accounting, and tax reporting. You do not need to speculate on outcomes—you need a map of exposures and what evidence would support your position.

Start with a tax exposure map per case

Create a one-page “tax exposure map” with:

• Transaction type (import, domestic sale, service, warehousing)
• Who is the principal (importer of record / owner)
• Status outcome (released, returned, disposed, destroyed, auctioned)
• Documents available (by Layer)
• Intended accounting treatment

PPN/VAT: focus on coherence and documentation

Practical questions to resolve early:

• If goods are never sold and become non-recoverable, what is your documented basis for how PPN was handled at import and any subsequent adjustment logic?
• If there is a later reversal/correction, do you have the documentary trail to support it?

Avoid blanket assumptions. Your Finance/Tax team should document the factual chain: import event → control event → outcome event.

PPh (income tax): deductibility hinges on evidence and business purpose

Common pain point: losses/write-offs recorded in accounting but challenged as not sufficiently supported or not connected to business activity.

To improve defensibility:

• Keep the evidence pack complete (especially outcome evidence).
• Document management’s decision logic and commercial rationale (why recovery was not economical or not possible).
• Track related costs (storage, handling, disposal) with invoices and approvals.

Disputes and corrections: position without promising outcomes

If your case may result in adjustments, set up a controlled file that makes it easier to respond to queries from DJP later:

• Chronology of events
• Cross-reference of accounting entries to evidence
• Clear identification of who approved what and when

This is not about being aggressive or conservative—it is about being able to explain and support your position under review.

How should importers, bonded warehouses, and logistics operators tailor the workflow differently (so you don’t copy-paste the wrong SOP)?

A single checklist fails because the business model changes the accounting boundary (whose inventory is it?), the risk boundary (who bears loss?), and the evidence boundary (who holds the primary documents?).

If you are an importer

Your SOP should emphasise:

• Import documentation completeness and traceability to inventory
• Decision gates for impairment/write-off
• Alignment between Ops reality and Finance recognition
• Vendor/customer communications when responsibility is shared

Key control: Importer case owner + Finance co-owner must exist, or cases drift.

If you operate a bonded zone/warehouse (gudang berikat)

Your SOP should emphasise:

• Physical segregation, status coding, and movement governance
• Record integrity and reconciliation routines
• Clear demarcation between your inventory and customer inventory

Key control: WMS discipline (case number ties everything together).

If you are a logistics operator (3PL/forwarder)

Your SOP should emphasise:

• Contractual exposure assessment (are you liable for loss/damage?)
• Customer notification and instruction logs
• Avoiding erroneous inventory recognition (you may hold but not own)

Key control: Correspondence trail and service revenue vs principal risk analysis.

In mixed businesses (many SMEs are both importer and distributor), treat each shipment as a role-based case: sometimes you are principal, sometimes agent.

What controls should the Company Secretary/Legal function put in place to keep the business audit-ready into 2027?

Company Secretary/Legal is often pulled in too late—after Finance has posted write-offs and Ops has already “closed” the matter informally. Under PER-10/BC/2026 scenarios, governance is a control tool.

Update internal governance documents (lightweight, but real)

• SOP addendum: “Customs-Controlled Goods & barang tidak dikuasai case management”
• Authority matrix: who can approve disposal routes, write-offs, settlements, and external letters
• Document retention schedule: case file retention period aligned to audit and tax record needs (set internally; be consistent)

Implement a case register reviewed by management

A simple register (spreadsheet is fine) managed by Company Secretary/Legal or Compliance:

• Case number, trigger date, parties, value at risk
• Current status and next action
• Accounting treatment applied
• Document pack completeness score (e.g., Layer A/B/C complete or missing)

Review monthly with management and Finance. This creates an evidence-backed narrative that is hard to reconstruct after the fact.

Train the business on “what good looks like”

Short training beats long manuals:

• 60-minute session for Ops/Warehouse on evidence and status coding
• 60-minute session for Finance on decision gates and documentation expectations
• A shared glossary so teams use the same words for the same status

Where an implementation partner helps (without turning this into a sales process)

Firms like Paul Hype Page & Co. typically add value in translating the regulation into cross-functional SOPs, building the accounting/tax playbook, and stress-testing the document pack against audit questions—especially for SMEs that don’t have internal compliance design capacity.

How do you implement this in 30–60 days without overhauling your entire system?

The practical constraint for SMEs is bandwidth. Aim for a controlled minimum viable implementation that reduces risk quickly, then refine.

Days 1–10: Design the workflow

• Finalise trigger register and case numbering
• Assign RACI owners
• Create templates: case file index, case summary memo, tax exposure map

Deliverable: approved SOP addendum draft.

Days 11–30: Build controls where work happens

• Warehouse: segregation zone + labels + movement tickets
• Systems: add status codes (even manual in spreadsheet if WMS changes take time)
• Finance: create sub-ledger mapping and journal pathways

Deliverable: first “pilot case” processed end-to-end.

Days 31–60: Operationalise and measure

• Run the process for all new triggers
• Clean up old open cases using the new case file standard
• Set monthly management review and completeness scoring

KPIs that indicate the SOP is working

• % cases with complete Layer A/B documentation within 10 working days
• # of month-end adjustments caused by missing inventory status info
• # of write-offs without outcome evidence (target: zero)
• Cycle count variance rate in hold zone

If your KPIs don’t move, the issue is usually ownership (unclear case owner) or friction (templates too complex). Simplify and re-assign.

Conclusion

PER-10/BC/2026 is operationally “customs”, but the business risk shows up in inventory integrity, month-end accounting, and tax defensibility—especially when goods become barang tidak dikuasai or follow a state-handling pathway. The practical implementation move is to treat every trigger as a formal case: open a case file, lock the goods physically and in the system, build a standard evidence pack, run decision gates before any write-down/write-off, and retain an audit-ready trail that Finance/Tax and Company Secretary can stand behind into 2027. If you need help translating requirements into workable SOPs and an accounting/tax playbook that fits your operations (importer vs bonded warehouse vs logistics operator), Paul Hype Page & Co. can support the workflow design, documentation standards, and readiness reviews so your team can execute consistently.