F7Finance and administrationPEC triage
Triage the PEC inbox: every message with its deadline
The PEC mailbox sorted on Monday morning: every message by sender and kind, with its deadline computed by code from the certified date and the rule — avviso bonario, cartella, INPS, court acts, SdI rejections — the amount to pay and who must act.
The problem
The PEC inbox gets opened once a week, and inside are a tax notice, a payment demand, an SdI rejection, maybe a payment order. Each has its own deadline, to be worked out from the certified delivery date.
Who it is for, and when
- Who it is for
- The administration office of a small company — or the owner who is that office — and the accountant who looks after it: whoever has the PEC password and opens it once a week.
- When
- Monday morning, back from the holidays, the day the accountant asks «has anything arrived?»: before a term passes with nobody having read it.
What you give it, what you get
You give it
The PEC messages exported from the webmail, as they are: the .eml files (with daticert.xml and the signed .p7m attachments) or a ZIP archive holding them; a PEC forwarded inside an e-mail is fine.
You get
The verdict on top — «N cose da fare questa settimana» — then every message as a card with its deadline and computation, the amount and who acts; the .ics calendar, the mailbox's CSV and the drafts for the accountant and the lawyer.
How it works, in three steps
- Export the PEC mailbox and upload the ZIP or the .eml files
- Read what to do this week and who acts
- Import the calendar and send the drafts
On its own, in a flow. Published as a page: whoever exports the mailbox (the office, the owner) uploads the messages and gets the triage; connected to a folder, every week the exported mailbox is read and the calendar updated.
The rules it applies
In the agent's own words: what it checks and what it never does.
- Every deadline by rule: 60 days, August, after 21:00
- Dates from daticert, never the e-mail's own header
- Who acts: accountant, lawyer, owner or the office
- Read-and-recommend only. The agent never moves money.
A real example
A case from the demo catalogue, with anonymised documents.
A week of Acme Impianti's PEC: eight messages, three things to do by Friday — the SdI rejection today, the formal demand tomorrow, the invoice on Wednesday
It is Monday 5 October. Giulia, in Acme Impianti's office, opens the PEC (certified e-mail) box nobody has looked at since last Monday and downloads it from the webmail as a ZIP: an avviso bonario from the tax agency, an INPS notice of charge, two supplier invoices, a supplier's lawyer's formal demand, an SdI rejection, a Chamber of Commerce notice and a webinar invitation. She needs to know what is due this week, who handles it and what can wait.
The recorded result
8 PEC lette · 3 cose da fare questa settimana: notifica di scarto SdI entro oggi 05/10 · diffida 6.344,00 € entro domani 06/10 · fattura 1.830,00 € entro mercoledì 07/10
real time 1 min 22 s21 credits
Frequently asked questions
From which date does it work out deadlines?
From the certified date (daticert), never the e-mail header, and from the rule for the type of act — 60 days, August, 9 pm. For every message it says who must act: accountant, lawyer, owner or office.
What does it cost, and how long does it take?
Usually 15–31 credits per mailbox (≈ €0.62–1.28) and 1–3 minutes. It depends on how many messages and attachments: computing the deadlines is code and costs no credits. The recorded example cost 21 credits in 82 seconds.
Can it run on its own, in a flow?
Published as a page: whoever exports the mailbox (the office, the owner) uploads the messages and gets the triage; connected to a folder, every week the exported mailbox is read and the calendar updated.
Who checks what the agent did?
You do — and it takes a minute, not an afternoon. Every run is a trace: the live timeline, each tool call, each document read, the cost per step, the confidence and sources. Actions that leave the building wait for your approval. The platform never sends, never touches a live store, never moves money.
Where does my data live, and how do you handle GDPR?
Your data is stored in the EU, on one server in Germany. The EU/US data-region setting limits which models an agent can be saved with, not where your data is stored. A no-retention mode and a local runner on your own machine are available. Your plan sets how many days your data is kept — you can change it — and when they run out it is deleted automatically. You download each run's results and delete files, agents and connections in the console; an owner deletes the whole workspace and each person their own account from Settings. The “Your data” page names the services that handle your data.
Guides on this job
Related agents
- F1Supplier invoice checkAn invoice has arrived — the SdI XML, a foreign supplier's PDF, a paper one. Before you register or pay it, it tells you whether the figures add up, what is odd and what you must do: withholding, VAT to integrate, stamp duty.
- F2Bank reconciliation and open itemsTells who has really paid and what is really open, from the bank export and the management software's open items.
- F3Overdue receivables and remindersTells who is really late, with what the bank shows paid taken out, and drafts the right letter for each client with the late-payment interest to the day.
Try it on your own documents
The demo shows the recorded cases without an account; with your own workspace you run it on your files.