Yes - use the france cir tax credit as a conditional pricing framework, not a guarantee. Your client claims the credit, while you support eligibility by proving ministry approval for subcontracted research, separating R&D from routine delivery, and keeping dated records from the work itself. Keep positioning tied to the scheme’s EU/EEA perimeter and to what the client’s adviser validates, rather than promising recovery on the full invoice.
Your client claims CIR, not you. Your job is to make sure your work can be treated as qualifying R&D. Your invoice should map cleanly to that scope, and the approval requirement should be met when subcontracted research is involved.
The Crédit d'impôt recherche (CIR) is France's R&D tax credit under CGI article 244 quater B. The ordering company may include eligible outsourced R&D in its CIR calculation base, subject to conditions. In practice, your work needs to fall within qualifying research activity, be carried out within the EU/EEA perimeter used by the scheme, and be documented in a way the client can defend.
As of the legal version in force from 1 January 2026, the published rates are 30% up to €100 million of eligible research spend and 5% above that. Treat this as a verification point, not a sales shortcut. Confirm current rates, caps, and approval process details before you quote outcomes to a client.
Start conservatively. If the project is mostly routine delivery using known methods, treat it as non-R&D unless the client's tax adviser confirms otherwise. Use this quick screen before you make any CIR-related promise:
These examples are directional only and do not replace a formal eligibility review.
| Service type | R&D-style work that may fit CIR | Delivery-style work that often needs separate review before CIR positioning |
|---|---|---|
| Software / product engineering | Systematic experimentation documented against a technical objective | Routine build or implementation work without a documented R&D objective |
| Data / AI consulting | Methodical testing of a new technical approach with traceable results | Standard analytics or model operations using established approaches |
| Technical / process consulting | Structured technical trials aimed at creating or materially improving a process | Execution support work where the method and outcome are already known |
Approval is a key compliance gate for subcontracted research. The provider must be approved by the ministry in charge of research, and clients can verify status on the ministry's approved list. In practice, you should be ready with proof of approval, clear R&D scoping, and support for the dossier justificatif built during execution. That file is supplied to the tax administration on request, and CIR reporting is tied to form 2069-A filed with the tax return.
If your work clears this first screen, the next question is whether accreditation is worth pursuing for your business. If you want a deeper dive, read The Ultimate Digital Nomad Tax Survival Guide for 2025.
Treat accreditation as a compliance step, not a slogan. Verify each assumption against current official materials and back it with dated records. If verification is incomplete, keep the point as a no-go placeholder.
Before you invest time, test whether your assumptions are actually verifiable. Use this four-point screen:
| Check | What to verify | Note |
|---|---|---|
| Source status | Key regulatory points against the official legal edition/PDF, not only a website rendering | If "no" on multiple items, pause and close those gaps first |
| Version status | Updates or corrections, including the 04/17/2023 correction linked from the 03/23/2023 page | If "no" on multiple items, pause and close those gaps first |
| Documentation readiness | Dated, contemporaneous records created during delivery | If "no" on multiple items, pause and close those gaps first |
| Disclosure awareness | Prepared for a public posting workflow via Regulations.gov after agency review | If "no" on multiple items, pause and close those gaps first |
If your answer is "no" on multiple items, pause and close those gaps first. For independent professionals, keep CIR-specific items as explicit verification placeholders until confirmed in current official materials:
Use this as an internal quality-control tool, not an official CIR checklist.
| Evidence item | Why it matters | Common weak point |
|---|---|---|
| Official source record (edition/PDF used) | A website rendering may not be the official legal edition | Team relies on page rendering without official-edition verification |
| Version log (publication + corrections) | Corrections can change details you rely on | Initial draft is used without re-checking updates |
| Legal-status note for each source | Some formats do not provide legal or judicial notice | XML/text copy is treated as legally sufficient on its own |
| Dated internal records for each claim | Reduces unsupported statements in the file | Claims are asserted without contemporaneous records |
| Open placeholders list | Prevents over-claiming on unknown CIR rules | Placeholders are silently converted into "facts" |
If a claim cannot be tied to a verified official source or dated internal evidence, rewrite it as uncertain or remove it.
The tradeoff is not just cost. It is time, control, and how much challenge your file needs before submission.
| Aspect | Self-managed application | Specialist-supported application |
|---|---|---|
| Effort | Can mean lower cash spend, higher founder time | Can mean higher cash spend, lower internal drafting load |
| Risk | Verification gaps can be easier to miss | External challenge can reduce drafting gaps, but facts still remain your responsibility |
| Control | Maximum control of narrative and file structure | External challenge can improve quality, with less direct control |
| Best fit | Strong internal records and disciplined source/version tracking | Borderline facts, cross-border complexity, or weak existing records |
Whichever path you choose, keep the process tight from the start.
| Step | Action | Detail |
|---|---|---|
| Before submission | Verify every legal/process assumption against the official publication/PDF | Log the exact version/date used |
| During review | Re-check for corrections or updates | Do this before relying on any previously copied requirement text |
| Escalate early | Bring in a qualified tax or legal advisor | Use this when eligibility depends on unresolved placeholders such as entity location, subcontracting chain, cross-border setup, rates, or filing mechanics |
Related: Can Digital Nomads Claim the Home Office Deduction?. Before you file, align scope, deliverables, and acceptance criteria in one draft so your narrative and contract stay consistent: Use the freelance contract generator.
Once you have accreditation, the commercial question shifts from provider status to positioning. Use your accreditation to frame price as a compliance-first net-cost decision, not as a promise of automatic tax savings.
Lead with the gross fee, then isolate the portion that may qualify as outsourced R&D under current rules and client-side validation. The right pitch is simple: accreditation removes a key blocker for subcontracted R&D treatment, but it does not guarantee that the full invoice is eligible. Outsourced R&D spend is included only under conditions, so your proposal should make scope boundaries and review assumptions explicit.
For current-year inputs, anchor your model to Article 244 quater B and verify rates before sending anything out. The legal structure includes a 30% rate up to 100 million euros of qualifying research spend and 5% above that threshold. Large client R&D bases should be modeled by tranche, not with one flat assumption.
Use a simple fee stack in the proposal:
If your engagement mixes experimental work with routine delivery, split those lines in the proposal.
A side-by-side table is usually clearer for procurement and finance than a long explanation.
| Provider setup | Gross fee | Potential CIR-eligible amount | Documentation burden for client | Net-cost view |
|---|---|---|---|---|
| Non-accredited provider | EUR [insert fee] | Not positioned under approved-subcontractor CIR treatment | Higher uncertainty for finance/tax review | Usually modeled at gross fee unless client advisor confirms another basis |
| Accredited provider, tightly scoped R&D work | EUR [insert fee] | EUR [insert R&D-only portion], subject to conditions | Moderate with approval proof and evidence mapping | Gross fee minus advisor-validated estimate using current rate(s) |
| Accredited provider, mixed R&D and routine delivery | EUR [insert fee] | EUR [insert separated R&D portion only], subject to conditions | Higher, because scope split and exclusions must be documented | Net view applies only to the separated eligible portion |
Include a verification note in your offer: clients can check accreditation status on the official ministry list. Attach your approval document so procurement and finance can validate it.
Your proposal is doing its job when finance can review it without rebuilding the file from scratch.
| Proposal element | What to include |
|---|---|
| Accreditation proof | Proof of current accreditation status |
| Scope mapping | Scope language mapped to technical objectives, uncertainties, tests, and deliverables |
| Exclusions | Explicit exclusions for routine or non-qualifying work |
| Pricing table | Separate gross fee from potentially eligible outsourced-research work |
| Finance handoff note | List the evidence you will provide: approval proof, invoices, work description, and dated project records for the annual dossier justificatif CIR |
The compliance workflow matters here. CIR is computed through 2069-A-SD and reported on 2069-RCI-SD, with annual supporting documentation and mandatory telefiling for the 2069-A form set. If your package is audit-ready, premium pricing is easier for the client to defend internally.
This is where good positioning matters most. Answer clearly, stay conditional, and do not slide into giving tax advice.
Can you tell us exactly what we will get back? You can explain the current rate structure and provide an indicative net-cost scenario. You should not present a fixed recovery percentage on the full invoice.
Can you confirm our project is fully eligible? No. You can explain how your accredited scope aligns with qualifying research work, but final eligibility belongs to the client and their tax advisor.
When should we escalate to a professional? Escalate when scope mixes R&D and routine work, when the client's existing R&D base may cross the 100 million euro tranche, when cross-border delivery facts are unclear, or when finance needs pre-filing certainty. In those cases, request written advisor guidance or consider a rescrit fiscal (silence-is-acceptance timeline shown as 3 months).
You might also find this useful: A Guide to France's Micro-Entrepreneur Regime for Freelancers.
You win better conversations when you frame your offer around compliance-ready value, not just price. Subcontracted R&D spend is not automatically CIR-eligible: provider approval, qualifying R&D activity, and documentation discipline all matter, and outcomes depend on the rules for the client's filing year.
That framing matches how the Crédit d'impôt recherche works in practice. For subcontracted R&D, the provider must be approved by the ministry in charge of research, and the client still needs qualifying R&D activity. When you reference policy values, keep the wording conditional and tied to the current filing year. For example: "potential CIR impact based on eligible research spend under Article 244 quater B, to be confirmed for the client's filing year."
| If you sell on price | If you sell on compliance-ready value |
|---|---|
| Proposal stays at day rate or project fee. | Proposal states approval status, maps potentially eligible R&D scope, and explains likely net client impact without guarantees. |
| Procurement compares you as a generic vendor. | Procurement gets a concrete approval and scope checkpoint to review. |
| A cheaper supplier is easier to justify. | Switching may require re-checking approval, scope, and evidence quality. |
| Documentation is assembled late, if at all. | Technical and billing support is built as work happens, ready for a dossier justificatif CIR if requested. |
In your next proposal, do three things. State your approval status exactly as shown on your notice. Map the work package to potentially eligible R&D scope while separating non-R&D tasks. Frame value around documented potential client impact rather than a blanket savings claim. Do not present simulator output as proof; it is indicative only.
If eligibility is uncertain, consider a CIR rescrit before the R&D operation starts and within the applicable timing window. If the scope is borderline, the legal structure is unusual, multiple incentives apply to the same project, or the client wants filing-level certainty before signing, involve a qualified French tax adviser before you make eligibility promises or lock contract language.
If you want a lower-friction operating setup for cross-border invoicing, collections, and payout visibility with French clients, talk to Gruv.
Possibly, but only in specific setups. The supported point is that subcontracting expenses paid to approved public or private subcontractors in the European Economic Area may qualify. If your entity, team, or billing chain falls outside that pattern, treat eligibility as uncertain until it is confirmed by a qualified tax advisor.
It can affect eligibility treatment because EEA subcontractor expenses are described as eligible when the subcontractor is approved by the French Ministry of Research. It does not, by itself, mean every cost will qualify.
No. Eligibility still depends on compliance with criteria set by the French Ministry of Research, and some qualifying expense categories are subject to ceilings. Approval is one condition, not blanket acceptance of every billed amount.
It does not guarantee tax-credit acceptance, contract awards, or any specific pricing outcome. Final treatment still depends on eligibility criteria and capped expense rules.
Do not assume mandatory wording without current primary-source confirmation. Keep your scope descriptions and records consistent so technical and financing documentation can support review.
Keep technical and financing documentation ready from the start. Your records should clearly connect billed work to the R&D scope so they are usable for tax audit and authority review. Escalate early if your documentation trail is incomplete or the client asks for filing-level certainty.
Track work by calendar year for eligible R&D expenses, regardless of fiscal year closing date. If work spans December and January, make sure records can be mapped cleanly to each year.
Use a conservative estimate. R&D subsidies can reduce the eligible expense base, so a simple headline estimate can overstate the outcome. Escalate when multiple incentives are stacked and the client needs a precise net figure.
No, not as a blanket statement. Unused credit can generally be carried forward against tax liability during the next three years, and amounts still unused after three years are generally refunded to the taxpayer. If they plan to transfer or sell the receivable, note that transferability is limited to credit institutions.
Do not rely on memory for validity timelines. The current validity period is not established in this grounding pack, so confirm it from current official documents before making commitments.
This grounding pack does not provide a confirmed rejection workflow. If an application or renewal is rejected, request written reasons and handle next steps with qualified tax counsel using current official guidance.
Use the authority and process names shown on current official application materials. Confirm the current authority and process naming before publish, before updating templates, and before giving procurement verification instructions.
Asha writes about tax residency, double-taxation basics, and compliance checklists for globally mobile freelancers, with a focus on decision trees and risk mitigation.
With a Ph.D. in Economics and over 15 years of experience in cross-border tax advisory, Alistair specializes in demystifying cross-border tax law for independent professionals. He focuses on risk mitigation and long-term financial planning.
Includes 3 external sources outside the trusted-domain allowlist.
Educational content only. Not legal, tax, or financial advice.
First decision: stop treating digital nomad taxes as a hunt for the lowest rate. The high-value move is identifying where you are taxable, what filings follow, and what evidence supports your position if a tax authority asks questions later.
Claim the deduction only when your facts and records can carry it. With the home office deduction for digital nomads, the real decision is usually a three-way call: claim it, do not claim it, or pause and get help because your file is not ready.
Low-stress compliance starts with one question: does the Micro-entrepreneur regime match your real setup right now? It is often presented as a simplified option for lower-revenue activity, so use it as a fit test, not a shortcut.