Skip to content

Actual Reserved Revenue Report Documentation

Menu Location: Reports > Financial Reports > Actual Reserved Revenue

Access Level: Kiva Admin

Last Updated: 2026-03-01

Overview

The Actual Reserved Revenue Report provides historical tracking of reserved or pending revenue with time-based snapshots. This specialized monitoring tool helps you track revenue that has been committed but may not yet be fully processed, allowing you to forecast cash flow and understand your revenue pipeline.

Primary Functions:

  • Track reserved revenue with automated time-based snapshots
  • View historical reserved revenue trends with order-level details
  • Enable or disable automatic reserved revenue tracking
  • Manually trigger reserved revenue snapshots on demand
  • Filter and analyze reserved revenue data by date range

Page Layout

Header Section

  • Page Title: Displays "Actual Reserved Revenue Report"
  • Enable/Disable Toggle: Control automatic reserved revenue tracking
  • Run Now Button: Trigger an immediate reserved revenue snapshot
  • Clear Data Button: Remove all historical snapshot data

Main Content Area

The primary display shows a comprehensive table of reserved revenue snapshots with the following columns:

  • Timestamp: When the snapshot was taken
  • Reserved Revenue: The recorded reserved revenue amount at that point in time
  • Order Details: Individual order breakdowns that contribute to the reserved total

Filter Section

Date range controls allow you to focus on specific time periods for detailed analysis of reserved revenue patterns.

Reserved Revenue Tracking System

Understanding Reserved Revenue

Reserved revenue represents orders and commitments that have been made but may not yet be fully processed or delivered. This metric is critical for understanding your revenue pipeline and forecasting future cash flow.

What Counts as Reserved Revenue:

  • Future scheduled subscription orders
  • Pending payment processing
  • Orders in fulfillment but not yet delivered
  • Committed purchases awaiting completion

Why Track Reserved Revenue:

  • Forecast upcoming cash flow with greater accuracy
  • Understand the health of your revenue pipeline
  • Identify potential fulfillment or processing bottlenecks
  • Plan inventory and staffing based on committed revenue

Automatic Snapshot Feature

The system can automatically capture reserved revenue snapshots at scheduled intervals, providing a continuous record of your revenue pipeline without manual intervention.

How It Works: When enabled, the system periodically records the current reserved revenue total along with detailed order information, creating a historical timeline of your pending revenue.

Actions & Operations

Enabling Automatic Tracking

Purpose: Start automated reserved revenue snapshot collection

Steps:

  1. Click the "Enable Tracking" toggle at the top of the page
  2. Confirm the activation when prompted
  3. System begins automatic snapshot collection at configured intervals

Requirements:

  • Kiva Admin access level
  • Understanding of what constitutes reserved revenue in your system

Running Manual Snapshots

Purpose: Capture an immediate reserved revenue snapshot

Steps:

  1. Click the "Run Now" button in the header
  2. Wait for the system to process pending orders
  3. New snapshot appears at the top of the data table with timestamp

When to Use:

  • Before financial planning meetings
  • After making changes to subscription schedules
  • When investigating revenue pipeline questions
  • To supplement automatic tracking during critical periods

Clearing Historical Data

Purpose: Remove all existing reserved revenue snapshot data

Steps:

  1. Click the "Clear Data" button
  2. Carefully read the confirmation warning
  3. Confirm the deletion (this action cannot be undone)
  4. All historical snapshots are permanently removed

Warning: This permanently deletes all reserved revenue tracking history. Only use when resetting the tracking system or resolving data corruption issues.

Common Use Cases

Use Case 1: Cash Flow Forecasting

Goal: Predict upcoming revenue based on reserved orders

Steps:

  1. Run a current reserved revenue snapshot
  2. Review the order details to see delivery dates
  3. Group orders by week or month based on delivery schedule
  4. Use reserved revenue totals to forecast cash flow

Example: If your current reserved revenue snapshot shows $50,000 in pending orders, review the delivery dates in the order details. If $20,000 is scheduled for next week and $30,000 for the following week, you can plan cash flow accordingly.

Tips:

  • Compare reserved revenue to historical completion rates
  • Account for potential cancellations in your forecast
  • Run snapshots weekly for consistent forecasting data

Use Case 2: Pipeline Health Monitoring

Goal: Track whether your revenue pipeline is growing or shrinking

Steps:

  1. Enable automatic tracking for consistent data
  2. Review snapshots weekly or monthly
  3. Calculate the change in reserved revenue over time
  4. Investigate significant increases or decreases

Example: If Week 1 shows $40,000 in reserved revenue and Week 4 shows $25,000, this 37% decrease indicates a shrinking pipeline. Investigate whether this is due to increased cancellations, fewer new subscriptions, or faster order processing.

Use Case 3: Subscription Schedule Analysis

Goal: Understand how subscription timing affects revenue pipeline

Steps:

  1. Run snapshots before and after subscription billing cycles
  2. Compare reserved revenue levels across different cycle periods
  3. Identify patterns in how quickly reserved revenue converts
  4. Adjust subscription timing or marketing based on patterns

Tips:

  • Document subscription billing dates alongside snapshot timestamps
  • Look for weekly or monthly patterns in reserved revenue
  • Consider seasonal variations in subscription behavior

Filters & Search Options

Date Range Filtering

  • Start Date: Set the beginning of your analysis period
  • End Date: Set the end of your analysis period
  • Quick Select: Common periods like last 30 days, last quarter, last year

Data Display Options

  • Sort by Timestamp: Chronological or reverse chronological order
  • Revenue Range Filter: Show only snapshots within specific reserved revenue amounts
  • Order Count Filter: Filter by number of pending orders in snapshot

Troubleshooting

Reserved Revenue Decreases Unexpectedly

Symptoms: Reserved revenue drops significantly between snapshots without explanation.

Solutions:

  1. Check if a large batch of orders was delivered or completed
  2. Verify if subscription cancellations occurred during this period
  3. Review payment processing failures that may have removed orders
  4. Look for changes in subscription schedules that moved orders out

Common Causes:

  • Normal order completion and delivery
  • Subscription cancellations or pauses
  • Payment processing issues removing failed orders
  • Rescheduling of delivery dates

Snapshots Show No Reserved Revenue

Symptoms: Recent snapshots display zero or very low reserved revenue.

Solutions:

  1. Verify that customers have active subscriptions with future delivery dates
  2. Check if order creation processes are working correctly
  3. Confirm that the snapshot is capturing the correct order statuses
  4. Review if definition of "reserved" revenue changed

Check:

  1. Active subscription count in your system
  2. Upcoming delivery schedule in order management
  3. Order status criteria for reserved revenue
  4. System changes or updates that may have affected tracking

If Problem Persists: Contact Kiva Logic support with recent snapshot timestamps and your expected reserved revenue amount for investigation.

Historical Data Seems Incomplete

Symptoms: Gaps appear in snapshot history or data looks inconsistent.

Solutions:

  1. Verify automatic tracking remained enabled throughout the period
  2. Check if system maintenance occurred during gap periods
  3. Review if manual data clearing was performed
  4. Confirm snapshot schedule settings
  • Actual Total Revenue Report (actual-total.php) - Tracks completed revenue
  • MRR Reports (mrr-reports.php) - Monthly recurring revenue analysis
  • Admin Subscription Reports (admin-subscription-reports.php) - Subscription analytics
  • Future Demand Report (admin_reports.php) - Forecasts upcoming order volume

Typical Workflow:

  1. Reserved Revenue Report → Review pipeline → Future Demand Report → Plan inventory
  2. Notice pipeline decrease → Admin Subscription Reports → Investigate subscription health

Permissions & Access

Required Access Level: Kiva Admin

Access Level Capabilities:

  • Customer Service: No access to reserved revenue reporting
  • Manager: No access to reserved revenue reporting
  • Administrator: No access to reserved revenue reporting
  • Kiva Admin: Full access to all features including tracking control, manual snapshots, and data management

Restricted Features:

  • All Features: Require Kiva Admin level access

Best Practices

Tracking Strategy

  1. Enable automatic tracking for consistent historical data
  2. Run manual snapshots before major business decisions or planning sessions
  3. Maintain snapshot data for at least 12 months for trend analysis
  4. Document the business events that correlate with significant changes

Analysis Approach

  1. Compare snapshots from similar time periods to identify trends
  2. Calculate the ratio of reserved to completed revenue over time
  3. Track how quickly reserved revenue converts to completed revenue
  4. Use multiple data points rather than single snapshots for decision-making

Forecasting Best Practices

  • Account for historical cancellation rates when forecasting from reserved revenue
  • Consider seasonal patterns in order conversion timing
  • Cross-reference with completed revenue to validate forecast accuracy
  • Update forecasts weekly as new snapshots become available

Things to Avoid

  • ❌ Treating reserved revenue as guaranteed cash flow (cancellations happen)
  • ❌ Comparing snapshots without considering delivery date distributions
  • ❌ Clearing data without exporting for historical records
  • ❌ Making major decisions based on a single snapshot anomaly

Quick Reference Card

Task Action/Location
Start automatic tracking Click "Enable Tracking" toggle
Capture snapshot immediately Click "Run Now" button
View specific date range Set date filters and click Filter
Calculate pipeline change Compare reserved revenue between two snapshots
Forecast cash flow Review order delivery dates in snapshot details
Remove all historical data Click "Clear Data" (use with extreme caution)
Export snapshot data Use browser export or print functionality
Sort snapshots by date Click "Timestamp" column header

FAQs

How is reserved revenue different from total revenue?

Reserved revenue tracks committed orders that haven't been completed or delivered yet, while total revenue tracks completed transactions. Reserved revenue helps forecast future cash flow.

What happens to reserved revenue when orders are delivered?

When reserved orders are delivered and completed, they move from reserved revenue to total revenue. You'll see reserved revenue decrease and total revenue increase accordingly.

Should reserved revenue always be increasing?

Not necessarily. A healthy business shows reserved revenue converting to completed revenue regularly, which decreases the reserved amount. Look for consistent pipeline refilling through new orders.

Can I customize what counts as reserved revenue?

The definition of reserved revenue is configured by Kiva Logic. Contact support if you need to adjust which order statuses or types are included in reserved revenue calculations.

Why doesn't my reserved revenue match my subscription value?

Reserved revenue typically includes only orders scheduled for the near future (next few weeks), while total subscription value might represent months or years of recurring revenue. Check your system's reserved revenue definition.

Change Log

2026-03-01

  • Initial documentation created
  • All sections completed following template structure
  • Customer-focused language for Kiva Admin users

End of Documentation

For additional help, contact your system administrator or Kiva Logic support.