PT PMA Capital Requirements for Multiple KBLI Codes and Project Locations
A project-allocation method for companies adding business lines, sites, shared assets, and working capital under the current investment framework.
A PT PMA with multiple KBLIs or project locations should not multiply the IDR 2.5 billion paid-up capital baseline by every code. Under BKPM Regulation No. 5 of 2025, the general issued and paid-up capital minimum applies per foreign investment company unless another rule requires more. The total investment plan is different: the general framework is applied by business line and project location, with detailed calculation rules and exceptions for particular activities.
The practical task is to build an allocation workbook. It should show each five-digit KBLI, location, assets, construction, working capital, shared resources, funding source, and realisation schedule. A single laptop, lease deposit, or management team should not be counted repeatedly simply to make each OSS line appear complete. Confirm the activity-specific method in a PT PMA capital planning review before adding projects or submitting figures.
| Level | Unit of analysis | Main record |
|---|---|---|
| Company equity | PT PMA and shareholders | Deed, register, ledger, bank evidence |
| Business-line plan | Five-digit KBLI | OSS project investment data |
| Location plan | Project site for the activity | OSS location and operating budget |
| Realisation | Actual eligible investment by period | Ledger, assets, evidence, LKPM |
Key takeaways
- The general IDR 2.5 billion paid-up capital minimum is company-level, while the investment plan is activity- and location-sensitive.
- Every project line needs a supportable operating budget rather than a copied threshold number.
- Shared assets and central costs require a consistent allocation method to avoid double-counting.
- Activity-specific calculation exceptions can change the general land, building, fixed-asset, or location treatment.
- OSS plans, ledger data, fixed-asset records, and LKPM realisation should reconcile by project.
In this article
Separate company-level equity from project-level investment
Start with the deed. Record authorised, issued, and paid-up capital, share allocation, and any higher sector-specific requirement. This is the company-level equity base. Then create an OSS project table that lists the activity and location combinations. These project lines can exceed the paid-up capital because the company may fund future investment through additional equity, shareholder or third-party financing, and cash generated from operations.
Do not use the words capital and investment interchangeably in approvals. A board paper should distinguish the equity subscribed now, total project investment planned, cash required in each phase, and financing source. This prevents shareholders from believing that the OSS plan must all be deposited on incorporation or, conversely, that paying the equity automatically realises every project.
Equity baseline
Apply the general paid-up minimum and any higher sector rule once at company level.
Project matrix
Create one row for each activity-location combination.
Funding plan
Connect equity, loans, and operating cash to project phases.
Reporting map
Track actual assets and working capital back to each project.
Build a matrix before entering anything in OSS
List every five-digit KBLI in rows and every proposed project location in columns. For each active combination, describe the deliverable, licence risk level, premises, people, fixed assets, construction, first operating cycle, launch date, and responsible business owner. Mark combinations that are only future options so they are not accidentally treated as committed operating projects.
A registered address is not automatically the project location for every activity. A trading head office, warehouse, restaurant, factory, and service site may have different locations and licensing dependencies. Confirm how OSS expects the activity and location to be recorded under current implementation and whether a new location creates a distinct investment calculation or amendment.
| Matrix field | Example input | Validation |
|---|---|---|
| KBLI | Exact five-digit code and deliverable | Ownership and risk-level check |
| Location | Project site and address type | Zoning, premises, and OSS treatment |
| Resources | Assets, staff, working capital | No duplicate counting |
| Timing | Setup and operating milestones | Realisation and licence sequence |
Allocate shared assets without counting them twice
A headquarters lease, enterprise software, central finance team, shared vehicle, server, or management equipment may support several KBLIs. Choose a rational allocation driver such as floor area, headcount, expected transactions, asset use, revenue capacity, or documented project ownership. Apply it consistently and retain the calculation. Do not show 100% of the same asset under every activity.
Some assets may belong wholly to one project even when the company has several KBLIs. A production machine used only at one factory should remain with that business line and location. A project workbook should include invoice, owner, location, commissioning date, accounting code, allocation, and OSS or LKPM category. This makes later reporting and inspection supportable.
- Unique asset or shared asset designation
- Project owner and physical location
- Allocation driver and approval
- Invoice, payment, and ledger reference
- Commissioning or operating date
- OSS and LKPM classification
Calculate working capital from the first operating cycle
Build working capital from payroll, rent, utilities, inventory, logistics, professional services, marketing, technology, insurance, licence maintenance, receivable days, and vendor payment terms that support each project. Use a defined period and avoid inserting a round residual solely to reach a threshold. Separate recurring operating costs from fixed assets and construction.
Shared working capital also needs allocation. Central staff can be divided using time budgets or headcount; shared rent can use area; platform costs can use users or transactions. The method does not need false precision, but it should be repeatable and understandable. Revisit it when actual contracts and hiring replace the original assumptions.
Volume
Estimate transactions, staff, inventory, and service capacity.
Cycle
Set receivable, inventory, and payable timing.
Costs
Build the real first operating-cycle cash need.
Allocate
Assign shared costs with a documented driver.
Apply activity-specific calculation rules before using the baseline
BKPM Regulation No. 5 of 2025 contains detailed investment-value provisions and special calculation treatment for certain activities. Property-related projects, food and beverage activities, construction, industry, and other categories may not follow the same simple interpretation of one KBLI and one address. Sector regulations can also impose higher capital or asset conditions.
Create an exception log for every project: general method, special article or sector rule, conclusion, source, reviewer, and date. If the project does not fit clearly, do not guess or copy a competitor’s OSS number. Obtain current regulatory confirmation. The PT PMA capital-by-KBLI guide can identify the questions, while the official rule should support the final calculation.
General method
Record the ordinary activity and location calculation.
Special rule
Identify the exact provision that changes the method.
Sector override
Test higher capital, facility, or licence requirements.
Implementation check
Confirm the current OSS input and evidence expectations.
Reconcile each project from plan to realisation
Assign project codes in the accounting system that mirror the OSS matrix. Tag fixed assets, construction, inventory, project payroll, and material vendor costs. Before LKPM, reconcile actual expenditure, asset status, production or service readiness, funding, employment, and project progress to the relevant KBLI and location. Explain changes rather than forcing the original budget to match.
When adding, closing, moving, or pausing a project, update the corporate approval, OSS data, investment workbook, accounting tags, licence tracker, and future reporting. A multi-project PT PMA needs this discipline because one incomplete or incorrectly allocated project can make company-wide capital and realisation data look inconsistent.
| Change | Records to update | Evidence |
|---|---|---|
| Add KBLI | Deed if needed, OSS, project matrix, licence | Ownership and investment screen |
| Add location | OSS project, premises, licence, allocation | Site and budget approval |
| Move shared asset | Asset register, project code, allocation | Transfer and location record |
| Pause project | Forecast, OSS or reporting as applicable | Management decision and status |
Official references and review basis
Primary materials checked on July 25, 2026. The cited rules should be read together with the current five-digit KBLI, OSS output, and any sector-specific regulation applicable to the proposed activity.
Final decision
Multiple KBLIs and locations require a project model, not a multiplication shortcut. Apply the company-level equity rule, build each project budget under the correct activity method, allocate shared resources once, and connect actual expenditure to the relevant project.
A well-designed matrix supports OSS amendments, budgets, bank explanations, asset control, and LKPM. It also shows management which projects are funded and licensable before capital is committed.
Frequently asked questions