---
id: adc-006
title: "KM retainer currency & composition (USD multicurrency vs EUR-at-settlement; line structure)"
status: Proposed
decided: null
effective_from: null
effective_until: null
supersedes: null
superseded_by: null
---

# adc-006 — KM retainer currency & composition (Proposed)

> **Proposed — operator input needed.** This stub reserves the decision slot
> per the PRD [compliance › ADC seed table](https://gitea.arcodange.lab/arcodange-org/factory/src/branch/main/vibe/PRD/ai-back-office/compliance.md#accounting-decision-records-adc)
> ("blocks erp#53 wiring; operator input needed"). Agents may enrich the
> draft with sources and alternatives; **only the operator Accepts**.

## Context

The recurring template id=1 carries 5100 while the actual May/June drafts were
2×2145.92 + 2×2575.11 EUR; the 2026-07-11 regularization surfaced a probable
**USD-denominated retainer** ($5,500/mo = $2,500 net-30 + $3,000 deferred
+3 months — erp#53; contract WIP `test/km_contract.json` in the trunk). FX
deltas have already been booked twice under adc-002. The invoicing method must
be stable before T05 automation wires it (permanence des méthodes — not
improvised per month).

## Decision

**To arbitrate — no decision recorded.** Open questions (erp#53):

1. USD multicurrency invoices vs EUR-at-settlement invoicing?
2. One invoice with two lines vs two invoices per month (net-30 part /
   deferred part)?
3. Écarts de change policy interaction with adc-002 (would a USD-multicurrency
   choice narrow or supersede it for future invoices)?

## Base légale & doctrine

To gather with the full draft: CGI art. 289 (invoice currency rules), PCG FX
treatment for multicurrency receivables, Dolibarr multicurrency module
implications. Nothing asserted here yet.

## Alternatives rejected

None yet — the alternatives above are open; each needs its why-it-loses
written before acceptance.

## Consequences

- **Blocks erp#53** (T05 monthly client invoice at A2): wiring waits for this
  record to be Accepted.
- May supersede or narrow adc-002's scope for future invoices.
- Annexe: revenue-recognition/currency method disclosure once Accepted.

## QA & validation

Planned per erp#53: dry-run parity (first agent-fired invoice == its manual
twin), then one real month through the gate — after acceptance.

## References

- erp#53 (T05 client invoice; decision D3) · erp#54 (register seeding).
- PRD compliance.md § ADC seed table (adc-006).
- adc-002 (current FX method) · trunk WIP `test/km_contract.json`.
