# Subscription Metric Effective-Date Crosswalk

Tie subscription metric movements to source effective dates instead of mixing event, invoice and payment timestamps.

## Scope
Preparation and review only. No account action or professional decision.

## Inputs
Subscription IDs; change events and effective dates; metric definition; invoices/payments dates; observation cutoff/timezone.

## Workflow
1. Choose the supplied metric date basis explicitly; retain all original timestamps.
2. Map each movement to that basis and identify events effective beyond cutoff.
3. Keep invoice and cash dates visible but do not substitute them for metric dates.
4. Return reconciled movements and held unknown effective dates; no subscription or billing change.

## Output contract
subscription | event_time | effective_time | invoice_time | cash_time | metric_basis | included_period | hold

## Fictional acceptance test
Fictional plan change loggedOct 8 but effectiveNov 1 stays outside anOctober effective-date metric. PaymentOct 9 does not move the change intoOctober; missing effective time is held.

## Review gates
Keep original values, source IDs and version dates. Unknown facts stay held. Use qualified review for hiring, legal and accounting conclusions. No send, share, sign-in, scheduling, ledger change or payment. Fictional contract review is not a live account compatibility test.

## Method source
https://docs.stripe.com/data/analytics/supported-metrics

Checked October 8, 2026. Oct8 live GSC through Oct5: marketing copilot 37 impressions, Planable/Claude 33 and Planable/ChatGPT 23, campaign brief 12 and reports 11. Marketing/social topics follow these parent-query leads; other professions follow method-source workflow needs, not exact query measurements. Exact monthly volume is unmeasured.