SIREKA (Sistem Informasi Rekonsiliasi Keuangan dan Aset) is a digital platform developed for BPKAD Kabupaten Tanah Laut to manage the end-to-end reconciliation process of financial and asset reports from all SKPDs.
More than a file upload portal, SIREKA was designed as a workflow platform that digitizes the entire reconciliation business process—from notification and template distribution to document collection, verification, revision, and final approval.
Visit sireka.bpkad.tanahlautkab.go.id ↗The Problem
Before SIREKA existed, the reconciliation process faced significant operational friction.
Before SIREKA
Five operational bottlenecks
The reconciliation process relied entirely on manual coordination. Click each card to see the consequences.
Fragmented Communication
Information was scattered across WhatsApp, email, phone calls, and face-to-face meetings.
- No single source of truth for reconciliation info
- SKPDs received inconsistent messages across channels
- Follow-ups consumed significant staff time
Manual Document Distribution
Report templates had to be sent manually to each SKPD individually.
- Template versions were not always consistent
- No way to confirm all SKPDs received the latest template
- Distribution tracking was impossible
Scattered Document Collection
Reports arrived via email, WhatsApp, flash drives, and external storage.
- Files spread across multiple locations
- Hard to find the latest version of any document
- Increased risk of data loss
Lack of Process Visibility
BPKAD couldn't answer simple operational questions without manual checks.
- Which SKPDs have submitted? Unknown without calling around
- How many reports need revision? Must check one by one
- How many are verified? No real-time dashboard
No Audit Trail
Revisions happened through separate conversations with no centralized record.
- No record of rejection reasons
- No revision history to reference
- No user activity logs for accountability
The core issue was that information existed but lacked structure. BPKAD couldn't answer basic questions like which SKPD had submitted, which reports needed revision, or how many were verified—without manually checking everything.
The cost of manual coordination
Each SKPD operated in isolation. Template versions drifted. Report files accumulated in email inboxes and WhatsApp groups. When a revision was needed, the feedback loop depended on someone remembering to follow up.
This wasn't a technology gap. It was a process design gap.
Goals
SIREKA was designed with six primary objectives:
- Create a structured reconciliation workflow that mirrors the actual business process
- Establish a single source of truth for all reconciliation activities
- Centralize all documents and communication in one system
- Provide a traceable audit trail for every action
- Eliminate manual administrative overhead
- Enable real-time monitoring by BPKAD leadership
The Solution
SIREKA transforms reconciliation into a standardized digital workflow with seven distinct stages. Each stage has automatic status tracking and history logging.
Digital workflow
End-to-end reconciliation process
Notification
BPKAD creates reconciliation notices distributed instantly to all SKPDs
Template Distribution
Admin uploads official templates; SKPDs download the correct version
Report Submission
SKPDs submit completed reports directly through the system
Verification
BPKAD reviewers examine submissions and provide structured feedback
Revision
Rejected reports return to SKPDs with clear revision notes
Approval
Verified reports receive final approval and are locked from changes
Archiving
Approved reports are archived with complete audit trail preserved
The workflow design was the heart of the system. Instead of treating reconciliation as a document storage problem, SIREKA treats it as a state machine—each report moves through defined states with clear transitions and accountability at every step.
Key Features
Notification Management
BPKAD can create reconciliation announcements that are instantly delivered to all relevant SKPDs. This eliminates the dependency on manual communication through WhatsApp broadcasts or email chains.
Template Distribution
Administrators upload official report templates into the system. SKPDs download the correct version for their reporting needs. One source for templates means no version drift and no confusion about which document to use.
Report Submission
SKPDs upload completed reports directly through the platform. Each submission is automatically linked to the relevant SKPD, bidang (division), sub-bidang (sub-division), and report type—creating a structured data relationship from the moment of upload.
Verification Workflow
BPKAD reviewers examine submissions within the system. They can add comments, approve reports, or reject them with specific reasons. All review activity is logged automatically.
Revision Management
When a report needs correction, the system creates a clear revision path. The admin provides specific feedback, the SKPD makes corrections and uploads a new version, and the entire history is preserved. No more tracking revisions through WhatsApp threads.
Audit Trail
Audit trail
Every action is tracked
This is critical in government environments that require high accountability. Changes to documents, status updates, comments, and user activity are all permanently recorded.
Report Submitted
03 Jun 14:22SKPD uploaded financial reconciliation report v1
Comment Added
03 Jun 16:05Admin BPKAD: 'Please verify total on sheet 3, line 47'
Revision Requested
03 Jun 16:07Report returned to SKPD for correction
Report Resubmitted
04 Jun 09:15SKPD uploaded corrected report v2
Report Approved
04 Jun 11:30Admin BPKAD verified and approved final version
User Activity
Logged
Document History
Versioned
Comments
Archived
SIREKA records every significant action—document changes, status transitions, comments, and user activity. In government environments where accountability is paramount, this permanent record is essential for both operational transparency and regulatory compliance.
Role-Based Access Control
The system supports multiple user roles, each with visibility scoped to their responsibilities:
- Admin BPKAD — full system oversight and verification authority
- Pengurus Barang — asset report submission
- Bendahara Pengeluaran — expenditure reconciliation
- Bendahara Penerimaan — revenue reconciliation
Each role sees only the reports relevant to their function. This permission design ensures data separation without complicating the user experience.
System Architecture
System architecture
Technology stack overview
The stack was chosen for its reliability and suitability for government deployment—Laravel provides a robust, well-documented backend framework that runs on standard Ubuntu infrastructure without exotic dependencies.
Data Structure
One of the most architecturally interesting aspects of SIREKA is its hierarchical data model, which mirrors the government organizational structure:
SKPD
└─ Bidang (Division)
└─ Sub Bidang (Sub-division)
└─ Referensi Laporan (Report Reference)
└─ Template
└─ Pengajuan (Submission)
└─ Revisi (Revision)
└─ Persetujuan (Approval)
This isn't simple CRUD. It's a lightweight workflow engine tailored to the specific reconciliation process of local government. The data model allows the system to grow without requiring changes to the underlying business process.
Before vs After
Transformation
Before vs After
Scattered messages across chat groups
Templates lost in inbox threads
Phone Calls
Status updates via voice calls
Excel Files
Manual spreadsheet tracking
Flash Drives
Physical media for file transfer
Face-to-Face
In-person coordination required
Proses tersebar. Informasi, template, dan laporan tersimpan di tempat berbeda tanpa koneksi.
The transformation wasn't just about moving forms online. It was about changing how an entire organization coordinates around a critical financial process.
Before
- Information scattered across multiple channels
- Templates distributed manually with version inconsistency
- Reports collected through email, WhatsApp, and physical media
- Status monitoring required manual checking
- Revisions undocumented with no centralized history
- Zero audit trail capability
After
- Information centralized in a single system
- Templates managed digitally with version control
- All reports stored and organized in one location
- Real-time status visible to all stakeholders
- Complete revision documentation
- Full audit trail for the entire process
Impact
For BPKAD
Operational Efficiency — Administrative work that previously required manual coordination is now handled by the system automatically.
Better Monitoring — Leadership can see real-time progress across all SKPDs without asking for status updates.
Faster Verification — The structured review workflow accelerates the validation process compared to manual document handling.
Improved Governance — Transparency and accountability are built into the system through the audit trail and role-based access.
For SKPDs
Remote Submission — SKPDs no longer need to physically visit the BPKAD office to submit reports, saving time and resources.
Clear Status Tracking — Each report's status is always visible—pending, under review, needs revision, or approved.
Faster Revision Cycle — Feedback arrives directly in the system with specific notes, enabling quicker corrections and resubmissions.
Reduced Errors — Standardized templates and processes minimize the administrative errors common in manual workflows.
Engineering Challenges
The greatest challenge in this project wasn't technical feature development. It was translating a complex government business process into a digital workflow that could be used effectively by SKPDs with varying levels of technology proficiency.
The system had to be:
- Simple enough for non-technical users to adopt without extensive training
- Flexible enough to accommodate the existing organizational structure
- Comprehensive enough to support multiple report types and user roles
- Auditable enough to meet government accountability requirements
This required deep engagement with the actual reconciliation process—understanding not just what forms needed to be filled, but how information flows between departments, where bottlenecks occur, and what a "complete" process actually looks like from every stakeholder's perspective.
Lessons Learned
SIREKA taught a fundamental lesson about digital transformation: it isn't about moving paper forms to a screen.
Real transformation happens when an organization can change a process that previously depended on manual communication into a structured, measurable, and traceable workflow.
Through SIREKA, the previously scattered process of financial and asset reconciliation was consolidated into a centralized digital platform that supports operational efficiency, transparency, and better governance.
The system's value lies not in any single feature, but in how all the features work together to make the reconciliation process predictable, visible, and accountable—for BPKAD, for SKPDs, and for the public they serve.