> ## Documentation Index > Fetch the complete documentation index at: https://learn.nexudus.com/llms.txt > Use this file to discover all available pages before exploring further. # Booking Charges and Billing > When Nexudus charges, invoices and collects payment for bookings, how booking due dates are set, and the booking payment settings. ## Overview A booking's price isn't invoiced the moment it's made. Nexudus first **charges** it, adding the price to the customer's account and using any credit, then includes the charge on an **invoice**, which is then **paid**. This page explains when each step happens and the settings that control it. To see how the price itself is worked out, see [Booking pricing and credit](/platform/operations/bookings/pricing-and-credit). ## Booking lifecycle | Status | Meaning | | - | - | | **Tentative** | Holds the slot while it waits for approval. Not charged. | | **Confirmed** | Confirmed, but not charged yet. | | **Charged** | The price has been added to the customer's account, and any credit used, but it isn't on an invoice yet. | | **Invoiced** | On an issued invoice. | | **Paid** | The invoice has been paid. | The booking form shows these steps at the top, with the current one highlighted. ## When charges are posted Nexudus charges bookings automatically. A booking is charged: * **After it ends** Every 23 minutes, Nexudus charges bookings that ended more than 5 minutes ago. * **Early, if the customer has credit that's about to expire** A few minutes after a customer's booking is made, changed or cancelled, Nexudus charges all their uncharged bookings up to the date their earliest credit expires, so the credit is used while it's still valid. For example, if a customer's credit expires on 15 June, a booking on 10 June is charged straight away. * **Straight away, if up-front payment is required** See [Pay when a booking is made](#pay-when-a-booking-is-made). * **When you save it**, if you tick **Calculate cost and post charges to customer account when this booking is saved** on the booking form. Nexudus only charges a booking automatically if it ends before the customer's next contract renewal, and gives up after 5 days. A booking that can't be charged, for example because no rate covers it, stays **Confirmed**, and admins who get [booking notifications](/platform/operations/bookings/notifications#notify-admins-about-bookings) are emailed. If a team shares credit, the expiry dates of the paying member's credit count too, so a team member's booking can be charged early. To charge a booking yourself, tick it in the bookings list and choose **Charge booking** from **Bulk actions**. To undo a charge that hasn't been invoiced, open the booking and select **Remove booking charges**. ## When bookings are invoiced Once charged, a booking goes on the customer's next invoice after its [due date](#due-dates). For members, that's usually their next contract renewal. It's invoiced sooner if: * **You invoice bookings as they end** See [Pay when a booking ends](#pay-when-a-booking-ends). * **Up-front payment is required** See [Pay when a booking is made](#pay-when-a-booking-is-made). To invoice a booking yourself, for example because a customer wants to pay in advance, open it and select **Invoice booking**, or tick bookings in the list and choose **Invoice booking** from **Bulk actions**. Any other pending charges on the customer's account are included on the same invoice. For a new booking, you can also tick **Invoice this booking when it is saved** ### Due dates A booking's charge has a **due date**, the date from which it can go on an invoice. Nexudus sets it using the first of these that applies: | Condition | Due date | | - | - | | **Calculate cost and post charges to customer account when this booking is saved** is ticked, or up-front payment is required for the customer | Straight away | | Bookings are invoiced as they end for the customer's type | When the booking ends | | The customer's plan sets **The charges for bookings made by members in this plan will be due:** to **A specific day of the month after the booking** | That day of the month after the booking ends. If it's the 28th or later, the last day of the month. | | The plan uses **When the booking ends** | When the booking ends | | The plan uses **When the booking was created** | When the booking was made | | The plan uses **When the next contract renews** (default) | The customer's next invoice date | | None of the above | When the booking starts | Set the plan option on the plan's **Pricing** tab. If the customer has several plans with different options, the first match in the order above is used. By default, the next invoice date includes recurring products as well as contracts. To only count contracts, turn on **Ignore recurrent products when calculating booking due dates** under **Settings → Features → Bookings and calendar settings → Charges & payments**. ## Booking payment settings ### Pay when a booking is made Go to **Settings → Features → Sign-up and checkout → Checkout** and, under **Bookings**: | Setting | Effect | | - | - | | **Require up-front payment for online bookings made by contacts** | Online bookings by contacts are charged and invoiced straight away, and payment is collected. | | **Require up-front payment for online bookings made by members** | The same, for members. | | **Cancel unpaid bookings requiring up-front payment after:** | How many minutes customers have to pay. Unpaid bookings are cancelled automatically after this time, and their charges removed. The default is 30. | Only bookings made by customers in the Members Portal or app are cancelled if unpaid. Bookings you create in the dashboard aren't. ### Pay when a booking ends In the same place: | Setting | Effect | | - | - | | **Invoice and collect payment for bookings made by contacts as they end** | Invoices each contact's booking at least 15 minutes after it ends, and collects payment. Only bookings that ended in the last 3 days are picked up. | | **Invoice and collect payment for bookings made by members as they end** | The same, for members. | | **Always calculate price and/or use credit as bookings are requested** | Lets credit from the customer's next billing period count towards a booking's price. It doesn't change when charges are posted. | With up-front payment, customers pay for every booking in a repeat series at checkout, on one invoice. With invoicing as bookings end, each booking in the series is invoiced separately after it ends. ### Charges and credit Go to **Settings → Features → Bookings and calendar settings → Charges & payments**: | Setting | Effect | | - | - | | **Portal and Passport App cancellation and change policy for invoiced bookings** | What happens when a customer cancels or changes a booking that's already been invoiced: **Invoiced bookings cannot be cancelled or changed by customers**, **Cancelling or changing an invoiced or paid booking will issue a credit note**, or **Cancelling or changing a paid booking will issue a refund** | | **Use available money credit to pay for products requested as part of bookings** | Lets money credit pay for booking products, not just the resource. | | **Reject bookings if customers do not have enough credit** | Stops customers booking when their credit doesn't cover the price. | | **Customers can request a quote instead of confirming a booking** | Lets customers ask for a price instead of booking straight away. | | **Ignore recurrent products when calculating booking due dates** | See [Due dates](#due-dates). | ## Cancelled bookings * **Not charged yet**: nothing to undo. * **Charged but not invoiced**: the charges are removed automatically. * **Invoiced or paid**: you choose whether to credit the invoice, refund it or leave it. See [Cancel a booking](/platform/operations/bookings/approve-and-cancel#cancel-a-booking). ## Related * [Bookings](/platform/operations/bookings) * [Booking pricing and credit](/platform/operations/bookings/pricing-and-credit) * [Invoices](/platform/finance/invoices) * [Plans](/platform/billing/plans) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.