Protected dates and late reconciliation effects

Verification Boundary

This browser suite exercises the live screens and public API observations recorded by its journey. It requires the coordinator’s isolated acceptance setup and serialized closing work.

What This Suite Proves

The journey refuses ordinary actions on a closed-date batch, moves eligible work into the following month and checks late reconciliation markers. Its absent-destination setup is not a general proof of that refusal.

What It Does Not Prove

The journey attempts to create a batch in a closed month before testing posting. The pinned persistence refuses that setup, so the later close-boundary chain is not established.

Real Dependencies and Test Doubles

The live console, Accounting APIs and authentication serve the run’s own business units and records. Fixture helpers also use CRM and the required payment infrastructure. This register does not claim those deployed dependencies were run.

Must Not Be Doubled

The public API authorization, close tasks, financial posting and retained records must remain real for the live acceptance outcomes.