Subscription Renewal Cash-flow Calendar

How to use Subscription Renewal Cash-flow Calendar

Describe your own recurring contracts and a date window. Keep each original due-day anchor, apply the last effective price on each renewal, exclude renewals at or after the cancellation cutoff, and review monthly cash totals.

1. Use the example as the schema; replace its labels and entered model assumptions.
2. Describe your own recurring contracts and a date window. Keep each original due-day anchor, apply the last effective price on each renewal, exclude renewals at or after the cancellation cutoff, and review monthly cash totals.
3. Calculate, inspect the complete witnesses and limitations, then copy or download the JSON report.

Good to know

• 1–30 contracts with 1–20 strictly dated prices each; 1–500 generated renewals total. Inclusive window spans at most 3,661 dates. Day steps are 1–366; month steps 1–120. First due and all generated calendar dates must remain in 1900–9999. A contract scan is capped at 10,001 cycles.
• The initial price must already apply on firstDue; prices are nonnegative amounts with exact cents up to 1,000,000,000. Short months clamp the original day without drift. A null cancellation means no cutoff; equality with firstDue produces no renewals.
• Generic full-renewal scenario in one two-decimal unit. No live subscription, payment, cancellation, tax, refund, trial, service entitlement, notification, business-day adjustment, exchange rate or billing-platform emulation.
• Local calculation with no upload, input persistence or outside lookup. Model JSON is limited to 30,000 characters and 10,000 values. Decimal quantities are strings with up to six places; count fields use plain JSON integers. Exact fractions are capped at 8,192 bits. The complete JSON output is limited to 1,000,000 characters; approximate numbers preserve their stored values. Unsupported states fail explicitly.