Skip to content
Novus Examples
csv577 B

Juniper Workspace Cloud: Dunning sequence

Dunning sequence for Juniper Workspace Cloud. The 6 escalation steps against invoice INV-10 for account ACC-04, the one invoice in the model carrying an outstanding balance of 19.00. Steps run 2026-09-01 to 2026-09-30: reminder, two card retries that fail on insufficient_funds, a final notice, a third retry that fails on do_not_honor, then cancellation. Each row's next_action_date equals the attempt_date of the following row, and the last row has none.

csv

text/csv

577 B
Document Set
saas
Industry
software
Source Kit
saas-subscriptions
Synthetic
true
As Of
2026-09-08
Rows
6

Binary csv: no in-browser preview. Download it above to open in a compatible application.

Specifications

Document Set
saas
Industry
software
Source Kit
saas-subscriptions
Synthetic
true
As Of
2026-09-08
Rows
6
Failed Attempts
3
Invoice Id
INV-10
Encoding
UTF-8

Testing contract

Expected to pass
Scenario
Replay the dunning sequence and check the ordering and the terminal state.
Expected result
Step numbers run 1 to 6 with strictly increasing attempt_date values; every next_action_date matches the next row's attempt_date; the balance_due stays at 19.00 throughout because no attempt succeeded; and the sequence ends in cancellation, which is the churn event dated 2026-09-30 on mrr-movement.csv.

What is a .csv file?

CSV (Comma-Separated Values) is a plain-text tabular format where rows are lines and fields are separated by commas, with quoting rules for values that contain delimiters, quotes, or newlines. It has no formal type system and depends on encoding and dialect conventions. It is the most portable format for tabular data exchange.

How to use this file

Use an example CSV to test parsers against quoting and embedded-delimiter edge cases, header handling, encoding detection, and import pipelines into databases or spreadsheets.

How to use this file for testing

“Juniper Workspace Cloud: Dunning sequence” is a deterministic Novus Examples fixture for Data import. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: 6 rows · UTF-8. 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.

Data fixtures document their exact quirks (delimiters, encodings, null handling, schema, and row counts) in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.

Code examples

import pandas as pd

df = pd.read_csv("dunning-sequence.csv")
print(df.head())
print(df.dtypes)

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