Pengadaan & Regulasi

Indonesia's Government Procurement Plan: Nine Required Fields, a New Address, and a 31 March Deadline

TAB
Tim Editorial TAB
6 min read
Close-up of a printed January calendar page, the month Indonesian agencies publish their annual procurement plan on SIRUP

Every Indonesian government body must publish what it intends to buy before it buys it. That list is the Indonesia government procurement plan — RUP in Indonesian — and it lives on a system called SIRUP, which moved to sirup.inaproc.id and is no longer reachable at its old address. A plan must carry nine specific fields, and the outer deadline is 31 March of the budget year it covers. Everything here was read off primary sources on 7 October 2026.

One system, two readers who rarely meet. An agency officer has to file it. A supplier can read it — often months before the work surfaces as a tender. Both sides are covered below, starting with the filing.

The address moved, and the old one was not redirected
LKPP announced on 28 November 2025 that from 1 December 2025 SIRUP would move from sirup.lkpp.go.id to sirup.inaproc.id. Features and stored data were unchanged, and integration with agencies’ local SIRUP installations continues as long as the new domain is whitelisted. The part worth knowing: the old hostname no longer resolves at all. It does not redirect — it is gone from DNS, checked 7 October 2026. Any guide still printing the old address predates December 2025, which means its dates deserve the same suspicion.

What the Indonesia government procurement plan must contain

People picture dozens of screens. The regulation asks for nine things. The list sits in Peraturan LKPP No. 11 of 2021, Annex III, and on screen those nine are spread across one package form. Pull them out of the budget document before logging in and a package takes minutes.

The nine required RUP fields, per Peraturan LKPP 11/2021 Annex III

Required fieldComes fromCommon mistake
Name and address of the budget holder (PA/KPA)The appointment decreeStill names last year’s official
Package nameThe RKA or DPA budget documentCopied raw from budget nomenclature, unreadable to a supplier
Procurement methodPackage value and typeSet to Tender when the value falls under direct procurement
Short descriptionThe terms of reference or draft specLeft blank, though it is the only clue to what is inside
VolumeThe spending breakdownUnit of measure omitted, so the number means nothing
Package value (ceiling)The RKA or DPAIncludes honoraria or travel, which are not procurement spending
Location of the workThe activity planThe office name instead of the regency or city
Funding sourceNational, regional, hospital or grant fundsRegional budget confused with central transfers
Expected time of useThe activity scheduleDecember entered for every package

The third column is not part of the regulation. It reflects packages that look broken in SIRUP’s own public search.

That third column matters more than it looks. A package with an empty description and "the agency office" as its location is still valid to the software, yet unreadable to anyone outside the agency — and being read is the entire point of publishing a plan.

Who does which part

Perpres 16 of 2018, Article 9(1), puts the duty on the budget holder: they set the procurement plan and they publish the RUP. Inside the software the work splits across four roles, and the order locks. If the role above you has not finished, your own screen shows nothing — which is the most common question in SIRUP’s official FAQ.

  1. The e-procurement administrator. Activates the work unit for the current budget year and creates its user accounts. In regencies whose procurement service unit is not yet formed, this is where everything stalls.
  2. The budget holder. Pulls or uploads the budget data — ministries pull it from the national RKAKL or SAKTI systems, regional governments upload an RKAD file — then delegates each ceiling onward.
  3. The commitment officer (PPK). Builds the packages, those nine fields, for each sub-activity, separating work done through a supplier from work done in-house.
  4. The budget holder again. Finalises the draft, then publishes. A finalised but unpublished package means nothing outside: it does not appear in the public search and cannot be pulled into the next stage.

And one thing no guide covers: officials rotate mid-year. A commitment officer transfers, a budget holder is replaced, accounts change with them. Published packages survive. Drafts tend to be left behind in the old account.

The date is 31 March, but the trigger is the budget

Peraturan LKPP 11/2021, Article 8(2), sets the deadline for publishing next year’s plan on SIRUP at no later than 31 March of that budget year. That is the outer limit, not a recommended schedule.

What decides when you may start is the budget, not the calendar. Perpres 16/2018 Article 22(1) has ministries publish once their spending allocation is set; Article 22(2) has regional bodies publish once the draft regional budget regulation is agreed between the regional government and its legislature. For work meant to begin ahead of the budget year — early tenders, early direct procurement, or buying through the Electronic Catalogue — publication is already allowed once the work plan and budget is approved.

Many regional governments impose an earlier date than the national one. The Lima Puluh Kota regency circular for budget year 2026, for instance, requires every plan matching the regional spending document to be published by 28 February 2026. So the date that binds you may not be the national one — read your own agency’s circular first.

What does not need to be filed at all
Not all spending belongs in SIRUP. That same circular separates non-procurement spending: honoraria and speaker fees, official travel and daily allowances, cash grants, and operational or social assistance paid in cash. A package ceiling contaminated with these reads far larger than the work actually being competed, which hurts the agency — suppliers price against the number they can see.

The duty most often skipped sits in Article 22(5): the plan must be published again whenever a package is revised, or whenever the budget execution document changes. Publishing a procurement plan is not a once-a-year January chore. It follows the money every time the money moves.

The other side: reading the plan before the tender exists

SIRUP’s national package search opens without a login, and its filters are better than most suppliers realise: keyword, agency, location down to regency and city, procurement type, method, value band, and the month the goods or services are wanted. Results export to Excel or PDF.

A real use, for a software supplier in Sidoarjo: filter location to Sidoarjo regency, type to Other Services and Consultancy, value up to Rp200 million, then sort by month. What comes back is work that will almost certainly run as direct procurement — the direct-procurement ceiling is Rp200 million for goods and other services and Rp100 million for consultancy under Perpres No. 46 of 2025, in force since 30 April 2025. Packages in that band never appear as a tender announcement, so a supplier watching only the tender page never sees them.

Two further filters are rarely used and favour small firms most: the small-business flag and the domestic-product flag. Perpres 46/2025 added Article 20(3), which obliges commitment officers to allocate at least 40 percent of goods and services spending to micro and small enterprises and cooperatives producing domestically. Those packages are tagged in the plan, and filtering on the tag cuts the list straight down to work reserved for a company your size.

What to know before relying on it too heavily

A plan is a plan, not a promise. Ceilings fall, months slip, packages get cancelled — and while the agency is obliged to republish when that happens, nobody sends you a notification. The national summary refreshes overnight rather than live; the page we opened stamped its data as last rebuilt in the early hours of 7 October 2026.

In our experience, suppliers who read the plan between January and March hold an advantage that nobody catches up on in June. Not because the information is secret — all of it is open — but because in January there is still time to meet the people who will use the thing, and by June the documents have been written without you.

If the package touches software or systems and you need a view of scope before pricing it, start from government IT procurement in Indonesia — the technical side is what most often pushes a bid far above the published ceiling.

Agencies around Surabaya that want a second opinion while drafting package descriptions and estimating values can talk to an IT consultant in Surabaya; where the work ends in an application that has to be built, that belongs to a software development team rather than to a form.

Is there any fee to file on, or read, SIRUP?+
No fee is published for either side. The national package search opens without an account. If anyone offers a paid service to "register" your company on SIRUP, they have the wrong system — SIRUP has no supplier registration at all.
My package was filled in but does not show in the public search. Why?+
Almost always because it was finalised but not published — those are two different buttons. The second cause is budget data the budget holder has not yet uploaded or delegated, which leaves the commitment officer’s package hanging. The national summary also rebuilds only overnight, so a package published at midday may not be counted in that day’s figures.
If the value changes after the plan is published, must it be updated?+
Yes. Perpres 16/2018 Article 22(5) requires the plan to be published again when a package is revised or the budget execution document is revised. Peraturan LKPP 11/2021 adds that a change can come from a shift in how performance targets will be met as well as from a budget change, and may originate in a review by the commitment officer or the procurement service unit.
TAB
Tim Editorial TAB - CV Trengginas Alfath Berkarya

IT consultants helping Indonesian businesses choose and manage cloud infrastructure, develop software, and keep IT operations running smoothly. Based in Sidoarjo, serving clients across East Java and Indonesia.