Skip to content
Testaroo
md4.3 KB

Juniper Workspace Cloud: Document set README

Document set README for Juniper Workspace Cloud. 24 files, 1 of them intentionally invalid, with the reconciliation identities and the exact defect in each broken file named in full.

Preview, first 50 linesmd
# Juniper Workspace Cloud: subscription billing, dunning, usage and revenue documents

A full subscription billing cycle: the invoice register across three months, the September invoices with a mid-cycle upgrade and downgrade prorated to the day, the dunning sequence that ends in a cancellation, metered usage billed on a three-band rate card, the revenue recognition schedule that carries an annual prepayment as deferred revenue, and the MRR movement report that has to reconcile to all of it.

All parties, amounts and identifiers are fictional. Fixed snapshot: 2026-09-08. Every record is derived from the shared operating model `saas-subscriptions`, so identifiers join across this set and across the business-kit fixtures that use the same model.

## Reconciliation identities this set asserts

- The recurring lines of the September invoices sum to 235.00, which is opening monthly recurring revenue.
- Opening 235.00 plus expansion 50.00 minus contraction 30.00 minus churn 19.00 equals closing 236.00.
- Closing MRR also equals the sum of the end-of-cycle plan rates in mrr-closing-by-account.csv, 236.00.
- Every proration amount equals plan_rate * 15 / 30 rounded half up.
- The tiered rate card applied to the raw usage events reproduces the 24.54 usage bill exactly.
- Cumulative billings equal cumulative recognition at 1963.20 by the end of the schedule, and the deferred balance returns to 0.00.

## Files

| File | Format | Validity | What it is |
| --- | --- | --- | --- |
| `invoice-register.csv` | csv | valid | Subscription invoice register |
| `invoice-lines-2026-09.csv` | csv | valid | September invoice lines with mid-cycle proration |
| `invoices-2026-09.json` | json | valid | September invoices with proration as JSON |
| `invoice-register-wide.csv` | csv | valid | Invoice register widened to 40 columns |
| `mrr-movement.csv` | csv | valid | MRR movement report |
| `mrr-closing-by-account.csv` | csv | valid | Closing MRR by account |
| `mrr-movement.json` | json | valid | MRR movement report JSON |
| `mrr-movement-unreconciled.csv` | csv | invalid | MRR movement report that does not reconcile |
| `dunning-sequence.csv` | csv | valid | Dunning sequence |
| `dunning-sequence.json` | json | valid | Dunning sequence JSON |
| `payment-attempts.csv` | csv | valid | Failed payment attempt log |
| `usage-events.csv` | csv | valid | Raw metered usage events |
| `usage-rate-card.csv` | csv | reference | Tiered usage rate card |
| `usage-billing-tiered.csv` | csv | valid | Tiered usage bill |
| `usage-billing-tiered.json` | json | valid | Tiered usage bill JSON |
| `revenue-recognition-schedule.csv` | csv | valid | Revenue recognition and deferred revenue schedule |
| `revenue-recognition-schedule.json` | json | valid | Revenue recognition schedule JSON |
| `plan-catalog.csv` | csv | reference | Subscription plan catalog |
| `subscription-events.csv` | csv | valid | Subscription lifecycle events |
| `invoice-INV-2609-02-proration.pdf` | pdf | valid | Mid-cycle upgrade invoice PDF |
| `annual-contract-invoice-INV-ANN-01.pdf` | pdf | valid | Annual contract invoice PDF |
| `billing-reconciliation.json` | json | reference | Billing reconciliation assertions |
| `subscription-billing.xlsx` | xlsx | valid | Subscription billing workbook |

## Deliberate defects

These files are broken on purpose. Each one is a single named mutation of a correct file in the same directory, so a parser under test can be checked against both.

- **`mrr-movement-unreconciled.csv`** The movement rows sum to 246.00 but the closing row states 236.00, an unexplained -10.00 difference. The contraction row is also internally inconsistent: Team 49.00 to Basic 19.00 is -30.00, not -20.00.

## Notes and limits
… 56 lines total: download for the full file.

Specifications

Document Set
saas
Industry
software
Source Kit
saas-subscriptions
Synthetic
true
As Of
2026-09-08
Documented Files
24
Documented Defects
1

Testing contract

Reference control
Scenario
Read the README before using the set, then check that every filename it lists exists in the same directory and that the defect list matches the files marked invalid.
Expected result
The file table lists 24 entries including this README, and the deliberate-defect section names 1 file(s). The reconciliation section states the arithmetic identities the valid files satisfy exactly.

What is a .md file?

Markdown (MD) is a lightweight plain-text markup language that uses simple punctuation conventions to denote headings, lists, links, emphasis, and code. It is designed to be readable as-is and to convert cleanly to HTML. It is widely used for documentation, READMEs, and content authoring.

How to use this file

Use an example Markdown file to test parsers and renderers, verify GitHub-Flavored Markdown extensions like tables and fenced code, and exercise HTML-conversion pipelines.

How to use this file for testing

“Juniper Workspace Cloud: Document set README” is a deterministic Testaroo fixture for Data import. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: MD · 4,384 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.

Document fixtures list their internal structure (pages, fields, tracked changes, embedded objects) in the spec table. Test extractors, converters, and OCR against that known structure, and compare searchable↔scanned or format-twin companions when present.

Code examples

import markdown  # pip install markdown

html = markdown.markdown(open("README.md").read())
print(html[:200])

Generated by generation/industry_documents.py. Free for any use, no attribution required, license.