Billing and payments

Understand billing and payments in Spaces

Products and Prices define what a customer purchases. A purchase can create a one-time Booking or a Subscription, after which the applicable payment and invoice flow records the commercial activity for the operator.

Payment methods can change how payment is confirmed and where financial records are managed, so not every purchase follows the same path.

Where billing is configured

Product and Price settings define the amount, purchase cadence, billing mode, cancellation policy, and whether a recurring Price supports auto-renewal. Organization settings provide the shared billing cycle, invoice due date, connected payment or accounting services, and bank details used by applicable workflows.

Billing mode, billing cycle, and due dates

Skedular generates the first Subscription invoice when the Subscription starts for both Upfront and In arrears billing. Subsequent Upfront invoices are generated when the next Subscription purchase period starts. Subsequent In arrears invoices follow the Organization's billing cycle.

The billing cycle controls when applicable billing activity is processed. The invoice due date is separate and controls when a generated invoice must be paid. These settings are separate from the Product purchase cadence and the recurrence of Booking instances.

Billing for Bookings and Subscriptions

One-time Booking purchases have their own payment and invoice state. Subscriptions create recurring Booking instances and may create additional invoices as each billing period is processed. Payment or invoice state does not replace the lifecycle state of the Booking or Subscription.

See Bookings and Subscriptions for the operational workflows.

Payment methods and confirmation

Stripe supports online card payment where connected. Bank transfer supports operator-managed payment workflows using the Organization's bank details. Xero supports invoicing and accounting workflows when connected. Payment status is separate from the Booking or Subscription lifecycle.

Depending on the payment path, operators may see Pending, Confirmed, or Rejected payment states. Available actions include Confirm Booking Payment, Reject Booking Payment, and Make Booking Payment Not Required where the workflow permits them.

Receiving payments

Card payments are processed through the Organization's connected Stripe account. Bank transfers move directly from the Customer to the Organization's configured bank account, while Skedular tracks the status and operator confirmation. Xero supports invoice delivery, payment recording, and reconciliation when the Organization's accounting connection is configured. Skedular does not hold Customer card or bank-transfer funds.

Invoices, cancellations, and refunds

Invoice handling depends on the configured financial path: Skedular records the applicable invoice activity, Stripe processes connected card payments, and Xero can manage connected invoicing and accounting workflows. Bank-transfer invoices follow the Organization's instructions and manual confirmation path. Cancelling a Booking or Subscription does not automatically cancel generated invoices, remove outstanding balances, reverse completed payments, or create a refund. Refunds are a separate financial decision.

Use Refunds for detailed refund handling.