Alert — Customer 84521, contract GAS-F-2024-09. April 2026 bill blocked. Anomaly: tariff component QVD applied with previous quarter's value instead of the value updated on 1 April 2026 per ARERA deliberation. Difference on total: €18.40 in the customer's favour. "Comparison with Placet" disclosure absent for this variable-price offer.
AGENT · BOLLETTA VALIDATOR
The bill goes out verified on calculation and ARERA disclosure.
Bolletta Validator checks every energy or gas bill before sending: correctness of the calculation (energy components, system charges, excise duties, VAT), presence of ARERA mandatory disclosures, consistency with the customer's active contract. It blocks the send and escalates to the billing team if anomalies are found.
Bolletta Validator at work.
Correct both. Recalculate with the right QVD and add the disclosure.
Recalculation complete with Q1 2026 QVD value. "Comparison with Placet" disclosure added per the current ARERA template. Updated bill ready for the second check. Awaiting confirmation to proceed with sending.
Why it exists.
The utility bill is the most frequently received document by the retail customer and the most common point of complaint. ARERA regulates the format with strict requirements — "Bolletta 2.0" format, mandatory elements, declared formulations. Calculation errors or missing disclosures generate disputes, formal complaints to the Conciliation Service, and ARERA sanctions.
How it verifies before sending.
Bolletta Validator activates before sending. It reads the bill from the utility billing system, verifies the calculation of the applied tariff components (energy, system charges, national and regional excise duties, VAT), verifies the presence of ARERA mandatory disclosures, and checks consistency with the customer's active contract. It identifies anomalies and escalates to the technical accounting team.
The decision stays with the billing manager.
For standard bills with no anomalies, the send proceeds automatically. For identified anomalies, the bill is blocked with escalation to the billing team with the specific point highlighted. The completeness of the calculation rules against current ARERA tariffs is the responsibility of the utility's billing and compliance team.
Who it serves and where it applies.
Billing manager
Sees the systematic calculation errors that generate the most operationally costly complaint flow shrink: the wrong bill in the customer's favour that the customer doesn't notice, and the wrong bill in the utility's favour that generates a formal dispute to the Conciliation Service.
fnol.receive 09:14:22 ALLOW
triage.classify 09:14:25 ALLOW
idd.check 09:14:31 WARN
liquidation.propose 09:15:02 ALLOW
SELECT * FROM audit_log WHERE claim_id = '2024-0847'
ARERA compliance officer
Has an inspectable trace of disclosure verification for every bill sent. In the event of an ARERA audit on the quality of commercial communications, the registry is queryable with a standard SQL client.
fnol.receive 09:14:22 ALLOW
triage.classify 09:14:25 ALLOW
idd.check 09:14:31 WARN
liquidation.propose 09:15:02 ALLOW
SELECT * FROM audit_log WHERE claim_id = '2024-0847'
Customer service team
Sees the volume of bill-explanation requests arriving from calculation anomalies fall — the problem is caught before the send, not after the customer's complaint. Customer service calls go back to being about new things, not corrections after the fact.
Ongoing outage ETA 35'
Zone Northeast cluster B
Field team 3 crews · in transit
Customer SLA reset · 20'
Regulator report in preparation · 4h
A concrete example.
A gas bill enters the verification flow.
For a mid-market utility with 200,000 retail customers, the billing system generates on average 16,000 bills per month. The agent is integrated with the billing system via pre-send webhook. A gas bill for customer ID 84521 — variable-price contract — enters the verification flow. The agent analyses the calculation.
Old-quarter QVD and missing disclosure.
It detects that the tariff component QVD has been applied with the previous quarter's value instead of the updated value from the ARERA deliberation that came into effect on 1 April. The difference on the total is €18.40 in the customer's favour. It also detects the absence of the "comparison with Placet" disclosure — mandatory for variable-price offers.
The manager confirms, the bill is released.
Bill blocked and alert sent to the billing manager with the two specific points highlighted. The manager confirms the correction. The agent recalculates with the correct QVD value and adds the disclosure from the current ARERA template. Second check: all compliant. Bill released for sending. The event stays in the audit registry for ARERA compliance inspection.
Configuration and technical resources.
The Bolletta Validator rules are declarative. The utility's billing team and ARERA compliance officer define in a readable format the active tariffs per contract type, the mandatory disclosures per communication channel and offer type, the tariff component calculation rules, and anomaly thresholds. The rules live in the utility's repository, versioned, validated at agent startup.
- Language
- TypeScript (Node.js)
- LLM model
- customer's choice: Anthropic, OpenAI, Mistral, open source models hosted internally, AWS Bedrock for a private model
- Built-in controls used
- pii-detector, tool-param-validator
- Native channels
- Slack, Telegram, OpenAI-compatible HTTP
- Utility billing system integration
- dedicated adapter delivered during the project
- ARERA tariffs
- declarative, updated by the compliance team at each new deliberation
- Memory
- persistent per instance, pgvector + PostgreSQL FTS
- Registry
- immutable, ARERA audit inspectable
Frequently asked questions about the agent.
The calculation rules in the repository are updated by the billing team each time ARERA publishes new tariff values — QVD, CCR, system charges. The responsibility for timely and complete updates against the current tariff landscape stays with the billing and compliance team. The repository is versioned: every change is tracked with date and author.
Adjustment bills fall within the standard verification flow if the adjustment calculation rules are configured in the repository. The type of verification depends on the complexity of the utility's specific adjustment calculation and the document format.
The typical pattern for Bolletta Validator is 12-18 weeks. Discovery and mapping of active contract types 2-3 weeks, configuration of calculation and disclosure rules for the main types 4-6 weeks, billing system integration 4-6 weeks, real-sample validation and team hand-off 2-3 weeks.
The agent processes bills in parallel via webhook per instance. Processing capacity is sized during the project based on the monthly volume and the available processing window (e.g. all bills in a batch processed within the overnight window).
From a 30-minute conversation to the squad in production.
A 30-45 minute conversation to understand how Bolletta Validator would configure to the utility's billing structure. Which billing system, which contract types, which monthly volume.