VALID ≠ READY
Valid XML.
Missing order context.
Technical validation cannot know your customer's order. Check the buyer reference, endpoint, PO, supplier number and line references against requirements you supply.
Why a green technical status is not enough
A standard can require a reference to exist without knowing whether it belongs to the intended customer or order. A recipient can reject a syntactically correct reference that is stale, belongs to another order or was entered in the wrong field.
Run a recipient preflight
Validate locally, select or create the recipient, add required fields and expected values from the actual order, then confirm that the configured checks cover your current customer requirements. Readiness checks exact values; it does not invent missing information.
A scoped result you can reproduce
The report includes selected technical versions, configured checks, profile version, timestamp, document hash and repair audit. READY means those checks passed. Unconfigured requirements and network acceptance remain outside the result.