Add SettlementStatement schema and a dedicated settlement_statements store (ingest_settlement_statement, current_settlement_statements) so resource-control internal transfer settlements join as a referenced projection without ever entering the booked-cost ledger. exchange_health now surfaces a current statement with payment_recognition=unknown as a settlement_awaiting_payment_join residual instead of booked cost. Adds CLI commands finhub ledger ingest-settlement / settlements. FIN-WP-0006-T01 is done; the workplan is finished. Reviewed all other open workplans for closeable work: FIN-WP-0004's only remaining task (T05) waits on an external provider fact from resource-control, and every FIN-WP-0005 task waits on operator/Steuerbüro confirmation or a non-production DATEV tenant. Neither has actionable in-repo work right now, so both move to status: blocked. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: sonnet Assistant-Process: 242919@bnt-lap001 Assistant-Session: 286d235a-1654-40ff-b8fd-eee4e2ff9ea6
3.5 KiB
| id | type | title | domain | repo | status | flavor | owner | topic_slug | created | updated | related | state_hub_workstream_id | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| FIN-WP-0005 | workplan | DATEV accounting adapter operations | financials | fin-hub | blocked | implementation | codex | financials | 2026-08-11 | 2026-09-27 |
|
58432770-da19-5b72-a946-cacbe1eb24ca |
FIN-WP-0005 — DATEV accounting adapter operations
Goal
Operationalize the provider-neutral accounting handoff selected in
FIN-WP-0002: DATEV Unternehmen online is the bookkeeping and document
authority, with Qonto as the preferred complementary invoice workflow and
managed DATEV transport where its capabilities are sufficient.
This workplan does not authorize fin-hub to issue invoices, assign legal invoice numbers, execute payments, or perform bookkeeping.
Confirm operational capabilities and ownership
id: FIN-WP-0005-T01
status: wait
priority: high
state_hub_task_id: "7cdda85d-cdd6-544c-b873-f27ec7ef448d"
With the operator and Steuerbüro, confirm the enabled Qonto plan, DATEV tenant and services, customer/tax master-data owner, invoice workflow, document retention policy, correction procedure, and required structured fields. Record which capabilities use Qonto's managed DATEV services and which require a direct DATEV integration. Route credentials only after this selection.
Status 2026-09-27: reviewed for closeable work. T01 requires a live
confirmation from the operator and Steuerbüro (plan/tenant selection,
master-data ownership, retention and correction policy) that no in-repo
change can substitute for; set to wait pending that conversation. T02-T04
already wait on T01 and a non-production DATEV tenant, so no task in this
workplan is actionable from the repo alone right now.
Implement the selected transport
id: FIN-WP-0005-T02
status: wait
priority: high
state_hub_task_id: "c2e0b529-43d5-5c17-af07-8140ae98d4c2"
After T01, implement the authorized transport behind the existing adapter contract. Prefer the managed Qonto-to-DATEV route when it preserves the full required record; otherwise use the approved DATEV API/export surface. Keep authentication and network side effects outside pure payload preparation.
Validate legal and bookkeeping completion
id: FIN-WP-0005-T03
status: wait
priority: high
state_hub_task_id: "c6b3177a-a9a3-5a91-9917-ffca94f77d7a"
In a non-production tenant, demonstrate customer and tax completion, legal invoice numbering and issuance by the authorized external system, document arrival in DUO, bookkeeping visibility, exception handling, and correction or cancellation flow. Do not treat transport acceptance as bookkeeping proof.
Certify upgrades and rollback
id: FIN-WP-0005-T04
status: wait
priority: medium
state_hub_task_id: "0be9e6cf-504f-5c63-a31c-12a9390fc79e"
Golden-test and dual-run the selected adapter against the same stable billing basis IDs. Reconcile counts, amounts, currencies, exceptions, and evidence references; record provider and adapter versions, cutover approval, monitoring, and rollback procedure.
Acceptance
- The Steuerbüro and operator have accepted the responsibility matrix and selected transport.
- Provider credentials are routed through their proper custodian and are absent from Git, artifacts, and logs.
- A non-production end-to-end transfer is reconciled in DATEV.
- Issuance, payments, and bookkeeping remain outside fin-hub.
- Upgrade, breaking-migration, monitoring, and rollback controls are tested.