# Juniper Workspace Cloud

Subscription accounts with status-aware recurring revenue, linked invoices and payments, and product usage.

All entities and transactions are fictional. Snapshot: 2026-09-08.

## Start with the linked model

1. Open operations.xlsx and review the Summary sheet. Source tables contain stable primary keys and declared references.
2. Change source values in the workbook to explore the calculated totals and editable chart.
3. Compare output values with expected-results.json. The JSON Schema checks types; primary-key uniqueness and joins also require the listed semantic checks.
4. Use invalid-records.json only in a local validation harness. Its three cases exercise duplicate keys, wrong types and an orphan reference.

## Included tables

| Table | Records | Primary key |
| --- | ---: | --- |
| accounts | 6 | account_id |
| invoices | 12 | invoice_id |
| usage | 18 | usage_id |
| tickets | 12 | ticket_id |
| ticket_events | 24 | event_id |
| service_reports | 3 | report_id |

## Expected totals

- Active monthly recurring revenue: 235.00 USD. Sum accounts.active_mrr over the included records.
- Paid invoices: 649.00 USD. Sum invoices.paid over the included records.
- Outstanding invoices: 19.00 USD. Sum invoices.outstanding over the included records.

## Platform mapping

primary-records.csv is a generic example table. It is not a native platform export. Where this kit includes a named profile, use that profile’s separate CSV and schema and review its compatibility level before uploading.

## Scope and assumptions

- MRR is the sum of active monthly plan rates at the snapshot date; cash receipts are reported separately.