root@fr:~$ solutions/daf
On the 5th, the reporting is ready. Variances come explained. Every figure points to its document.
Agents that prepare the close, the reporting pack, the cash forecast and the reminders overnight. Every amount cites its source, every action is logged. In the morning, you arbitrate. On your own instance, in France.
What happens on the night of the 4th.
Every line of the log is traced: which agent, which action, which data, what time.
The stakes
Finance teams spend the month producing numbers, not using them.
The close eats the month
Exports, cross-checks, the consolidation workbook, version 7 of the pack: by the time the reporting lands, the decisions it was meant to inform are already made.
The verification tax
A figure produced without a source has to be re-checked by hand. That is what disqualifies consumer AI tools for reporting: the time saved generating is lost controlling.
Data scattered everywhere
The bank, the ledger, invoicing, Excel: each tool holds one piece of the number. Consolidation redoes the same assembly by hand, every single month.
What the agent prepares
The finance function's recurring work, whatever your tools.
The agent works inside your tools, not instead of them. It collects, reconciles and formats, and only surfaces what needs a call from you.
Monthly close
Reconciliations run throughout the month: bank, customers, suppliers. When closing time comes, most of the matching is already done.
Reporting pack
P&L, cash, KPIs: the pack builds up in your templates, every figure tied to its source. You arbitrate the variances, not the formatting.
Cash forecast
Receipts, payments, due dates: the forecast refreshes continuously, with its assumptions documented.
Customer reminders
Drafted to your schedule and your tone, with the account's history. Sent after your approval.
Consolidation
Several entities, several tools: the figures come up in one format, with inter-entity discrepancies flagged and explained.
E-invoicing
The September 2026 reform structures your invoice flows. The agent reads them, matches them and prepares the e-reporting.
Your tools stay
The agent plugs into what you already run.
Excel, Sage, Cegid, Agicap, Qonto, Pennylane, your bank: the agent connects to your tools through APIs and MCP, an open standard. Nothing to migrate, nothing to replace. And if you switch tools tomorrow, the agent follows: the AI layer is yours, it depends on no vendor.
September 2026
E-invoicing reaches the company side. The agent absorbs the change.
From 1 September 2026, your company must be able to receive electronic invoices through an accredited platform. Issuing and e-reporting follow in waves. Every structured flow is one more piece of data for the finance team to process. The agent reads them, matches them against your orders and keeps your deadlines.
Control and compliance
Numbers you can stand behind. An architecture your CIO can audit.
Every figure points to its document
Invoice, statement, entry: every amount in the pack cites its source. An unsourced figure gets flagged, not presented. You verify in one click before the board meeting.
Audit log
Which agent, which action, which data, what time. A complete trail, available to your CIO as well as your statutory auditor.
Data in France
Your financial data stays in France, on your own instance. Nothing passes through a consumer platform, nothing trains a public model.
Reversibility
Your data, your reporting templates and your settings stay exportable. You are nobody's tenant.
Augment, not replace
The agent prepares. The human decides.
Never a credit decision, never an autonomous financial commitment: the agent pays nothing, signs nothing, commits the company to nothing. It prepares, reconciles and documents, evidence attached. Judgment and the decision stay with the finance team: that responsibility cannot be delegated.
Questions from finance teams
What CFOs ask us.
Where does the company's financial data go?
To your own instance, hosted in France. It trains no public model and passes through no platform subject to the CLOUD Act. Reversibility is contractual: you leave with your data, your reporting templates and your settings.
What does the agent do, and what does it never do?
It prepares: the close, the reporting pack, the cash forecast, reminders, consolidation. It never decides: no payment, no credit decision, no financial commitment is ever made by an agent. Every outgoing item waits for your approval, every figure cites its document.
Is it compatible with our tools?
The agent connects through APIs and MCP to what you already run: Excel, Sage, Cegid, Agicap, Qonto, Pennylane, your bank. One workshop is enough to check your exact setup.
What changes for the accounting team?
It stops collecting and cross-checking, and starts arbitrating. Reconciliations and formatting run at night. The team takes back variance analysis, the dialogue with operations and data quality. The work that trains and retains.
How do we start?
With a workshop on your close and reporting processes, then a thirty-day pilot on your instance: the one that becomes your production instance. You judge on your next month-end, not on promises.
What if we are a financial entity subject to DORA?
DORA's vocabulary is our native vocabulary: register of information, data location, audit log, exit strategy. We answer the articles 28-30 due diligence before your compliance team asks. Our checklist covers the clauses.
The demo runs on a reporting pack. Not on slides.
In one workshop, we map your close and your reporting pack, plug an agent into demo data, and you watch the collection, the reconciliations and the citations at work.