AZURO

SII Czech Republic · Automation program · Delivery review

Everything is built.
Two modules run in production.

Status of the 5 modules, the August 2026 numbers, and the one decision we take together today.

9 September 2026Thomas Berton · Azuro AI

01 · Where we stand

Five modules, at a glance.

MODULE 1

Smart Reminder & Escalation

In production

Opening emails, detection and filing, tracker, reminders, closure. 91% collected automatically in August.

MODULE 2

Invoice Validation

In production

Days x rate = amount, checked before anyone opens a PDF. Two cycles of testing.

MODULE 3

Parallel Automations

Built, in test

BM Data Collector, Inbox Classification, Attendance Report. Invoice Push next.

MODULE 4

Logging & Dashboard

Live

Every action logged. Dashboard with cycle view, exceptions, performance and time saved.

MODULE 5

Knowledge Agent

Ready, surface to decide

Agent built, knowledge base v1 built. Where it lives is today's decision.

Nothing changed in the admin team's habits. Same mailbox, same files, same checklist. The automation runs in parallel, with no duplicates and no one stepping on the other.

SII Automation Program02 / 12

02 · August 2026 cycle, real numbers

What the automation did last month.

Timesheets collected automatically

91%

detected, named, filed in the consultant's folder, tracker updated

Invoices detected

read with Azure Document Intelligence, no LLM ever sees the PDF

Validated automatically

days worked x daily rate = invoiced amount, exact match

Discrepancies caught

amount or currency gap against the timesheet, isolated for review

A flagged invoice is not an automation error. It is the check doing exactly what it is there for: finding the gap before payment, so the admin team only looks at the 8, not the 24.

Source: automation ledger (Tracking file, execution log), visible in the dashboard03 / 12

03 · Module 1 · Smart Reminder & Escalation · in production

The collection cycle runs itself.

01
Opening emailEvery consultant gets the right template at cycle opening. Nataliya drops the month's templates in one folder, the flow redistributes them.
Built
02
Detection and auto-filingEach incoming timesheet is identified, named and filed. 91% of August collected without a human touch.
Production
03
TrackerLive status per consultant: received, pending, late, error, with latency.
Production
04
Reminders and escalationThree reminders: two to the consultants, one to the admin with the really late ones. Dates and on/off editable through the Cycle Review agent.
Built
05
Cycle Review agentAt cycle start, validates with the admin: opening date, template send date, reminder dates, deadline, working days of the month.
Surface to decide

Left to do: hand Nataliya the new Timesheet Checklist Master, one file for both sides04 / 12

04 · Module 2 · Timesheet & Invoice Validation · in production, 2 cycles of testing

Invoices checked before anyone opens them.

01
ExtractionAzure AI Document Intelligence, non-generative, approved by SII security on 17 August. Only structured fields leave the step.
02
The checkDays worked x daily rate = invoiced amount. Exact match, zero tolerance. Currency and rate verified.
03
ExceptionsMismatch, missing rate, low confidence: routed to the admin, never auto-validated on doubt.
04
One folder per consultantTimesheet and invoice side by side. One click from the dashboard opens it.

August 2026

16 validated

8 flagged

out of 24 invoices detected. Some cases (on-call, mobile allowances) will keep needing a human decision, and the flow routes them instead of guessing.

Keeps improving cycle after cycle05 / 12

05 · Module 3 · Parallel Automations · built, entering test

Four automations around the cycle.

R1.P1.1

BM Data Collector

Surface to decide

An email reaches each Business Manager at cycle start. The agent collects leavers, newcomers and rate changes through a conversation or a voice message. Buffer table, admin review.

R2.P1.1

Inbox Classification

In test now

Timesheet mail is already handled deterministically. The classifier covers the rest, signatures stripped. Validated with Nataliya at the end of the September cycle, then production.

R1.P2.3

Attendance Report

Built

Every detected timesheet is written day by day into one generic Excel, each line flagged with the manager. One paste per manager. No hard-wired manager list to break.

R1.P3.2

Invoice Push

Same mechanism, applied to the "invoices to issue" file. Cloned once the Attendance Report is validated with the admin team.

The day-by-day manual transfer disappears06 / 12

06 · Module 4 · Logging System · offered · live

Every action logged, one console to see it.

AUDIT TRAIL

Execution log

Timestamp, cycle, flow, consultant, result, details. The evidence layer for what the automation actually did, and raw material for maintenance.

DASHBOARD

Cycle, consultants, activity

Timeline of the cycle, what needs attention today, every consultant with one-click folder access. The admin checklist is the source of truth and overrides the automation's view.

PERFORMANCE

Automation vs admin team

Consultant by consultant: what the flows handled against what the admin ticked. Exceptions caught. Time saved for SII, computed from the audit's minutes per task.

Local HTML file, reads the Excel files directly, nothing written back, no server. More statistics as the team gets used to the automation.

Delivered 2 September, updated today07 / 12

07 · Module 5 · Internal Knowledge Agent · ready, surface to decide

The FAQ agent is ready.

01
Agent builtAnswers the team's recurring operational questions: processes, rules, deadlines.
02
Knowledge base v1 builtFrom the SII website content. Internal documents added next, each reviewed by SII before indexing.
03
No personal dataCurated content only, as agreed with Jakub on 18 and 19 August. No mailbox ingestion.

"Where do we put this agent?"
Answer that today, and Module 5 is complete.

Progressive rollout: sandbox, supervised, autonomous08 / 12

08 · The decision for today

Where do the agents live?

Three agents are built in Copilot Studio: Cycle Review (admin), BM Data Collector (Business Managers), Knowledge Agent (whole team). Teams was surface number one and is blocked by the custom app policy.

Option	Fits	Requirements
Teams (custom app approved)	All three agents, best experience, proactive messages	Teams admin: allow Power Platform apps, approve the app, setup policy for BMs and admin
Copilot access for the admin team	Cycle Review, and the knowledge agent for a small group	Copilot licences for the users concerned
Dedicated email address (answers only to @sii.cz)	BM Data Collector, Knowledge Agent	A mailbox and a mail-triggered flow, no Teams change

The choice can differ per agent. Once SII France confirms, a precise request goes to Jakub09 / 12

09 · Deliverables and next steps

What happens after today.

Azuro, after today

01
Complete documentationFlows, agents, files, folders, how to operate and pause each automation.
02
New Timesheet Checklist MasterHanded to Nataliya, one file for both sides.
03
One-hour training with NataliyaBefore the next cycle starts.
04
September cycle validationsInbox Classification against Nataliya's sorting. Attendance Report, then clone into Invoice Push.

SII, decisions and requests

05
Surface for the three agentsWith SII France's confirmation on Teams.
06
Authorization request to JakubPrecise, once the surface is chosen.
07
AI Builder creditsModule 2 at production volume, about 5 to 15 USD per month.
08
Director's email addressFor the escalation reminder.

SII Automation Program10 / 12

10 · Real deliverables

What is actually handed over.

FILES

The control set

Timesheet Checklist Master: one file for admin and automation.

Control files: Execution Log, Cycle Calendar, Consultant Tracking, BM Update Collection.

Saved files: every timesheet and invoice, by year / month / entity / category / consultant.

CONSOLE

HTML dashboard

Cycle timeline, what needs attention, consultants with one-click folder access, activity log, cycles history, performance and time saved.

Local file, reads the Excel files directly, no server.

3 AGENTS

Copilot Studio

BM Update Collector: consultant changes from each Business Manager.

Cycle Review: validates and adjusts each cycle with the admin.

Internal Knowledge Base: the team's FAQ agent.

10 AUTOMATIONS

Power Automate

Email collection trigger (detection and filing) · Orchestrator · Cycle Generator · Reminders and Escalation · Invoice Validation · Attendance Report · Closure and Archiving

Agent flows: Confirm cycle · Modify cycle · Get latest cycle

Plus the full documentation: one guide per flow and per agent, the folder structure, how to operate and how to pause each automation.

Everything lives in the SII Microsoft 365 tenant11 / 12

11 · What SII gets today

A cycle that runs itself, for real.

Collection on autopilot

Templates out, files in, tracker live, reminders and escalation on schedule.

Invoices checked first

Discrepancies isolated before payment. The admin looks at the 8, not the 24.

One folder, one click

Timesheet and invoice side by side, opened from the dashboard.

A console for the cycle

What needs attention, what the automation did, the time it saved.

An audit trail

Every automated action, evidenced and searchable.

Three agents ready

Live the day their surface is chosen.

Thomas Berton · Azuro AI · contact@thomas-berton.com12 / 12

Everything is built.Two modules run in production.

Five modules, at a glance.

What the automation did last month.

The collection cycle runs itself.

Invoices checked before anyone opens them.

Four automations around the cycle.

Every action logged, one console to see it.

The FAQ agent is ready.

Where do the agents live?

What happens after today.

What is actually handed over.

A cycle that runs itself, for real.

Everything is built.
Two modules run in production.