Joint-operation tax control
KSO Registration in Indonesia: Joint Operations, NPWP and VAT
A contract-and-ledger framework for KSO registration, NPWP, PKP, VAT, income tax, and lead-firm responsibilities.
An Indonesian KSO must be analysed from its real joint-operation flow: who contracts with the customer, receives revenue, incurs costs, supplies contributions, and keeps the tax records. PMK 79/2024 makes the NPWP, PKP, VAT, and income-tax treatment depend on those facts rather than on a project nickname alone.
The practical control is to design the agreement, lead-firm mandate, invoice chain, and KSO/member ledgers together before the first customer contract or taxable supply is executed.
Key takeaways
- PMK 79/2024 provides a specific tax regime for KSO and distinguishes KSO that must have NPWP and PKP status from those whose members perform the obligations.
- The NPWP test follows the agreement and execution: customer supplies, income, and costs or payments in the KSO’s name are central facts.
- For a registered KSO, the lead firm, domicile, customer flow, member contributions, ledger, and tax calendar must be documented together.
- PKP and VAT treatment require a planned invoice chain from members to KSO and from KSO to customer, matched to the agreement and current tax rules.
- Income-tax reporting, bookkeeping, withholding, and member recognition should be designed at transaction level before revenue arrives.
Classify the KSO’s operating model
A KSO (Kerja Sama Operasi) is not automatically a separate company, but it can have its own tax treatment where the agreement and its execution meet the current criteria. PMK 79/2024 defines KSO as a joint arrangement among members with joint control or rights to assets and obligations for liabilities, whatever its name or form. Start with the agreement and the actual operating model: who signs with the customer, receives income, incurs costs, provides goods or services, issues invoices, holds assets, appoints staff, and carries performance risk.
That fact pattern matters because PMK 79/2024 distinguishes KSO that must have NPWP and may need PKP status from KSO whose tax obligations are performed by the individual members. The official DJP explanation of PMK 79/2024 explains that a KSO must register for NPWP when its agreement or execution includes activities such as supplying goods or services, receiving income, or incurring costs or making payments to third parties in the KSO’s name. Do not classify the KSO from its project nickname or the lead firm’s preference; follow the agreement, customer flow, and actual accounting execution.
Prepare a one-page operating model before registration. It should name every member, the lead firm, scope, contract party, revenue recipient, cost payer, contributor roles, asset ownership, invoice issuer, payroll owner, tax owner, and how residual profit or loss is allocated. This factual map is the foundation for NPWP, VAT, income-tax, and bookkeeping decisions.
Map the KSO’s real contract and cash flow first
A short operating-model review can distinguish a member-only arrangement from a KSO that must be registered and operated as a tax-relevant joint operation.
Apply the NPWP decision test
Use the KSO agreement and execution evidence together. A KSO that supplies goods or services, receives or earns income, and/or incurs costs or pays income to third parties in its own name meets the core tests highlighted in PMK 79/2024. Where those facts are absent, the members may perform the tax obligations themselves. The distinction is evidence-driven: small wording changes in who invoices or pays can change the tax operating model.
For a KSO that is required to register, the DJP explanation says registration is made at the tax office whose territory covers the KSO’s domicile, which is the domicile or residence of a member designated to represent the KSO as lead firm. Check the current procedure and data fields with the Directorate General of Taxes ; do not assume a generic corporate-registration checklist applies to the KSO.
Run the test at signing and at every operational change
- Customer contract: is the KSO itself named as provider, is a member named, or do members contract separately for their own share?
- Revenue: does the KSO receive cash or issue a claim, or does each member bill the customer directly?
- Costs: does the KSO contract with vendors or pay staff, subcontractors, and suppliers in its own name?
- Contributions: what goods or services do members supply to the KSO, at what agreed value, and who records the evidence?
If a KSO was registered under an earlier approach but no longer meets the current NPWP criteria, do not ignore the mismatch. The DJP article notes that an existing KSO that does not meet the mandatory-NPWP criteria must seek deletion of its NPWP. Confirm the current facts and procedure before changing registrations or tax filings.
Build the lead-firm and KSO ledger
A lead firm is not simply a ceremonial contact. It should have a documented mandate to represent the KSO for tax registration and the agreed operating tasks, while the agreement separately states what remains with each member. Build a KSO ledger that can identify every source document, customer event, member contribution, vendor cost, tax invoice, withholding item, cash movement, and allocation to members. Without this ledger, a KSO can have an NPWP but still be unable to support the reporting it needs.
| Ledger area | KSO record | Member record | Reconciliation point |
|---|---|---|---|
| Customer revenue | Contract, invoice, collection, output tax, recognition date. | Member allocation and resulting income recognition. | Invoice and customer receipt match. |
| Member contribution | Agreed type and value of goods/services received. | Supply evidence and any invoice to the KSO. | Contribution value matches KSO cost entry. |
| Third-party cost | Vendor contract, payment, withholding, asset or service use. | Member support only if separately agreed. | Payer, beneficiary, and tax owner agree. |
| Profit/loss and close | Tax calculation, return, residual allocation, closing record. | Member accounting and tax treatment where applicable. | KSO and member ledgers close to the same result. |
If the project is actually an incorporated operating company rather than a time-bound joint operation, assess the entity route through company registration in Indonesia . A KSO agreement cannot substitute for a corporate structure where the business needs permanent ownership, broader operations, or a different investment and governance architecture.
Align the lead firm, KSO ledger, and member records
A controlled reconciliation can connect the KSO agreement, customer contract, contribution values, third-party costs, tax invoices, payments, and member allocations before reporting begins.
VAT and invoice flow
PMK 79/2024 also covers PKP confirmation and VAT/PPnBM treatment. The official DJP explanation says a KSO must report for PKP confirmation if it crosses the small-entrepreneur VAT threshold and/or one or more members are already PKP. It further describes VAT on taxable goods or services supplied by members to the KSO and by the KSO to customers, subject to the current tax rules. The exact PKP, timing, e-invoice, and credit position must be verified against live requirements.
The invoice chain should be agreed before the first taxable supply. When the KSO supplies the customer, it needs the KSO-side invoice and output-tax record. When a member supplies goods or services to the KSO, the member’s contribution must be documented at the agreed value under the KSO agreement. The official explanation states that the relevant tax-invoice timing for member-to-KSO supplies is linked to the KSO’s taxable supply to the customer. Keep the agreement, contribution detail, and invoices together.
For a broader PKP context, see the Indonesia VAT registration overview . That article is a general company reference; KSO invoicing must still follow PMK 79/2024 and the KSO’s actual contract and contribution flow.
Income tax, withholding, and members’ recognition
PMK 79/2024 has a dedicated income-tax regime for KSO with NPWP. The DJP explanation says such a KSO must calculate, pay, and report corporate income tax and prepare bookkeeping and financial statements for the annual return starting with the 2025 tax year. It also explains that member-contribution costs can be income for members when the KSO receives customer income and recognises the related contribution cost. Do not treat every cash transfer as the same tax event.
Create a tax calendar that names the KSO taxpayer, lead firm, accounting owner, invoice owner, return owner, withholding owner, payment approver, member-reporting contact, and document-retention location. For construction-service KSO or arrangements with foreign members, identify the sector and cross-border questions separately. Tax rates, treaty treatment, and withholding conditions can depend on current rules and the members’ status, so verify them before invoicing or distributing amounts.
Where the KSO makes withholding or collection, or receives a payment subject to withholding, match the tax evidence to the same contract and ledger entry. The KSO agreement, invoices, accounting records, tax filings, and member allocations must reconcile at transaction level; a year-end spreadsheet cannot repair a broken invoice chain. Use the official PMK 79/2024 on KSO tax treatment and current DJP procedures for the final implementation details.
Final decision: register and operate a KSO on its actual facts
Register and operate the KSO under the PMK 79/2024 route when its agreement and real execution meet the NPWP criteria. Keep the obligations with the members when the arrangement does not meet that route, while preserving the evidence for why. Then reassess at each operational change—especially when the KSO begins invoicing customers, receiving revenue, paying vendors, or adding a PKP member.
The core control is a complete flow map from member contribution to KSO activity to customer delivery and back into each member’s records. A compliant KSO is not created by an NPWP alone; it is created by an agreement, contract, invoice, accounting, tax, and allocation trail that all identify the same operating model.
Before closing the project, reconcile final revenue, contributions, costs, taxes, residual allocations, document retention, and the need for any registration or tax-status update. This closes the KSO as deliberately as it was formed.
Set the KSO tax model before the first customer invoice
A KSO readiness review can align the agreement, lead-firm mandate, NPWP and PKP tests, VAT chain, income-tax ledger, and member reporting responsibilities.
Frequently asked questions
Does every KSO need NPWP?
No. PMK 79/2024 distinguishes KSO that meet the NPWP criteria from arrangements where members perform the tax obligations. Test the agreement and actual execution.
Who represents a registered KSO for tax registration?
The DJP explanation identifies a member designated as lead firm. The current process, data, and mandate should be checked before filing.
When may a KSO need PKP status?
PMK 79/2024 applies a PKP test tied to the VAT small-entrepreneur threshold and/or PKP status of one or more KSO members. Confirm current rules and facts.
Can members invoice the customer directly if the KSO is registered?
The agreement and actual flow must be assessed. The KSO/customer and member/KSO invoice chain should be designed to match PMK 79/2024 and the real contract model.
Does KSO tax treatment settle the legal entity structure?
No. KSO tax registration does not replace corporate, investment, sector, construction, or licensing analysis for the underlying project.