Entry Coding Inference Proposals

Infer a coding for one suspensed entry from its counterparty-IBAN history.

The detail-page "infer coding from history" action (doc/pipeline.md §"Bank-transaction coding from IBAN history"). Advisory: records a held autopost:bankcode: decision (idempotent — an existing decision is returned as-is); the human books it via the accept-decision flow. The service drops DB locks before the accountant call (two-transaction choreography). 503 when the accountant is unreachable.

⚠️ 409 since ZET-316 — a contract change; this route previously only ever answered 200 or 503. It refuses when no fiscal year the company has books for covers the movement's date and the R2-32 rollover rule will not open one (a prior year, or a gap between two existing years). Coding the entry would otherwise have MINTED that year, with no opening balances, as a side effect of an advisory inference. The remedy is named in the message: open the year with POST /companies/{company_id}/gl/fiscal-years. No decision row is recorded for that refusal, so the entry stays inferable once the year exists.

⚠️ 409 conflict.bankAccountNotMapped since F2779 — the entry's bank account has no ledger account number (or one its fiscal-year chart lacks), so the accountant could not resolve the bank leg. Refused before the accountant call; nothing is recorded.