Payments, invoices and refunds

Financial configuration

Explicitly configure the selling legal entity and required invoice details. Check currency, tax configuration, payment method and document language on the selected release. An existing obligation’s seller must not silently change with later edition settings.

Rules for pricing, invoice payment, due dates and access come from the financial specification. Undefined or optional release points are not a general promise that invoice payment is always available.

Follow up payments

1. Open the correct order or obligation and establish the amount due.
2. Check the payment actually recorded and the obligation to which it is allocated.
3. Investigate partial payment, overpayment or uncertain provider outcomes.
4. Separately verify the effects on registration and ticket rights.

After a lost provider response, reconcile the actual outcome first. Do not blindly create a second payment attempt or refund. Use concrete operation/provider references in the appropriate management environment.

Invoices and corrections

An issued financial document must not be rewritten as if it never existed. Corrections and credit notes follow their designated workflow and retain their relationship with the original document.

A refund and ticket revocation/change are separate questions. Verify both outcomes. The full provider, document and refund chain was not executed in this screenshot pass; include it in financial acceptance testing.