French Year-End Closing Checklist:
Clear the Expense Report Backlog
The May deadline everyone talks about — the liasse fiscale filing — is not when French year-end closing (clôture des comptes) actually gets decided. It gets decided in January, when the accountant faces a stack of unprocessed expense reports (notes de frais) that December's business trips, holiday spending, and employee procrastination have left behind — and the clôture provisoire is due in two weeks. The date on the calendar that matters most is not May 20. It is the moment the accountant realizes the expense report pile is too deep to clear manually before the provisional accounts must be locked.
Key Takeaways
- The real French year-end deadline hits in mid-January — not May — when the arrêté des comptes (provisional account lock) forces every December expense report to be booked, and the pile that arrives in the first week of January is deeper than manual entry can clear before the lock date.
- The bottleneck is not review — it is typing: 200 expense lines at 3 minutes each adds up to 10 hours of keystrokes, and the January CA3 VAT return (monthly TVA declaration) runs on the same clock, meaning recoverable TVA sits unclaimed in the backlog while you type.
- Redefine the task from data builder to data reviewer — define column names once, upload the entire backlog as a single batch into ImageToTable.ai, and the 10 hours of keystrokes collapse into a 100-minute anomaly scan where you check numbers instead of creating them.
Why the Real Year-End Deadline Hits in January, Not May
The statutory filing deadline for French annual accounts falls in May or June, but the operational closing timeline — when expense reports must be processed or the books cannot close — compresses into the first three weeks of January. Under Article L225-100 of the Code de commerce, the annual general meeting (assemblée générale ordinaire) must approve the accounts within six months of the year-end — June 30 for a calendar-year company. The liasse fiscale must be filed by May 5 on paper or May 20 via electronic transmission (EDI-TDFC) for the same timeline. The deposit of annual accounts (dépôt des comptes annuels) at the commercial court registry follows within one month of the AG — July 31 on paper, August 31 electronically.
But these are downstream consequences. The upstream choke point is mid-January. By January 15 to 20, the provisional closing (clôture provisoire) requires that all December transactions be captured — every supplier invoice, every bank transaction, and every expense report. The arrêté des comptes (closing cut-off) cannot exclude employee expenses without creating a gap in the P&L (compte de résultat). If expense reports are not entered by this window, the accounting team has two bad options: book provisional entries (écritures provisoires) that will need revision later — effectively doing the same work twice — or delay the entire closing sequence, pushing the AG and statutory deposit toward their respective penalties. The penalty for missing the dépôt des comptes is 1,500 €, doubling to 3,000 € for a repeat offence.
The calendar-year French company's year-end expense report deadline is not the May 20 liasse fiscale filing — it is the mid-January arrêté des comptes, roughly three weeks after the champagne corks hit the floor. Every expense report still in the pile on January 15 is an entry that the provisional closing cannot absorb — and a decision the accountant must make under time pressure.
How the Year-End Expense Report Backlog Forms
The expense report backlog at year-end is not a discipline failure — it is what happens when the French reimbursement cycle, December economic activity, and the accounting closing calendar collide in the same three-week window. N2F's user research describes the dynamic plainly: "les collaborateurs ont tendance à attendre la fin du mois pour renseigner leurs notes de frais" — employees wait until month-end to fill in expense reports. December amplifies this three ways: Q4 deal-closing business trips generate high-value expense claims, holiday-season spending (client gifts, year-end dinners) creates another wave, and employees on leave through the Christmas-to-New-Year period submit nothing until they return in January.
On the accounting side, January is already the densest month of the year. The accounting team is simultaneously closing December supplier invoices, reconciling bank statements, preparing the monthly VAT return (déclaration CA3, due between the 15th and 24th), and running payroll. For a 50-employee company where each employee submits an average of 4 expense lines per month, that is 200 individual lines — all concentrated into the first two weeks of January. At three minutes of manual data entry per line — reading the receipt, determining the correct VAT treatment (TVA déductible or not), and typing it into the accounting software — the raw data entry alone consumes 10 hours. Add manager validation and the accountant's verification pass, and the total processing cost exceeds 25 hours, all compressed into the same period in which the clôture provisoire must be locked.
French accounting forums reflect the pressure. Mooncard's research quotes accountants describing the closing period as "la pire période de l'année" — the worst time of the year. Lucca's operations team observes that the accounting department is "envahi par les notes de frais" (overrun by expense reports) at month-end — and year-end concentrates twelve months of this pattern into a single closing event. Emburse benchmarks the cost of a single manually processed expense report at approximately 53 €, once the cumulative time of the employee, manager, and accountant is factored in.
What an Unresolved Backlog Costs Beyond Overtime
The most expensive consequence of an unprocessed expense report backlog at year-end is not the overtime — it is the lost VAT recovery (TVA déductible). Under Article 271 of the General Tax Code (Code Général des Impôts, CGI), VAT paid on goods and services used for taxable operations is recoverable — but a cascade of specific exclusions in Annexe II of the CGI creates a patchwork of rules per expense type. Diesel (gasoil) recovers 80% TVA under CGI Article 298-4 and electricity for EVs recovers 100%; petrol (essence) recovers 0%. Péage (motorway tolls) and parking recover 100% at 20%. Client meals recover at the applicable rate — 10% on food, 20% on alcohol. Employee accommodation and train tickets recover nothing (CGI Annexe II Art. 206-IV-2-2°).
Each expense line carries a different TVA treatment — and if a line is not processed before the January CA3 filing deadline, the recoverable TVA sits in the backlog instead of offsetting the month's TVA collected on sales. The VAT can theoretically be recovered later through a régularisation (account 4458, TVA à régulariser) on the annual CA12 declaration, but that means the company has effectively lent the tax authority the recoverable amount for up to 12 months. Under CGI Article 1727, interest on underpaid VAT accrues at 0.20% per month — so the cashflow impact is real even if the eventual recovery is possible.
| Expense Type | TVA Recovery | January CA3 Impact If Unprocessed |
|---|---|---|
| Client meal (20 € TVA at 10% = 2 €) | 2 € recoverable | 2 € of offset lost from January's TVA collected; recovered months later via CA12 régularisation |
| Diesel (80 € fill, 16 € TVA at 20%, 80% recoverable) | 12.80 € recoverable | 12.80 € deferred — multiplied across a fleet, this becomes material |
| Péage / parking (tolls, 50 € TVA at 20%) | 10 € recoverable | 10 € per trip — a traveling salesperson with 15 péage receipts loses 150 € of January offset |
| Hotel (200 €, no TVA recovery) | 0 € | No TVA impact, but un-booked expense = incomplete P&L = auditor question |
Beyond TVA, the audit risk compounds. Companies that exceed two of three thresholds — 4 M€ total bilan, 8 M€ revenue, 50 employees — must appoint a statutory auditor (commissaire aux comptes, CAC). The CAC's standard is sincérité des comptes: a true and fair view of the company's financial position. If expense reports representing 5% of annual external charges remain unbooked at the provisional closing, the auditor asks why — and the answer cannot be "we ran out of time."
The same dynamic applies to year-end invoice processing, which runs on a parallel timeline with similar deadline pressure — the supplier invoice backlog and the expense report backlog converge in the same January window, competing for the same accounting hours. The approach to clearing both is covered in our year-end invoice processing guide.
7 Days to Zero Backlog: A Pre-Closing Checklist for Finance Teams
The checklist below assumes a mid-January arrêté des comptes deadline and a backlog of 50 to 200 unprocessed expense reports — the scale at which manual entry stops being slow and starts being impossible within the available window. The approach uses Custom Column Extraction: instead of training templates or drawing rectangles around fields on every report format, you type the column names you want — "Employee Name," "Date," "Expense Type," "Amount HT," "TVA Rate," "PCG Account Code" — and the AI locates each value on every document by understanding what the field means, not where it sits on the page. One set of column definitions covers every format in the pile — scanned PDFs, smartphone photos of receipts, Excel exports from last month's template — without per-format configuration.
Collect: Set a hard submission deadline
Send a company-wide notice with a cut-off date for year-end expense report submission — no later than January 10. Use a Collection Link (a shareable upload URL that lets anyone submit files to your processing queue without creating an account) so employees upload their scanned notes de frais and supporting documents (justificatifs) directly — no email attachments to chase, no shared folders to manage. Each uploader sees only their own submissions; all files land in your account's processing queue, organized by submitter.
Batch: Upload everything at once
Drag all collected expense reports — PDFs, JPGs, scanned documents — into a single batch. Do not pre-sort by format, department, or employee. The tool processes them in parallel and merges results into one output table. The batch approach is covered in depth in our batch expense report processing guide, including verification strategies and TVA reconciliation.
Define: Set up columns for accounting-ready output
Type the field names you need: Employee Name, Date, Expense Type (options: Transport/Accommodation/Meal/Mileage/Office Supplies/Client Gift/Other), Description, Amount HT, TVA Rate (%), TVA Amount, Amount TTC, PCG Account Code, Supplier. The expense type column is an inferred column: the AI reads each receipt's content and classifies the expense, even though "Expense Type" is not printed on the document. For mileage claims, add a computed column to calculate the indemnité kilométrique from distance and véhicule fiscal horsepower (CV). Full column setup is covered in the single-report extraction guide.
Extract: Run the batch and review
The AI reads every expense line and its attached supporting receipt, extracting the fields you defined and classifying each expense type. Results appear in a table where you can verify each row before export. A review pass of 30 seconds per row — scanning for expense type misclassifications and TVA anomalies — replaces 3 minutes of manual entry per row.
Files are processed securely and not stored.
Verify: Sort by expense type, scan for outliers
In the output table, sort by the Expense Type column. All rows classified as "Transport" should reference train tickets, péage receipts, fuel purchases, or mileage. A row tagged "Transport" whose Description field contains a restaurant name is a misclassification — fix it on the spot. This scan takes under two minutes for 200 rows. Then spot-check the top and bottom employees by total TTC: an employee who consistently claims 300 to 400 € per month who suddenly shows 1,200 € likely has a duplicate row or misread distance value.
Reconcile: Filter by TVA rate and verify against the CA3
Filter the output by TVA rate. Sum the TVA Amount column for each rate category. For rows at 20%: the TVA amount should approximate 20% of the HT total in that group. For 10% rows: approximately 10%. If the ratio is off, one or more rows carry a misassigned rate — and filing the CA3 with incorrect TVA splits triggers interest under CGI Article 1727. This reconciliation takes five minutes on a 200-row output and is the difference between a defensible VAT return and an audit exposure.
Export: One spreadsheet, coded for the journal des achats
Export to XLSX. Each row carries its PCG account code (compte comptable) — 6251 for transport and mileage, 6256 for accommodation and employee meals, 6257 for client entertainment, 6064 for office supplies. Sort by account code, and the output is already in journal des achats order. The TVA column maps directly to the CA3 declaration: filter to compte 44566 to populate the recoverable TVA total. If your accounting platform is Pennylane, Sage 100, Cegid Loop, or EBP Compta, the structured CSV imports directly into the purchase journal with minimal field mapping. For converting PDF expense reports into structured Excel output outside the year-end context, see the PDF expense report to Excel use case.
When Expense Reports Arrive Coded for the Journal, Not for Re-Entry
The structural cost of the year-end expense report backlog is not measured in overtime hours. It is measured in what those hours displaced — the analysis work that didn't happen because the accountant was typing receipt data, the TVA deductions that shipped late, the provisional entries that needed revision in March, and the statutory auditor's raised eyebrow at a P&L with a visibly incomplete month of December.
When extraction replaces manual entry, the batch of 50 reports that normally consumed two working days becomes a review pass measured in minutes. Each row in the output already carries its classification — expense type determined by AI from the receipt content, PCG code mapped from the classification, TVA split calculated from the receipt data. The accountant's role shifts from building the data row by row to scanning the output for anomalies: sorting by expense type to catch a client meal misclassified as transport, filtering by TVA rate to verify the ratio before the CA3 filing. A 30-second review per row replaces three minutes of manual entry per row. On 200 lines, that is 100 minutes of review instead of 600 minutes of data creation.
For teams that also process supplier invoices alongside expense reports — and most French accounting teams do both in January — the same column-based extraction approach applies to factures (invoices), SIRET verification, and multi-rate TVA splits. The parallel year-end invoice processing timeline is covered in our year-end facture extraction guide, which addresses the same closing-pressure dynamic from the supplier side. For the supplier invoice part of the backlog, the batch French supplier invoice guide covers the multi-rate TVA handling that supplier invoices introduce.
The January arrêté des comptes is a hard date. Every expense report still in the pile when the provisional closing locks is an entry that someone must create, verify, and book — or leave as a provisional entry that multiplies the work in March. The difference between clearing the backlog in a morning and spending two weeks catching up is whether the extraction step replaces the typing step. Not eliminating the review — the accountant still checks the output. Eliminating the part that consumed 600 minutes per closing cycle while the TVA deadline ticked.
FAQ — Year-End Expense Report Backlog
What if some employees haven't submitted their expense reports by the January deadline?
If a report arrives after the clôture provisoire cutoff, the expenses must be booked as charges à payer (accrued expenses) or handled through a provision — both of which require manual entries and subsequent reversal when the actual report is processed. Set an internal deadline (January 10 at the latest) and communicate that reports submitted after the cutoff will be processed in the following month's cycle. The Collection Link approach removes the friction that causes late submission — no login, no email attachments, upload from phone.
Can the extraction handle the barème kilométrique (kilometric scale) across different employee vehicles in a batch?
Yes, through computed columns. For a team with a uniform vehicle fleet (e.g., all 4 CV diesel), define a single formula column: Indemnité Kilométrique (Distance × 0.606). For mixed fleets — different CV brackets, electric vehicles requiring the 20% surcharge, employees using both cars and scooters — extract Distance and Vehicle CV as direct columns, then apply the correct barème formula in Excel post-export. The extraction captures the inputs; the computation happens downstream where it is auditable and editable. The barème for 2026 remains unchanged from 2025; the last revaluation was in 2023.
What happens to TVA if an expense report is processed after the January CA3 deadline?
The recoverable TVA is not permanently lost, but it is deferred. You must recover it through a régularisation on the next monthly declaration or the annual CA12 — recorded through compte 4458 (TVA à régulariser). The practical consequence is a cashflow gap: the company has paid the tax authority the full TVA collected on January sales without offsetting the recoverable TVA on January expenses, effectively lending the tax authority that amount for the period until the régularisation processes. For a company with 10,000 € of recoverable TVA sitting in unprocessed expense reports, that is 10,000 € of working capital unavailable until the correction clears.
Does the tool replace the commissaire aux comptes review?
No. The statutory auditor (CAC) independently verifies the accounts — the extraction tool produces the structured expense data that feeds into those accounts. The value for the audit is traceability: a merged output with a Source Document column links every expense line to its original justificatif, so when the auditor requests the supporting document for a specific expense, you can locate it in seconds rather than searching through 50 individual PDFs. The tool does not certify compliance; it produces data that is ready for the auditor to review.
How does year-end expense report processing differ from year-end invoice processing?
Both converge on the same January closing window and compete for the same accounting hours, but the data challenges differ. Invoice processing involves supplier-side data — SIREN/SIRET verification, multi-rate TVA splits (a Metro facture can carry four TVA rates on a single page), and legal payment deadlines (délai de paiement). Expense report processing involves employee-side data — kilometric scale calculations per individual vehicle profile, expense type classification across inconsistent templates, and a validation chain (manager to accounting) that invoices skip. The backlog-clearance approach — collecting everything into a single batch, defining columns once, extracting in one pass — is structurally identical. The column definitions are what change between the two.
What Changes When the January Closing Stops Being a Crisis
The year-end expense report backlog has been a fact of life in French accounting because it was structurally unavoidable — manual entry at the scale of 200 lines in two weeks can only be done with overtime, and something always had to give. Usually, it was the quality of the data: entries booked provisionally without exact TVA splits, later corrected. The correction pass in March ate the time saved in January, and the cycle repeated every year.
Extraction changes the shape of the problem. The bottleneck shifts from "can we type 200 lines in 10 days" to "can we review 200 lines in an hour and a half" — and the answer to the second question was always yes. The accountant still controls the output. The difference is that the output already exists when the review starts. The P&L closes intact. The CA3 carries the right TVA splits. The commissaire aux comptes gets a clean dossier. And January stops being la pire période de l'année.
Try it on your own backlog. See if the pile that normally fills the first two weeks of January becomes a morning's review — where you are checking numbers, not creating them.