Everything we automate in SAP, we also automate in your ERP
Our robots take over the SAP work that eats the most time: invoice posting, master data, the purchasing chain, month-end steps. We do the same work in Microsoft Dynamics 365, Oracle, Logo, Mikro, Canias, IFS, Infor, Uyumsoft and any other ERP. A robot uses the screen the way a person does, so what decides whether a task can be automated is not the ERP but whether its rule can be written down. You describe the work, we automate it.
Which ERPs we work with
Most of our projects are in SAP, but our robots do not need SAP. The same approach works in any ERP where an employee signs in with their own user and enters records on screen. ERPs we work with include:
- SAP
- Microsoft Dynamics 365
- Oracle: NetSuite and JD Edwards
- Logo: Tiger and Netsis
- Mikro
- Canias
- IFS
- Infor
- Uyumsoft
- Any other ERP you run, including packages not on this list and systems written for your company
The systems around the ERP count too
Most repetitive work happens between the ERP and something else. Invoices arrive by e-mail or through an e-document portal, requests are collected in Excel, approvals wait in Outlook and Teams, and account movements sit in the bank's portal. A robot runs that whole chain. Systems it can work with include:
- Excel and shared files
- Outlook and shared mailboxes
- Teams channels and messages
- Bank and e-document portals
- Customer and supplier web portals
- CRM
- In-house applications and older desktop programs
What we automate
Almost everything we take over in SAP has an equivalent in other ERPs. The screens have different names; the work is the same. Some of the work we can automate:
- Posting incoming invoices to the ERP: e-invoices, PDFs, scans and foreign invoices, under your account and cost centre rules
- Master data: creating and bulk-updating item, customer and supplier records from a request list, with checks before anything is saved
- The purchasing chain: requisition, approval, purchase order and receipt, with the invoice amount compared against the ERP
- Month-end steps: period tasks, recurring entries, pre-close and post-close checklists
- Reports: ERP data turned into a standard template and sent to the right people at a set time
- Moving data between systems: no more manual copying between the ERP and Excel, a portal, a CRM or a second ERP
A robot works on anything with a screen
A robot uses an ERP the way the person who does the work today uses it: it opens the screen, fills in the fields, saves and reads the result the system returns. From the ERP's point of view, the work is still done by that employee. Records carry their user, and your permissions do not change.
That is why your ERP needs no changes and no add-on modules. A desktop ERP, a browser-based ERP and software written for your company are all automated the same way. If a screen changes, the robot does not guess; it stops and tells someone. The part that talks to the screen is kept apart from the business rules, so updates are usually small.
If your ERP offers a way to connect, we use it
Many ERPs offer their own way to send and receive data. When volume is high and the flow is permanent, that route is faster and sturdier than working through the screen, and we will recommend it. When there is no way to connect, when it needs an extra licence, or when the work is small and changes often, a robot is the more practical choice.
Most projects use both: data comes in one way, gets checked, and goes out the other. We recommend a route in writing during analysis, with our reasons. Whichever route is chosen, the rules are the same: no record is entered twice, a record that fails to transfer is listed with its reason, and every step is logged.
Your data stays in the company
The robot runs on your own machines, and ERP data is not sent to the cloud. The ERP password is stored encrypted on that computer and never appears in any log, report or e-mail. Under KVKK, Turkey's data protection law, and similar rules elsewhere, this is the simplest setup there is: the data stays where it already lives.
Every step is written to an activity log: which document, when, under whose user, with which result. In an audit, the answer to who entered this record is the same as when the work was done by hand, with the robot's detailed log added on top.
From our SAP work
For the accounting team of a manufacturing group, monthly invoice posting went from a week to 15 minutes. At another manufacturer, the repetitive work of the finance, purchasing and production teams now runs on one modular platform. Both were built in SAP. The same robot structure and the same rules carry over to another ERP; what changes is the part that talks to the screen.
How we start
Every project starts with a single process and follows the same order:
- 01Discovery call (30 minutes): you tell us which ERP you run and describe the work; we tell you whether it suits a robot.
- 02Process analysis (1-2 weeks): we walk through the steps on the screen of the person who does the work and write down exceptions and stop points.
- 03Pilot (2-4 weeks): the robot runs in trial mode, and nothing is posted to the live ERP until its results match the manual work.
- 04Go-live (1-2 weeks): installation, control panel, activity log and user training.
- 05Maintenance and support: when your ERP is updated or its screens change, we update the robot.
Questions
We use Logo, Netsis or Mikro. Does this work?
Yes. The robot uses the ERP through its screens, the way an employee does, so in Logo Tiger, Netsis and Mikro it does the same work it does in SAP: invoice posting, opening customer and item records, entering orders and delivery notes, periodic reports. Your ERP does not need to change.
Our ERP has no API. Can you still automate it?
Yes. A robot does not need a way to connect; any task that can be done by hand on screen can be handed to it. If your ERP offers a connection later, the business rules and checks stay the same and only the part that reads or writes data changes.
What happens if we change ERP?
The business rules, checks, activity log and reports carry over to the new ERP; the part that talks to the screen is rebuilt for the new system. So if an ERP change is on the horizon, you do not have to wait to start automating. We do not run the migration project itself; we move the robots to the new system once it is live.
We move data between several ERPs and systems. Can that be automated?
Yes. If one group company runs SAP and another runs Logo, or orders sit in a portal, stock in the ERP and invoices somewhere else, the robot takes data from one system, checks it and writes it to the other. Records that do not match are not transferred; they are listed with the reason.
Do we need an extra ERP user licence for the robot?
The robot usually runs under the user of the person who does the work today. If your ERP vendor's licence terms require a separate user for the robot, we clarify that with you during analysis and put the cost in writing up front.
Give us 30 minutes and one job.
Tell us about a repetitive task or a tool your team is missing. We'll tell you plainly what it needs. If it needs nothing, we'll say that too.
Free, 30 minutes, no commitment.