Share receivable facts with Commerce
What It Does
Financial sharing is asynchronous and receiver configuration controls whether Commerce is actually called. Acknowledging an unconfigured batch leaves reconstruction as a separate concern.
The Flow
The numbered hops identify the participating services, synchronization boundary and evidence. Branch conditions in the frontmatter explain where preparation, completion and recovery diverge.
When Something Fails
Each hop records its rollback, retry or compensation boundary and the result visible to callers or operators. External outcomes can remain unresolved after local preparation commits; the listed recovery behavior defines what remains pending.
Open Design Questions
A working Commerce reconstruction path and agreement of its position view with receivable facts remain unproved.