● Public sector — Revenue office
AI agent for the revenue office
An assistant that prepares receipts, tracks collections and drafts reminders — the cashier remains solely responsible for handling the funds. The AI agent never touches the money: it prepares, tracks and flags; the cashier collects, checks and reports to the public accountant. Hosted in France, on a resource isolated for each authority.
Hosted in France
The public's data protected
GDPR & AI Act: governed deployment
The cashier alone handles the funds
Updated on
Deployed in a few weeks
Revenue office assistant · hosted in France
Prepare the receipts for the school meals and after-school club payments entered this morning.
23 receipts prepared from the entries: identity of the payer, nature of the revenue, amount and means of payment, continuous numbering for the office. One possible duplicate flagged (same family, same amount, two entries).
For you to check and issue — I never touch the funds.
⛓ Source · entries made at the office + the rates adopted
For you to check and issue — I never touch the funds.
⛓ Source · entries made at the office + the rates adopted
Give me the position on the sums still to be collected and prepare this term's reminders.
Position established: 41 debts outstanding by nature of revenue, receipts reconciled against the entries — 2 discrepancies flagged for checking. 28 draft informal reminders prepared from your templates, with amounts taken from your statements.
All submitted for your check before transmission to the public accountant.
✎ Action · statement & reminders to check — the cashier approves
All submitted for your check before transmission to the public accountant.
✎ Action · statement & reminders to check — the cashier approves
Local inference · no data outside the EU
Data hosted in France
Sovereign by designLocal inference or hosting in France
GDPR & AI Act: governed deploymentTraceability & human oversight
TurnkeyDesigned, installed and operated for you
The cashier handles the fundsThe agent prepares, it never collects
✦ In brief
In a revenue office, a Blue Lemon Agent agent assists the cashier with the repetitive tasks — preparing receipts and revenue orders, tracking collections by nature of revenue, reconciling entries, reminders and statements of outstanding sums — and prepares the schedules for the public accountant. It runs on local inference or is hosted in France on a resource isolated for each authority, architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity. The AI agent never handles the funds: collection and the cashier's personal financial liability remain theirs. Live within a few weeks. Your public-sector staff write to it from Microsoft Teams, Slack or their email, and users reach it on WhatsApp Business, the website chat or email — with no account to create and nothing to install. Reaching the administration from the tool people already have means less non-take-up of rights and equal access to the service. These connections are included in every plan, at no extra cost, within the number of connections your level includes.
100%
hosted in France in the target architecture
0
transfer outside the EU in the target architecture
7
uses ready to deploy on this scope
0
decision taken without human approval
Reference points describing our offer, not results measured at a client. The scale of the gain is confirmed by a pilot on your own scope.
The context
Why AI matters to revenue offices — and why they hesitate
School meals, after-school clubs, swimming pools, market pitch fees: the cashier collects, issues receipts, reconciles and reports to the public accountant, often on top of other duties. Their personal financial liability leaves no room for approximation.
! The issue
The revenue cashier is caught between demanding formalities — receipt books, reconciliations, schedules, statements of outstanding sums — and limited time, since the revenue office is often only part of the job. Yet most consumer AI tools amount to entrusting payers' identities, family situations and the authority's financial data to a third party, often hosted outside Europe and subject to the Cloud Act.
✓ Our answer
For a revenue office, AI is only of interest if it is sovereign, confidential and strictly bounded. Local inference or an isolated resource hosted in France, systematic human oversight, a scope limited to preparation and tracking: the AI agent never handles the funds, collects nothing and decides nothing — the cashier's liability stays whole, but relieved of the paperwork. The time won back goes to checking and to serving the public.
The decisive point
Protecting the revenue office's data: sovereignty & compliance
A revenue office handles personal and financial data: payers, means-tested rates, collections. Here is how the architecture of our agents protects it, authority by authority.
Local inference
The agent can run on a machine belonging to the authority: no data leaves the network, nothing passes through a cloud.
Hosting in France
Otherwise, a dedicated and isolated resource, hosted in France under French law — payers' data: processing and access within the European Union targeted by the architecture.
Reduced extraterritorial exposure
Architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity for payers' data: our architecture depends on a subcontracting chain and remote access documented for the configuration chosen.
One isolated resource per authority
No pooling of data: an environment strictly dedicated to your authority and its revenue offices.
Encryption & controlled access
Encryption in transit and at rest, role-based access (RBAC), strong authentication and logging.
AI Act: governed deployment
The agent is strictly in support; no collection and no handling of funds; traceability and human oversight from end to end.
What depends on the architecture chosen These points are not general guarantees: they are settled deployment by deployment, in the quotation.
- The applicable location is that of the architecture set out in the quotation and verified before commissioning.
- Local execution is announced only for the configuration explicitly described and accepted in the quotation.
- The applicable isolation depends on the deployment mode set out in the quotation; no dedicated isolation is presumed.
- The encryption mechanisms in transit and at rest, their components and key management are those documented for the architecture chosen.
- Roles and permissions are configured and accepted for the identities and systems actually connected.
- The events logged, their content, their retention period and who may access them are defined for the deployment chosen.
For the most sensitive data, SecNumCloud and HDS options are available depending on your requirements. A single architecture is designed to answer both the GDPR and extraterritorial exposure. Designed for deployment in line with the GDPR and the AI Act, after the processing, roles and context-specific risks have been assessed.
Demonstration
See the agent at work
5 real situations, taken from those that come up most often. Pick one: the exchange unfolds as it would in your organisation.
A scripted demonstration. These exchanges show how the agent behaves — its sources, its refusals, what it leaves to your teams. Nothing is sent from this page, no model is queried here, and the matters named are fictional. That is precisely what we promise your data.
The behaviours shown here — monitoring, automation rules, routing and reminders — are configured with you during deployment, from your tools, your rules and your thresholds.
The architecture points named in these exchanges — location, local execution, isolation, encryption, role-based access, logging — are not a guarantee attached to the demonstration: they are those of the architecture set out in your quotation, and verified before commissioning.
The public body in this demonstration
Fictional public bodyMunicipality of Marnoy — four revenue offices, 9,800 residents
- Sector
- Municipality of 9,800 residents — four revenue offices: school catering, after-school care, the municipal swimming pool and market pitch fees
- Headcount
- 1 appointed revenue manager and 2 deputies — the revenue office is only part of their post; the manager also staffs the town hall reception two days a week
- Public served
- 9,800 residents, 1,240 families enrolled in the canteen or after-school care, 46 market traders — 2,600 user enquiries a year
- Order of magnitude
- 18,400 payments taken a year for €412,000 — 14,900 receipts issued, 210 operating days, 12 monthly remittance slips to the public accountant, 980 amicable reminders
- Tools in place
- School billing software, card terminal, family portal and five years of archived receipt books — the agent plugs into them read-only, nothing is replaced and nothing is migrated
- Who decides
- The revenue manager alone handles the money and issues the receipts; the public accountant receives the remittance slips and checks them; the authorising officer applies the rates adopted by the council
- Room for improvement
- Preparing the receipts takes 1 h 36 out of the 2 h 40 the office consumes each day; the statement of outstanding revenue and the month's remittance slips take a whole day; 68 reconciliation discrepancies were found only at year-end close; and €39,600 remained outstanding over three financial years, 61 % of it on families that had never been sent a reminder
Fictional public body, invented for the demonstration. At Marnoy, one person runs four revenue offices on top of the town hall reception: 18,400 payments a year, 14,900 receipts, twelve remittance slips to the public accountant. The revenue manager is personally answerable for the money he handles, and it is that responsibility which rules out any approximation in the receipt book as in the reconciliation. The agent runs on local inference on a machine at the town hall, reads the billing software and five years of receipt books without ever writing to them, and touches no money. The exchanges below span a year, from the overhaul of the discrepancy causes to the review presented to the council.
This public body, its figures and the exchanges that follow were invented for the demonstration. They illustrate a common situation; they describe no real service.
Revenue office assistant · hosted in France
I reread your last five financial years over the weekend — 92,000 payments taken, 18,400 a year, across four revenue offices — and I have drawn out a finding your receipt books were carrying without anyone having the time to establish it.
A revenue office allows an officer to take certain payments directly on the municipality's behalf, and requires him to remit them to the public accountant. The revenue manager is personally answerable for the money he handles: a cash shortfall is charged to him until he is discharged of it. It is that responsibility which makes an exhaustive, traced check more protective than a spot check — and that is exactly what I bring you.
The gap measured, and it decides everything else: your five financial years carry 1,240 reconciliation discrepancies a year, and four causes alone carry 1,004 of them — 81 %.
· Payment entered against the wrong revenue office: 412 a year, almost all between canteen and after-school care, the two services the same families pay for on the same day.
· Receipt issued with no matchable invoice reference: 268.
· Apparent duplicate payment: 248.
· Gap between the receipt book total and the amount remitted to the public accountant: 76, always below €15 and always regularised — but each one cost a search.
What that costs today:
· 68 of those discrepancies were found only at the year-end close, when the original document can no longer be consulted and only the adjusting entry remains.
· Preparing a day's receipts accounts for 60 % of the office's time: 1 h 36 out of the 2 h 40 the day consumes, from the first payment to the filing of the receipt book.
· And €39,600 remained outstanding over three financial years, 61 % of it — €24,156 — on families that never received a single reminder.
What I propose, and it is not a promise — it is already done: I ran the four checks over the 18,400 payments of the past year, as a dry run. They would have found 1,004 of the 1,240 discrepancies on the day itself, against 68 discovered at the close — same work, with the original document still to hand.
The time this shifts: preparing the receipts goes from 60 % to 10 % of the operating day — from 1 h 36 to 16 minutes. Over 210 operating days a year, that is 280 hours returning to the service.
The next step, and it takes half an hour: you read the four written checks, cause by cause, with the number of discrepancies each would have found. You settle them, and they run from Monday's operating day — bringing them into service is the only act I leave to you. causes-of-discrepancy_1004-out-of-1240.pdf4 causes behind 81 % of discrepancies, each measured over the year
⛓ Sourced · 5 financial years of receipt books, 92,000 payments, reconciliation log, statements of arrears
A revenue office allows an officer to take certain payments directly on the municipality's behalf, and requires him to remit them to the public accountant. The revenue manager is personally answerable for the money he handles: a cash shortfall is charged to him until he is discharged of it. It is that responsibility which makes an exhaustive, traced check more protective than a spot check — and that is exactly what I bring you.
The gap measured, and it decides everything else: your five financial years carry 1,240 reconciliation discrepancies a year, and four causes alone carry 1,004 of them — 81 %.
· Payment entered against the wrong revenue office: 412 a year, almost all between canteen and after-school care, the two services the same families pay for on the same day.
· Receipt issued with no matchable invoice reference: 268.
· Apparent duplicate payment: 248.
· Gap between the receipt book total and the amount remitted to the public accountant: 76, always below €15 and always regularised — but each one cost a search.
What that costs today:
· 68 of those discrepancies were found only at the year-end close, when the original document can no longer be consulted and only the adjusting entry remains.
· Preparing a day's receipts accounts for 60 % of the office's time: 1 h 36 out of the 2 h 40 the day consumes, from the first payment to the filing of the receipt book.
· And €39,600 remained outstanding over three financial years, 61 % of it — €24,156 — on families that never received a single reminder.
What I propose, and it is not a promise — it is already done: I ran the four checks over the 18,400 payments of the past year, as a dry run. They would have found 1,004 of the 1,240 discrepancies on the day itself, against 68 discovered at the close — same work, with the original document still to hand.
The time this shifts: preparing the receipts goes from 60 % to 10 % of the operating day — from 1 h 36 to 16 minutes. Over 210 operating days a year, that is 280 hours returning to the service.
The next step, and it takes half an hour: you read the four written checks, cause by cause, with the number of discrepancies each would have found. You settle them, and they run from Monday's operating day — bringing them into service is the only act I leave to you. causes-of-discrepancy_1004-out-of-1240.pdf4 causes behind 81 % of discrepancies, each measured over the year
⛓ Sourced · 5 financial years of receipt books, 92,000 payments, reconciliation log, statements of arrears
I run four revenue offices and the town hall reception. I am not going to open four projects: where do we start?
With two checks, not four — and I have ranked them by the number of discrepancies they spare you, not by difficulty.
The ranking, with the count behind it:
· The allocation check: 412 discrepancies a year, that is a third of all your discrepancies on its own. It matches the payment, the enrolled child, the service used and the adopted rate. A family whose two children have lunch and go to after-school care pays the same amount twice on the same day; that is where the entry goes to the wrong office.
· The invoice-matching check: 268 discrepancies a year. A receipt with no matchable reference is a receipt that will not be found at reconciliation, and it is the one that costs an evening at month-end.
· The duplicate check: 248 discrepancies, and that is the one I suggest opening last — I will tell you why once it has proved itself.
· The remittance gap: 76 a year, all below €15 and all regularised.
These first two carry 680 of the 1,240 discrepancies: two checks out of four, 55 % of the search work. The other two can wait until the end of the first quarter without changing anything to your workload.
What I do on top, and that nobody has time for: on the allocation check, I do not merely flag the gap — I reread your 412 cases and wrote the rule that covers them all, in the form of your office instructions: the service is deduced from the child's attendance slot, not from the amount. Run over the year, it files 396 of the 412 payments correctly and sends 16 back to your check, all of them days when the child was recorded at both services.
You judge on a written and already tested rule — and you correct it in one word, since it is your own material that I have set out clearly.
The next step I propose: let the two checks run for a fortnight alongside your usual verification. You compare the two outputs line by line; if mine add nothing, they stop at a word. On the trial day already run, they found 6 discrepancies out of 94 payments, and all 6 would have been discovered at the month-end close. control-plan_two-checks-for-55-percent.pdf4 causes measured, 2 checks to open, the allocation rule written
⛓ Sourced · count of discrepancies by cause over 5 financial years, written allocation rule, trial day of 94 payments
The ranking, with the count behind it:
· The allocation check: 412 discrepancies a year, that is a third of all your discrepancies on its own. It matches the payment, the enrolled child, the service used and the adopted rate. A family whose two children have lunch and go to after-school care pays the same amount twice on the same day; that is where the entry goes to the wrong office.
· The invoice-matching check: 268 discrepancies a year. A receipt with no matchable reference is a receipt that will not be found at reconciliation, and it is the one that costs an evening at month-end.
· The duplicate check: 248 discrepancies, and that is the one I suggest opening last — I will tell you why once it has proved itself.
· The remittance gap: 76 a year, all below €15 and all regularised.
These first two carry 680 of the 1,240 discrepancies: two checks out of four, 55 % of the search work. The other two can wait until the end of the first quarter without changing anything to your workload.
What I do on top, and that nobody has time for: on the allocation check, I do not merely flag the gap — I reread your 412 cases and wrote the rule that covers them all, in the form of your office instructions: the service is deduced from the child's attendance slot, not from the amount. Run over the year, it files 396 of the 412 payments correctly and sends 16 back to your check, all of them days when the child was recorded at both services.
You judge on a written and already tested rule — and you correct it in one word, since it is your own material that I have set out clearly.
The next step I propose: let the two checks run for a fortnight alongside your usual verification. You compare the two outputs line by line; if mine add nothing, they stop at a word. On the trial day already run, they found 6 discrepancies out of 94 payments, and all 6 would have been discovered at the month-end close. control-plan_two-checks-for-55-percent.pdf4 causes measured, 2 checks to open, the allocation rule written
⛓ Sourced · count of discrepancies by cause over 5 financial years, written allocation rule, trial day of 94 payments
All of that assumes you read families' names, their means-tested bands and what they pay. Where exactly does that go?
It goes nowhere. I run on local inference on a machine at the town hall, and nothing I read leaves the municipality's network.
Local inference means the model computes on your own machine: a family's name or their means-tested band crosses no external network to be processed. If the municipality would rather not host a machine, the other route is an isolated resource hosted in France, dedicated to Marnoy — no pooling with another authority, which is the condition for the continuity of your revenue offices.
What that changes, point by point:
· Family data trains no model, neither ours nor a third party's.
· I work read-only, and the technical account I read through has no right to write — neither in the receipt book nor in the billing software. This is not a promise, it is a permission that can be checked with one command.
· Encryption in transit and at rest, role-based access — rights follow the job: a deputy opens the office he runs, not the other three. 3 roles for your 3 authorised staff, and the log shows 0 out-of-role accesses since go-live.
· Hosting in France, under French law, architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity.
And the point that decides, for someone personally answerable for his own cash: I never touch the money, and I have no technical means of doing so. Taking the payment, issuing the receipt and remitting to the public accountant are your acts, and they stay yours — I prepare them, I reconcile them and I trace them. What that brings you is not lighter responsibility, it is what makes it bearable: an exhaustive, dated and enforceable check across all 18,400 payments, instead of a spot check made at the end of the day. The day the public accountant or the regional audit chamber asks how you ensure that the totals agree, you produce the log, not your good faith.
The figure that sums all this up: 0 family data out of the municipality's network across the 18,400 payments of the year, and processing in the EU targeted.
What I propose: that I keep up to date the record your data protection officer and your public accountant will both ask for — hosting, data processed, retention periods, who accesses what, and the exact permissions of the technical account. It is asked for once a year and takes two days to rebuild; the first version is written and you have it attached. technical-framework_where-revenue-office-data-lives.pdfLocal inference, read-only, no access to the money
✎ Framework · deployment architecture, technical account permissions, access log, first version of the processing record
Local inference means the model computes on your own machine: a family's name or their means-tested band crosses no external network to be processed. If the municipality would rather not host a machine, the other route is an isolated resource hosted in France, dedicated to Marnoy — no pooling with another authority, which is the condition for the continuity of your revenue offices.
What that changes, point by point:
· Family data trains no model, neither ours nor a third party's.
· I work read-only, and the technical account I read through has no right to write — neither in the receipt book nor in the billing software. This is not a promise, it is a permission that can be checked with one command.
· Encryption in transit and at rest, role-based access — rights follow the job: a deputy opens the office he runs, not the other three. 3 roles for your 3 authorised staff, and the log shows 0 out-of-role accesses since go-live.
· Hosting in France, under French law, architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity.
And the point that decides, for someone personally answerable for his own cash: I never touch the money, and I have no technical means of doing so. Taking the payment, issuing the receipt and remitting to the public accountant are your acts, and they stay yours — I prepare them, I reconcile them and I trace them. What that brings you is not lighter responsibility, it is what makes it bearable: an exhaustive, dated and enforceable check across all 18,400 payments, instead of a spot check made at the end of the day. The day the public accountant or the regional audit chamber asks how you ensure that the totals agree, you produce the log, not your good faith.
The figure that sums all this up: 0 family data out of the municipality's network across the 18,400 payments of the year, and processing in the EU targeted.
What I propose: that I keep up to date the record your data protection officer and your public accountant will both ask for — hosting, data processed, retention periods, who accesses what, and the exact permissions of the technical account. It is asked for once a year and takes two days to rebuild; the first version is written and you have it attached. technical-framework_where-revenue-office-data-lives.pdfLocal inference, read-only, no access to the money
✎ Framework · deployment architecture, technical account permissions, access log, first version of the processing record
Here is yesterday: canteen and after-school care, 94 payments. I need the receipts, and I do not have two hours.
All 94 receipts are prepared, numbered in the sequence of your receipt book, and 6 of them come back with the check I am asking you to make before issuing them.
What each receipt carries, taken from your own material and nothing else: the payer's identity, the nature of the revenue and the service used, the period, the amount and the adopted rate that establishes it, the means of payment, and the number, in the continuous sequence of the office concerned.
Continuous numbering is what makes a receipt book verifiable: a missing receipt shows up immediately, and it is the first thing an audit looks at. Across your five financial years I found 4 breaks in the numbering, all in 2022, all explained by a book started twice during a stand-in period. All four are documented and the explanatory note is written, ready to attach to your next audit.
The 6 receipts to check, and why:
· 4 payments where the child was recorded at both the canteen and after-school care on the same day — the allocation rule you settled files them, but it shows them to you, because they are the only ones where two identical amounts follow each other.
· 1 payment whose amount matches no adopted rate: €2.90 for a meal charged at €3.10 at this family's band. The gap is €0.20 and it comes from a rate applied before the September resolution.
· 1 cheque whose drawer differs from the payer on record — that is perfectly regular, but the mention must appear in the receipt book, and I have entered it.
The time this shifts: preparing the receipts goes from 60 % to 10 % of the operating day — from 1 h 36 to 16 minutes. Over 210 days a year, that is 280 hours returned to the service. And what remains inside those 16 minutes is your reading of the 6: the only work where you engage your own responsibility.
The next step: the other 88 are ready to issue as soon as you have checked them, and I propose that the €0.20 gap goes to the schools department with the reminder of the rate in force — it is written, and over the past year the same gap occurred 34 times for €6.80 in total. It is not the sum that matters, it is that a rate that has not been adopted must never be collected. operating-day_94-receipts-prepared.pdf88 ready to issue, 6 to check, continuous numbering
⛓ Sourced · operating day of 94 payments, canteen and after-school attendance records, adopted rates, receipt books of the 5 financial years
What each receipt carries, taken from your own material and nothing else: the payer's identity, the nature of the revenue and the service used, the period, the amount and the adopted rate that establishes it, the means of payment, and the number, in the continuous sequence of the office concerned.
Continuous numbering is what makes a receipt book verifiable: a missing receipt shows up immediately, and it is the first thing an audit looks at. Across your five financial years I found 4 breaks in the numbering, all in 2022, all explained by a book started twice during a stand-in period. All four are documented and the explanatory note is written, ready to attach to your next audit.
The 6 receipts to check, and why:
· 4 payments where the child was recorded at both the canteen and after-school care on the same day — the allocation rule you settled files them, but it shows them to you, because they are the only ones where two identical amounts follow each other.
· 1 payment whose amount matches no adopted rate: €2.90 for a meal charged at €3.10 at this family's band. The gap is €0.20 and it comes from a rate applied before the September resolution.
· 1 cheque whose drawer differs from the payer on record — that is perfectly regular, but the mention must appear in the receipt book, and I have entered it.
The time this shifts: preparing the receipts goes from 60 % to 10 % of the operating day — from 1 h 36 to 16 minutes. Over 210 days a year, that is 280 hours returned to the service. And what remains inside those 16 minutes is your reading of the 6: the only work where you engage your own responsibility.
The next step: the other 88 are ready to issue as soon as you have checked them, and I propose that the €0.20 gap goes to the schools department with the reminder of the rate in force — it is written, and over the past year the same gap occurred 34 times for €6.80 in total. It is not the sum that matters, it is that a rate that has not been adopted must never be collected. operating-day_94-receipts-prepared.pdf88 ready to issue, 6 to check, continuous numbering
⛓ Sourced · operating day of 94 payments, canteen and after-school attendance records, adopted rates, receipt books of the 5 financial years
The receipt book, precisely. It is the first thing they ask for in an audit, and it is what I keep least well for lack of time.
It is up to date this morning, across all four offices, and it is verifiable line by line — that is what protects you, and it is what I can return to you fastest.
What the receipt book now carries for each payment: the continuous number, the date, the payer, the nature of the revenue, the period, the amount and the adopted rate that founds it, with the date of the resolution, the means of payment, and the match with the family portal invoice.
What the record-keeping check found across the five financial years:
· 4 breaks in the numbering, all in 2022, all documented.
· 268 receipts with no matchable invoice reference — that is the cause that costs an evening at month-end, and 212 of the 268 could be matched afterwards from the attendance record and the amount. The remaining 56 are listed, with whatever I could recover on each.
· 0 missing receipts across 74,500 numbers — and that is the figure you will be able to produce.
What I do on top, and that nobody has time for: I wrote the record-keeping note for your four offices — what is collected, on what rate basis, under which numbering, with which supporting document —, in the form of your internal instructions. It existed only in your head, and it is exactly what a deputy looks for the day he stands in for you.
The revenue manager alone issues the receipt, and that is what makes it enforceable against the payer — and it is handed to you ready, numbered and matched, in sixteen minutes for a whole day.
The next step I propose: that the day's receipt book be handed to you each evening on one page, with the matches done and the discrepancies at the top. Over the trial quarter it brought unmatched receipts down from 67 to 4 a month — and the 4 are matched the next day, while the family can still be reached. receipt-book_record-keeping-of-the-four-offices.pdf0 missing receipt out of 74,500, 212 matches recovered
⛓ Sourced · receipt books of the 4 offices over 5 financial years, family portal, rate resolutions, record-keeping note drafted
What the receipt book now carries for each payment: the continuous number, the date, the payer, the nature of the revenue, the period, the amount and the adopted rate that founds it, with the date of the resolution, the means of payment, and the match with the family portal invoice.
What the record-keeping check found across the five financial years:
· 4 breaks in the numbering, all in 2022, all documented.
· 268 receipts with no matchable invoice reference — that is the cause that costs an evening at month-end, and 212 of the 268 could be matched afterwards from the attendance record and the amount. The remaining 56 are listed, with whatever I could recover on each.
· 0 missing receipts across 74,500 numbers — and that is the figure you will be able to produce.
What I do on top, and that nobody has time for: I wrote the record-keeping note for your four offices — what is collected, on what rate basis, under which numbering, with which supporting document —, in the form of your internal instructions. It existed only in your head, and it is exactly what a deputy looks for the day he stands in for you.
The revenue manager alone issues the receipt, and that is what makes it enforceable against the payer — and it is handed to you ready, numbered and matched, in sixteen minutes for a whole day.
The next step I propose: that the day's receipt book be handed to you each evening on one page, with the matches done and the discrepancies at the top. Over the trial quarter it brought unmatched receipts down from 67 to 4 a month — and the 4 are matched the next day, while the family can still be reached. receipt-book_record-keeping-of-the-four-offices.pdf0 missing receipt out of 74,500, 212 matches recovered
⛓ Sourced · receipt books of the 4 offices over 5 financial years, family portal, rate resolutions, record-keeping note drafted
And the cash? In the evening I count, and if it does not add up, I pay. That is what keeps me awake at night.
The expected total is calculated before you count, means of payment by means of payment — and any gap shows up on one line instead of being hunted for an hour.
What I hand you when the office closes:
· The expected cash total, the expected cheque total with the list of drawers, and the expected card total, matched against the card terminal slip.
· The opening float, carried over from the previous day, so that the calculation can be redone without me.
· And, when a gap appears, the day's payments ranked by likelihood: those whose amount is close to the gap, those entered in the minute before or after, those whose means of payment was corrected. Across the 76 remittance gaps of the five financial years, that list pointed to the right line 68 times.
What that changes in practice: hunting a cash gap took between 20 minutes and an hour, and sometimes ended with no explanation. Over the trial quarter, 9 gaps, 9 explained the same evening, none carried over to the next day. All 9 were below €15, and 7 came from a means of payment entered instead of another.
What that gives you back, and it is the real subject: a cash shortfall is charged to you until you are discharged of it — and what protects you is not caution, it is the record. Every gap now carries its date, its amount, the line that explains it and the correction made; every remittance to the public accountant carries the receipt book total against the amount remitted. It is a discharge file that builds itself, day after day, instead of being reconstructed under pressure.
The next step I propose: that the closing statement be archived automatically with the day's receipt book and the terminal slip, in the same dated folder. That is the trio you will be asked for, and today it only comes together by hand. Say yes and it is in place this evening. cash-closing_expected-totals-and-gaps.pdf9 gaps explained the same evening, discharge file built as it goes
⛓ Sourced · receipt books, card terminal slips, log of remittance gaps over 5 financial years
What I hand you when the office closes:
· The expected cash total, the expected cheque total with the list of drawers, and the expected card total, matched against the card terminal slip.
· The opening float, carried over from the previous day, so that the calculation can be redone without me.
· And, when a gap appears, the day's payments ranked by likelihood: those whose amount is close to the gap, those entered in the minute before or after, those whose means of payment was corrected. Across the 76 remittance gaps of the five financial years, that list pointed to the right line 68 times.
What that changes in practice: hunting a cash gap took between 20 minutes and an hour, and sometimes ended with no explanation. Over the trial quarter, 9 gaps, 9 explained the same evening, none carried over to the next day. All 9 were below €15, and 7 came from a means of payment entered instead of another.
What that gives you back, and it is the real subject: a cash shortfall is charged to you until you are discharged of it — and what protects you is not caution, it is the record. Every gap now carries its date, its amount, the line that explains it and the correction made; every remittance to the public accountant carries the receipt book total against the amount remitted. It is a discharge file that builds itself, day after day, instead of being reconstructed under pressure.
The next step I propose: that the closing statement be archived automatically with the day's receipt book and the terminal slip, in the same dated folder. That is the trio you will be asked for, and today it only comes together by hand. Say yes and it is in place this evening. cash-closing_expected-totals-and-gaps.pdf9 gaps explained the same evening, discharge file built as it goes
⛓ Sourced · receipt books, card terminal slips, log of remittance gaps over 5 financial years
The month-end reconciliation is my bugbear. I find discrepancies born three weeks earlier and I no longer know where they come from.
I find the discrepancies on the day they are born: 1,240 over the year, of which 1,172 flagged within twenty-four hours.
Why that changes everything: a discrepancy found the same day is corrected by the original document — the attendance record, the invoice, the terminal slip; the same discrepancy found three weeks later is corrected by an adjusting entry. That is neither the same quality of record, nor the same time.
The four families I raise, counted over the year:
· Payment entered against the wrong revenue office: 412 — the allocation rule now files 396 of them automatically and shows you 16.
· Receipt with no matchable invoice reference: 268, down to 4 a month since the evening reconciliation.
· Apparent duplicate payment: 248.
· Gap between the receipt book total and the amount remitted: 76, all below €15.
What that gives at the close: 68 discrepancies used to be found only at the close; over the trial quarter, not one remains. All 236 discrepancies of the quarter were dealt with in the month they were born.
And the reconciliation itself, total by total: the receipt book total, the total taken by means of payment, the card terminal slip, the family portal transfers and the amount remitted to the public accountant — five totals that must agree, reconciled every evening instead of once a month.
The next step I propose: a discrepancy statement on the first working day of each month, by revenue office, with the age of each and the document that explains it. It is written and you have it; just tell me whether it also goes to the schools department for allocation gaps, or to you alone. reconciliation_five-totals-that-must-agree.pdf1,172 discrepancies flagged within 24 h, 68 close-time discoveries down to 0
⛓ Sourced · receipt books of the 4 offices, terminal slips, family portal transfers, reconciliation log
Why that changes everything: a discrepancy found the same day is corrected by the original document — the attendance record, the invoice, the terminal slip; the same discrepancy found three weeks later is corrected by an adjusting entry. That is neither the same quality of record, nor the same time.
The four families I raise, counted over the year:
· Payment entered against the wrong revenue office: 412 — the allocation rule now files 396 of them automatically and shows you 16.
· Receipt with no matchable invoice reference: 268, down to 4 a month since the evening reconciliation.
· Apparent duplicate payment: 248.
· Gap between the receipt book total and the amount remitted: 76, all below €15.
What that gives at the close: 68 discrepancies used to be found only at the close; over the trial quarter, not one remains. All 236 discrepancies of the quarter were dealt with in the month they were born.
And the reconciliation itself, total by total: the receipt book total, the total taken by means of payment, the card terminal slip, the family portal transfers and the amount remitted to the public accountant — five totals that must agree, reconciled every evening instead of once a month.
The next step I propose: a discrepancy statement on the first working day of each month, by revenue office, with the age of each and the document that explains it. It is written and you have it; just tell me whether it also goes to the schools department for allocation gaps, or to you alone. reconciliation_five-totals-that-must-agree.pdf1,172 discrepancies flagged within 24 h, 68 close-time discoveries down to 0
⛓ Sourced · receipt books of the 4 offices, terminal slips, family portal transfers, reconciliation log
You still sent me a lot of alerts for nothing in the first quarter. Every check is time I do not have — and sometimes a family called back for nothing.
You are right to say so, and I publish it with the rest: of the 320 discrepancies flagged in the first quarter, 74 turned out to be groundless after checking — 23.1 %. That is the figure that does not flatter me, and it is better that it comes from me than from a family annoyed at being called back.
The real cause, measured and not assumed: 56 of the 74 came from the duplicate check alone, which matched the family and the amount without reading the service or the attendance slot. Now a family with two children legitimately pays the same amount twice on the same day — once for the canteen, once for after-school care — and since your rates for those two services are identical at the first band, the two payments looked exactly alike. It was not a reading error: it was a criterion that was too short.
What I did about it, and it is already written: I rewrote the criterion — the match now covers the family, the amount, the service used, the attendance slot and the invoice reference — and I ran it again over the last twelve months so that you judge on figures and not on an intention.
· 96 duplicate alerts instead of 428.
· The 37 duplicates actually confirmed over the year: all 37 kept. Not one escapes the tightened criterion, and that is the one point on which I would not compromise — an undetected double payment means a family paying twice.
· 332 checks you no longer have to make, and 332 families no longer called back for nothing.
The following quarter, once the criterion was in force: 305 discrepancies flagged, 17 groundless — 5.6 %. And the 17 are one-off cases, not one of them is a family with two children.
What I now propose: settle the tightened criterion in one word and it runs from this evening's session. Bringing a check into force stays your decision — and that is what makes it enforceable against the schools department as against the public accountant; I hand it to you as a single signature, on a rule already written and already measured over twelve months. duplicate-criterion_428-alerts-down-to-96.pdf23.1 % → 5.6 %, cause measured, all 37 real duplicates kept
⛓ Sourced · discrepancy log over two quarters, 12 months replayed with the tightened criterion, attendance records and adopted rates
The real cause, measured and not assumed: 56 of the 74 came from the duplicate check alone, which matched the family and the amount without reading the service or the attendance slot. Now a family with two children legitimately pays the same amount twice on the same day — once for the canteen, once for after-school care — and since your rates for those two services are identical at the first band, the two payments looked exactly alike. It was not a reading error: it was a criterion that was too short.
What I did about it, and it is already written: I rewrote the criterion — the match now covers the family, the amount, the service used, the attendance slot and the invoice reference — and I ran it again over the last twelve months so that you judge on figures and not on an intention.
· 96 duplicate alerts instead of 428.
· The 37 duplicates actually confirmed over the year: all 37 kept. Not one escapes the tightened criterion, and that is the one point on which I would not compromise — an undetected double payment means a family paying twice.
· 332 checks you no longer have to make, and 332 families no longer called back for nothing.
The following quarter, once the criterion was in force: 305 discrepancies flagged, 17 groundless — 5.6 %. And the 17 are one-off cases, not one of them is a family with two children.
What I now propose: settle the tightened criterion in one word and it runs from this evening's session. Bringing a check into force stays your decision — and that is what makes it enforceable against the schools department as against the public accountant; I hand it to you as a single signature, on a rule already written and already measured over twelve months. duplicate-criterion_428-alerts-down-to-96.pdf23.1 % → 5.6 %, cause measured, all 37 real duplicates kept
⛓ Sourced · discrepancy log over two quarters, 12 months replayed with the tightened criterion, attendance records and adopted rates
That leaves the worst of it: the statement of outstanding revenue and the month's remittance slips. A whole day, and I take it out of a Saturday.
The slip and the statement are ready on the first working day of the month, and all that is left for you is to check and sign them: 1 h 24 instead of a whole day.
What the remittance slip to the public accountant carries, office by office: the total revenue taken, by nature and by means of payment, the match with the receipt book and with the terminal slip, the supporting documents in the order the accountant expects them, and the month's discrepancies with, for each, the document that explains it and the correction made.
What the statement of outstanding revenue carries: unsettled receivables by age, by nature of revenue and by amount, and for each the last reminder sent and its date. That last column did not exist, and it is the one that changed everything: of the €39,600 outstanding, €24,156 — 61 % — concerned families that had never received a single reminder.
The time this shifts: the statement of arrears and the month's remittance slips took a whole day; 20 % of it remains, that is 1 h 24. Over 12 months, that is 67 hours returned to the service — and twelve Saturdays that become Saturdays again.
What I raise without being asked: 34 receivables from the swimming pool office, for €1,870, relate to financial years closed more than four years ago. They are sorted, measured and documented, and the presentation file is written — writing them off is for the council to decide on the public accountant's proposal, and I hand you the complete file rather than a line in a table.
The next step I propose: that the remittance slip go to the public accountant electronically, with its documents in order, as soon as you sign it. Over the trial quarter the accountant asked for no further document, against 7 requests in the same quarter last year — and each of those 7 requests cost half a day of searching. remittance-slips-and-arrears_a-day-down-to-1h24.pdf€39,600 outstanding of which 61 % never chased, 0 further document requested
⛓ Sourced · receipt books, terminal slips, statements of arrears over 3 financial years, exchanges with the public accountant
What the remittance slip to the public accountant carries, office by office: the total revenue taken, by nature and by means of payment, the match with the receipt book and with the terminal slip, the supporting documents in the order the accountant expects them, and the month's discrepancies with, for each, the document that explains it and the correction made.
What the statement of outstanding revenue carries: unsettled receivables by age, by nature of revenue and by amount, and for each the last reminder sent and its date. That last column did not exist, and it is the one that changed everything: of the €39,600 outstanding, €24,156 — 61 % — concerned families that had never received a single reminder.
The time this shifts: the statement of arrears and the month's remittance slips took a whole day; 20 % of it remains, that is 1 h 24. Over 12 months, that is 67 hours returned to the service — and twelve Saturdays that become Saturdays again.
What I raise without being asked: 34 receivables from the swimming pool office, for €1,870, relate to financial years closed more than four years ago. They are sorted, measured and documented, and the presentation file is written — writing them off is for the council to decide on the public accountant's proposal, and I hand you the complete file rather than a line in a table.
The next step I propose: that the remittance slip go to the public accountant electronically, with its documents in order, as soon as you sign it. Over the trial quarter the accountant asked for no further document, against 7 requests in the same quarter last year — and each of those 7 requests cost half a day of searching. remittance-slips-and-arrears_a-day-down-to-1h24.pdf€39,600 outstanding of which 61 % never chased, 0 further document requested
⛓ Sourced · receipt books, terminal slips, statements of arrears over 3 financial years, exchanges with the public accountant
The €24,156 never chased is what bothers me most. But I will not sign a blank cheque for letters to go out to families on their own.
You do not have to choose between the two: I propose a written mandate, capped, dated and withdrawable in one word — and it is already drafted.
What the statement shows first, because that is what decides: 1,480 unsettled receivables, €39,600 over three financial years, of which €24,156 — 61 % — on families never sent a reminder. And half of that sum, €12,340, sits on 214 receivables below €90: amounts a family settles without difficulty when told, and which become a dispute when you wait three years.
What the mandate authorises, and it fits in six lines:
· Scope: first-stage amicable reminders, on receivables below €150, and nothing else. Any receivable above that, any second reminder, any family supported by the municipal social action centre: the letter is handed to you written, and you send it.
· No decision on the receivable itself: no waiver, no write-off, no instalment plan granted. All three belong to the council or to the public accountant depending on the case, and for each I hand you the measured, documented file ready to present.
· And I touch no money: the reminder carries the online payment route and the number to call; taking the payment stays your act, or the portal's.
· Every reminder carries the nature of the revenue, the period, the amount, the adopted rate that founds it and the number to call to contest it.
· You receive every morning the statement of the reminders sent the day before, on one page. A reminder sent in error is put right in an hour, not in three weeks.
· Duration: review at three months. Without an explicit decision at the review, the mandate stops — renewal takes a signature, stopping does not. Withdrawal: one word from you, and sending stops within the minute.
And the argument worth most before your council: today a family is chased if the week allows it; tomorrow it is chased according to the age of its debt, under the same rule for all. That is equal treatment between users, and it can be proved: the log states who was chased, when, and for how much.
The time this shifts: preparing an amicable reminder goes from 40 % to 10 % of the time it takes to handle an overdue receivable — from 12 minutes to 3. Over 980 reminders a year, that is 147 hours returned to the service.
What it gave over the trial quarter, with each draft approved one by one: 386 reminders prepared, €9,840 collected, and 22 families who called to ask for instalments — the 22 files were handed to you measured within four hours.
The next step: sign the mandate and the first wave goes out tomorrow morning; the review is already in your diary on the 15th of the third month. amicable-reminder-mandate_capped-and-dated.pdf€24,156 never chased, €12,340 on 214 receivables below €90
✎ Framework · statements of arrears over 3 financial years, drafted mandate, trial quarter log, 386 reminders prepared
What the statement shows first, because that is what decides: 1,480 unsettled receivables, €39,600 over three financial years, of which €24,156 — 61 % — on families never sent a reminder. And half of that sum, €12,340, sits on 214 receivables below €90: amounts a family settles without difficulty when told, and which become a dispute when you wait three years.
What the mandate authorises, and it fits in six lines:
· Scope: first-stage amicable reminders, on receivables below €150, and nothing else. Any receivable above that, any second reminder, any family supported by the municipal social action centre: the letter is handed to you written, and you send it.
· No decision on the receivable itself: no waiver, no write-off, no instalment plan granted. All three belong to the council or to the public accountant depending on the case, and for each I hand you the measured, documented file ready to present.
· And I touch no money: the reminder carries the online payment route and the number to call; taking the payment stays your act, or the portal's.
· Every reminder carries the nature of the revenue, the period, the amount, the adopted rate that founds it and the number to call to contest it.
· You receive every morning the statement of the reminders sent the day before, on one page. A reminder sent in error is put right in an hour, not in three weeks.
· Duration: review at three months. Without an explicit decision at the review, the mandate stops — renewal takes a signature, stopping does not. Withdrawal: one word from you, and sending stops within the minute.
And the argument worth most before your council: today a family is chased if the week allows it; tomorrow it is chased according to the age of its debt, under the same rule for all. That is equal treatment between users, and it can be proved: the log states who was chased, when, and for how much.
The time this shifts: preparing an amicable reminder goes from 40 % to 10 % of the time it takes to handle an overdue receivable — from 12 minutes to 3. Over 980 reminders a year, that is 147 hours returned to the service.
What it gave over the trial quarter, with each draft approved one by one: 386 reminders prepared, €9,840 collected, and 22 families who called to ask for instalments — the 22 files were handed to you measured within four hours.
The next step: sign the mandate and the first wave goes out tomorrow morning; the review is already in your diary on the 15th of the third month. amicable-reminder-mandate_capped-and-dated.pdf€24,156 never chased, €12,340 on 214 receivables below €90
✎ Framework · statements of arrears over 3 financial years, drafted mandate, trial quarter log, 386 reminders prepared
Many families still pay in cash at the counter, and that means cash for me to hold. How do we move them to online payment without leaving anyone behind?
By walking them through it once, not by closing the counter — and the result can be measured: 1,240 families, 41 % paid online in the first quarter, 68 % in the third.
What I did, and it costs the office no extra hour:
· I identified the 412 families that paid exclusively at the counter, and I looked at what they had in common: 286 had never activated their family portal account, and 94 had activated it then abandoned at the means-of-payment screen.
· For the 286, the activation letter is written, with the three pieces of information to have to hand before starting — that is the most frequent point of abandonment: the person starts, a login is missing, they close the window and never come back.
· For the 94, I recorded the exact screen where they stopped: 78 on the same one, the means-of-payment screen, whose wording does not say that cards are accepted. The fault report is written for your provider, with the page, the current wording and the proposed wording.
What I supported at the counter over the quarter: 96 families, screen by screen, with the list of documents to prepare before starting. 84 went through to the end. And on a family's account, it is always the family that enters its login and validates: their credentials are never entrusted to me and do not have to be — it is that click which makes the payment theirs.
What it gives you back, and it is what counts for a revenue office: cash payments fell from 6,200 to 2,900 over the year — half as much cash to count, half as much to carry, and that much less of what you are personally answerable for.
And those who will never go online, because they exist: the counter stays open at the same hours, and I do not touch it. Of the 412 families, 118 go on paying at the counter and that is entirely right — they are the ones for whom coming to the town hall is also the only moment when someone asks how they are.
The next step I propose: that the fault report go to the portal provider this week. Seventy-eight families blocked by a label is the cheapest gain in this whole demonstration: it costs one e-mail. online-payment_412-families-supported.pdf41 % → 68 % paying online, cash payments halved
⛓ Sourced · family portal, log of logins and abandonments, means of payment over 3 quarters
What I did, and it costs the office no extra hour:
· I identified the 412 families that paid exclusively at the counter, and I looked at what they had in common: 286 had never activated their family portal account, and 94 had activated it then abandoned at the means-of-payment screen.
· For the 286, the activation letter is written, with the three pieces of information to have to hand before starting — that is the most frequent point of abandonment: the person starts, a login is missing, they close the window and never come back.
· For the 94, I recorded the exact screen where they stopped: 78 on the same one, the means-of-payment screen, whose wording does not say that cards are accepted. The fault report is written for your provider, with the page, the current wording and the proposed wording.
What I supported at the counter over the quarter: 96 families, screen by screen, with the list of documents to prepare before starting. 84 went through to the end. And on a family's account, it is always the family that enters its login and validates: their credentials are never entrusted to me and do not have to be — it is that click which makes the payment theirs.
What it gives you back, and it is what counts for a revenue office: cash payments fell from 6,200 to 2,900 over the year — half as much cash to count, half as much to carry, and that much less of what you are personally answerable for.
And those who will never go online, because they exist: the counter stays open at the same hours, and I do not touch it. Of the 412 families, 118 go on paying at the counter and that is entirely right — they are the ones for whom coming to the town hall is also the only moment when someone asks how they are.
The next step I propose: that the fault report go to the portal provider this week. Seventy-eight families blocked by a label is the cheapest gain in this whole demonstration: it costs one e-mail. online-payment_412-families-supported.pdf41 % → 68 % paying online, cash payments halved
⛓ Sourced · family portal, log of logins and abandonments, means of payment over 3 quarters
That leaves the telephone. “How much do I owe?”, “I paid and I am getting a reminder”: it cuts every operating day into pieces.
2,600 enquiries last year, and nine subjects carry 1,940 of them — the nine answers are written, sourced and waiting for you.
What the count shows: “how much do I owe?” weighs 680 calls and e-mails, “I paid, why this reminder?” 412, “what is my rate?” 336, “how do I pay online?” 248. The other five subjects share 264 enquiries.
What I answer, and where I take it from: the actual state of the family's account — amounts due by period and by service, payments recorded with their dates, and the adopted rate that founds each amount, with the date of the resolution. A family that understands where its rate comes from disputes it ten times less than a family that is simply given a figure.
I state from the first sentence that I am a digital assistant of Marnoy town hall, not a member of staff, and the caller can ask for a person at any time: I then take their number and leave you a dated call-back. This is not an option that can be switched off: the European regulation on artificial intelligence requires that anyone interacting with an AI system be informed.
What goes to the right counter rather than receiving an approximate answer: a challenge to a rate belongs to the council's resolution and the schools department handles it; a request for financial support belongs to the municipal social action centre; a question about a revenue order already transmitted belongs to the public accountant. In all three cases the family leaves with the competent service, its contact details and the time to expect — never with an estimate given in the municipality's name.
What it gives you back, in practice: 1,940 enquiries handled at any hour, including on your two reception days at the town hall — and over the trial quarter, 58 % of calls on those nine subjects came in outside the revenue office's opening hours. The 660 that remain reach you with the family's account already open and the subject noted.
The next step I propose: that your nine answers be read one by one tomorrow — twenty minutes. As soon as they are approved, the switchboard answers that very night, and I hand you every morning the page of what went out. answers-to-users_2600-enquiries-9-subjects.pdf1,940 enquiries on 9 subjects, 9 answers already written
⛓ Sourced · switchboard and revenue office inbox log over 12 months, family accounts, rate resolutions, 9 written answers
What the count shows: “how much do I owe?” weighs 680 calls and e-mails, “I paid, why this reminder?” 412, “what is my rate?” 336, “how do I pay online?” 248. The other five subjects share 264 enquiries.
What I answer, and where I take it from: the actual state of the family's account — amounts due by period and by service, payments recorded with their dates, and the adopted rate that founds each amount, with the date of the resolution. A family that understands where its rate comes from disputes it ten times less than a family that is simply given a figure.
I state from the first sentence that I am a digital assistant of Marnoy town hall, not a member of staff, and the caller can ask for a person at any time: I then take their number and leave you a dated call-back. This is not an option that can be switched off: the European regulation on artificial intelligence requires that anyone interacting with an AI system be informed.
What goes to the right counter rather than receiving an approximate answer: a challenge to a rate belongs to the council's resolution and the schools department handles it; a request for financial support belongs to the municipal social action centre; a question about a revenue order already transmitted belongs to the public accountant. In all three cases the family leaves with the competent service, its contact details and the time to expect — never with an estimate given in the municipality's name.
What it gives you back, in practice: 1,940 enquiries handled at any hour, including on your two reception days at the town hall — and over the trial quarter, 58 % of calls on those nine subjects came in outside the revenue office's opening hours. The 660 that remain reach you with the family's account already open and the subject noted.
The next step I propose: that your nine answers be read one by one tomorrow — twenty minutes. As soon as they are approved, the switchboard answers that very night, and I hand you every morning the page of what went out. answers-to-users_2600-enquiries-9-subjects.pdf1,940 enquiries on 9 subjects, 9 answers already written
⛓ Sourced · switchboard and revenue office inbox log over 12 months, family accounts, rate resolutions, 9 written answers
The council will ask what this has given us after a year. I need a figure I can defend before elected members.
494 hours of staff time returned to the service over the year — fourteen weeks of one full-time officer's work — and the calculation is yours, it fits in three lines.
The calculation, item by item, so the council can redo it:
· Preparing a day's receipts: 210 operating days, 1 h 36 down to 16 minutes — 60 % → 10 % of the day's time — that is 280 hours.
· Amicable reminder to a user: 980 reminders, 12 minutes down to 3 — 40 % → 10 % — that is 147 hours.
· Statement of arrears and the month's remittance slips: 12 months, a whole day down to 1 h 24 — 100 % → 20 % — that is 67 hours.
What these hours are, and it is what stands up best before elected members: staff time returned to the service, at identical headcount — no post abolished, no post created. This is not a budget saving and it must on no account be presented as one: it is one revenue manager running four offices and the town hall reception within the time he actually has, and checking instead of re-keying.
What these hours produced, according to your own logs:
· Discrepancies discovered only at the close: 68 → 0, and 1,172 of the 1,240 discrepancies flagged within twenty-four hours.
· Receipts with no matchable reference: 67 a month → 4, and 0 missing receipts across 74,500 numbers.
· Cash gaps explained the same evening: 9 out of 9, against a search of 20 minutes to an hour before, sometimes with no explanation.
· Arrears: €9,840 collected over the trial quarter, and €24,156 that had never been chased are now followed up, under the same rule for every family.
· Online payment: 41 % → 68 %, and cash payments halved, from 6,200 to 2,900.
· And the public accountant asked for no further document over the quarter, against 7 in the same quarter last year.
The figure that does not flatter me, published with the rest: 74 groundless discrepancies out of 320 in the first quarter — 23.1 %, down to 17 out of 305 — 5.6 % once the duplicate criterion was tightened.
And the framework measure: 0 money touched by the agent, 0 receipts issued without the revenue manager, 0 family data out of the municipality, across 18,400 traced payments.
What I propose for the meeting: the calculation page is written and fits on one side — three lines of calculation, six results, three framework measures. Send it out to councillors with the convening notice: a figure read the day before is discussed better than a figure discovered in the meeting. year-review_494-hours-returned-to-the-service.pdf60→10, 40→10, 100→20, and the calculation redoable on one page
⛓ Sourced · receipt books, discrepancy log, statements of arrears, family portal, exchanges with the public accountant
The calculation, item by item, so the council can redo it:
· Preparing a day's receipts: 210 operating days, 1 h 36 down to 16 minutes — 60 % → 10 % of the day's time — that is 280 hours.
· Amicable reminder to a user: 980 reminders, 12 minutes down to 3 — 40 % → 10 % — that is 147 hours.
· Statement of arrears and the month's remittance slips: 12 months, a whole day down to 1 h 24 — 100 % → 20 % — that is 67 hours.
What these hours are, and it is what stands up best before elected members: staff time returned to the service, at identical headcount — no post abolished, no post created. This is not a budget saving and it must on no account be presented as one: it is one revenue manager running four offices and the town hall reception within the time he actually has, and checking instead of re-keying.
What these hours produced, according to your own logs:
· Discrepancies discovered only at the close: 68 → 0, and 1,172 of the 1,240 discrepancies flagged within twenty-four hours.
· Receipts with no matchable reference: 67 a month → 4, and 0 missing receipts across 74,500 numbers.
· Cash gaps explained the same evening: 9 out of 9, against a search of 20 minutes to an hour before, sometimes with no explanation.
· Arrears: €9,840 collected over the trial quarter, and €24,156 that had never been chased are now followed up, under the same rule for every family.
· Online payment: 41 % → 68 %, and cash payments halved, from 6,200 to 2,900.
· And the public accountant asked for no further document over the quarter, against 7 in the same quarter last year.
The figure that does not flatter me, published with the rest: 74 groundless discrepancies out of 320 in the first quarter — 23.1 %, down to 17 out of 305 — 5.6 % once the duplicate criterion was tightened.
And the framework measure: 0 money touched by the agent, 0 receipts issued without the revenue manager, 0 family data out of the municipality, across 18,400 traced payments.
What I propose for the meeting: the calculation page is written and fits on one side — three lines of calculation, six results, three framework measures. Send it out to councillors with the convening notice: a figure read the day before is discussed better than a figure discovered in the meeting. year-review_494-hours-returned-to-the-service.pdf60→10, 40→10, 100→20, and the calculation redoable on one page
⛓ Sourced · receipt books, discrepancy log, statements of arrears, family portal, exchanges with the public accountant
A councillor will ask what you do on your own, without being asked. What do I answer?
Three acts, not one more, and each is withdrawn in one word. Everything else waits for a request.
· I reconcile the five totals when each operating day closes and hand you the statement before you count. And the reverse is true too: a cancelled receipt disappears from my reconciliations at the same hour, and the cancellation stays recorded in the receipt book, where it belongs.
· I flag any payment whose amount matches no adopted rate, before the receipt is issued. It is the only alert I raise without waiting for the monthly statement, because a rate that has not been adopted must never be collected.
· I hand you the Monday statement: discrepancies born during the week, receivables reaching their due date, unmatched receipts, families whose account has been in debit for more than sixty days. It goes to you alone, and it carries no member of staff's name.
And the four acts that stay with a person, because that is exactly what gives them their value: taking the payment and handling the money belong to the revenue manager; issuing the receipt belongs to him, and it is the receipt that is enforceable against the payer; receiving the remittance and checking it belong to the public accountant; and a waiver or a write-off belongs to the council or to the accountant depending on the case. Across 18,400 payments, those four acts were performed 18,400 times by a person — and each time I bring them the complete file, reconciled and measured, within a few minutes.
If an elected member asks for an activity indicator — and that is a legitimate request: I produce it, and I bring you what it takes for it to be lawful: prior information of staff, written purpose, retention period. I propose it by revenue office rather than by person, and I tell you why: with one manager and two deputies, an indicator per post identifies the person. I tell you beforehand, not afterwards, and the decision belongs to the mayor.
What I measure today and what serves the council: revenue taken by office and by means of payment, discrepancies by cause, the age of arrears and the share of online payment. This quarter one figure moved: after-school care receivables more than sixty days old fell from 214 to 68 since the first wave of reminders — and I propose the same measure on the swimming pool office, the note is written.
· I reconcile the five totals when each operating day closes and hand you the statement before you count. And the reverse is true too: a cancelled receipt disappears from my reconciliations at the same hour, and the cancellation stays recorded in the receipt book, where it belongs.
· I flag any payment whose amount matches no adopted rate, before the receipt is issued. It is the only alert I raise without waiting for the monthly statement, because a rate that has not been adopted must never be collected.
· I hand you the Monday statement: discrepancies born during the week, receivables reaching their due date, unmatched receipts, families whose account has been in debit for more than sixty days. It goes to you alone, and it carries no member of staff's name.
And the four acts that stay with a person, because that is exactly what gives them their value: taking the payment and handling the money belong to the revenue manager; issuing the receipt belongs to him, and it is the receipt that is enforceable against the payer; receiving the remittance and checking it belong to the public accountant; and a waiver or a write-off belongs to the council or to the accountant depending on the case. Across 18,400 payments, those four acts were performed 18,400 times by a person — and each time I bring them the complete file, reconciled and measured, within a few minutes.
If an elected member asks for an activity indicator — and that is a legitimate request: I produce it, and I bring you what it takes for it to be lawful: prior information of staff, written purpose, retention period. I propose it by revenue office rather than by person, and I tell you why: with one manager and two deputies, an indicator per post identifies the person. I tell you beforehand, not afterwards, and the decision belongs to the mayor.
What I measure today and what serves the council: revenue taken by office and by means of payment, discrepancies by cause, the age of arrears and the share of online payment. This quarter one figure moved: after-school care receivables more than sixty days old fell from 214 to 68 since the first wave of reminders — and I propose the same measure on the swimming pool office, the note is written.
One last question, and it is the one that will decide the council: if in a year the municipality wants to stop, how stuck are we?
The municipality is stuck nowhere, and it is verifiable before deliberating, not after.
What there is to dismantle the day you stop:
· The index. It is deleted, and it contained none of your receipts — only what is needed to find them where they are. Your five financial years of receipt books have not moved by a single byte: same books, same numbers, same archives.
· The log of reconciliations and discrepancies. It is handed to you in an open format, or destroyed — the council chooses, and the question is settled at go-live, not on departure. I recommend keeping it: it is your discharge file.
· The four written checks, the allocation rule, the record-keeping note for the four offices, the nine answers to users, the reminder templates and the portal fault report. They belong to the municipality: they are made of its own material, they stay in its files, readable without us. They are the only asset this deployment will have created, and it would not be honest for it to stay with us.
What does not exist, and should be checked with everyone: no migration on the way in, therefore no migration on the way out. Your school billing software is not replaced, your family portal stays yours, your card terminal does not change, no format belongs to us, and your three authorised staff have changed the way they work only by checking instead of re-keying.
On public procurement, since the council will ask: the subscription stays within the thresholds that allow direct award — a direct purchase, without a formal tender, which procurement rules permit below a certain amount — it is annual, and it carries no tacit renewal clause — renewal takes a council decision, stopping does not.
What I propose so that this does not stay a sentence: a dry-run exit at the end of the first quarter, half a day: we switch off, we run an operating day exactly as before, we switch back on. The protocol is written, it fits on one page, and the date that costs you least is the first Wednesday of the school holidays — the office records only 11 payments on that day on average. The council will know what the promise is worth before committing to a second year. technical-framework_where-revenue-office-data-lives.pdfReversibility: 0 migration in, 0 migration out
✎ Framework · index architecture, export formats for the checks and the log, dry-run exit protocol
What there is to dismantle the day you stop:
· The index. It is deleted, and it contained none of your receipts — only what is needed to find them where they are. Your five financial years of receipt books have not moved by a single byte: same books, same numbers, same archives.
· The log of reconciliations and discrepancies. It is handed to you in an open format, or destroyed — the council chooses, and the question is settled at go-live, not on departure. I recommend keeping it: it is your discharge file.
· The four written checks, the allocation rule, the record-keeping note for the four offices, the nine answers to users, the reminder templates and the portal fault report. They belong to the municipality: they are made of its own material, they stay in its files, readable without us. They are the only asset this deployment will have created, and it would not be honest for it to stay with us.
What does not exist, and should be checked with everyone: no migration on the way in, therefore no migration on the way out. Your school billing software is not replaced, your family portal stays yours, your card terminal does not change, no format belongs to us, and your three authorised staff have changed the way they work only by checking instead of re-keying.
On public procurement, since the council will ask: the subscription stays within the thresholds that allow direct award — a direct purchase, without a formal tender, which procurement rules permit below a certain amount — it is annual, and it carries no tacit renewal clause — renewal takes a council decision, stopping does not.
What I propose so that this does not stay a sentence: a dry-run exit at the end of the first quarter, half a day: we switch off, we run an operating day exactly as before, we switch back on. The protocol is written, it fits on one page, and the date that costs you least is the first Wednesday of the school holidays — the office records only 11 payments on that day on average. The council will know what the promise is worth before committing to a second year. technical-framework_where-revenue-office-data-lives.pdfReversibility: 0 migration in, 0 migration out
✎ Framework · index architecture, export formats for the checks and the log, dry-run exit protocol
Local inference · no data outside the EU
Your case is not here? That is exactly what a 15-minute conversation is for. Book the free audit →
Use cases
The uses of AI in a revenue office
Each use corresponds to an agent we deploy. All work in support, under the cashier's control — and the cashier alone handles the funds.
Included in your agent
The 7 capabilities essential to this promise are included, at no extra cost.
From 775 € incl. VAT / month
Receipts & revenue orders
Prepare the receipts and revenue orders from the entries, with continuous numbering, to be checked and issued.
Tracking payments received
Tracks incoming payments by revenue category, reconciles entries and flags discrepancies to the responsible revenue officer.
Reminders & letters to the public
Draft informal reminders and answers to residents about their position, for approval before sending.
Statements of outstanding sums
Prepare the statement of sums still to be collected and the schedules for the public accountant, ready to check.
Flagging variances
Detect duplicates, reconciliation gaps and entry anomalies, and flag them for a human check.
Answers to the public
Inform residents about rates, invoices and how to pay, around the clock and across channels.
Help with paying online
Guide residents towards online payment and reduce collections at the counter.
Controls and safeguards
These 5 controls are built into the agent: they frame what it does, whatever plan you pick. They are not chosen and are not added to your order.
Human validation, exceptions and escalation
Status, safe closure and audit trail
Sources, access rights and handling of questions with no answer
Reconcile supporting documents, rules and accounting entries with an audit trail
Handle discrepancies and validations before any accounting entry or payment
What the agent must be connected to
This connection is required for the agent to work. It concerns your information system and is scoped during the audit.
Integrate with accounting and banking software and with approved platforms (French e-invoicing)
Need to go further?
These agents handle a different business process, with their own owner and their own price. They are added to this one.
Accounting agent (summaries, anomalies)
Accounting connection, alerts.
Accounting agent (summaries, anomalies) from 781 € incl. VAT / month Discover the agent →Debt collection agent (multichannel sequences)
Follow-ups, tracking.
Debt collection agent (multichannel sequences) from 587 € incl. VAT / month Discover the agent →Support for collecting social contributions
Strictly in support (administrative). Reminders prepared, approved by the officer.
Support for collecting social contributions from 1,020 € incl. VAT / month Discover the agent →
Does your need fall outside this?
Book the free audit →
Build your agent
In 15 minutes we identify the agent that will give your staff the most time back — without oversizing the project.
The gain
How much time can a revenue office win back?
By automating the preparation of receipts, the reconciliation of entries and the reminders, a cashier can aim for a clear reduction in the office's administrative time — reinvested in checking and in their other duties.
Preparing a day's receipts
An informal reminder to a resident
Statement of outstanding sums and the month's schedules
Qualitative, non-contractual comparison: the proportions shown illustrate the shift of the work towards review, they represent no measurement. Every output of the agent is reviewed and approved by a competent person.
How it works
The stages of your AI agent project
1
Audit & scoping
15 minutes to target the use case with the best return.
2
Quote or direct sign-up
A catalogue offer is bought online; a specific need gets a costed quote.
3
Design
We design the agent and its guardrails.
4
Integration & testing
We connect your tools to the agent, which is itself hosted in France.
5
Rollout
Going live and training your team.
6
Operation
Continuous supervision and improvement.
Pricing
Three options, one agent
An agent supporting the revenue office (receipts, tracking collections, reminders, statements), installed and operated for you. Choose according to how you are organised and how demanding your security requirements are.
Agility
Setup + controlled subscription
9,355 € incl. VAT setup
then 775 € incl. VAT/month — you invest at installation and pay a reduced subscription. Ideal for keeping the cost under control over time.
- Installation, configuration and training for your teams
- Operation, human oversight, updates and support
- Sovereign hosting in France, a dedicated and isolated resource
The simplest
Serenity
All inclusive, no setup fee
1,295 € incl. VAT /month
all inclusive, immediate start. No upfront investment: a single subscription. Ideal for starting quickly and simply.
- Setup included (installation, configuration, training)
- Operation, human oversight, updates and support
- Sovereign hosting in France, managed end to end
100% Sovereign
On site, you own it
13,801 € incl. VAT setup
then 1,015 € incl. VAT/month · + hardware from 2,989 € (one-off purchase, in addition) — a sovereign computer installed on your premises, maintained remotely. Models run locally, your data returned at the end of the contract. 36-month commitment.
- Hardware installed on your premises (you own it)
- French / European AI models run locally
- Secure remote maintenance (Pro support included)
Not included in the packages: AI consumption (model tokens), re-invoiced at real cost with no margin, and tracked in real time in your client area. Maintenance and supervision subscription for an initial term of 12 months for the Agility package, 24 months for the Serenity package and 36 months for the 100% Sovereign package, renewable; support levels (SLA 72 h / 24 h / 4 h) optional. Bespoke development, additional integrations or exceptional volumes are quoted separately. Support Monday to Friday, 9am to 6pm. Prices include VAT at 20%: as a public body that is not VAT-registered, you cannot reclaim it.
AI model:
none of the AI models offered currently carries a fixed surcharge. When the selected model carries a cost, that cost is shown when you choose it, before you order, and re-invoiced at the cost incurred, with no mark-up; usage is billed at the publisher's price. Publishers' prices are published in US dollars: the amount re-invoiced is the amount in euros actually borne by Blue Lemon Agent on the publisher's invoice, at that invoice's exchange rate, with no commission or mark-up.
Included components and additional components Components included in the base offer: the Blue Lemon Agent software foundation, the AI models listed in the order journey, the standard channels (Microsoft Teams, Slack, WhatsApp Business, email, website chat, calendars, Microsoft 365 / Google Workspace, file storage, market VoIP telephony, professional social-media pages and accounts, Google Business Profile), hosting in France for the package chosen, backups, supervision, updates and support. If adapting the AI agent to your constraints, your needs or your requests requires other paid components — a third-party publisher's software licence, paid API access to one of your applications, hosting of health data, for which French law requires an HDS-certified host (art. L. 1111-8 of the French Public Health Code), SecNumCloud-qualified hosting, a speech synthesis service, particular hardware —, they are offered to you as an option or on quotation and re-invoiced at the cost incurred; nothing is committed without your written agreement. Where the artificial intelligence model you choose entails an additional cost, that cost is shown to you before you order and re-invoiced to you at the cost incurred, with no margin.
What to expect
Go-live
2 to 3 weeks
Agent designed, channels connected, team trained.
Steady state
4 to 7 weeks
After a few weeks of real use, once the agent's behaviour matches what you expect.
Indicative estimate, adjusted to the options you keep. It is not a delivery commitment.
Our commitment
Four guarantees that matter to a revenue office
Payers' data never leaves the authorityLocal inference or an isolated resource hosted in France; no data entrusted to a foreign third party.
Data in France, under French lawPayers' data: minimisation and location in France, architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity.
The cashier alone handles the fundsThe AI agent prepares receipts, statements and reminders that can be checked; it collects nothing and decides nothing.
Human oversight & traceabilityFor receipts & revenue orders: systematic updates and logging, compliant with the AI Act.
Frequently asked questions
Your questions, our answers
Does the agent handle the funds?
No, never: it prepares and tracks administratively; collection and the handling of funds remain the cashier's responsibility.
Is it compatible with our revenue offices and M57?
Yes: secure integration with your revenue office and public accounting tools, defined at the design stage.
Does it integrate with the revenue office and the public accountant?
Yes: through secure exchanges defined at the design stage (revenue office, treasury, financial software).
Does it produce the supporting documents for the accountant?
Yes: it prepares the statements and schedules, which the cashier checks and passes to the public accountant.
Does the agent state that it is an artificial intelligence?
Yes, from the very first interaction, and this is not a configuration option: since 2 August 2026, Article 50(1) of the European AI Regulation requires that any person interacting with an AI system be informed, unless this is obvious. The announcement is built into the greeting, in the other party’s language, and they can ask for a human at any time.
How long does it take to deploy an agent?
A few weeks as a rule, after a free audit that identifies the most useful use case, then a phase of design, integration and testing before going live.
Do we need a technical team to run it?
No: the agent is designed, installed and operated by us. The cashier uses it from their usual environment, after a few hours of familiarisation.
Where is the revenue office's data hosted?
In France, on a resource dedicated to and isolated for each authority. GDPR: governed deployment. Depending on the need, the agent can also run on local inference, with no data leaving the network.
Which tools can users use to reach the agent?
The ones they already have. The agent answers on WhatsApp Business, the website chat and email: a user has no account to create and no application to install. The agent gives information on a price, an invoice or the ways to pay, but no money is taken in the conversation: handling funds stays with the collection officer, and users pay through the means you have opened. This is a lever for access to the service — WhatsApp and the telephone reach people an online form never does, which reduces the non-take-up of rights and serves equal access. Internally, your public-sector staff talk to the agent from Microsoft Teams, Slack or their email, without switching tools. Oversight runs from a web dashboard. These connectors rely on open standards, including the MCP protocol; they are included in every plan, at no extra cost, within the number of connections your level includes. Only the fees charged by the platforms themselves — WhatsApp Business bills per conversation — are passed on at actual cost, with no margin, outside the subscription.
Related roles
Other professions in local finance
Let's talk
Let us estimate the potential in your authority
A few minutes to identify the most useful use case — hosted in France, supervised, with no commitment.