Updated on 30 October 2026
Payroll has one feature accounting does not: a deadline every month, the same one for everybody. When a question blocks a payroll manager on the evening of the 27th, it cannot wait three days. It is for that kind of moment that a firm gives its teams an assistant that has already read the whole Silae help.
The same question, on the evening of the 27th
A payroll administrator is stuck on a payslip: an absence that isn't calculating the way she expected, a pay item specific to the client file's convention collective (industry-wide collective agreement) that she doesn't have to hand. She asks the office next door, who knows, answers, and goes back to their own payslips. The following month, someone else hits the same screen, another 27th in the evening, and the same office gets interrupted all over again.
Silae's online help had the answer all along, or Silae support gave it last year, in an email nobody can find. That is the time IntraIA cuts: not the fix, which stays with the vendor, but the question whose answer already existed.
What the assistant has already read
Silae's public help lives at support.silae.fr. On 28 August 2026, our catalogue held 397 of its articles, and the assistant resyncs on its own: every software update, every new procedure published ends up in its answers without anyone lifting a finger. Ask the question the way you'd ask a colleague; it answers by citing the source article, with the link. When it can't find it, it says so, rather than inventing a payslip setting. These figures describe our catalogue, never an instance.
What your payroll managers teach it
Your payroll managers get answers from Silae support every week, through the client area or over the phone. Those answers, often precise and specific to one convention collective (French sector-wide collective agreement), used to live in mailboxes. The assistant consolidates them and adds them to the firm's knowledge base: an answer obtained once holds for the whole team, including the person who joined last month.
An answer only enters the knowledge base once an authorised person has validated it, in a single queue to work through, and a wrong answer is corrected in one place, for everyone. Added to that are your internal notes, your payslip templates, and the way your firm handles each collective agreement, the part that appears in no online help. The page on knowledge management sets out the method.
Between your teams and Silae support
When the answer exists neither in the help nor in the firm's memory, the assistant can step in, if you decide so: it writes to Silae support, follows the request, chases it up if needed, on working days, and brings the answer back to you. Who asked and for which client file, how long the wait has been: it is all visible. And once the answer comes back and is validated, it joins the knowledge base. This relay is live at our client firms.
The line stays clear: a payslip that is wrong because of a fault in the software, a filing that goes out badly, that is the vendor's job, and nobody else's. What the assistant removes is the already-solved question being asked again, and the wait for a call back over a step set out in black and white in a manual.
Your Silae payroll, connected to reporting
Since 24 October 2026, the connection to Silae through its programming interface has been live at our clients, on real client files. With the firm's API account, entered in your resources and verified before being saved, the instance reads each client file's payroll months through its social declarations (DSN), picking up only what has changed, at the frequency you set. It reads; it writes nothing into Silae.
Monitoring draws the HR and payroll picture of each client file from it: headcount, contracts, ages and length of service, payroll costs, sick leave, joiners and leavers, the pay gap between women and men. Two rules bring payroll and accounting together: a social declaration (DSN) that doesn't describe the same company as the client file record, and declared payroll that doesn't match the payroll booked in the accounts. The HR manager, one of your AI agents, writes the HR reading of it, checked amount by amount and signed as automatic, and answers HR questions from the official factsheets, citing the factsheet and its date. For firms that also handle their clients' payroll and HR, the HR and payroll page says more.
The questions we get asked
- Do you need a Silae API account?
- Yes, to connect payroll to the dashboard: the firm's API account, entered in Administration › Resources, checked before it is saved, and encrypted inside your instance. The assistant itself doesn't need one: it reads Silae's public help and your documents.
- Does the assistant change anything in Silae?
- No. The connection reads payroll months through the DSN declarations and writes nothing into Silae. Payslips, declarations and settings stay in your software, handled by your payroll staff.
- Is this official Silae help, or a partnership with Silae?
- Neither. We have no partnership with Silae and we don't publish help about their software: we read what they publish, and we keep what your firm learns. The documentation stays with the vendor, the memory stays with you.
- And for a firm that runs payroll without Silae?
- Monthly payroll declarations (DSN) are uploaded by hand into the dashboard, exactly as your software produces them, and the payroll figures are calculated the same way. Other payroll software will connect later, and this page will say so when the time comes.
Watch it answer
The online demo takes place at Cabinet Dumont & Associés, a demo firm whose software documentation is genuinely plugged in. Go in, ask a configuration question, and look at where the answer comes from. Try the demo, or read what a firm finds there.









