SII Czech Republic
Progress Update
Administrative cycle automation project
Wednesday, July 1, 2026 · Thomas Berton · Azuro AI
Overview
Roadmap progress
01Reminder & Escalation
Phase 2 testing
80%
Deliverymid-July
02Timesheet & Invoice Validation
1 step left
85%
Deliverylate July
03Parallel Automations
1 piece in testing
30%
DeliveryAugust
04Logging System
Delivered
100%
DeliveryDelivered
05Knowledge Base
Data collection
20%
DeliverySeptember
Indicative progress and delivery estimates. Module-by-module detail in the following slides.
How it works
How it works, end to end
1
Cycle manager
A new cycle each month, with its parameters
→
2
Opening email
Sent on the set day, collects the files
→
3
Inbound scan
Everything incoming is scanned continuously
→
4
Auto-detection
Timesheets and invoices identified and filed
→
5
Validation
Timesheet checked, then invoice cross-checked
↑ these parameters feed the cycle manager
Admin-controlled
Opening day
Reminders D-4 / D-2
Escalation D-1
Closure D+1
Public holidays
Module 1 · Reminder & Escalation
Automatic detection of submissionsPhase 1 tested in May, on real data, in a sandbox environment
Emails missing from the databasefixed
20% of cases
Unanticipated formats (PDF, image)handled
15% of cases
Phase 1 · May→Phase 2 · wrapping upwith the fixes, to fully validate the module
Module 2 · Timesheet & Invoice Validation
Automatic calculation and controlTested on 10+ invoice + timesheet pairs
10+ pairs
invoice + timesheet tested
Days x Rate
auto calc vs invoiced · OK
Validation
clean or exception
One step remains to validate the module: the timesheet's own control criteria, before the calculation against the invoice (consistent number of days, valid entries, etc.).
Module 3 · Parallel Automations
Parallel automationsThe scope sold, built on the Module 1 foundation
BM updates collection
before the cycle, reminders and escalation
upcoming
Email classification
invoice, payment, timesheet, admin
upcoming
Attendance report
validated timesheets, 2 entities
built, in testing
Invoice data push
days pushed after approval
upcoming
The attendance report is already built and in testing. The rest builds on the Module 1 foundation, adding it will be quick.
Control
You set it, the system does the restNo code, everything is controlled from a simple Excel
1 · You set
Cycle_Calendar.xlsx · Config
Deadline anchor day30
OpeningD-8 working
Reminder 1D-4
Reminder 2D-2
EscalationD-1
Closure / archivingD+1
Public holidaysCZ calendar
Plus the weekend rule and the escalation email. You change a value, that's it.
→
2 · The system runs
⟳
Sending, filing, reminders and escalations, automatically.
→
3 · You track
Consultant A · submitted
Consultant B · submitted
Consultant C · pending
Consultant D · late
Real-time status, latecomers flagged.
A structure still evolving, but already fully controllable by the team.
Module 4 · Logging System
Already in place, and it opens what's next
09:14:02 timesheet_044.xlsx · filed
09:14:09 validation 044 · OK
09:14:12 reminder D-2 · 6 sent
09:14:20 anomaly 071 · flag
Dashboards
cycle activity statistics
Chatbot enablement
data foundation for Module 5
Every action logged: timestamp, file, status. Full audit trail.
Module 5 · Knowledge Base
Towards an internal knowledge base
Documents
process, templates
→
Knowledge base
to validate and enrich with the admin team
Teams / Copilot
conversational agent
Goal: capture internal knowledge, then deploy an agent that answers routine questions.
What's next
Next steps
01
Finalize Module 1 phase 2 testing and validate it.
02
Define the timesheet control criteria to validate Module 2.
03
Start Module 3 on the existing foundation.
04
Enrich the Module 5 knowledge base with the admin team.
Admin keeps control via the Excel control file and consultant tracking.
Thank you
Any questions?
Thomas Berton · Azuro AI