Software robots for the work your team repeats by hand
Robotic process automation means handing a repetitive screen task to software that uses the same screens a person does: posting in SAP or whichever ERP you run, downloading a list, merging it in Excel, sending the result by e-mail. You describe the work, we build the robot. It runs inside your company, under the user who used to do the work, and it stops and asks when it is not sure.
What a robot can take over
A good candidate is any task someone can describe step by step: open this, copy from here, paste there, check that. Which application it happens in matters less than whether the rule can be written down.
Some of the work we can automate:
- SAP: incoming invoice posting, creating and updating master data (materials, customers, vendors), purchase requisitions and orders, month-end close steps, periodic reports
- Other ERPs: the same work in Microsoft Dynamics 365, Oracle (NetSuite, JD Edwards), Logo (Tiger, Netsis), Mikro, Canias, IFS, Infor, Uyumsoft and any other ERP
- Excel: collecting files from several people, merging them, filling a template, checking totals
- E-mail: reading data from attachments, sending results and reports to the right people
- Portals: downloading lists and documents from bank, e-document, government or partner portals
- CRM, in-house applications and older desktop programs: anything with a screen but no way to connect to anything else
- Teams and Outlook: sending the team plans, reminders and summaries
You describe the work, we automate it
The person who does a task every day knows its rules best, so every project starts next to them. We walk through the steps on their screen and note each exception: what happens if this field is empty, who to ask when the totals do not match, what changes at month end.
Those notes become a written process description for you to approve. You decide which account is used and how each exception is handled; we turn those decisions into the robot's rules. When the rules change, the robot changes with them.
In SAP, in other ERPs and outside them
Because a robot uses the screen the way a person does, the ERP you run is not the deciding factor. Everything we automate in SAP we also automate in Logo, Netsis, Mikro, Dynamics 365, Oracle or Canias, with no changes or add-on modules in your ERP.
A large share of repetitive work also happens outside the ERP, somewhere between Excel and Outlook, and most processes mix the two: data comes out of the ERP, gets reshaped in Excel and goes out by e-mail, or the other way round. A robot runs the whole chain regardless of the application.
If you already have a macro or script that works, you do not have to throw it away. Often the best move is to make it traceable and build the robot around it, adding memory and brakes instead of replacing it.
The rules every robot follows
What a robot will not do matters as much as what it will. Every robot we deliver works to the same principles:
- The same record is never entered twice. Finished items are skipped on the next run.
- It stops when unsure. An action with an unclear result is never retried automatically; it is flagged for a person.
- It resumes where it left off, even after the computer restarts.
- Data stays in the company. The robot runs on your machines, with no cloud in between.
- Every step is logged: who, when, what, and with which result.
- It works with your permissions. No separate super-user is created.
- Every change is protected by tests. Every product we deliver runs automated tests.
What is not a good fit
Work that needs judgement every time, decisions that change from person to person, and short tasks done once a year are rarely worth a robot. Simplifying the process, a small development inside SAP or a small internal tool is often the better answer, and we will say so on the first call.
How a project runs
Every project starts with a single process:
- 01Discovery call (30 minutes): you describe the work and we tell you plainly whether it suits a robot.
- 02Process analysis (1-2 weeks): steps, exceptions and stop points are written down.
- 03Pilot (2-4 weeks): the robot runs in trial mode and its results are compared with the manual work.
- 04Go-live (1-2 weeks): installation, control panel, activity log and user training.
- 05Maintenance and support: when screens or rules change, we update the robot.
From our projects
For the accounting team of a manufacturing group, monthly invoice posting went from a full week to 15 minutes, with no one watching over it. At another manufacturer, the finance, purchasing and production teams run their repetitive SAP work from one modular platform, and each new process is added as a module. Outside SAP, one team's planned work now goes out every morning and evening through Teams and e-mail without anyone writing it up.
Related work
- Invoice posting automationInvoice robot15 min New run time of a monthly job that took a week
- SAP process automation platformAutomation platformHours → minutes Time spent on repetitive SAP work
- Team planning and notification appTeam plannerAutomatic Morning plan and evening summary go out by themselves
Questions
Do we need to buy an RPA platform licence?
No. We build our robots ourselves, so no separate RPA platform licence is required. If you already run an RPA platform, we will look at your process and recommend whether it belongs there or in a standalone robot.
What happens when the robot hits an error?
It does not guess. It stops that item, marks it as needing a check, writes the reason to the log and notifies the right person. Other items can continue. Incomplete data never reaches SAP or your ERP.
We do not use SAP. We run a different ERP. Does this still work?
Yes. Robots work on any system with a screen: Microsoft Dynamics 365, Oracle, Logo, Mikro, Canias, IFS, Infor, Uyumsoft or software written for your company. Invoice posting, master data, purchasing and month-end steps move to a robot in those ERPs the same way they do in SAP.
Will the robot break if the screens change?
The part that talks to the screen needs updating. When the robot notices a change it stops instead of typing into the wrong field. Business rules and checks are kept separate, so updates are usually small and covered by maintenance.
Do we have to document the process ourselves?
No. Describe the work and show it to us once on screen. We write down the steps, exceptions and stop points and send them to you for approval.
How soon do we see results?
Analysis takes 1-2 weeks and the pilot 2-4 weeks. Simple tasks are faster, and work spanning several applications takes longer. Timeline and price are confirmed in writing after the analysis.
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.