Your Cloud Software Has a 99.9% Uptime SLA. Your URSSAF Deadline Has 0% Tolerance for Lateness.
Eleven forty-seven pm on the 5th of the month. You've had a 14-hour day. Your DSN — the monthly social security declaration your company must file for every employee — still needs to be submitted. You open the software. "Service temporarily unavailable — planned maintenance until 02:00." You have 13 minutes. You try refreshing. You try your phone. You call your accountant; no answer. At midnight, the deadline passes. The fine arrives six weeks later.
Your accounting software guarantees 99.9% uptime. URSSAF — the French agency that collects social security contributions — does not accept vendor maintenance windows as a reason for missing your DSN filing. The fine is yours. Not your vendor's. Yours.
Twelve deadlines, one outage window
French DSN deadlines fall on the 5th of every month at midnight for most businesses, and the 15th for smaller ones. That's 12 hard cutoffs per year — not rolling windows, not grace periods, not "we'll accept it if you call us." The government portal net-entreprises.fr receives the file or it doesn't. Midnight on the 5th is not a guideline.
Run the math on what cloud reliability means against 12 fixed moments. An SLA — a Service Level Agreement, the contractual promise your software vendor makes about how often their service will be available — of 99.9% translates to 8.7 hours of unavailability per year. A 99.5% SLA, common in mid-tier cloud services, means 43.8 hours. These hours are distributed unpredictably. No vendor's SLA specifies which 8.7 hours you'll lose. To be clear: vendor outages causing missed deadlines are not common. Most businesses running cloud accounting software never hit this scenario. The risk per individual month is small. The problem is that when it does happen, the consequence is not small — and no one else covers it.
Twelve mandatory filing deadlines mean 12 danger windows. If downtime events are random, a 99.9% reliable service has roughly a 10% annual chance of an outage overlapping with at least one of those windows — depending on how long outages typically last and how tight your filing window is. For businesses that file their DSN on the evening of the 5th (which most do, because they built that into their month-end routine), the risk window is measured in hours, not days.
When platforms go down on deadline day
Scheduled maintenance is the quieter risk that rarely makes headlines. While sudden outages get status-page notifications and incident reports, planned maintenance windows appear in vendor dashboards or get buried in support emails. Sage's French user forums document multiple instances of maintenance windows falling on deadline-adjacent evenings. Customers filed support tickets. Sage apologised. URSSAF received no apology and no amended deadline.
Real incidents confirm this isn't theoretical. Fastly's June 8, 2021 global outage — Fastly is a major internet infrastructure provider used by thousands of cloud services — lasted approximately one hour and took down platforms worldwide. Any cloud accounting software dependent on Fastly's servers was unavailable during that window. AWS us-east-1 (Amazon's primary US data centre region, used by thousands of European software companies) logged eight major incidents between 2019 and 2023, including a December 2021 disruption lasting over four hours. Neither Fastly nor Amazon compensated the businesses that received URSSAF fines because software they were paying for was unavailable.
Every SLA document contains a clause that protects the vendor, not the customer. Standard remedies for downtime are service credits — typically a percentage of your monthly fee. A 99.9% SLA on a €150/month subscription credits you approximately €4.50 for a full day of downtime. The URSSAF fine that downtime triggered? That starts at €58.88 per employee.
After the fine: the math nobody ran
Who bears the fine when the software is down on deadline day? You. Not your vendor. Your contract with the accounting software company contains no clause holding them liable for regulatory penalties incurred during their outages. This is not an oversight — it is standard contract design across the entire cloud accounting industry.
For a restaurant with 15 employees, a single missed DSN deadline costs €882.60. That amount repeats every month the situation isn't resolved, because URSSAF applies the penalty retroactively until the declaration is correctly filed. One missed deadline can cascade into €2,647.80 over three months while you navigate the correction process. A missed DPAE — the pre-hiring declaration required before a new employee's first day — adds a separate €1,068 fine per undeclared employee on top of that.
As headcount grows, the exposure multiplies. A sole trader with one employee owes €58.88 for a missed month. A small manufacturer with 30 employees owes €1,766.40. Each hire you make increases the financial consequence of a single deadline failure without changing the probability of the platform being available when you need it.
Forty-eight hours of buffer, zero risk window
Filing 48 hours early eliminates the risk window entirely. If your DSN is submitted on the 3rd instead of the 5th, a 24-hour outage starting on the evening of the 4th doesn't affect your compliance. You've already filed. The confirmation from net-entreprises.fr — the acknowledgment that the declaration was received — arrived two days ago. The 5th of the month is just a date on the calendar.
Liberté generates and submits your DSN automatically on the 3rd of each month using a direct automated connection to net-entreprises.fr — no manual login, no dashboard to check at 11:47pm, no dependency on whether a third-party server is having a difficult evening. The filing happens whether or not you're awake. If the net-entreprises.fr portal itself is briefly unavailable (which happens occasionally — it handles 28 million declarations per month), the system retries automatically until confirmation is received.
This is what's missing from standard thinking about cloud accounting software: the question isn't "is the software reliable?" It's "what happens when it fails on the one day it must not?" When that cost is €882.60, multiplied by every month the problem persists, the architecture of when you file matters as much as the quality of the software doing the filing.
The 5th when it's already handled
When your software is down and your deadline is midnight, URSSAF doesn't care about your vendor's maintenance schedule. That sentence is the one worth writing down. You're not protected by SLA percentages. You're protected by filing before the risk window opens.
Imagine checking your phone on the 5th and seeing: DSN — received and acknowledged on the 3rd. The accounting is closed for the month. Your accountant has the summary. You haven't thought about net-entreprises.fr since last Tuesday.
That's what filing infrastructure should feel like — not a deadline to manage, but a task that completed before you needed to worry about it. The €882.60 stays in the business. The midnight session on the portal doesn't happen. The 5th of the month is just the day after the 4th.