Advanced automation
No more re-keying in software with no programming interface: a robot enters the data, checks it and keeps a record.
Your teams copy data from one application to another, download, rename, follow up. We automate these repetitive tasks, including in legacy software that offers no programming interface. What is entered is checked, and every run leaves a record.
Your teams are doing the job of an interface that does not exist.
Two applications that do not talk to each other and, between them, a person copying. That is daily life in many firms and finance departments: hours of data entry, attention wearing thin, and errors discovered too late.
Many desktop applications offer no programming interface. A software robot then does what the person would do: it opens the screen, enters, checks. The difference is that it starts from data that has already been validated, and reads back what it has just entered.
When to consider it
- Hours of re-entry every week between two applications that do not talk to each other.
- Typing errors discovered too late.
- A legacy application, indispensable, that nobody can connect to the rest.
- Peak periods when the team is no longer enough.
What you get
Data-entry robots
A software robot enters data in your existing applications the way a person would, from data that has already been validated.
Hand-offs between systems
Your applications, emails and files connected by automated flows.
Built-in controls
What is entered is read back by the machine and compared with the source; discrepancies are reported to you.
Run log
Who launched what, when, and with what result.
Use cases
Entry into a desktop application
Data validated upstream is entered into accounting or tax software that offers no way to import it.
Batch processing
The files validated during the day are processed one after another, on a dedicated machine, without tying up a workstation.
Hand-offs between applications
A document received by email is filed, recorded and flagged to the right person, with no manual handling.
How it goes
Choose the right task
We measure with you what is repetitive, stable and costly. Not everything deserves to be automated.
Automate and test
The automation is tested on your real cases, including the exceptions.
Monitor and adjust
When an application changes, the automation has to be adjusted; we plan that follow-up with you.
Why Kantia
Checking is part of the robot
Every entry is read back by the machine and compared with the source. If something goes wrong, a screenshot is kept.
We check before we automate
The terms of use of your software’s publisher are checked before any engagement.
We say what a robot does not do
A robot depends on the software’s screen: it has to be adjusted when the publisher releases a new version. We plan for that from the start.
Frequently asked questions
- My software has no programming interface. Is it possible?
- Often, yes: that is exactly the case data-entry robots exist for. We check it on your software during the diagnostic.
- What happens if the robot finds a discrepancy?
- It decides nothing: it enters data that has already been validated, reads back what it entered and stops if there is a discrepancy. The discrepancy is reported to you.
- Does the robot replace people?
- It replaces re-entry. Your teams keep the review, the special cases and the client relationship.
- Where does the robot run?
- On a team member’s workstation, on demand, or on a dedicated machine on your premises for batch processing.
Your case deserves thirty minutes.
A conversation to understand your context and tell you, frankly, whether we are the right choice. The diagnostic that follows is free of charge.
Book a call