In an Indonesian financial institution, "CMS" has two meanings, and the older one isn't about websites. In a bank, CMS first means Cash Management System, the corporate banking service that DJPb, the Ministry of Finance's treasury directorate, describes as letting institutions transact in real time online. This article is about the other one: a content management system, the software that lets people write, approve and publish a website's content without touching code. For an Indonesian listed company, that website has been mandatory since POJK 8/POJK.04/2015, issued on 25 June 2015, and it has to carry the same information in Bahasa Indonesia and at least English.

We wrote this for CTOs and enterprise architects at Indonesian banks, insurers, multifinance companies and Tbk issuers. And for the people who can veto their CMS choice: Compliance, internal audit (SKAI, the Satuan Kerja Audit Intern) and the CISO. On 22 November 2026 the first page Google Indonesia returns for "what is CMS" runs from Spocket and a LinkedIn post to a 2011 Quora thread and one Indonesian agency. Every snippet stops at the definition. None mentions an Indonesian regulation.

What is a CMS: two applications in one system

A CMS has two parts. The content management application (CMA) is where editors write, revise and approve. The content delivery application (CDA) serves that content to visitors. A blog owner only needs to know the CMA is easy to use. An OJK-supervised institution needs a different answer: when internal audit or an OJK examiner asks who changed the annual report page, when, and on whose approval, the CMA has to produce the evidence.

A scoping note for readers coming from bank IT. Vendors also sell ECM, enterprise content management, which governs internal documents and records. That's not this article. We cover web content management only: the system behind the public corporate site.

What POJK 8/2015 requires of a listed company's website

POJK 8/POJK.04/2015 on Situs Web Emiten atau Perusahaan Publik (Websites of Issuers or Public Companies) was promulgated and took effect on 26 June 2015. The JDIH BPK legal database lists it as "Berlaku" (in force), with no amendment or revocation. Article 6 sets four minimum content categories: general information, investor information, corporate governance and corporate social responsibility. Article 5(1) requires information that's current and up to date ("aktual, dan terkini"). Article 5(2) requires it to be correct, not misleading and accessible at all times. And under Article 4(3), the Bahasa Indonesia text prevails if the two languages are read differently.

Be clear about one thing first. POJK 8/2015 says nothing about approval workflows, audit trails, version history, or how the site is built and hosted. The words "maker" and "checker" don't appear in it once. The table below is our own mapping: the content obligation from the POJK, then the CMS capability needed to meet it without manual steps that someone will eventually forget.

Content obligation (POJK 8/2015)CycleCMS capability needed
Bahasa Indonesia and English, same information (Art. 4)Every publicationA page can't go live without its other-language twin
Shareholders and their percentages (Art. 7 letter d)Each month-endUpdate schedule and reminders
Annual reports (Art. 8 letter b)Last 5 financial yearsDated archive that can't be deleted quietly
Annual and half-year financial statements, 17-item summary (Art. 8 letter c)Last 5 financial yearsDated archive, summary template
GMS (RUPS): notice, summons, materials, summary minutes (Art. 8 letter d)Per eventApproval before publishing, timestamps
10 types of corporate action and material facts (Art. 8 letters i and j)Per eventMulti-level approval, audit trail
Board and committee charters, code of conduct, risk policy (Art. 9)When changedVersion history

Two articles turn this table from housekeeping into exposure. Article 11 requires the website to carry the same information required by the related regulations, so a page that diverges from a document already filed with OJK is a problem in its own right. Article 12 sets administrative sanctions running from a written warning and a fine up to revocation of a business licence, approval or registration. At that point the corporate site's CMS stops being a marketing tool. It's part of the disclosure system.

Seven CMS requirements for an OJK-supervised institution

The list below uses the regulators' own wording. For commercial banks the main reference is PADK 1/2026 on IT Operations by Commercial Banks, issued 23 January 2026 and in force from 1 March 2026. It revoked SEOJK 21/SEOJK.03/2017. One caveat up front: PADK never mentions "website" or "content". Treating a change to a disclosure page as a data change in a production environment is our interpretation, and you should test it with your own Compliance team.

1. Approval before publishing (maker-checker)

"Maker-checker", or the four-eyes principle, is industry vocabulary. The term appears in none of PADK 1/2026, POJK 11/2022, POJK 4/2021 or POJK 8/2015. The regulatory wording sits in PADK Chapter II.C.3.d: a change-management policy covers "at a minimum the request, analysis, approval of changes and installation of changes", including review before modification and authorisation (our translation). For a CMS, that means an author can't publish their own disclosure page. Ask the vendor whether approval can be enforced per content type, not merely offered as an option.

2. An audit trail you can export

For every electronic system operator, non-financial issuers included, Article 22(1) of Government Regulation (PP) 71/2019, promulgated 10 October 2019, reads:

Penyelenggara Sistem Elektronik wajib menyediakan rekam jejak audit terhadap seluruh kegiatan penyelenggaraan Sistem Elektronik.

In English: an electronic system operator must keep an audit trail of every activity in operating the electronic system (our translation). Insurers, pension funds and finance companies carry a similar duty under Article 19(1) of POJK 4/POJK.05/2021, promulgated 17 March 2021. For banks, PADK Chapter IV.B.1.c.5 asks the bank to define log types and retention periods, protect logs from tampering and unauthorised access, and synchronise clocks across all systems. The minimum CMS spec: who, when, which page, content before and after, who approved. Exportable. Not deletable by the site admin.

3. Role separation beyond author, editor and admin

PADK Chapter II.A.2.b point 3 requires segregation of duties, so that no single person holds several critical functions in a way that lets errors go undetected. In a CMS that means roles per site or division, per language and per content type. The communications team may publish news, but the financial statements page needs the Corporate Secretary's sign-off. The admin who manages user accounts shouldn't also approve content.

4. Disclosure pages that can't change quietly

Annual reports and financial statements must stay available for the last 5 financial years. The CMS should keep every version with its publication date, replace "delete" with a logged "unpublish", and show the archive by financial year. Someone swaps a report PDF for a file with the same name and leaves no record? That's exactly the event that's hard to explain during an examination.

5. Bilingual parity as a control, not a habit

Article 4(2) of POJK 8/2015 requires the foreign-language version to carry the same information as the Bahasa Indonesia version. A CMS can enforce that. An example from our own house: the CMS behind webarq.com, built on Laravel and our in-house admin framework, refuses to save an article if the title, slug or body is empty in either language, and each language gets its own slug. The page you're reading couldn't have been saved without its Indonesian version. We cover multilingual sites more broadly in our guide to building a multilingual website.

6. Data location and hosting

Article 35(1) of POJK 11/POJK.03/2022, promulgated 7 July 2022, requires banks to place electronic systems in a data centre and disaster recovery centre inside Indonesia. Placement abroad needs OJK approval (Article 35(2)). Article 1 point 3 defines an electronic system to include devices that display, announce and disseminate electronic information. We read that as covering a public website's CMS, but in the texts we've read OJK hasn't said so explicitly about websites. The list of internal management systems that PADK Chapter VI.A allows offshore (HR, remuneration, internal audit, collaboration and the like) doesn't include a public website.

For non-bank financial institutions, Article 23 of POJK 4/2021 applies to those running their own data centre, and offshore placement needs OJK approval. Non-financial issuers have more room: Article 21(1) of PP 71/2019 lets private-scope operators store data inside or outside Indonesia. The practical upshot: a SaaS CMS hosted in Singapore is a question for Compliance before procurement, not after the contract is signed.

7. Source-code ownership and vendor change control

PADK Appendix I Chapter II.C.2 letter i asks a bank to hold the source code of software developed specifically for it, so it can be accessed for examination and investigation. Letter f on the same page separates development and production environments, and letter h asks for an audit trail. Where the bank doesn't hold the source code of an application run by an IT service provider, Chapter V B.4.c names an escrow agreement as a mitigation the bank may use. Not an obligation. Write code ownership, admin accounts and change records into the terms of reference for a bank website or app from day one, and price the impact into the owner's estimate (HPS) for the website project.

Headless, off-the-shelf or custom CMS, judged on the seven requirements

Off-the-shelf means a ready-made product, open source like WordPress and Drupal or commercially licensed, self-hosted or bought as SaaS. Custom is built for one institution. A headless CMS stores content and serves it through an API, while the site's front end is built separately. The comparison deliberately leaves out "ease of use". That's never the reason Compliance vetoes a CMS.

RequirementOff-the-shelfCustomHeadless
Multi-level approvalUsually via a plugin or a paid editionDesigned to the authorisation matrixIn some products; check per content type
Before-and-after audit trailVia a plugin; test whether an admin can delete itWritten into the specVersion history is common; test the export
Role separationBuilt-in roles, needs customisationMirrors the org structureDepends on product and plan
Language parityMultilingual pluginCan be a validation rulePer-language content model
Data locationSelf-hosted: you decideYou decideSaaS edition: the vendor's server region
Source codeOpen core; plugins owned by third partiesThe institution's, if the contract says soPlatform owned by the vendor; front end yours

Our view, with the reasons. For a commercial bank, a SaaS headless CMS hosted offshore is the hardest option to defend against Article 35 of POJK 11/2022, however good its features. Install the same headless CMS in an Indonesian data centre and that objection goes away. Self-hosted off-the-shelf can pass if its approval and audit plugins are chosen, tested and maintained as audited components, not installed and forgotten. Custom makes sense when the site has to connect to core systems, or when the authorisation matrix can't be expressed through built-in roles. Provided, that is, the source code is handed over as PADK expects.

An example from WEBARQ's own projects

The BCA Group case study covers the websites for BCA Insurance, BCA Syariah and BCA Sekuritas. It lists the challenge as "developing an advanced CMS with capabilities for draft creation, preview, merge, and multi-layer approval processes". Three divisional sites, one workflow: draft, preview, merge, then layered approval before anything goes live. The case study doesn't mention an audit trail, so we don't claim one here.

What this means for the CTO, internal audit and the CISO

  • CTO: put the seven requirements into the TOR as pass/fail criteria, then score off-the-shelf, custom and headless against them. Not against the vendor demo.
  • Compliance and internal audit (SKAI): ask for a sample audit-trail export and a 5-year annual report archive before go-live, not after the first examination.
  • CISO: write the server region, the owner of the admin accounts and the procedure for revoking vendor access into the contract. Securing the site itself is covered in our website security guide.

If your corporate site needs to connect to core systems or carry its own approval matrix, see WEBARQ's web application development and website development services.