"Our system has no API, so it can't be automated." It's the sentence we hear most. And it's understandable: for years automation meant integrations, and without integrations there seemed to be nothing to do. That left two options: replace the ERP, with months of work and high costs, or keep typing data in by hand.
Today there's a third option, and it's the one we use on ourselves.
A robot that uses the software like a person
If the system runs in a browser or as an application, an agent can use it the same way: it opens screens, fills in fields, saves and checks that the save worked. It runs on a dedicated server with its own user account, and works when the system is free, usually at night.
The difference from the old robots that replayed recorded clicks is that the agent understands what it sees. If a window moves, a warning pops up or a field is already filled, it doesn't break: it reads the screen and decides the next step. When something doesn't add up, it stops and asks.
What you can do this way
- Post supplier invoices and journal entries that have already been checked.
- Enter customer orders received by email or through portals.
- Match approved receipts and payments.
- Update customer records, price lists and stock.
- Pull reports the system can't export on its own.
The rules for doing it safely
A robot that writes into your accounting system should follow the same rules as a new colleague.
- A dedicated user with the minimum permissions for that process. Never a person's credentials.
- Nothing final without approval: the robot only records what the team has already approved.
- A full log: every action saved with date, time and the data entered, so you can always see what happened.
- Error alerts: if the system doesn't respond or an entry fails, you get an alert and the action is retried, not lost.
When it really makes sense
When the ERP does its job well and the only problem is data entry. Replacing software to get an API costs months, training and risk. Keeping the ERP and adding an agent next to it takes weeks, and the team keeps working with the tool it knows.
It's not the right answer when the system genuinely needs replacing, because of missing features or because the vendor no longer updates it. In that case it's better to say so upfront, and we do in the first assessment.
Our own case
We use a cloud accounting system that is slow and has no API. Every month our admin team matched hundreds of transactions by hand. Today a robot on a dedicated server records at night what the team approved during the day. The software is the same; everything around it has changed.