The Center for Financial Professional Development and Regulation, known as P2PK, operates under Indonesia’s Ministry of Finance. It is responsible for policy support, development, supervision, monitoring, and information services across several financial professions, including accountants, public accountants, appraisers, actuaries, and accounting technicians.
P2PK also inspects audit work and checks whether professionals and firms meet licensing and quality-control requirements. Because these responsibilities involve many professional groups and regulatory processes, P2PK depends on reliable digital systems to manage reports, applications, and approvals.
One of its systems, e-GovPPPK, was initially built as a reporting database. Over time, it evolved into a licensing application with separate functions for licensing, reporting, and KJPP reports. As the Ministry of Finance developed eLSa-PK (e-Layanan Satu Atap Profesi Keuangan), a broader digital platform, P2PK needed e-GovPPPK to become part of that shared environment.
In 2018, Suitmedia helped integrate e-GovPPPK into eLSa, creating a more unified and role-based way for users to access professional licensing and related services online.
A Reporting Database Had Become a Fragmented Licensing Experience
1. P2PK managed a wide range of professional responsibilities
P2PK’s work covered several regulated financial professions. Each profession involves its own requirements, documentation, approvals, and monitoring needs.
This created a complex administrative environment. Professionals needed to apply for or manage licenses. Firms needed to meet quality and reporting obligations. P2PK needed to review information, supervise compliance, and maintain reliable records.
A digital system could make these activities more efficient, but only if the system reflected the real relationship between applications, reports, licensing requirements, and user roles.
The original e-GovPPPK application was not designed for the full scope of this responsibility. It began as a reporting database and later expanded into a licensing application.
That evolution created functionality, but not necessarily a unified experience.
2. The application had grown without a single operating model
e-GovPPPK included menus for licensing, reporting, and KJPP reports. These functions were useful, but they existed within a system that had developed over time rather than being designed as one complete service.
As applications evolve incrementally, new modules can create duplicated processes, inconsistent interfaces, and unclear relationships between user actions.
For users, this can make a straightforward task feel more complicated. They may not know which module to use, how a report relates to a license, or which information is required at each stage.
For administrators, separate functions can create more manual work and make it harder to maintain a consistent view of each professional or organization.
3. The Ministry needed one connected digital environment
The Ministry of Finance had already developed eLSa as a broader application environment.
Keeping e-GovPPPK separate would require users to move between systems, remember different access points, and potentially enter similar information more than once.
This fragmentation could slow the licensing process and increase the risk of inconsistent records.
Integration into eLSa created an opportunity to establish one digital entry point for P2PK-related services. Users could access the functions relevant to them through a shared platform, while the Ministry could manage related applications under a common structure.
The goal was not simply to move one application into another. It was to create a more coherent service experience.
4. Different users needed different access
P2PK’s services involved multiple roles. A professional applying for a license would not need the same access as an auditor, firm representative, reviewer, or government administrator.
If every user saw the same menus and functions, the system could become difficult to understand and increase the risk of inappropriate actions.
Role-based access was therefore an important requirement. Users needed to see the services and information relevant to their responsibilities.
This would make the system easier to use and help protect the integrity of licensing and reporting activities.
5. The old technology limited future improvement
The existing system needed to be updated to align with the Ministry’s technology direction and the requirements of eLSa.
A platform built on older technology can become difficult to maintain, extend, and integrate. Even when it continues to operate, it may slow the delivery of new functions and make improvements more expensive.
P2PK needed a more modern technical foundation that could support better performance and future module development.
Technology modernization was therefore not an isolated IT upgrade. It was necessary to improve the way the institution delivered professional services.
6. Productivity depended on the whole workflow
The central challenge was productivity.
P2PK needed to process professional licensing and related reports more efficiently, while users needed a clearer way to access services and submit information.
Improving one screen would not solve the problem if the wider workflow remained fragmented. The system needed to connect the user interface, application logic, role permissions, reporting processes, and Ministry platform.
The project had to improve the complete path from access to submission, review, and service delivery.
Rebuilding the Application Around Integration and Role-Based Access
1. We treated integration as a service design decision
Suitmedia’s approach began with the role e-GovPPPK needed to play inside eLSa.
The key question was not only how to connect two technical systems. It was how users should experience the combined service.
The integrated environment needed to help users understand where to access licensing and reporting functions, while allowing the Ministry to retain control over the underlying processes.
This required attention to user journeys, data flow, authentication, roles, application modules, and the relationship between front-end actions and back-end services.
Integration was treated as a way to reduce user effort, not simply as a technical connection.
2. We mapped functions and user roles
The existing e-GovPPPK functions were reviewed alongside eLSa’s broader structure.
The system needed to distinguish between licensing, reporting, and KJPP-related activities while making them accessible through the right user roles.
This helped define what different users should be able to see and do.
A professional seeking a license could access the relevant application process. A firm or authorized representative could submit required information. P2PK staff could review and manage applications. Other authorized users could access reporting or monitoring functions appropriate to their responsibilities.
Role-based access reduced unnecessary complexity and supported better control over sensitive information.
3. We updated the front end with AngularJS
The new interface used AngularJS, an open-source JavaScript framework, to improve the application’s front-end structure and interaction.
The choice supported a more responsive user experience and provided a clearer basis for managing the application’s different views and functions.
A licensing system must communicate status, required actions, form fields, and supporting information clearly. The front end needed to help users understand what to do without forcing them to interpret a technical workflow.
The updated interface created a more consistent environment for accessing the application’s modules.
4. We used ASP.NET Web API for the backend
The backend was supported by ASP.NET Web API.
This helped create a structured way for the front end to communicate with the application’s underlying services and data.
Separating the interface from the backend services supported maintainability and future development. Changes to how information was presented could be managed separately from the core application logic, provided the connection between the two remained clearly defined.
This was important for an application that needed to integrate with eLSa and potentially support future modules.
5. We rebuilt modules within the broader eLSa environment
The integration required more than embedding the old application inside eLSa.
Other modules needed to be adapted to work within the Ministry’s shared platform and technology direction.
This helped create a more unified user experience. Users could access P2PK services through the same broader environment rather than encountering a disconnected application with a different structure or interaction model.
The work also reduced the long-term risk of maintaining parallel systems that handled related government services separately.
6. We focused on a smoother licensing journey
The integrated application gave users a clearer path to professional licensing services.
Instead of navigating among separate applications, users could access the relevant services from eLSa according to their role.
This reduced the effort required to begin an application and made the overall process more predictable.
A smoother licensing journey also helps reduce administrative questions. When the system clearly presents the relevant service and required steps, users are less likely to submit incomplete information or seek clarification about basic navigation.
7. We preserved the importance of reporting and supervision
The system’s reporting functions remained important because P2PK’s responsibilities extended beyond issuing licenses.
The application needed to support the information required for supervision, inspection, monitoring, and reporting across the regulated professions.
Integration helped connect these functions to licensing activity within one broader environment.
This supported a more complete institutional view. Licensing was not treated as a standalone transaction; it was part of a wider process of professional oversight and quality assurance.
8. We designed for government service reliability
Government applications need to be dependable because users rely on them for official processes.
The updated technology and integrated architecture supported a more stable platform for users and administrators.
Reliability includes more than uptime. It also means that users can access the right function, submit information with confidence, and understand what happens next.
A system that behaves consistently helps strengthen trust in the institution behind the service.
9. We reduced the need to manage separate access points
Before integration, users could face the burden of moving between e-GovPPPK and eLSa.
A unified entry point reduced this friction and made P2PK services easier to locate.
This also supported operational efficiency for the Ministry. A shared environment can reduce duplicated administration and create a more consistent approach to managing access, data, and application functions.
10. We created a foundation for future digital services
The updated architecture was designed to support future modules and improvements within eLSa.
This mattered because government service requirements change over time. New professional categories, licensing rules, reporting requirements, or administrative needs may need to be introduced.
A more flexible technical foundation allows these changes to be managed without repeating the limitations of the original system.
From Separate Application to One More Efficient Licensing Environment
1. Users gained one access point for professional licensing services
The integration of e-GovPPPK into eLSa allowed users to access P2PK-related services within one Ministry platform.
This reduced the need to move between separate websites or applications and created a more consistent starting point for licensing and reporting.
The benefit was especially important for users who were unfamiliar with the Ministry’s application landscape. They could begin from one environment and access functions according to their role.
2. The licensing process became easier to navigate
The updated interface and clearer role-based access helped users identify the services relevant to them.
This made the licensing journey more predictable and reduced unnecessary searching.
A more direct workflow can also improve the quality of submissions. When users understand the process and see the information required, they are more likely to provide complete and accurate data.
3. P2PK gained a more connected approach to supervision
The platform linked licensing with reporting and monitoring functions in a broader digital environment.
This supported P2PK’s role in supervising financial professions and reviewing whether professionals and firms met regulatory and quality requirements.
The system could therefore support not only the applicant’s experience, but also the institution’s responsibility to manage oversight more effectively.
4. The Ministry reduced platform fragmentation
Integrating e-GovPPPK into eLSa reduced the need to maintain separate user experiences for related services.
This created a more coherent environment for users and a stronger basis for managing applications across the Ministry.
The second-order effect was organizational clarity. Digital services could be developed within a shared framework rather than as isolated systems that gradually became harder to connect.
5. Modern technology improved the platform’s capacity for development
The use of AngularJS and ASP.NET Web API provided a more updated foundation for the application.
The technology choices supported better front-end interaction, clearer separation between interface and services, and more manageable future development.
This did not automatically solve every operational issue, but it gave P2PK and the Ministry a stronger basis for continued improvement.
6. Professional licensing became more accessible online
Users seeking licensing services could access them through one integrated application.
This reduced the need for physical or fragmented digital processes and helped make P2PK’s services more convenient.
The platform supported a broader shift toward government services that users could access more efficiently and with greater visibility into the process.
7. The application supported institutional productivity
Productivity improved through a combination of better navigation, system integration, updated technology, and role-based access.
Users could spend less time finding the correct application or understanding disconnected workflows. P2PK staff could work within a more unified environment for managing services and information.
The improvement was therefore shared across external users and internal teams.
8. eLSa created a more scalable environment for future expansion
By bringing e-GovPPPK into eLSa, the Ministry gained a stronger platform for expanding digital services related to professional regulation.
The system could support future modules and changes more effectively than the earlier standalone application.
This created long-term value beyond the immediate integration. The Ministry could continue building a connected service environment rather than adding more isolated applications.
What Kemenkeu P2PK Reveals About Government Application Integration
1. Integration should be measured by reduced user effort
Two systems are not meaningfully integrated simply because they exchange data.
The real test is whether users can access services more easily, avoid repeated steps, and understand the process more clearly.
2. Role-based access improves both usability and control
Showing users only what they need reduces confusion and supports information governance.
It also helps institutions manage responsibility by ensuring that different roles can perform the actions appropriate to them.
3. Modernization should address architecture, not only appearance
A new interface cannot solve the limitations of a fragmented or outdated system.
Technology, application structure, data flow, security, and user experience need to be improved together.
4. Reporting and licensing are often connected workflows
Licensing decisions may depend on reporting, supervision, and quality control.
Treating these functions as part of one connected system can improve both public service delivery and institutional oversight.
5. Government platforms need room to evolve
Regulations, professional categories, and service requirements change.
A flexible architecture makes it easier to add or revise services without creating another disconnected system.
6. Productivity improvements can come from reducing uncertainty
Users and administrators lose time when they are unsure which application to use, what information to submit, or what happens next.
A unified and role-aware platform can reduce this uncertainty and improve the pace and quality of work.
Strategic Insights for the C-Suite
- Judge integration by the experience it creates, not the connection it claims.
A technically connected system is valuable only when users face fewer steps, clearer pathways, and less repeated data entry. Measure integration through reduced effort and improved completion. - Use role-based access to simplify public services.
Different users need different functions. Showing each role the right services improves usability while strengthening control over sensitive information and administrative responsibility. - Modernize the architecture before adding more features.
Adding functions to a fragmented system can increase long-term complexity. A stable foundation, clear separation of components, and manageable APIs create better conditions for future development. - Connect service delivery with institutional oversight.
Licensing, reporting, inspection, and monitoring often depend on one another. Integrating these workflows can improve the user experience while strengthening regulatory effectiveness. - Build government platforms for policy and service change.
Regulations and professional requirements evolve. Choose technology and structures that allow new modules and workflows to be added without recreating fragmented applications.
