--- title: Revenue Reports description: "Eventixa Pro exposes financial information at the individual booking level, including booking totals, discounts, payment details, transaction information, and WooCommerce order data where applicable. The current Reports module does **not** include a dedicated aggregated Revenue Report that automatically calculates total…" url: "https://eventixawp.com/docs/revenue-reports/" updated: "2026-09-26" category: Reports --- # Revenue Reports Eventixa Pro exposes financial information at the individual booking level, including booking totals, discounts, payment details, transaction information, and WooCommerce order data where applicable. The current Reports module does **not** include a dedicated aggregated Revenue Report that automatically calculates total event revenue across a selected period. > **Available in:** Eventixa Pro > **Primary Location:** Eventixa → Reports → Bookings > **Related Sections:** Bookings, Operational Reports, Exports > **Important:** Aggregated revenue totals are not currently provided as a dedicated Eventixa report. ## Does Eventixa Have a Revenue Report? The current Eventixa Reports implementation does not provide a dedicated **Revenue Report** that calculates totals such as: - Gross Revenue - Net Revenue - Revenue by Event - Revenue by Ticket - Revenue by Payment Gateway - Revenue by Date - Average Order Value Instead, Eventixa exposes financial fields within individual booking records and booking exports. This means you can access the underlying financial information, but Eventixa does not currently aggregate those values into a dedicated revenue dashboard. ## Where Financial Data Is Available The primary location for financial reporting data is **Eventixa → Reports → Bookings**. Depending on the booking workflow and integrations, booking rows can include payment and transaction information such as: - Booking Number - Booking Date - Event - Ticket(s) - Quantity - Coupon - Booking Status - Payment Status - Payment Method - Transaction ID Additional monetary fields can be available through the booking reporting and export system. ## Booking-Level Financial Fields Eventixa's booking reporting system can expose fields such as: - Subtotal - Discount - Tax - Final Total - Currency - Payment Method - Payment Status - Transaction ID - External Payment ID These values belong to individual booking records. ## Subtotal **Subtotal** represents the booking amount before applicable discounts or adjustments reflected in the booking data. For example: **Subtotal:** $100.00 ## Discount **Discount** represents the discount amount applied to the booking. For example: **Subtotal:** $100.00 **Discount:** $20.00 The discounted amount contributes to the final booking total. ## Tax Where the payment workflow provides tax information, Eventixa reporting can expose the booking's **Tax** value. Tax availability depends on the checkout/payment integration used for the booking. ## Final Total **Final Total** represents the final booking amount stored in the reporting data after applicable discounts and other adjustments. For example: **Subtotal:** $100.00 **Discount:** $20.00 **Final Total:** $80.00 When tax is handled through an integrated checkout such as WooCommerce, the corresponding financial data can also be available. ## Currency Booking reports and exports can include the **Currency** associated with the transaction. This is especially important if your Eventixa installation processes bookings using more than one currency or integrates with an external commerce system. ## Payment Method The **Payment Method** field identifies the method used for the booking. Depending on your Eventixa configuration, this may include: - PayPal - Stripe - Local / Offline - WooCommerce Other supported methods may also appear according to the actual booking data. ## Payment Status The **Payment Status** field shows the current payment state associated with the booking. Use this when deciding whether a booking should be considered successfully paid. A booking appearing in a report does not automatically mean the payment was completed. ## Booking Status The **Booking Status** is separate from Payment Status. Always review both fields when analyzing financial booking data. For example, a booking may have one payment state while its booking lifecycle is in another state. ## Transaction ID The **Transaction ID** field can be used to associate an Eventixa booking with its payment transaction. This is useful when reconciling Eventixa data with your payment gateway. ## External Payment ID Booking exports can also include an **External Payment ID** where one exists. This can help when matching Eventixa booking records with an external payment provider or order system. ## Coupon Information The Bookings Report includes coupon information for applicable bookings. This lets you identify which bookings used a discount code and analyze the financial effect outside Eventixa if needed. ## Revenue Data and Free Tickets Free tickets can appear in booking and registration reports even though their financial value is zero. Do not treat ticket registration count as revenue. For example: **100 free registrations** does not mean the event generated revenue from those registrations. ## Revenue Data and RSVP RSVP registrations are also not equivalent to paid revenue. An RSVP registration may indicate **Going** or **Not Going**, but it does not necessarily represent a payment transaction. Use Registration Type and payment information together when reviewing financial booking data. ## Revenue Data and Offline Payments Local or Offline Payment bookings may appear in Eventixa reports with the appropriate payment method. Because payment can be handled outside the website, the report should be interpreted according to the booking and payment statuses recorded in Eventixa. Do not assume that every Offline booking shown in the report has already been financially settled outside the system. ## Revenue Data and PayPal PayPal bookings can include payment status and transaction information. Use the Eventixa booking record together with the PayPal transaction data when financial reconciliation is required. ## Revenue Data and Stripe Stripe bookings can include payment status and transaction information when Stripe is active through Eventixa Pro. Use the Eventixa transaction references when reconciling the booking with Stripe. ## WooCommerce Financial Data When WooCommerce checkout is used, Eventixa Reports can expose additional WooCommerce order information. This can include: - Subtotal - Discount - Tax - Final Total - Currency - WooCommerce Gateway - WooCommerce Order - Transaction ID WooCommerce is therefore especially useful when you need detailed commerce-level reporting around Eventixa bookings. ## WooCommerce Order The report can include the related **WooCommerce Order** reference. This lets you move from Eventixa booking analysis to WooCommerce order management when detailed financial information is needed. ## WooCommerce Gateway The **WooCommerce Gateway** field identifies the gateway used to pay for the associated WooCommerce order. This may differ from Eventixa's native gateway workflow because WooCommerce manages the actual checkout transaction. ## WooCommerce Tax and Totals WooCommerce reporting integration can provide detailed totals including tax, discounts, and final order totals. These values come from the related WooCommerce order data. ## Failed and Refunded WooCommerce Bookings Eventixa's WooCommerce reporting integration includes configuration controlling whether failed/refunded WooCommerce bookings are counted in applicable reports. Review that setting when comparing Eventixa booking data with WooCommerce financial reports. ## Payment Status Breakdown Under **Eventixa → Reports → Operational Reports**, the **Payment Status Breakdown** report groups booking activity by payment status. It can show: - Payment Status - Bookings - Tickets This report counts booking activity but does not calculate money totals. ## Payment Method Breakdown The **Payment Method Breakdown** report groups bookings according to their payment method. It can show the number of Bookings and Tickets associated with each payment method. For example: **Stripe — 45 bookings** **PayPal — 30 bookings** **Offline — 10 bookings** These are count-based values and are not revenue totals. ## Coupon Usage Report The **Coupon Usage** Operational Report groups coupon activity. It can show values such as: - Coupon - Bookings - Tickets This helps you understand coupon usage frequency but does not calculate total discount value or net revenue across all bookings. ## Revenue vs Booking Count Booking counts should never be interpreted as revenue. For example: **100 bookings** could include: - Free bookings - Paid bookings - Discounted bookings - Refunded bookings - Offline bookings - RSVP registrations Always review the underlying financial fields before calculating revenue. ## Revenue vs Ticket Quantity Ticket quantity is also not revenue. For example: **500 tickets registered** does not tell you how much money was collected. Those tickets may have different prices, discounts, payment states, or registration types. ## Revenue vs Payment Status A Payment Status Breakdown can tell you how many bookings are in a particular payment state, but it does not calculate the value of those bookings. For financial totals, use the detailed booking data or your payment platform's reporting tools. ## Booking Date Range The Bookings Report uses the **booking created date** for its date filtering. This means the report period reflects when bookings were created, not when the associated event occurs. For example, a booking created in September for an event taking place in December belongs to the September booking report period. ## Filter Financial Booking Data You can narrow the Bookings Report using filters such as: - Date Range - Event - Occurrence - Ticket - Registration Type - RSVP Response - Booking Status - Payment Status - Payment Method - Coupon - Customer or Booking search These filters can help you isolate the booking data you want to export and calculate externally. ## Filter by Event Select an **Event** when you want financial booking data related to one event. You can then further narrow the results by Ticket or Occurrence. ## Filter by Ticket Use the **Ticket** filter when you want to analyze financial information associated with a specific ticket type. For example, you could isolate all bookings for **VIP Pass** before exporting them for further calculation. ## Filter by Occurrence For recurring events, use **Occurrence** to isolate bookings associated with one recurring date. This is important when the same event sells tickets across multiple occurrences. ## Filter by Payment Status Use **Payment Status** when you need to separate financially completed bookings from other payment states. This is particularly important when preparing data for external revenue calculations. ## Filter by Payment Method Use **Payment Method** to isolate bookings processed through a particular gateway. For example, you can filter for Stripe bookings before comparing those records with your Stripe dashboard. ## Filter by Coupon Use the Coupon filter to review bookings associated with a specific discount code. This can help when investigating a promotion or campaign. ## Export Financial Booking Data The most flexible way to work with Eventixa financial information is through the **Bookings** export. Go to **Eventixa → Reports → Exports** and select **Bookings**. ## Booking Export Fields The Bookings export can include fields such as: - Booking ID - Booking Number - Booking Date - Booking Time - Event - Occurrence - Tickets - Quantity - Customer information - Coupon - Subtotal - Discount - Final Total - Currency - Booking Status - Payment Status - Payment Method - Transaction ID - External Payment ID - Booking Notes WooCommerce integrations can add further commerce-related fields. ## Choose Only Financial Columns When creating a Bookings export, you can select only the columns relevant to financial analysis. For example: - Booking Number - Event - Ticket - Quantity - Subtotal - Discount - Final Total - Currency - Payment Status - Payment Method - Transaction ID This produces a cleaner CSV for external analysis. ## Preview Before Export Use **Preview Export** before generating the CSV. The preview shows the number of matching records and the first 20 matching rows so you can verify that your filters and selected columns are correct. ## Export All Filtered Results Use **All filtered results** when you need the entire financial booking dataset matching your current filters. This is preferable to exporting only the current page when calculating totals outside Eventixa. ## Background Export Large Bookings exports can be generated in the background. Completed files appear in **Export History** and remain available for download until they expire. ## Export Expiration Background export files expire automatically after **48 hours**. Download financial exports you need to retain before the expiration period ends. ## Calculating Revenue Outside Eventixa Because Eventixa currently does not aggregate revenue, you can export the booking data and calculate totals in a spreadsheet. For example, you can sum the **Final Total** column after filtering to the payment and booking states appropriate for your accounting workflow. Eventixa itself does not decide which records should count as recognized revenue. ## Be Careful with Refunds A booking marked Refunded should not automatically be treated the same as an active paid booking when performing external revenue calculations. Review both booking and payment statuses when calculating financial totals. ## Be Careful with Failed and Cancelled Payments Failed, cancelled, or expired payment records can exist in reporting data depending on the workflow and selected filters. Exclude or include them according to the financial calculation you are performing. ## Manual Refunds Eventixa can support a manual refund workflow where a booking is marked Refunded after the administrator handles the actual payment refund externally. Because the payment reversal can occur outside Eventixa, your payment provider remains important for authoritative financial reconciliation. ## Payment Gateway Reports For gateway-specific financial reporting, use the reporting tools provided by the payment system itself. Examples include: - PayPal transaction reports - Stripe payment reports - WooCommerce Analytics - Offline accounting records These systems are better suited to authoritative settlement and payout reporting. ## Eventixa Reports vs Accounting Reports Eventixa Reports are designed primarily for event operations and booking management. They are useful for: - Identifying bookings - Reviewing payment states - Reviewing payment methods - Reviewing transaction IDs - Reviewing booking totals - Exporting financial booking data They should not be treated as a complete accounting ledger. ## WooCommerce Analytics If Eventixa bookings use WooCommerce checkout, WooCommerce Analytics can provide broader financial reporting. This may include sales totals, orders, refunds, taxes, products, coupons, and payment-related commerce data depending on your WooCommerce configuration. Use Eventixa Reports for event context and WooCommerce for commerce-focused analysis. ## Example Financial Review Workflow Suppose you want to analyze financial booking data for **Community Science Festival**. A useful workflow is: 1. Go to **Eventixa → Reports → Bookings**. 2. Select the required Date Range. 3. Select **Community Science Festival**. 4. Filter by Payment Status if needed. 5. Filter by Booking Status if needed. 6. Review individual booking totals and payment methods. 7. Open **Exports**. 8. Select **Bookings**. 9. Apply the same filters. 10. Include the relevant financial columns. 11. Preview the export. 12. Export all filtered results. 13. Calculate financial totals in your spreadsheet or accounting system. ## Example Gateway Reconciliation Workflow To reconcile Stripe bookings: 1. Open the Bookings Report. 2. Select the required Date Range. 3. Set Payment Method to Stripe. 4. Filter to the payment states relevant to your reconciliation. 5. Export Booking Number, Final Total, Currency, Payment Status, and Transaction ID. 6. Compare the data with your Stripe transaction records. The same approach can be used with PayPal or another payment system. ## Example WooCommerce Workflow For WooCommerce-based Eventixa bookings: 1. Filter Eventixa Bookings to the relevant Event. 2. Review WooCommerce Order references. 3. Export financial fields if needed. 4. Open the corresponding WooCommerce orders. 5. Use WooCommerce Analytics or order reporting for aggregated commerce totals. ## Why Eventixa Does Not Label Counts as Revenue Operational reports such as Payment Method Breakdown and Payment Status Breakdown intentionally report Bookings and Tickets rather than money totals. This avoids presenting registration counts as financial revenue. ## Common Problems ### I Cannot Find a Revenue Tab This is expected because the current Eventixa Reports implementation does not provide a dedicated Revenue tab. Use the Bookings Report and Bookings export for booking-level financial information. ### Overview Does Not Show Revenue This is expected because the Reports Overview is focused on operational booking, ticket, attendee, and check-in statistics. ### Payment Method Breakdown Shows Bookings but No Money Total This is expected because Payment Method Breakdown is a count-based Operational Report. ### Ticket Sales Count Does Not Show Revenue This is expected because Ticket Sales Count measures registration quantities rather than financial totals. ### Coupon Usage Does Not Show Total Discount Amount The current Coupon Usage Operational Report focuses on booking and ticket counts rather than aggregated financial discount values. ### Final Total Is Missing Available financial fields depend on the booking/payment workflow and integrations used. WooCommerce-based bookings can provide additional order-level totals. ### Revenue Calculated from All Bookings Looks Too High Check Booking Status and Payment Status before calculating totals. Do not automatically include failed, cancelled, expired, or refunded transactions in a successful-payment total. ### Stripe or PayPal Totals Do Not Match Eventixa Export Compare transaction IDs and payment statuses and consider refunds, gateway fees, settlements, and transactions completed outside Eventixa. The payment provider should be used for authoritative payment reconciliation. ### Offline Payment Appears in the Report This is expected if the booking used Local / Offline Payment. The actual transfer of money may have happened outside Eventixa. ### WooCommerce Totals Differ Review the corresponding WooCommerce orders because WooCommerce controls the commerce transaction when its checkout workflow is used. ## Recommended Financial Reporting Workflow 1. Use Eventixa Reports to identify the relevant event bookings. 2. Filter by Event, Date Range, Booking Status, and Payment Status. 3. Review Payment Method and Transaction ID. 4. Export all filtered Booking records. 5. Include Subtotal, Discount, Final Total, Currency, and transaction fields. 6. Remove records that should not count toward your intended calculation. 7. Calculate totals externally. 8. Reconcile the results with the payment gateway or WooCommerce. 9. Use the payment provider or accounting system as the authoritative source for settlement reporting. ## Important Notes - Eventixa Pro exposes booking-level financial reporting data. - The current Reports module does not include a dedicated aggregated Revenue Report. - Reports Overview does not calculate revenue. - Ticket Sales Count is a count-based report, not a sales-value report. - Payment Status Breakdown and Payment Method Breakdown report booking/ticket counts rather than financial totals. - Booking reports can expose Subtotal, Discount, Final Total, Currency, Payment Method, Payment Status, and transaction information. - WooCommerce integrations can add Tax, Order, Gateway, and other commerce data. - The Bookings export is the primary Eventixa tool for external financial analysis. - Booking date filtering is based on booking creation date. - Financial calculations should account for failed, cancelled, expired, and refunded records. - Payment gateways and WooCommerce should be used for authoritative payment reconciliation. - Eventixa Reports should not be treated as a complete accounting ledger. ## Related Documentation - [Reports Overview](https://eventixawp.com/docs/reports-overview/) - [Event Reports](https://eventixawp.com/docs/event-reports/) - [Ticket & Registration Reports](https://eventixawp.com/docs/ticket-registration-reports/) - [Filtering Reports](https://eventixawp.com/docs/filtering-reports/) - [Payment Overview](https://eventixawp.com/docs/payment-overview/) - [Payment Statuses](https://eventixawp.com/docs/payment-statuses/) - [Transactions](https://eventixawp.com/docs/transactions/) - [Refunds](https://eventixawp.com/docs/refunds/) - [WooCommerce Payments](https://eventixawp.com/docs/woocommerce-payments/) - [PayPal Payment](https://eventixawp.com/docs/paypal-payment/) - [Stripe Payment](https://eventixawp.com/docs/stripe-payment/) - [Offline Payment](https://eventixawp.com/docs/offline-payment/)