Rule-based and precise
It does exactly what it has been told - the same way every time. No typos, no skipped rows, no month-end fatigue.
RPA Automation
Software robots for businesses
RPA · Robotic Process Automation
Software robots that take over the routine - precisely, day and night.
RPA robots work on the same screens as your colleagues: they log in to systems, copy data, fill in forms, process e-mails and send reports - by the rules, fully logged, without ever getting tired.
60–80%
cost reduction on the automated steps
3-6 mo
typical payback period
24/7
unattended operation
Work queue · incoming invoices
6/6 processed
- INV-0141 184 500 Ft done
- INV-0142 92 340 Ft done
- INV-0143 1 240 000 Ft to human
- INV-0144 56 900 Ft done
- INV-0145 310 000 Ft done
- INV-0146 18 750 Ft done
Orchestrator · scheduled run, weekdays at 08:00
01 · Basics
What is RPA?
Robotic Process Automation is software that performs repetitive, rule-based computer work - on the very same screens your colleagues use. It is most valuable where systems do not talk to each other and people have been moving data between them by hand.
Works like a person
It logs in, clicks, copies and fills in forms - so it can connect even old or closed systems that have no programming interface (API).
Attended or autonomous
It can run on an employee's computer at their request (attended), or on a server, scheduled, without human intervention (unattended) - even around the clock.
Glossary - the language of RPA
RPA
Robotic Process AutomationSoftware that performs repetitive, rule-based computer tasks. The "robot" is a program that works on the same interfaces as a person - it opens applications, logs in, copies data, fills in forms, processes e-mails and produces reports.
Software robot (bot)
Software robotThe executor of an automated process: a program responsible for one clearly defined task - for example recording incoming invoices or the daily bank reconciliation.
Attended robot
Attended botRuns on an employee's computer and starts at their request - for instance, it gathers the data needed from several systems in seconds during a customer call.
Unattended robot
Unattended botRuns on a server without human intervention. It starts on a schedule or in response to an event and can work 24 hours a day - weekends and holidays included.
Orchestrator
Control centerThe control center of the robots: it schedules and assigns tasks, manages permissions and credentials, monitors runs, and raises an alert when something does not go to plan.
Process discovery
Process & task miningAnalysis of system logs and user activity that shows, based on real data, how work actually happens - and which processes are best suited for automation.
Intelligent document processing
IDP · Intelligent Document ProcessingUses artificial intelligence to extract data from scanned or unstructured documents - invoices, contracts, applications - so the robot can work with clean, structured data.
Intelligent automation
RPA + AICombining RPA with AI (for example large language models). The classic robot follows fixed rules, while AI interprets free-text e-mails, categorizes requests and suggests the next step.
Hyperautomation
HyperautomationUsing RPA, AI, and integration and process management tools together, with the goal of automating as many business processes as possible from end to end.
Manual work, RPA or RPA + AI?
| Capability | Manual work | RPA | RPA + AI |
|---|---|---|---|
| Continuous, 24/7 operation | |||
| Error-free, rule-compliant execution | |||
| Complete logging and traceability | |||
| Capacity that scales at peak times | |||
| Handling old systems without an API | |||
| Unstructured input (free text, varying documents) | |||
| Decisions that require judgement |
If the process is mostly about judgement, free-text communication and re-planning on the fly, an AI agent may be the better choice - or both together: AI interprets, the robot executes by the rules. Discover AI agents →
Quick check
Can your process be automated?
Six questions, thirty seconds: tick what is true for one of your processes, and we will show you how good a candidate it is for RPA.
Suitability score
0/100
Tick the statements that are true for your process - the assessment will appear here.
Not ideal in its current form
The process is currently not well suited to classic RPA. It is worth redesigning it first (TO-BE): simplify the steps, standardize the input - or look at where AI could help.
Promising candidate
There is real potential, but a few conditions are missing. Often a little process simplification or AI-based document processing (IDP) makes it fully automatable.
Ideal RPA candidate
A rule-based, repetitive, digital process - classic RPA territory. A pilot robot is typically ready within a few weeks and pays for itself within months.
As the decisions are not purely rule-based, consider an RPA + AI solution or an AI agent: AI interprets and suggests, the robot executes.
Let's discuss your process
Catalog
Robots you can deploy
We have proven robot templates for the most common business routines - each one tailored to your systems, rules and schedules.
Event-driven
Invoice entry robot
Finance & accounting
Reads incoming supplier invoices, extracts the data, matches it against the purchase order and records it in the ERP.
IDP / OCR
ERP
E-mail
Example
1,200 invoices a month recorded without manual typing - only the exceptions go to the accountant.
Scheduled
Bank reconciliation
Finance & accounting
Matches bank statement items against open invoices and collects the unmatched ones in a separate list.
Bank API
ERP
Excel
Example
Daily reconciliation at 6 am - finance starts the day with a finished list.
Scheduled
NAV Online Invoice sync
Finance & accounting
Downloads incoming invoices from the Hungarian tax authority's Online Invoice system and compares them with the accounting records.
NAV API
ERP
Excel
Example
Missing or mismatched incoming invoices flagged immediately - before the VAT return.
Scheduled
Month-end reporting robot
Finance & accounting
Collects closing data from several systems, builds Excel and PDF reports and sends them to management.
SQL
Excel
PDF
E-mail
Example
The management report is ready by 7 am on the first working day of the month.
On demand
New joiner (onboarding)
HR & payroll
When a new colleague arrives, it creates the accounts, requests permissions and sends the welcome pack.
HRIS
AD / M365
Ticketing
Example
Every account and equipment request is ready the day before the start date.
Scheduled
Attendance & payroll prep
HR & payroll
Aggregates attendance and absence data, checks discrepancies and prepares the payroll inputs.
HRIS
Excel
SQL
Example
An error list for HR two days before payroll closing - no corrections afterwards.
Event-driven
Order entry robot
Sales & customers
Checks orders arriving by e-mail or from the webshop, enters them into the ERP and sends a confirmation.
E-mail
Webshop
ERP
Example
Order confirmations within minutes, at any time of day.
Scheduled
CRM-ERP data sync
Sales & customers
Keeps customer and partner data in sync between the CRM and the ERP and filters out duplicates.
CRM
ERP
REST API
Example
A single, up-to-date customer master - without manual copying.
Event-driven
Delivery note processor
Procurement & logistics
Matches incoming delivery notes with orders, records the goods receipt and flags discrepancies.
IDP / OCR
WMS
ERP
Example
Warehouse goods receipt without paperwork, with a discrepancy report.
Scheduled
Price & stock monitor
Procurement & logistics
Collects prices and stock levels from supplier portals and websites and builds a comparison table.
Web
Excel
E-mail
Example
A morning procurement price table from 40 suppliers, with changes highlighted.
On demand
Account & access manager
IT & administration
Creates, modifies or disables user accounts based on tickets and logs every change.
Ticketing
AD / M365
Audit log
Example
Password resets and access requests in minutes, fully auditable.
On demand
Data migration robot
IT & administration
During a system replacement, it reads data from the old system's screens and transfers it to the new one with validation.
Legacy UI
SQL
REST API
Example
Tens of thousands of records migrated over a weekend, with an itemized validation report.
No robot matches your search. Try another keyword, or describe your process in the configurator below.
02 · Design
How a good robot is built
When replacing a task with a robot, the hardest part is not the programming but breaking the process down into clear parts. A well-built robot does not just do its job: it is maintainable, extensible and behaves predictably when something goes wrong.
Current state
Together with the colleagues who run the process, we record step by step what happens: which systems they log in to, where the data comes from, which rules they decide by, and what to do when something fails.
Target state
We rethink first, then automate: is every approval round needed, can incoming document formats be standardized, can a screen-based step be replaced by a direct data connection?
Automating a poorly designed process only delivers the wrong result faster.
The four modules of a robot
Start-up - getting ready for work
Loads the settings, logs in to the required systems and checks that everything is available. Settings (paths, recipients, thresholds) live in a separate configuration, not in the code - so a small change does not require redevelopment.
Gathering the work
Collects the items to process - invoices, requests, records - and puts them into a shared work queue. At high volumes several robots can work in parallel from the same queue, and you can always see where each item stands.
Item-by-item processing
Runs the business logic item by item, independently: checks, records, forwards. If an item is faulty, it flags only that one and moves on to the next - a single bad record never stops the whole process.
Close-down and report
Logs out, closes the applications and sends a summary report: how many items were completed, what went to a human as an exception, and what is waiting for a retry. Recurring elements (login, reporting) are reusable components shared by other robots.
When things don't go to plan: exception handling
Business exception
A piece of data is missing or breaks the rules - for example the invoice has no purchase order number. The robot does not guess: it forwards the item for human review and carries on with the rest.
→ human reviewTechnical exception
An application does not respond or a connection times out. The usual remedy is an automatic retry; if that does not help, an alert goes to the operator.
→ automatic retryWe separate the two branches at design time and log them in detail - so operation stays transparent and quick to fix. For high-risk decisions we deliberately build in a human approval point.
Read more: Structure - how a process is broken down for a robot
03 · Integration
How the robot connects to your systems
A typical process runs through several systems: an order starts as an e-mail and travels through the CRM and the ERP to invoicing. The robot links them together - and its reliability depends on how stable those connections are.
Software robot
run by the Orchestrator
Desktop and web applications
API + UIERP, accounting software, web portals. Where there is an API we connect through it; where there is none, the robot works on the screen just like a person. It finds elements via selectors - a well-chosen identifier keeps working even if the window is resized or a button moves.
ERPCRMSaaS
Files and documents
FileExcel, CSV, PDF, Word: the robot reads, merges and produces them. For scanned or variable-format documents, AI-based document processing (IDP) extracts the data.
ExcelCSVPDFWord
Processes incoming mail, saves attachments, sends notifications and reports. A language model can be added to interpret free-text messages.
Outlook / M365GmailIMAP
Databases
APIDirect SQL queries and data entry - faster and more stable than doing the same through the screen. For reading, we typically use a separate read-only account.
SQL ServerPostgreSQLMySQL
APIs and webhooks
APIReal-time data exchange with modern cloud services and government systems (such as the Hungarian NAV Online Invoice). If a reliable API exists, we always choose it: it is faster, more stable and immune to interface changes.
RESTWebhookNAV API
Legacy systems
UITerminal or mainframe applications that are often reachable only through UI automation. On remote desktops or virtualized environments, image recognition and OCR help - flexible, but it requires more careful design.
3270 / 5250Citrix / RDPMainframe
Screen or API? The rule is simple.
UI automation
Works like a person: clicks, fills in fields, reads from the screen. It finds elements via stable technical identifiers (selectors); where there are none, image recognition and OCR help.
- Works with old or closed systems too
- Requires no development in the target system
- More sensitive to interface changes
- Slower: it has to wait for screens to load
API integration
Exchanges data with the system directly through a programming interface - bypassing the screen entirely.
- Fast and stable
- Unaffected by interface redesigns
- Scales well at high volumes
- Only available where a reliable API exists
Where there is a reliable API, we use it - where there is none, carefully designed UI automation. The best results come from a mix of both.
Security is part of the design
Dedicated robot account
Every robot works with its own dedicated user and receives only the permissions its task requires.
Encrypted credential vault
Passwords are never stored in code or files: the robot retrieves access from an encrypted vault at runtime.
Complete audit log
A detailed log records which robot accessed which data and when - searchable at any time.
04 · Scheduling
Ready for work at the right moment
In theory a robot could work at any time - in practice systems are not always available: maintenance windows, overnight batch jobs, closing periods. Good scheduling starts the robot when all conditions are met and makes good use of capacity.
- Scheduled
- Event-driven
- On demand
- Maintenance
- Batch run
- Transfer deadline
Dependencies
The reporting robot only starts once the reconciliation robot has finished - the control center enforces the order automatically.
Working calendar
A robot cannot know on its own when there is a holiday or a moved working day: the company calendar is built into the schedule.
Cloud elasticity
At peak times several robots can work in parallel, and in quiet periods you do not pay for unused capacity.
Monitoring and alerts
If a run is missed, takes longer than usual or ends with an error, an automatic alert notifies the person responsible.
A robot's working day
Three scenarios, three trigger types - follow step by step where the robot works on its own and where the decision goes to a human.
-
06:00
Working-day check
The robot checks the company calendar to confirm today is the first working day of the month - it does not start on a holiday.
-
06:01
Start-up and login
Loads the configuration, retrieves access from the encrypted vault and logs in to the ERP.
-
06:05
Data collection
Queries the general ledger extract, open items and bank balances.
-
06:18
Reconciliation
Compares the data item by item; finds three discrepancies and puts them on a separate list.
-
06:20
Approval of discrepancies
The three discrepancies go to the controller - the robot does not decide for them, it only prepares the decision.
-
07:00
Management report
Builds Excel and PDF reports, sends them to management and logs the result of the run in the control center.
-
09:41
A new order arrives
An order with an attached PDF arrives in the orders@ mailbox - this event starts the robot.
-
09:41
Data extraction
Document processing extracts the customer, line items, quantities and delivery address.
-
09:42
Validation
Checks the customer in the CRM, and stock and prices in the ERP.
-
09:42
ERP entry
Enters the order into the ERP - this module has no API, so it uses UI automation.
-
09:43
Confirmation
Sends the customer a confirmation e-mail with the expected delivery date.
-
09:43
Exception flagged
If an item is out of stock, the robot alerts the sales rep and does not promise a delivery date.
-
14:02
HR starts the robot
With one click, HR starts the onboarding robot with the new colleague's details.
-
14:02
Account creation
Creates the directory and e-mail accounts and assigns groups based on the job role.
-
14:04
Access requests
Requests the system permissions belonging to the role via tickets.
-
14:05
Manager approval
Elevated permissions are approved by the manager - the robot does not proceed without it.
-
14:30
Equipment and tasks
Records the laptop and access card requests and sets up the first week's to-dos.
-
14:31
Welcome pack
Sends the joining details to the colleague and their manager; the run is logged.
Business value
What could a robot deliver?
Enter the figures for one of your processes - the calculator instantly shows how much working time and labour cost could be freed up.
Estimated result
96
hours / month
of working time freed up
0.6
FTE equivalent
7,488,000 HUF
annual labour cost savings
Manual work today
120 h
Left with a robot
24 h
* An indicative estimate based on the figures entered (160 working hours/month/FTE). We calculate the exact payback - including licence and implementation costs - in the free assessment.
0%
less manual work on the automated steps*
24/7
operation - weekends and holidays included
0mo
typical payback for a well-chosen process
0%
of robot steps logged and traceable
* Savings vary by process; in the free assessment we provide a concrete estimate calculated for your processes.
Implementation
From idea to a robot in production
A predictable project validated step by step - with a fast first result and a robot that survives changes in your systems.
01 /
Process discovery
We assess the current process (AS-IS), select the candidates with the best payback and estimate the savings.
1-2 weeks
02 /
Design (TO-BE)
We rethink the process, write the process definition and capture the exceptions and approval points.
1-2 weeks
03 /
Development and testing
We build a modular robot from reusable components and test it on real data together with key users.
2-4 weeks
04 /
Go-live and operations
Scheduling, monitoring, alerts - we keep a constant eye on the robot and adapt it to your changing systems.
ongoing
Knowledge base
Want to go deeper? Read the series
Our four-part article series takes you from the basic concepts of RPA through design and integration to scheduling.
1/4 · BASICS
Basic Concepts
Thanks to the development of the IT industry, our everyday language has been enriched with countless new words. This article invites the reader on a short journey through the RPA glossary. #RPA #BASICS
2/4 · DESIGN
Structure
The real challenge in replacing a task with a robot is breaking it down into sub-units and solving these individual problems. #DESIGN #STRUCTURE
3/4 · INTEGRATION
Connections
To ensure process execution, numerous systems must communicate with each other, making good surface automation critically important. #API #INTEGRATION
4/4 · SCHEDULING
Timing
Due to corporate financial systems, it cannot always be guaranteed that the necessary servers are available at any moment of the day. #TIMING #SCHEDULE
Configurator
Request a robot
Put together in a few clicks what you would automate - in the free consultation we will show you how it can be done and how quickly it pays back.
1Which area would the robot work in?
Pick one - it is the starting point.
2Which tasks should it perform?
Multiple choices allowed.
3Which systems should it work with?
Multiple choices allowed.
4How should it start?
Pick one - if you are not sure yet, we will help with that too.
Your robot request
Choose an area, tasks, systems and a trigger type - the summary is assembled here.
Continue to contact form
The button takes you to the contact page where the summary is pre-filled - you can edit it freely before sending.
FAQ
What companies usually ask about RPA
An RPA robot follows precisely defined rules, the same way every time - ideal for stable, repetitive processes. An AI agent is built on a language model: it interprets, plans and adapts to new situations. The two complement each other well: often AI interprets the input and the robot executes the steps by the rules.
Wherever possible we connect via API, which is immune to interface changes. For screen-based steps we use stable selectors and organize the connection logic into reusable modules - so a change has to be fixed in only one place, and every affected robot works again. It helps a lot if IT announces planned updates in advance.
UiPath, Microsoft Power Automate and custom, code-based robots (for example in Python). We match the platform to your existing licences, system landscape and volumes - not every process needs an enterprise licence.
Yes, if security is part of the design. Every robot works with its own dedicated account and only the permissions it needs; passwords are kept in an encrypted vault, not in the code; and every access is recorded in a detailed audit log.
Typically within 3-6 months, and even sooner for high-volume, rule-based processes. In the free assessment we build a concrete payback estimate from your real figures - item volume, handling time, labour cost.
In our experience robots take over the monotonous, low-value steps - typing, copying, reconciling. Your colleagues can then focus on exceptions, customers and value-adding work; decisions stay in human hands.
Which process shall we start with?
In the free assessment we pick the process with the fastest payback and show you how a software robot would work on it - with concrete numbers.