A folder, a bot, an archive and a control report
IN folder
order_1041.csv
order_1042.csv
order_1043.csv
bot
parsing
field validation
transactional save
archive
log entry
OUT folder
archive + logs
control report
zero-price documents
weekly, by email
Files come in, the bot processes them and moves them to the archive, and every operation stays in the log. The control report goes out on its own.
Starting point
Thirty-five minutes for one file.
Save the file, open it, check the data, import it, verify it. Fifteen to twenty-five errors a month, and zero-price documents only surfaced when the period closed. In peak season the team couldn't keep up.
What we built
A platform at the client's site, and three bots.
We set up the platform on the company's own server, with a connection to the Firebird database and folders for input files and archives. The first bot imports, the second builds reports, the third watches both.
Monitors the input folder at a set time
Checks the file: format, required fields, data types
Imports in a single transaction, moves the file to the archive, logs it
A control report that flags zero-price documents, sent weekly
A supervisor bot: watches tasks, resources and the database connection, sends alerts
Results
30–35 min → 2–3 min
one file import
15–25 → <3
errors per month
5–8 → 100+
files per day
2–4 h → 15 min
human work per day
8 h → 24/7
process availability
Tools
Prometeusz / Dedal
Firebird
Scheduling and logs
XLSX / CSV / PDF reports
Email notifications
EDIH hub4industry
Data import without a person in the loop.
We don't name the company. Numbers come from the audit and process measurement at the client.