Part of the AI back-office PRD — POC-6 + challenge C12. Hard regulatory deadline: 2026-09-01 (e-invoice reception mandatory for all French companies). Operator direction: Qonto as the PA (plateforme agréée, ex-PDP — DGFiP-registered, e-invoicing included in all plans, the fleet's richest API integration).
Deliverables
[HUMAN] Activate the e-invoicing address in the Qonto UI (account-settings change — operator only); agent then verifies Arcodange appears reception-ready in the annuaire.
Receive a real or test e-invoice → pull it through the business API (/v2/supplier_invoices family — the fleet already authenticates) into the T02 structured schema (Factur-X/UBL/CII parsing lane). If no FR supplier sends one naturally, plan a test emission (another PA's sandbox, or ask a cooperating sender).
Archive the original in the GED (the PA is a conduit, never the archive — needs the attach op #43).
Map the 2027 e-reporting path for the KM export invoices (Dolibarr stays invoicing system of record → API push vs manual, documented).
Close D4 with an ADR on the factory repo (vibe/ADR/), cross-linked to the PRD STATUS per house convention.
Fallback if blocked: any other DGFiP-registered PA (138 as of 2026-06); minimum-compliance manual reception via the Qonto UI while the API lane matures.
Acceptance: reception verified end-to-end before 2026-09-01; ADR merged; e-reporting requirements captured as backlog issues with dates.
Execution — Blocked by: #43 for step 3 only (steps 1–2 + 4 can proceed now) · Blocks: P6 e-reporting (2027) · Human gates: step 1 (Qonto UI) — the single unblock the operator owes this milestone; possibly a cooperating sender for step 2. Start: [HUMAN] step 1 first; then claude --worktree qonto-pa from the erp repo root; probe bank-curl.sh qonto /v2/supplier_invoices (read-only) to inventory what the API already exposes. Done means: evidence comment here (annuaire status + pulled e-invoice JSON + GED attach id) → ADR merged on factory (Closes via factory#22 flow) → PR(s) merged with Closes #46.
Part of the **AI back-office PRD** — [POC-6](https://gitea.arcodange.lab/arcodange-org/factory/src/branch/main/vibe/PRD/ai-back-office/poc-plan.md) + [challenge C12](https://gitea.arcodange.lab/arcodange-org/factory/src/branch/main/vibe/PRD/ai-back-office/challenges.md). **Hard regulatory deadline: 2026-09-01** (e-invoice reception mandatory for all French companies). Operator direction: **Qonto as the PA** (plateforme agréée, ex-PDP — DGFiP-registered, e-invoicing included in all plans, the fleet's richest API integration).
**Deliverables**
1. **[HUMAN]** Activate the e-invoicing address in the Qonto UI (account-settings change — operator only); agent then verifies Arcodange appears reception-ready in the annuaire.
2. Receive a real or test e-invoice → **pull it through the business API** (`/v2/supplier_invoices` family — the fleet already authenticates) into the T02 structured schema (Factur-X/UBL/CII parsing lane). If no FR supplier sends one naturally, plan a test emission (another PA's sandbox, or ask a cooperating sender).
3. Archive the original in the GED (the PA is a conduit, never the archive — needs the attach op #43).
4. Map the 2027 e-reporting path for the KM export invoices (Dolibarr stays invoicing system of record → API push vs manual, documented).
5. Close **D4 with an ADR** on the factory repo (`vibe/ADR/`), cross-linked to the PRD STATUS per house convention.
**Fallback if blocked:** any other DGFiP-registered PA (138 as of 2026-06); minimum-compliance manual reception via the Qonto UI while the API lane matures.
**Acceptance:** reception verified end-to-end before 2026-09-01; ADR merged; e-reporting requirements captured as backlog issues with dates.
---
**Execution** — Blocked by: #43 for step 3 only (steps 1–2 + 4 can proceed now) · Blocks: P6 e-reporting (2027) · Human gates: **step 1 (Qonto UI)** — the single unblock the operator owes this milestone; possibly a cooperating sender for step 2.
**Start:** [HUMAN] step 1 first; then `claude --worktree qonto-pa` from the erp repo root; probe `bank-curl.sh qonto /v2/supplier_invoices` (read-only) to inventory what the API already exposes.
**Done means:** evidence comment here (annuaire status + pulled e-invoice JSON + GED attach id) → ADR merged on factory (`Closes` via factory#22 flow) → PR(s) merged with `Closes #46`.
arcodange
added this to the P2 — E-invoicing reception (hard 2026-09-01) milestone 2026-07-11 18:17:47 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Part of the AI back-office PRD — POC-6 + challenge C12. Hard regulatory deadline: 2026-09-01 (e-invoice reception mandatory for all French companies). Operator direction: Qonto as the PA (plateforme agréée, ex-PDP — DGFiP-registered, e-invoicing included in all plans, the fleet's richest API integration).
Deliverables
/v2/supplier_invoicesfamily — the fleet already authenticates) into the T02 structured schema (Factur-X/UBL/CII parsing lane). If no FR supplier sends one naturally, plan a test emission (another PA's sandbox, or ask a cooperating sender).vibe/ADR/), cross-linked to the PRD STATUS per house convention.Fallback if blocked: any other DGFiP-registered PA (138 as of 2026-06); minimum-compliance manual reception via the Qonto UI while the API lane matures.
Acceptance: reception verified end-to-end before 2026-09-01; ADR merged; e-reporting requirements captured as backlog issues with dates.
Execution — Blocked by: #43 for step 3 only (steps 1–2 + 4 can proceed now) · Blocks: P6 e-reporting (2027) · Human gates: step 1 (Qonto UI) — the single unblock the operator owes this milestone; possibly a cooperating sender for step 2.
Start: [HUMAN] step 1 first; then
claude --worktree qonto-pafrom the erp repo root; probebank-curl.sh qonto /v2/supplier_invoices(read-only) to inventory what the API already exposes.Done means: evidence comment here (annuaire status + pulled e-invoice JSON + GED attach id) → ADR merged on factory (
Closesvia factory#22 flow) → PR(s) merged withCloses #46.