Payments Table Overview

Edited

The Payments Table in Pitchbooking Manager provides a comprehensive view of all recorded payments over a selected date range. It includes summaries by payment method, product type, and revenue category, supporting accurate financial tracking and export.


Accessing the Payments Table

  1. Select the desired date range using the date picker.

  2. Use the Site/Location filter to select the relevant venue (e.g. All Sites or a specific facility).

  3. Click Search to generate the table.

  4. Use the ‘Get Payment Report’ button to export results as a CSV file.


Breakdowns Available

Payment Method Breakdown

Displays the total revenue and number of transactions by method:

  • Card

  • Cash

  • Stripe

  • Additional methods (e.g. Bank Transfer, Subscriptions) if used

Each method displays:

  • Number of transactions

  • Revenue amount

  • Percentage of total revenue

Product Revenue Breakdown

Summarises revenue by product category:

  • Event bookings

  • Custom Invoice Items

  • Other applicable types

Recurring / Non-Recurring Revenue

  • Recurring Total: Recurring payments processed (if applicable)

  • Non-Recurring Total: One-off payments within the date range


Order Table

Each payment record in the table includes:

  • Order ID (clickable for full details)

  • Booker name and user role

  • Total amount (with tax breakdown if applicable)

  • Payment method and invoice reference

  • Status (e.g. Success)

  • Time processed and the user who recorded the payment

Use the search bar to locate transactions quickly.

Note: Bookings created manually in the Manager Dashboard with the status ‘Unpaid’ will not appear until payment is recorded. Once marked as ‘Paid’, the booking is added to the Order Table.


Stripe Transactions

Clicking the Stripe link in the Payment Method column redirects to the corresponding entry in Stripe for more details. This applies only to Stripe payments.

Was this article helpful?

Sorry about that! Care to tell us more?

Thanks for the feedback!

There was an issue submitting your feedback
Please check your connection and try again.