bill/status reports a lifecycle event against one or more existing documents — an acknowledgement, an approval, a refusal. Each lines entry names the document it concerns and the status being reported.
Invopop usually creates status documents from workflow steps and from inbound network messages, so you rarely author them by hand.
Types
Status line keys
Eachlines entry carries a key naming the event being reported.
A rejection or a partial approval must also carry a
reason, and may carry an action suggesting what the recipient should do next.
Statuses have their own Console section. Where a regime tracks its own lifecycle flow, the statuses also appear in that app’s dashboard — France lists them on the E-Invoicing Flow 6 tab.
Regime requirements
France’s Chorus Pro Flow 6 lifecycle codes are the fullest worked example: each CDVProcessConditionCode maps onto a status document, except the payment codes which use bill/payment instead. Spain’s NO VERI*FACTU workflows also send status documents for supplier registration and summary events.