Use multiple dates in the same Cloudbeds Insights report

Introduction

A Cloudbeds Insights report can include more than one date field. Most combinations work, but the result depends on what each date represents.

A guest may stay on one date, have a charge posted on another, receive an invoice on another, and have a payout processed later. Those events belong to the same reservation, but they are recorded separately and do not always line up row by row.

This article explains the main groups of dates, which combinations work together, why combining Stay Date with certain financial dates can leave summary figures blank, and what to use instead.

Table of contents

• Understand the main date groups
• Which dates can be used together
• Why Stay Date and money dates can leave values blank
• Which date fields are affected
• What to do instead

Understand the main date groups

Different date fields describe different events. Thinking about the event behind the date makes it easier to understand which fields will work together in the same report.

Which dates can be used together

Most date combinations are supported. The important distinction is whether the dates describe events that can be related accurately at the level of detail used in the report.

• Dates from the same group can be used together. For example, Service Date and Business Date both describe financial activity, while Check-In Date and Booking Date Time both describe events associated with the reservation.
• Reservation dates can be used with Stay Date. For example, revenue by Stay Date grouped by Check-In Date can be used for pace or length-of-stay analysis. The reservation date repeats across the nights of that booking.
• Reservation dates can also be used with money dates. Check-In Date and Check-Out Date can appear in a transaction-level report and repeat across the charges belonging to the reservation.

Why Stay Date and money dates can leave values blank

A booking can have several stay nights and several financial transactions, and those events do not necessarily happen on the same dates. For example, a payment can be taken after checkout, so its financial date falls outside the stay entirely.

When a report combines Stay Date with a money date such as Service Date, the report can contain date combinations that do not represent a direct relationship between a stay night and a transaction.

Transaction-level figures such as Debits can still appear on those rows because they are recorded for each individual transaction. A nightly summary figure such as Total Room Revenue cannot be accurately divided across both dates, so the affected cells show a dash.

The following example shows the behavior:

Total Room Revenue is populated at the Stay Date subtotal and overall total because room revenue belongs to a stay night. Only the rows that combine Stay Date with the financial date show dashes.

Which date fields are affected

The limitation applies when Stay Date is paired with dates tied to charges, payments, payouts, or invoices.

Dates to watch when used with Stay Date

• Charges: Service Date, Business Date, Transaction Date Time, Invoice Create Date Time
• Payments: Payment Schedule Date Time, Card Created Date Time, Chargeback Resolution Date Time
• Payouts: Payout Date, Payout Transaction Date
• Invoices: Document Date, Due Date, Document Created At, Document Updated At

This also includes the corresponding Property and UTC variants where those date fields are available.

Dates that work with Stay Date

• Check-In Date, Check-Out Date, Room Check-In Date, Room Check-Out Date
• Booking Date Time, Cancellation Date Time, Last Modified, Reservation Import Date Time
• Allotment Block Start, Allotment Block End, Allotment Block Release, Shoulder Start, Shoulder End
• Room Condition Last Updated
• Guest Date of Birth, Primary Guest Date of Birth, Document Issue Date, Document Expiration Date

What to do instead

If your report combines Stay Date with a money date and a summary figure shows dashes, choose the approach that best matches the analysis you need.

• Choose one date. Remove the second date when you need the summary figure displayed at its natural level.
• Build two reports. Create one report by Stay Date and another by the relevant financial date, such as Service Date. Each report can show the data correctly at its own level.
• Use a transaction-level figure. If you need both dates in the same report, use Debits or Transaction Amount instead of a nightly summary figure.

Related articles

Now that you understand how different date fields interact in Cloudbeds Insights, review these resources for more information about levels of detail and other field combinations that can affect report results:

• Understand levels of detail in Cloudbeds Insights reports
• Why nightly totals can't be split by transaction detail in Cloudbeds Insights