Part of the AI back-office PRD — compliance › Dolibarr verifications. Run EARLY: if the double-entry accounting module needs enabling + chart mapping, the chantier must finish well before FY-2026 close so the year's FEC is producible.
Checklist (each on a fresh iso-prod checkpoint, results into the PRD STATUS):
Accounting module state — is Comptabilité (partie double) enabled? chart of accounts bound? invoice/payment journals generated? If NOT → open the conditional follow-up issue (chantier: enable + map + journalize 2026).
FEC export — produce on sandbox, validate with the DGFiP Test Compta Demat tool, file the report.
Validation locking — a validated invoice must reject mutation through UI and API with the write agent's permissions (evidence for the ledger grammar).
BlockedLog trial — enable on a checkpoint, exercise invoice/payment flows, verify the chain, then checkpoint refresh (the sandbox provides the reversibility the module denies); decide adoption via a short ADR (not legally required for B2B-only, but cheap belt-and-braces).
Numbering masks — customer/supplier sequences gapless across a validate + avoir cycle.
Acceptance: the 5 findings documented in PRD STATUS + expert-comptable question list updated (FEC expectations for the first exercice, BlockedLog opportunity).
Execution — Blocked by: none — startable today (checkpoint tooling live) · Blocks: #57 (capital-entry path), FY-2026 close readiness · Human gates: none during the checks (expert-comptable Q-list is an output; DGFiP tool runs locally). Start:claude --worktree compliance-verifs from the erp repo root; first commands: bin/arcodange sandbox checkpoint status → bin/arcodange sandbox checkpoint refresh. Done means: the 5 findings posted here as evidence comment → PRD STATUS updated (paired factory PR) → conditional follow-up issue opened if finding 1 is NOT-enabled → Closes #51.
Part of the **AI back-office PRD** — [compliance › Dolibarr verifications](https://gitea.arcodange.lab/arcodange-org/factory/src/branch/main/vibe/PRD/ai-back-office/compliance.md). Run EARLY: if the double-entry accounting module needs enabling + chart mapping, the chantier must finish well before FY-2026 close so the year's FEC is producible.
**Checklist (each on a fresh iso-prod checkpoint, results into the PRD STATUS):**
1. **Accounting module state** — is `Comptabilité (partie double)` enabled? chart of accounts bound? invoice/payment journals generated? If NOT → open the conditional follow-up issue (chantier: enable + map + journalize 2026).
2. **FEC export** — produce on sandbox, validate with the DGFiP **Test Compta Demat** tool, file the report.
3. **Validation locking** — a validated invoice must reject mutation through UI and API with the write agent's permissions (evidence for the ledger grammar).
4. **BlockedLog trial** — enable on a checkpoint, exercise invoice/payment flows, verify the chain, then `checkpoint refresh` (the sandbox provides the reversibility the module denies); decide adoption via a short ADR (not legally required for B2B-only, but cheap belt-and-braces).
5. **Numbering masks** — customer/supplier sequences gapless across a validate + avoir cycle.
**Acceptance:** the 5 findings documented in PRD STATUS + expert-comptable question list updated (FEC expectations for the first exercice, BlockedLog opportunity).
---
**Execution** — Blocked by: none — **startable today** (checkpoint tooling live) · Blocks: #57 (capital-entry path), FY-2026 close readiness · Human gates: none during the checks (expert-comptable Q-list is an output; DGFiP tool runs locally).
**Start:** `claude --worktree compliance-verifs` from the erp repo root; first commands: `bin/arcodange sandbox checkpoint status` → `bin/arcodange sandbox checkpoint refresh`.
**Done means:** the 5 findings posted here as evidence comment → PRD STATUS updated (paired factory PR) → conditional follow-up issue opened if finding 1 is NOT-enabled → `Closes #51`.
arcodange
added this to the Ledger compliance milestone 2026-07-11 18:18:53 +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 — compliance › Dolibarr verifications. Run EARLY: if the double-entry accounting module needs enabling + chart mapping, the chantier must finish well before FY-2026 close so the year's FEC is producible.
Checklist (each on a fresh iso-prod checkpoint, results into the PRD STATUS):
Comptabilité (partie double)enabled? chart of accounts bound? invoice/payment journals generated? If NOT → open the conditional follow-up issue (chantier: enable + map + journalize 2026).checkpoint refresh(the sandbox provides the reversibility the module denies); decide adoption via a short ADR (not legally required for B2B-only, but cheap belt-and-braces).Acceptance: the 5 findings documented in PRD STATUS + expert-comptable question list updated (FEC expectations for the first exercice, BlockedLog opportunity).
Execution — Blocked by: none — startable today (checkpoint tooling live) · Blocks: #57 (capital-entry path), FY-2026 close readiness · Human gates: none during the checks (expert-comptable Q-list is an output; DGFiP tool runs locally).
Start:
claude --worktree compliance-verifsfrom the erp repo root; first commands:bin/arcodange sandbox checkpoint status→bin/arcodange sandbox checkpoint refresh.Done means: the 5 findings posted here as evidence comment → PRD STATUS updated (paired factory PR) → conditional follow-up issue opened if finding 1 is NOT-enabled →
Closes #51.