Product documentation

Booking Payments and Invoices

Purpose: This article explains how booking finances work in Administrate, including how invoices and payments relate to a booking, what financial state does…

Purpose: This article explains how booking finances work in Administrate, including how invoices and payments relate to a booking, what financial state does and does not mean operationally, and what to check when financial records affect booking behavior.

For the broader booking workflow, see Managing Bookings. For the domain overview, see Bookings Overview.

Invoices and payments do not define booking status

Invoices and payments describe financial state, not booking state. Do not assume a booking is confirmed, completed, or properly progressed through its lifecycle just because an invoice exists, has been paid, or is locked.

  • Creating or linking an invoice does not confirm a booking.
  • Paying an invoice does not guarantee that the booking status has changed.
  • Locked financial records can restrict what can be changed on a booking without changing the booking status itself.

This distinction matters because finance activity and operational lifecycle activity often happen alongside one another, but they are not the same thing.

How bookings, invoices, and payments are connected

When a booking has a linked invoice or payment record, certain booking actions may be influenced by the financial state. This helps keep booking, payment, and audit records consistent.

  • Some bookings generate invoices automatically.
  • Other bookings may be linked to invoices that were created separately.
  • The invoice state can affect what you are allowed to change on a booking.
  • The payment state helps explain financial progress, but not necessarily operational completion.

A useful way to review a booking with finance involved is to check these in order:

  1. Confirm the booking state.
  2. Confirm the invoice state.
  3. Confirm the payment state.

Common invoice states and their impact

Unpaid

The booking may remain editable, but some actions such as confirmation, rescheduling, or cancellation can be restricted depending on your configuration.

The booking may become partially or fully locked to preserve financial accuracy.

Locked

When an invoice is locked, related booking fields may become read-only to prevent inconsistencies between booking data and finance records.

What you can and cannot change

What remains editable depends on timing, permissions, and financial state.

  • Before payment or locking, most booking details are usually still editable.
  • After payment, edits may be limited to non-financial fields.
  • After locking, significant booking changes may be blocked entirely.

If you are trying to update or cancel a booking and the action is restricted, always check the invoice state before assuming the problem is with the booking itself.

An invoice exists but I cannot find or reconcile it

Start by confirming you are looking at the correct booking and reviewing the correct financial context. If visibility or record relationships appear inconsistent, continue with Booking Troubleshooting.

Payment status does not match expectations

Confirm which invoice the payment was applied to and whether a booking change, such as cancellation or editing, affected the expected financial outcome.

I need to change a booking but finance appears to be blocking it

Check whether the linked invoice is unpaid, paid, or locked. The financial state may be restricting the action you want to take.

Edge cases and exceptions

Financial locks can block booking actions

If a linked invoice is unpaid or locked, you may be unable to confirm, reschedule, or cancel the booking. In some setups, the booking status may not update as expected until the invoice state is resolved.

Payments do not always mean the booking is complete

A paid invoice does not necessarily mean the booking has finished or been completed. Booking completion may still depend on time elapsed, attendance tracking, or other downstream operational processes.

Cancellations and refunds are not always automatic

Cancelling a booking does not automatically issue a refund in every workflow. Refunds may need to be handled separately depending on how payments were processed and how your organization manages finance corrections.

Partial payments and split outcomes

Some bookings may have partial payments or multiple invoices. In those cases, booking behavior may differ depending on which records are paid, outstanding, or locked.

Legacy bookings and migrated financial data

Legacy bookings may be linked to historical invoices that follow different locking or update rules. Migrated data can make bookings appear locked earlier than expected or behave differently from newer bookings.

What to check when something does not look right

If a booking does not behave as expected and payments or invoices are involved, check the following before making changes:

  • whether there is a linked invoice
  • the invoice payment state
  • the invoice lock state
  • whether attendance tracking has begun
  • whether the booking came from a legacy or migrated workflow

These checks usually explain why a booking cannot be edited, cancelled, or moved through the expected operational path.

Where to go next