This commit is contained in:
Pablo Martin 2025-07-11 16:15:17 +02:00
parent 729d6d6db4
commit a256b48b01
630 changed files with 16494 additions and 0 deletions

View file

@ -0,0 +1,29 @@
# Revenue naming - 2024-09-30
**Goal**: agree on what we consider as “Revenue” in the different reporting areas. Clarify revenue splits and adapt naming conventions.
**Context:** Main discrepancy between “Finance Revenue” and “Data Revenue” is the fact of deducting/not deducting the Waiver Amount Paid back to Hosts
Current setup in Main KPIs Power BI Reporting
- **`Total Revenue`**
- **`Invoiced Operator Revenue`**, coming from Xero
- **`Invoiced Booking Fees`** (Booking net fees)
- **`Invoiced Listing Fees`** (Listing net fees)
- **`Invoiced Verification Fees`** (Verification net fees)
- **`Invoiced APIs Revenue`**, coming from Xero
- **`Invoiced E-Deposit Fees`** (E-deposit net fees)
- **`Invoiced Guesty Fees`** (Guesty net fees)
- **`Guest Revenue`**, coming from Backend + Xero
- **`Waiver Net Fees`**, coming from Backend
- **`Waiver Amount Paid by Guests`** - **`Waiver Amount Paid back to Hosts`** (Xero)
- **`Deposit Fees`**, coming from Backend
- **`Check-in Hero Amount Paid by Guests`**, coming from Backend
→ For **Invoiced Operator Revenue** and **Invoiced APIs Revenue**, `net` means `invoice` - `credit notes`
→ We also have measures of **Guest Payments** that do not deduct the **Waiver Amount Paid back to Hosts**.
→ We also compute **Host Resolutions Amount Paid** but these are NOT applied to any Revenue aggregation metric (standalone situation).
Link to Whiteboard: https://guardhog-my.sharepoint.com/:wb:/g/personal/pablo_martin_superhog_com/EYv55vSak_pNhU3ShjFgCvQBk35XD75oo1ozxAmhSFYWHg?e=KYr8bD