Analyze revenue and collections

The Revenue & collections analysis wizard compares invoiced revenue and collected amounts over a period to link sales and cash flow. It covers sales tickets with at least one revenue line; aggregated amounts are limited to the chosen date range.

Important: invoicing and collections may not follow the same calendar. Correct date framing is essential to interpret gaps.

Open the wizard

1. From the dashboard, click Revenue & collections analysis.
2. Set a start date and end date.
3. Click Refresh to reload data.

“Revenue & Collections” view

This view shows in parallel:

• a chart of revenue over the period;
• a chart of collections over the period;
• reconciliation panels.

The Revenue detail menu breaks down the revenue pie chart by accounting nature or activity category.

Invoiced (incl. VAT) and collected amounts may not fall on the same dates; complement with exports for precise accounting — see Export data for accounting.

“Breakdown by resource” view

Choose Breakdown by resource for a table with two values per column: Invoiced (revenue incl. VAT) and Collected.

• Rows are resources (instructors, guides…); a No resource row groups the rest.
• Columns depend on grouping: by sales ticket, activity name, first activity category, or month.

Collections by resource: limitations

For collections, the tool allocates pro rata based on each resource’s share of revenue (incl. VAT) in the column — this is not payment-by-payment traceability. With tickets spanning multiple activities or multiple resources, displayed allocation may be approximate.

Best practices:

• Start with grouping by sales ticket for a careful reading of collections.
• Use the table CSV to check or archive amounts.
• For legal or contractual value, cross-check with detailed accounting exports.

For detail on limitations: Why are collections by resource approximate?.

Common issues

• Revenue / collections gap: widen or shift the date range depending on your goal (invoiced revenue vs cash collected).
• Inconsistent amounts per resource: check grouping and see the FAQ above.