The situation we meet most often
An ERP more than a decade old, running on its own server, its vendor long inactive, and IT holding one rule: do not touch it. This is not an edge case — it is the normal condition of Indonesian companies that have been operating for a while.
Between those systems there is usually an unofficial bridge: an export to Excel, copy-paste between applications, an attachment sent by email. That is where most of the time is lost, and where automation is felt most.
Three integration routes
- API integration — the cleanest route where the system supports it. Data flows both ways and every call can be audited.
- Database connector — for systems without an API. Read-only access to a replica rather than the primary, so load and risk stay on our side.
- RPA — the last resort for systems reachable only through their interface. Fragile against UI changes, so always paired with monitoring and a clear escalation path to a human.
Processes we typically automate
- Invoice processing — extraction, validation against the PO, and posting to the ERP
- Reconciliation between systems currently bridged by hand
- Inbound document handling: classification, extraction, and routing to an owner
- Recurring reports assembled manually from several sources
- Triage of inbound requests from email or chat into the right queue
People keep the decision
Every flow we build has an exception path. The system handles the routine cases and raises the unusual ones to the person with authority, along with the reason it was raised.
In the invoice processing case study we ran, the biggest change was not a machine replacing the finance team — it was the finance team stopping routine data entry and handling only exceptions.
Typical duration: 8–12 weeks. Final scope is set after the audit.