Invoice issuance vs. fiscal acceptance
Two authoritative state domains
Section titled “Two authoritative state domains”| Question | Read model | Meaning |
|---|---|---|
| Was a commercial invoice issued? | Invoice resource | Number and immutable issued snapshot. |
| What happened to the provider registration? | Fiscal status / operation resource | Queued, submitted, accepted, rejected, or unresolved outcome. |
| Was a document generated? | Invoice document resource | Document processing state and stored artifact metadata. |
Do not conflate fields
An invoice’s issuance-policy field can be NotRequired while a provider operation has its own Accepted outcome. Display the dedicated fiscal operation/status projection.
Safe integration behavior
Section titled “Safe integration behavior”Persist invoice and operation IDs separately. Refresh provider status using the read APIs or signed webhook events. If a response is lost after a possible transmission, preserve an indeterminate state and reconcile before any retransmission.