Why nightly totals can't be split by transaction detail in Cloudbeds Insights

Introduction

Summary revenue and occupancy figures in Cloudbeds Insights are recorded at specific levels, such as per reservation, per room, or per night. Transaction-level fields describe individual charges associated with those reservations and nights.

One night can have one summary revenue figure but several charges with different transaction statuses, types, taxes, or other transaction details. Because there is no accurate way to divide the single summary figure among those individual charges, Cloudbeds Insights does not display the summary value on those detailed rows.

This article explains what you will see in the report, why the total remains correct, and which alternatives to use depending on the information you need.

Table of contents

• Why a summary figure cannot be split by transaction detail
• Example: Total Room Revenue and Transaction Status
• What to do instead
• Why Stay Date is not affected

Why a summary figure cannot be split by transaction detail

Fields such as Total Room Revenue represent summary values recorded at a broader level. Transaction-level fields such as Transaction Status, Transaction Type, Tax Type, and general ledger codes describe individual charges.

A single night can have several charges associated with it. For example, some charges may be Posted while others are Pending. The night's Total Room Revenue is still one figure, so there is no correct way to determine how much of that total belongs to each transaction status.

When you place transaction-level detail next to a summary figure, the summary figure shows a dash on the detailed rows and remains available where it can be calculated accurately, such as the total line.

Example: Total Room Revenue and Transaction Status

In this example, a room has 370 in Total Room Revenue across three nights. Charges associated with the stay have a mix of Posted and Pending transaction statuses.

Debits can be split by Transaction Status because Debits is recorded for each transaction. Total Room Revenue cannot be divided between Posted and Pending charges because it is a summary figure for the room nights.

The 370 Total Room Revenue shown on the total line is correct. The dashes simply prevent that figure from being assigned to transaction-level rows where there is no accurate split.

What to do instead

Choose the report structure based on whether you need transaction detail or the summary figure.

• Use Debits or Transaction Amount when you need transaction-level detail. These figures are recorded per transaction, so they can be broken down by fields such as Transaction Status, Transaction Type, or Tax Type.
• Remove the transaction-level field when you need the summary figure. Without the finer transaction breakdown, the summary value can display at the level where it is recorded.

Why Stay Date is not affected

Stay Date does not create the same issue. Breaking a summary figure down by Stay Date works, including for whole-stay figures such as Room Rate Total.

In those cases, the figure can be divided across the nights of the stay. The limitation described in this article applies to transaction-level detail, not to Stay Date itself.

Related articles

Now that you understand why summary figures cannot always be split by transaction detail, review this foundational guide for more information about how levels of detail affect field combinations throughout Cloudbeds Insights:

• Understand levels of detail in Cloudbeds Insights reports