THE PROBLEM
Replacing Paper Approval Chains With A Custom Web Application
A purchase requisition that needs four signatures usually spends most of its life waiting on a desk, and nobody can say which desk without walking the building. Replacing that chain with a custom web application changes two things: the form moves in seconds instead of days, and every step leaves a record that survives an audit ten years later. The build is ordinary software engineering, and most of the difficulty sits in the approval rules rather than in the screens.
THE PROBLEM
Where A Paper Approval Chain Loses Time
A paper chain loses time in the gaps between signatures, and those gaps are invisible until someone goes looking. The signing itself takes seconds. The form sitting in a tray while an approver is on site, in a meeting or on leave takes days, and there is no delegate rule, because a paper tray has no delegate rule.
The second cost is reconstruction. When an internal auditor asks who approved a specific payment and on what authority, somebody pulls a binder, and the binder answers only if the form was filed correctly at the time. A scanned copy in a shared drive is an improvement on the binder, and it still cannot prove that the signature was applied before the goods were ordered.
The third cost is the one finance notices. ARSA’s published figures for enterprise web projects are a 30 to 60 percent reduction in manual process time and a 70 to 90 percent reduction in data entry errors. Both are consequences of the same change: the person requesting the spend types the figures once, into fields that validate, instead of writing them on a form that a second person retypes into the accounting system.
THE MECHANICS
What Replaces A Signature Block
A digital approval carries three things that a signature line carries implicitly, and the application has to make each of them explicit.
Identity
Who acted. The account, the authentication method, and the device or network the action came from. Anonymous approvals and shared logins defeat the entire exercise, so shared service accounts are usually the first thing an approval build removes.
Authority
Whether that person was permitted to approve that item, at that value, on that date. Authority is a matrix of role, cost centre and threshold, and it changes when people move jobs. The application stores the version of the matrix that applied on the day, so a later reorganisation cannot rewrite history.
Evidence
The immutable record of the decision: timestamp, the exact document version approved, the comment, and any rejection and resubmission before it. This is the audit trail, and it is a design input at the start of the build.
COMPLIANCE
What Indonesian Law Asks Of A Digital Approval Record
Electronic documents and electronic signatures have legal standing in Indonesia under the ITE Law and its implementing regulation, PP 71/2019, which distinguishes a certified electronic signature from an uncertified one. A certified signature uses an electronic certificate issued by an Indonesian electronic certification authority, created with equipment that meets the regulation’s requirements. An uncertified signature is made without that authority. Both exist in law, and they carry different evidential weight, so the choice belongs in the requirements document rather than in the sprint where the approve button gets built.
Retention is the constraint that catches teams late. Law 8/1997 on company documents requires accounting records and their supporting evidence to be kept for ten years from the end of the financial year in which they arise, and it permits transfer to other media with the transfer itself formally legalised. An approval system that holds records for two years and then prunes them is a compliance problem dressed as a storage saving.
Two further constraints apply depending on who you are. Personal data in the workflow, including approver names and staff identifiers, falls under Law 27/2022 on personal data protection. Banks and other institutions supervised by OJK also sit under POJK 11/POJK.03/2022 on the operation of information technology by commercial banks, which governs IT risk management, information security, and the internal audit of the systems themselves. Where an approval chain touches a regulated process, the regulator’s expectation is part of the scope, and it is cheaper to establish it in week one than in user acceptance testing.
THE RECORD
What The System Stores For Every Approval Step
Every step in the chain writes a fixed set of fields, and the value of the system is that the set is fixed. The table below is a working baseline for an internal approval workflow, and your own audit function will add to it.
| Field | What It Holds | Why It Matters |
|---|---|---|
| Actor | Account identifier and full name at the time of the action | A leaver’s account must still resolve to a name years later |
| Action | Submitted, approved, rejected, returned, delegated, cancelled | Rejections and resubmissions are part of the history |
| Timestamp | Server time, recorded to the second, with time zone | Client clocks carry no evidential weight |
| Authority applied | Role, cost centre and approval limit in force on that date | Proves the approver was inside their limit |
| Document version | Hash or version identifier of the exact content approved | Stops a later edit inheriting an earlier approval |
| Comment | Free text from the approver, retained verbatim | The reasoning is usually what the auditor asks for |
| Delegation | Who delegated to whom, with start and end dates | Absence is the most common cause of a stalled chain |
| Retention | Ten years from the end of the financial year | Law 8/1997, for accounting records and supporting evidence |
SCOPE
What A Build Costs And How Long It Takes
ARSA’s published range for a custom enterprise web platform is $20,000 to $250,000 and above, with a functional system in 8 to 16 weeks. An approval workflow for one department with a defined set of forms sits at the lower end of that range. A platform that replaces every approval chain in a group of companies, with delegation, multi-entity cost centres and an ERP posting on final approval, sits considerably higher.
| Phase | Duration | What It Produces |
|---|---|---|
| Discovery and requirements | 1 to 2 weeks | Requirements document and roadmap, including the authority matrix |
| UX and UI design | 2 to 3 weeks | Design specification and a clickable prototype |
| Iterative development | 6 to 12 weeks | Working modules in staging, demonstrated fortnightly |
| Integration and testing | 2 to 4 weeks | System integration, security testing, user acceptance testing |
| Deployment and training | 1 to 2 weeks | Live system, trained users, documentation |
Before any of that, ARSA runs a feasibility assessment at $4,500 over two weeks, which establishes the data model, the integration surface and the permission model, and delivers a go or no go recommendation. The fee is deducted from the project fee if you contract within 90 days. Camera led projects start somewhere else, with a Remote Camera Design Review at $1,500 for one week, which is a different engagement for a different kind of problem. The full list sits on the services page.
LIMITS
What Digitising An Approval Chain Does Not Fix
A workflow application makes a bad process faster and more visible, and it leaves the process bad. If a capital request needs seven approvals because nobody has ever been willing to remove one, the software will collect seven approvals. Discovery is where the chain should be shortened, and that decision belongs to the business rather than to the engineering team.
Two other honest limits. An application cannot confer authority that the company has never written down, so where approval limits live in custom and memory, the first deliverable of the project is the authority matrix itself, agreed and signed. And a certified electronic signature depends on an electronic certificate from a registered Indonesian certification authority, which is an external service the application integrates with. If your legal function requires certified signatures, ask ARSA during the assessment which authorities the integration has been built against, and budget for the certificates separately.
Offline behaviour deserves an early decision too. A plant supervisor approving from a shop floor with poor coverage has different needs from a director approving from an office, and offline first design is a build decision rather than a setting to switch on afterwards.
Frequently Asked Questions
What Is The Difference Between An Enterprise Web Application And An Ordinary Web Application?
Scale, identity and integration. An ordinary web application serves pages. An enterprise web application authenticates against your corporate directory, enforces role based permissions, writes an audit trail, integrates with the systems of record you already run, and is expected to stay in service for five to ten years, which changes how it is architected and how it is documented.
How Long Does It Take To Replace A Paper Approval Chain?
A functional system in 8 to 16 weeks, preceded by a two week feasibility assessment. A single workflow for one department lands near the short end of that. The variable is rarely the software. It is how long the organisation takes to agree who may approve what.
Is An Approval Recorded In A Web Application Legally Valid In Indonesia?
Yes, subject to how the signature is made. PP 71/2019 recognises both certified and uncertified electronic signatures, and a certified one, issued through an Indonesian certification authority, carries the stronger evidential position. Many companies accept authenticated user actions with a full audit trail for internal approvals, and use certified signatures for documents that bind third parties. Take your legal function’s view before the design phase.
Can The Application Run On Our Own Servers?
Yes, and for most ARSA clients it does. On premise deployment is treated as a design input from the start, and air gapped deployment is supported. Where you would prefer ARSA to host it, that is available as well, quoted against the delivered system.
Can It Connect To Our Existing ERP Or Legacy Database?
Yes. The integration surface is established during the feasibility assessment, including the case where the legacy system has no API and a different approach is needed. Agreeing that surface before development starts is the single largest cost control on a project of this kind.
Do We Get The Source Code?
For custom application code, typically yes, agreed in writing before work starts. ARSA platform components and reusable libraries are licensed rather than transferred. Ongoing maintenance is quoted against the delivered system as an annual percentage of project value, and agreed before the build.
Start With The Authority Matrix
If your approval chain is on paper and you can describe it in one sentence, it is a small build. If describing it takes a meeting, and two people disagree about who signs above 50 million rupiah, the feasibility assessment is where that gets settled, before anyone writes code. ARSA builds these systems as Enterprise Web Applications, deployed on your own infrastructure where that is what you want, and you can contact the team to scope one against your own forms and your own approval limits.