Skip to content

docs: switch approved platforms without losing invoice history - #28

Merged
btouchard merged 1 commit into
mainfrom
docs/changer-plateforme-historique
Oct 5, 2026
Merged

btouchard merged 1 commit into
mainfrom
docs/changer-plateforme-historique

Conversation

@btouchard

@btouchard btouchard commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • New article docs/comprendre/changer-plateforme-historique.md: what the 27 July 2026 decree guarantees when switching approved platforms (PA) — portability of invoicing data, routing addresses, and invoice history — and what to check before switching (routing address update timing, in-flight invoices, testing flows before cutover).
  • Adds the article to mkdocs.yml nav (both the Comprendre la réforme section and the llmstxt sections list).
  • Deliberately omits the exact minimum-service duration owed by the departing platform: sources disagree (six vs. twelve months, moved during parliamentary debate) and the primary text could not be re-verified from this session (network egress to Légifrance is blocked here). The article tells readers to check the current duration directly rather than repeating an unverified figure.

Test plan

  • mkdocs build --strict passes locally, no warnings.
  • Reviewed against comms/GUARDRAILS.md in gofact-comms: no unverified regulatory figures, no claim that gofact is an approved platform, reference formula ("gofact produit le fichier ; votre plateforme agréée le transporte") present where transmission is discussed.

… history

Covers the portability rights introduced by the 27 July 2026 decree (data,
routing addresses, invoice history) and what to check before switching,
without citing the disputed minimum-service duration still moving in
parliamentary debate.
@btouchard
btouchard merged commit dfdf9fc into main Oct 5, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant