Database checks for Adjust Allowance

Verification Boundary

The suite checks module persistence or service behavior against prepared PostgreSQL with scoped records.

What This Suite Proves

Correction values require a valid signed amount. Only existing or current months can be corrected. Refund cannot exceed an existing charge. Request references must match organization and month. Correction and audit move together. Combined bindings require every named suite; a component assertion alone does not establish the full experiment.

What It Does Not Prove

The suite does not establish browser behavior, deployed routing, live model quality or actual recipient inbox delivery.

Real Dependencies and Test Doubles

PostgreSQL, production correction validation, period movement and security audit persistence are real. A fixed clock selects the current month.

Must Not Be Doubled

Retain PostgreSQL constraints, transaction behavior and the production persistence or dispatcher path under test. A scripted provider must not replace accounting or authorization.