fin-hub/workplans/FIN-WP-0006-internal-transfer-settlement.md

id	type	title	domain	repo	status	owner	topic_slug	created	updated	related	origin	origin_ref	state_hub_workstream_id
FIN-WP-0006	workplan	Consume resource-control internal transfer settlement	financials	fin-hub	proposed	codex	financials	2026-08-14	2026-08-14	FIN-WP-0004 RESOURCE-WP-0005	residual	RESOURCE-WP-0005	e9413a20-5b11-50ff-ba21-15215841cf11

FIN-WP-0006 — consume internal transfer settlement

Goal

Accept proposed internal transfer charges and credit-state records from resource-control without taking resource authority or creating a second ledger. Recognize internal payments as booked facts joined by financial_fact_id, financial_entity_id, and period.

Origin: RESOURCE-WP-0005-T07. Terms live in resource-control/docs/TermsOfResourceProcurement.md. Outbound shape: resource-control/schemas/settlement-statement.schema.json.

Boundaries

• resource-control owns transfer-price arithmetic, statements, and consumption mode.
• fin-hub owns booked provider cost, tax, recognized payments, and any later DATEV-facing internal settlement posting.
• A settlement statement is not booked spend.

T01 — Join proposed transfer charges

id: FIN-WP-0006-T01
status: todo
priority: high
state_hub_task_id: "9ef3fab5-51a6-57ef-8121-b9714298c502"

Document and implement the inbound join for resource-control settlement statements. Preserve financial_entity_id, period, terms_version, and statement identity. Reject any path that would post the statement as a provider invoice.

Done when an inbound fixture can be stored as a referenced projection and exchange_health shows statements lacking a payment join as a visible residual, not as booked cost.