Posting-time account resolution and preservation

Verification Boundary

The browser and API clients use the deployed development console and services with run-owned records. Skipped fixture steps do not count as executed behavior.

What This Suite Proves

The journey posts an invoice batch, checks configured and fallback accounts, changes setup and verifies existing posted accounts remain unchanged.

What It Does Not Prove

A successful run covers only asserted steps; skipped database work and recorded observations do not establish domain rollback, complete export delivery or remote compensation.

Real Dependencies and Test Doubles

The console, signed personas and development APIs are real dependencies. The run supplies its own unit, chart and records; unavailable infrastructure can skip a walk.

Must Not Be Doubled

Do not replace authentication, service responses, persistence, posting or workspace isolation with browser stubs when claiming a deployed lifecycle result.