A valid payload can still be unprojectable

Schema acceptance does not prove that an integration can project a payload into the fields required by the application. A schema may accept one location shape while the normalizer reads only alternate collection shapes, allowing receipt persistence to succeed while origin, destination, date, or time remain unavailable. Treat accepted, projected, and ready-for-creation as separate states. Before enabling creation, capture representative payload shapes and test that every accepted shape either projects the required fields or yields an explicit non-ready reason.