TL;DR: Monthly plans follow calendar-month anniversaries or fixed 30-day cycles depending on vendor—read terms. Annual plans add 365/366 days from last charge, not “same date next year” if vendor uses 52-week billing.
Calendar-month renewal
Subscribed Jan 31, next bill often Feb 28/29, then Mar 31—anniversary on last valid day of month. Adding “one month” repeatedly differs from adding 30 days each cycle—compare both in calculator when disputing unexpected charge date.
Fixed-interval 30-day cycles
Some SaaS bills every 30 days from signup—drifts relative to calendar months. Add 30 days from last invoice date iteratively to predict next three charges.
Annual renewal
Last charged 2025-03-01, annual plan → add 365 or 366 days depending on leap path, verify landing 2026-03-01. Some vendors charge 52 weeks (364 days)—one day drift yearly unless corrected in contract.
Free trial conversion
Trial 14 days from signup: add 14 to signup timestamp’s calendar date (date-only layer), set cancel reminder subtract 2 days before conversion if policy allows cancel until last trial day.
Grace periods and dunning
“Service suspended 10 days after failed payment” → add 10 to failure notice date for last good service day—calendar days unless terms say business days.
Proration mid-cycle
Upgrade mid-month: vendors prorate in cents; date calculators give cycle boundaries (start/end of current period) you plug into their formula—not replace it.
Credit card expiry alignment
Card expiring before renewal: subtract 30 from renewal to receive new card—logistics, not billing engine math.
Multi-subscription households
List each next renewal as ISO date via add-days from last charge per vendor rules. Sort ascending for cash-flow planning in shared spreadsheet.
Cancel-by deadlines
“Cancel 30 days before renewal” → subtract 30 from renewal date; between today and cancel-by shows remaining decision days.
Audit one statement
Pick one recurring charge this month, trace last invoice date forward with the same rule vendor cites, match statement within one day or open ticket with screenshot from Date Calculators.
Worked example: overlapping trials
Streaming trial 7 days, VPN trial 14 days from same signup date—two add operations from signup, two cancel-by subtract operations. Spreadsheet sorted by cancel-by date prevents surprise double charge week.
Annual plan renewal after leap year February signup—recompute with add-days, do not copy last year’s renewal date from email archive.
Price increase notices
“30 days notice before renewal price increase” → subtract 30 from renewal, compare notice email date with between-dates to validate compliance if disputing.
Family plan renewal alignment
Multiple subscriptions renew on different rules—calendar month vs 30-day—sort next renewal ISO dates ascending in shared family budget meeting; add-days from last charge per line item, never assume one rule fits all vendors.
Price protection “renew before increase” subtract notice days from increase effective date—between today and last day to renew at old price drives decision.
Gift card and promo expirations
Credit expiring add 90 days from grant email date—between today and expiry for urgency; inclusive “last day usable” often inclusive of expiry calendar day—read terms.
Hardware warranty vs subscription
Laptop warranty 365 days from purchase uses add-days from receipt; SaaS renewal may use calendar month—same household, different rules. Spreadsheet columns: vendor, rule type, last anchor, next ISO renewal.
Extended warranty offers “purchase within 30 days of device purchase”—between device purchase and today validates eligibility window.
Tax software and annual renewals
Tax prep annual renewal often Feb–Apr seasonal—do not assume 365-day cycle from last year’s arbitrary purchase date during promo window.
Chargeback and dispute windows
Card issuer chargeback windows often count calendar days from statement date or transaction date—read issuer PDF, subtract window from today to find last day to file. Between transaction and filing attempt validates eligibility.
Free trial converted by mistake: subtract cancel-by from renewal charge date using policy “within 30 days”—between charge and cancel request must fit window.
Annual subscriptions bought on sale: renewal may jump to full price on anniversary—add 365 from purchase to see renewal ISO date, set subtract-14 reminder for cancel-if-not-worth-it decision.
Household subscription audit quarterly
Every quarter, list subscriptions sorted by next renewal ISO date ascending, flag any landing on Feb 29 or month-end anomalies, and set cancel-by subtract 7 for trials you might drop. One hour prevents year-long unwanted renewals.
Bundle mobile carrier with streaming promo: two renewals, two rules—track phone bill cycle separately from streaming trial add-14 cancel-by; conflating them causes surprise charges when promo ends mid-cycle.
Hardware subscription bundles (phone + cloud storage) may renew on different anchors—split line items in budget sheet even when one invoice email bundles them.
Annual gym membership billed on join date anniversary drifts from calendar-month budgets—list separately from rent on first-of-month rhythm to avoid cash-flow surprise when both hit same week once per year.
Streaming family plan seat removal timing: some services prorate to next renewal, others immediate—between today and renewal shows decision window; read help center before removing teen profile day before rebill.
Annual software true-up audits compare license count to HR headcount on fixed ISO audit date—between hire dates and audit date identifies seats needing purchase, separate from subscription renewal add-365 math.
