Data-layer swarm · Customer-Data-Graph Agent · Subscription-billing-ingestion skill · Build pillar · Published July 12, 2026
How to build multi-platform subscription billing ingestion
This guide explains how to architect the subscription-billing-ingestion skill on the customer-data-graph agent end-to-end at multi-platform multi-portfolio subscription operator scale: per-portfolio per-banner per-subscriber per-canonical-per-platform-connector-spec + per-canonical-per-plan-schema-normalization-spec + per-canonical-per-invoice-quality-scoring-spec + per-canonical-cross-platform-joining-spec + per-canonical-multi-LLM-pre-publish-check + per-canonical-FBC-feedback-loop + per-canonical-audit-trail + per-portfolio audit-trail.
Or take the 3-question shape diagnostic first — no email required.
What you will build
- Per-portfolio per-banner per-subscriber per-canonical-per-platform-connector-spec across per-Recharge + per-Smartrr + per-Stay-AI + per-Loop-Subscriptions + per-Ordergroove + per-Awtomic + per-Subbly + per-Chargebee + per-Stripe-Billing + per-Recurly + per-Zuora + per-ProfitWell + per-Maxio + per-NetSuite-SuiteBilling + per-Sage-Intacct-Subscription-Billing + per-Salesforce-Revenue-Cloud + per-canonical-16-billing-platform + per-OAuth-token-management + per-API-rate-limit + per-15-webhook-events (subscription created/updated/paused/resumed/cancelled/reactivated/upgraded/downgraded/trial converted/trial expired + invoice created/paid/failed/refunded/disputed) + per-pagination + per-batch-vs-stream + per-CDC + per-API-version-pinning + per-API-deprecation-handoff + per-retry + per-circuit-breaker + per-dead-letter-queue + per-replay.
- Per-canonical-per-plan-schema-normalization-spec — per-20-canonical-plan-field (plan ID + plan name + plan tier + billing cycle + MRR + ARR + list price + discount + credit + tax + currency + tender + line item + quantity + subscriber ID + subscription status + trial period + cancellation reason code) + per-unit-canonicalization (USD/cents/monthly/quarterly/semi-annual/annual) + per-late-arriving-correction + per-schema-version-pointer + per-schema-confidence-tier + per-schema-explainability.
- Per-canonical-per-invoice-quality-scoring-spec + per-cross-platform-joining-spec — per-completeness + per-accuracy + per-timeliness + per-uniqueness + per-consistency + per-validity + per-anomaly-detection-XGBoost-LightGBM-CatBoost + per-Transformer + per-Bayesian + per-quality-confidence-tier + per-quality-explainability + per-canonical-subscriber-ID-resolution (internal/Stripe/Chargebee/Recurly/Zuora/Recharge) + per-canonical-payment-method-ID-PCI-DSS-tokenized + per-canonical-plan-ID + per-canonical-subscription-state (12 states: trialing + active + past due + paused + cancelled + cancelled-saveable + cancelled-recoverable + cancelled-non-saveable + reactivated + graduated + downgraded + upgraded) + per-canonical-time-bucket + per-cross-platform-conflict-resolution + per-recency-priority + per-confidence-priority + per-joining-confidence-tier + per-joining-explainability.
- Per-canonical-per-subscriber-multi-LLM-pre-publish-check — per-multi-LLM-ensemble + per-MRR-ARR-claim-substantiation + per-churn-rate-claim-substantiation + per-cohort-analysis-cross-check + per-cross-platform-reconciliation + per-FTC-ROSCA-disclosure + per-FTC-negative-option-rule-disclosure + per-state-auto-renewal-laws-CA-NY-DC-OR-VT-CT-Florida-disclosure + per-LLM-confidence-scoring + per-LLM-self-consistency + per-LLM-chain-of-thought.
- Per-canonical-per-subscriber-FBC-feedback + per-audit-trail + per-cross-skill-handoff — per-extraction-success-vs-failure + per-API-rate-limit-detection + per-API-deprecation-detection + per-schema-drift-detection + per-quality-score-recalibration + per-anomaly-detection-recalibration + per-cross-platform-reconciliation + per-cross-platform-joining-recalibration + per-pattern-learning + per-emerging-platform-detection + per-cannibalization-detection + per-late-arriving-correction-detection + per-per-subscriber-canonical-audit-record + per-OAuth-2.0-token-revocation + per-PCI-DSS-tokenization + per-PCI-DSS-Level-1-2-3-4 + per-data-residency-US-EU-Canada-Brazil-India + per-CCPA-CPRA-DSAR + per-GDPR-DPIA + per-LGPD-ANPD + per-DPDP-India + per-PIPEDA-OPC + per-CASL-CRTC + per-FTC-ROSCA + per-FTC-negative-option-rule + per-FTC-substantiation-doctrine + per-FTC-MARS + per-FDD-Item-12-Item-17-Item-19 + per-state-auto-renewal-laws + per-SOC-2-Type-II + per-EU-AI-Act-Article-13 + per-EU-AI-Act-Article-14 + per-NIST-AI-RMF + per-immutable-WORM + per-7-year-IRS-tax-retention + per-SEC-7-year-revenue-recognition-retention + per-Sarbanes-Oxley-Section-302-404-attestation + per-handoff-to-13-sibling-skills.
Why per-vendor-Recharge-account-flat-billing-cycle-extraction breaks at multi-platform multi-portfolio subscription operator scale
Per-vendor-Recharge-canonical-account-flat-billing-cycle-extraction ships per-account per-billing-cycle per-flat-extraction primitive. Per-vendor-Smartrr + Stay-AI + Loop-Subscriptions + Ordergroove + Awtomic + Subbly + Chargebee + Stripe-Billing + Recurly + Zuora + ProfitWell + Maxio + NetSuite-SuiteBilling-canonical-account-flat-billing-cycle-extraction ship per-vendor per-native account-flat-billing-cycle-extraction primitives.
At 1-account-1-billing-cycle-flat-extraction scale per-account per-billing-cycle per-flat-extraction primitive is enough. At multi-platform multi-portfolio subscription operator scale per-per-platform-connector-spec + per-per-plan-schema-normalization-spec + per-per-invoice-quality-scoring-spec + per-per-subscriber-cross-platform-joining-spec + per-per-subscriber-multi-LLM-pre-publish-check + per-per-subscriber-FBC-feedback-loop + per-per-subscriber-audit-trail.
Per-account-flat-billing-cycle-extraction + per-per-platform-connector-blind + per-per-plan-schema-normalization-blind + per-per-invoice-quality-scoring-blind + per-per-subscriber-cross-platform-joining-blind + per-per-subscriber-multi-LLM-pre-publish-blind + per-per-subscriber-FBC-feedback-loop-blind + per-multi-format-audit-trail-blind + per-OAuth-2.0-token-revocation-blind + per-PCI-DSS-Level-1-2-3-4-blind + per-FTC-ROSCA-blind + per-FTC-negative-option-rule-blind + per-state-auto-renewal-laws-blind + per-FDD-Item-12-Item-17-Item-19-blind + per-SOC-2-Type-II-blind + per-EU-AI-Act-Article-13-Article-14-blind + per-NIST-AI-RMF-blind + per-7-year-IRS-tax-retention-blind + per-SEC-7-year-revenue-recognition-retention-blind + per-Sarbanes-Oxley-Section-302-404-blind.
The operator-side architecture above per-vendor-flat-billing-cycle-extraction primitive is canonical-per-platform-connector-spec + per-per-plan-schema-normalization-spec + per-per-invoice-quality-scoring-spec + per-per-subscriber-cross-platform-joining-spec + per-per-subscriber-multi-LLM-pre-publish-check + per-per-subscriber-FBC-feedback-loop + per-per-subscriber-audit-trail + per-portfolio-audit-trail.
What is in market today
Per-platform per-subscription-billing-vendor
Recharge, Smartrr, Stay AI, Loop Subscriptions, Ordergroove, Awtomic, Subbly, Chargebee, Stripe Billing, Recurly, Zuora, ProfitWell, Maxio (SaaSOptics), NetSuite SuiteBilling, Sage Intacct Subscription Billing, Salesforce Revenue Cloud, Aria Systems, Gotransverse, BillingPlatform. Per-account per-billing-cycle per-flat-extraction primitive. Per-canonical-per-platform-connector-canonical-per-plan-schema-normalization-canonical-per-invoice-quality-scoring-canonical-cross-platform-joining-canonical-multi-LLM-pre-publish-canonical-FBC-feedback-canonical-audit-trail is not the primitive.
Per-platform per-subscription-analytics-vendor
ProfitWell (Paddle), ChartMogul, Baremetrics, RevenueCat, Maxio (SaaSOptics), Subscript, Equals, Mosaic, Putler, Reditus, Funnel.io, Supermetrics. Per-account per-rolled-up per-flat-MRR-ARR primitive. Per-canonical-per-plan-MRR-ARR-canonical-per-plan-churn-rate-canonical-per-plan-LTV-canonical-per-plan-cohort-analysis-canonical-per-plan-late-arriving-correction-canonical-per-plan-schema-version-pointer-canonical-per-plan-schema-confidence-tier-canonical-per-plan-schema-explainability is not the primitive.
Per-platform per-payment-tokenization-PCI-DSS-vendor
Stripe Tokenization, Braintree Vault, Adyen, Worldpay Tokenization, Cybersource Token Management, TokenEx, Spreedly, VGS (Very Good Security), Basis Theory, Skyflow, Apple Pay, Google Pay, Samsung Pay, PayPal. Per-account per-token primitive. Per-canonical-per-subscriber-canonical-payment-method-ID-resolution-canonical-per-subscriber-canonical-plan-ID-resolution-canonical-per-subscriber-canonical-subscription-state-canonical-per-subscriber-canonical-time-bucket-canonical-per-subscriber-cross-platform-conflict-resolution-canonical-per-subscriber-cross-platform-recency-priority-canonical-per-subscriber-cross-platform-confidence-priority-canonical-per-subscriber-cross-platform-joining-confidence-tier-canonical-per-subscriber-cross-platform-joining-explainability is not the primitive.
Per-platform per-subscription-compliance-vendor
Termly, OneTrust, TrustArc, DataGrail, Securiti, BigID, Transcend, Ketch, Osano, Cookiebot, Iubenda, ComplyDog, Avalara (subscription tax), Anrok, Sovos, Vertex Cloud. Per-account per-vendor per-flat-compliance-check primitive. Per-canonical-per-subscriber-FTC-ROSCA-disclosure-canonical-per-subscriber-FTC-negative-option-rule-disclosure-canonical-per-subscriber-state-auto-renewal-laws-CA-NY-DC-OR-VT-CT-Florida-disclosure-canonical-per-subscriber-CCPA-CPRA-DSAR-canonical-per-subscriber-GDPR-DPIA-canonical-per-subscriber-LGPD-ANPD-canonical-per-subscriber-DPDP-India-canonical-per-subscriber-PIPEDA-OPC-canonical-per-subscriber-CASL-CRTC-canonical-per-subscriber-SOC-2-Type-II-canonical-per-subscriber-7-year-IRS-tax-retention-canonical-per-subscriber-SEC-7-year-revenue-recognition-retention-canonical-per-subscriber-Sarbanes-Oxley-Section-302-404-attestation is not the primitive.
How the architecture is built
- Per-portfolio per-banner per-subscriber per-canonical-per-platform-connector-substrate. Per-16-canonical-billing-platform + per-OAuth-token-management + per-API-rate-limit + per-15-webhook-events + per-pagination + per-batch-vs-stream + per-CDC + per-API-version-pinning + per-API-deprecation-handoff + per-retry + per-circuit-breaker + per-dead-letter-queue + per-replay canonical-connector.
- Per-portfolio per-canonical-per-plan-schema-normalization-spec. Per-20-canonical-plan-field + per-unit-canonicalization + per-late-arriving-correction + per-schema-version-pointer + per-schema-confidence-tier + per-schema-explainability canonical-schema.
- Per-portfolio per-canonical-per-invoice-quality-scoring-spec. Per-completeness + per-accuracy + per-timeliness + per-uniqueness + per-consistency + per-validity + per-anomaly-detection-XGBoost-LightGBM-CatBoost + per-Transformer + per-Bayesian + per-quality-confidence-tier + per-quality-explainability canonical-quality.
- Per-portfolio per-canonical-per-subscriber-cross-platform-joining-spec. Per-canonical-subscriber-ID-resolution + per-canonical-payment-method-ID-resolution + per-canonical-plan-ID-resolution + per-canonical-subscription-state + per-canonical-time-bucket + per-cross-platform-conflict-resolution + per-recency-priority + per-confidence-priority + per-joining-confidence-tier + per-joining-explainability canonical-joining.
- Per-portfolio per-canonical-per-subscriber-multi-LLM-pre-publish-check. Per-multi-LLM-ensemble + per-MRR-ARR-claim-substantiation + per-churn-rate-claim-substantiation + per-cohort-analysis-cross-check + per-cross-platform-reconciliation + per-FTC-ROSCA-disclosure + per-FTC-negative-option-rule-disclosure + per-state-auto-renewal-laws-disclosure + per-LLM-confidence + per-LLM-self-consistency + per-LLM-chain-of-thought canonical-LLM.
- Per-portfolio per-canonical-per-subscriber-FBC-feedback-loop. Per-extraction-success-vs-failure + per-API-rate-limit-detection + per-API-deprecation-detection + per-schema-drift-detection + per-quality-score-recalibration + per-anomaly-detection-recalibration + per-cross-platform-reconciliation + per-cross-platform-joining-recalibration + per-pattern-learning + per-emerging-platform-detection + per-cannibalization-detection + per-late-arriving-correction-detection canonical-FBC.
- Per-portfolio per-canonical-per-subscriber-audit-trail + per-portfolio-audit-trail. Per-per-subscriber-canonical-audit-record + per-OAuth-2.0-token-revocation + per-PCI-DSS-tokenization + per-PCI-DSS-Level-1-2-3-4 + per-data-residency + per-CCPA-CPRA-DSAR + per-GDPR-DPIA + per-LGPD-ANPD + per-DPDP-India + per-PIPEDA-OPC + per-CASL-CRTC + per-FTC-ROSCA + per-FTC-negative-option-rule + per-FTC-substantiation-doctrine + per-FTC-MARS + per-FDD-Item-12-Item-17-Item-19 + per-state-auto-renewal-laws + per-SOC-2-Type-II + per-EU-AI-Act-Article-13 + per-EU-AI-Act-Article-14 + per-NIST-AI-RMF + per-immutable-WORM + per-7-year-IRS-tax-retention + per-SEC-7-year-revenue-recognition-retention + per-Sarbanes-Oxley-Section-302-404 canonical-audit.
- Per-portfolio per-canonical-per-subscriber-cross-skill-handoff. Per-handoff-to-13-sibling-skills canonical-handoff.
- Per-portfolio per-customer-data-graph-agent-canonical-bundle. Per-subscription-billing-ingestion + per-subscription-analytics + per-multi-stream-subscription + per-customer-data-graph + per-identity-resolution + per-canonical-customer-ID-resolution + per-canonical-household-resolution + per-LTV-math-primitives + per-per-member-monthly-clv + per-per-member-next-best-action canonical-bundle.
- Per-portfolio per-canonical-end-to-end-SLA. Per-platform-extraction-to-plan-schema-normalize-to-invoice-quality-score-to-cross-platform-join-to-pre-publish-to-present-to-FBC-SLA canonical-end-to-end-SLA.
- Per-portfolio per-canonical-end-to-end-replay. Per-replay-spec + per-replay-trace + per-replay-decision + per-per-platform-extraction-replay + per-per-platform-schema-version-rewind + per-per-subscriber-cancellation-rewind canonical-replay.
Frequently asked questions
What is multi-platform subscription billing ingestion?
Multi-platform subscription billing ingestion is the discipline of pulling subscriber records, plan records, and invoice records out of every billing platform an operator runs subscriptions on; normalizing each to a single canonical schema; scoring each for quality and anomalies; resolving subscriber + payment-method + plan IDs across platforms; pre-publishing through a multi-LLM check for FTC ROSCA + Negative Option Rule + state auto-renewal disclosure compliance; and emitting a per-subscriber audit trail with WORM retention sufficient to clear IRS + SEC + Sarbanes-Oxley requirements. The Shopify-native subscription market (Recharge + Smartrr + Stay AI + Loop Subscriptions + Ordergroove + Awtomic + Subbly) ships excellent ecommerce-native subscription mechanics. The horizontal billing-platform market (Chargebee + Stripe Billing + Recurly + Zuora + ProfitWell + Maxio) ships excellent dunning + revenue recognition + tax + multi-currency mechanics. The enterprise revenue-recognition market (NetSuite SuiteBilling + Sage Intacct Subscription Billing + Salesforce Revenue Cloud) ships excellent GAAP-aligned recognition + ASC 606 + multi-element arrangement handling. None of them is built for a DTC + multi-channel-retail operator running 2-4 of them concurrently. The operator-side architecture sits above all three layers: per-platform connector with OAuth + rate-limit + 15-event webhook + CDC + API version pinning + retry + circuit-breaker + dead-letter-queue + replay; per-subscriber per-plan schema normalization with unit canonicalization + late-arriving correction + schema version pointer + confidence tier + explainability; per-subscriber per-invoice 6-dimension quality scoring (completeness + accuracy + timeliness + uniqueness + consistency + validity) + 3-method anomaly detection (XGBoost/LightGBM/CatBoost ensemble + deep-learning Transformer + Bayesian posterior); cross-platform subscriber-ID + payment-method-ID + plan-ID resolution against a 12-state subscription-state spec; multi-LLM pre-publish check against MRR + ARR + churn-rate claim substantiation + FTC ROSCA + FTC Negative Option Rule + state auto-renewal laws (California + New York + DC + Oregon + Vermont + Connecticut + Florida); per-subscriber FBC feedback loop; per-subscriber audit trail with PCI DSS tokenization + GDPR + CCPA/CPRA + LGPD + DPDP + PIPEDA + CASL data residency + SOC 2 Type II + EU AI Act Articles 13-14 + NIST AI RMF + 7-year IRS + 7-year SEC + Sarbanes-Oxley Section 302/404 attestation in WORM storage.
Why does single-vendor billing-cycle extraction break at multi-platform subscription operator scale?
Single-vendor extraction works when the operator runs subscriptions on one platform — Recharge alone, or Chargebee alone, or Stripe Billing alone — and the vendor’s own dashboard + accountant export covers the operator’s needs. It breaks the moment the operator runs subscriptions on two or more platforms, which is the descriptive industry pattern for any DTC + multi-channel-retail operator past about $5M in subscription revenue. A typical configuration: Recharge for Shopify-native consumer subscriptions, Chargebee for the SaaS-style B2B tier, NetSuite SuiteBilling for revenue recognition. Each vendor extracts its own data correctly. None of them resolves whether a Recharge subscriber + a Chargebee subscriber + a NetSuite contact represent the same human customer. None of them resolves whether a Recharge payment method + a Chargebee payment method are tokens against the same underlying card. None of them resolves whether a Recharge plan + a Chargebee plan should be treated as equivalent tiers for cohort analysis. None of them tracks the 12-state subscription-state spec (trialing + active + past-due + paused + cancelled + cancelled-saveable + cancelled-recoverable + cancelled-non-saveable + reactivated + graduated + downgraded + upgraded) consistently across platforms. None of them runs a multi-LLM pre-publish FTC ROSCA + FTC Negative Option Rule + state auto-renewal disclosure check against MRR + ARR + churn-rate claims the operator is making in its investor decks + LP letters + S-1 + earnings reports. None of them emits the WORM audit trail that an IRS audit + SEC enforcement inquiry + Sarbanes-Oxley Section 302/404 attestation requires. The Recharge + Smartrr + Stay AI + Loop Subscriptions + Ordergroove + Awtomic + Subbly + Chargebee + Stripe Billing + Recurly + Zuora + ProfitWell + Maxio + NetSuite SuiteBilling + Sage Intacct + Salesforce Revenue Cloud vendors do not ship the missing layer — they correctly execute their per-platform extraction. The fix is the operator-side architecture above the per-platform primitive.
How does per-platform connector + per-plan schema normalization + per-invoice quality scoring work?
Per-portfolio per-banner per-subscriber per-canonical-per-platform-connector-spec runs per-portfolio per-canonical-per-platform-OAuth-token-management + per-canonical-per-platform-API-rate-limit-spec + per-canonical-per-platform-webhook-event-spec (per-subscription-created + per-subscription-updated + per-subscription-paused + per-subscription-resumed + per-subscription-cancelled + per-subscription-reactivated + per-subscription-upgraded + per-subscription-downgraded + per-subscription-trial-converted + per-subscription-trial-expired + per-invoice-created + per-invoice-paid + per-invoice-failed + per-invoice-refunded + per-invoice-disputed + per-canonical-webhook-event) + per-canonical-per-platform-pagination-spec + per-canonical-per-platform-batch-vs-stream-spec + per-canonical-per-platform-CDC-Debezium-AWS-DMS-Striim-Fivetran-HVR-Qlik-Replicate + per-canonical-per-platform-API-version-pinning + per-canonical-per-platform-API-deprecation-handoff-to-integration-health-monitoring (sibling build-pillar at /how-to-build-marketing-stack-integration-health-for-multi-vendor-campaign-operations) + per-canonical-per-platform-retry-spec + per-canonical-per-platform-circuit-breaker-spec + per-canonical-per-platform-dead-letter-queue + per-canonical-per-platform-replay-spec. Per-canonical-per-subscriber-per-plan-schema-normalization-spec runs per-portfolio per-canonical-per-plan-canonical-schema-mapping (per-plan-ID + per-plan-name + per-plan-tier + per-billing-cycle + per-MRR + per-ARR + per-list-price + per-discount + per-credit + per-tax + per-currency + per-tender + per-line-item + per-quantity + per-subscriber-ID + per-subscription-status + per-trial-period + per-cancellation-reason-code + per-canonical-plan-field) + per-canonical-per-plan-unit-canonicalization (per-USD + per-cents + per-monthly + per-quarterly + per-semi-annual + per-annual + per-canonical-unit) + per-canonical-per-plan-late-arriving-correction-spec + per-canonical-per-plan-schema-version-pointer + per-canonical-per-plan-schema-confidence-tier + per-canonical-per-plan-schema-explainability. Per-canonical-per-subscriber-per-invoice-quality-scoring-spec runs per-portfolio per-canonical-per-invoice-completeness-score + per-canonical-per-invoice-accuracy-score + per-canonical-per-invoice-timeliness-score + per-canonical-per-invoice-uniqueness-score + per-canonical-per-invoice-consistency-score + per-canonical-per-invoice-validity-score + per-canonical-per-invoice-anomaly-detection-XGBoost-LightGBM-CatBoost-ensemble + per-canonical-per-invoice-anomaly-detection-deep-learning-Transformer + per-canonical-per-invoice-anomaly-detection-Bayesian-posterior + per-canonical-per-invoice-quality-confidence-tier + per-canonical-per-invoice-quality-explainability.
What does per-subscriber cross-platform joining + multi-LLM pre-publish + FBC feedback do?
Per-portfolio per-banner per-subscriber per-canonical-cross-platform-joining-spec runs per-portfolio per-canonical-per-subscriber-canonical-subscriber-ID-resolution (per-internal-customer-ID + per-Stripe-customer-ID + per-Chargebee-customer-ID + per-Recurly-account-code + per-Zuora-account-number + per-Recharge-customer-ID + per-canonical-subscriber-ID) + per-canonical-per-subscriber-canonical-payment-method-ID-resolution (per-PCI-DSS-tokenized-PAN + per-bank-account-token + per-canonical-payment-method) + per-canonical-per-subscriber-canonical-plan-ID-resolution + per-canonical-per-subscriber-canonical-subscription-state-spec (per-trialing + per-active + per-past-due + per-paused + per-cancelled + per-cancelled-saveable + per-cancelled-recoverable + per-cancelled-non-saveable + per-reactivated + per-graduated + per-downgraded + per-upgraded + per-canonical-state) + per-canonical-per-subscriber-canonical-time-bucket-spec + per-canonical-per-subscriber-cross-platform-conflict-resolution + per-canonical-per-subscriber-cross-platform-recency-priority + per-canonical-per-subscriber-cross-platform-confidence-priority + per-canonical-per-subscriber-cross-platform-joining-confidence-tier + per-canonical-per-subscriber-cross-platform-joining-explainability. Per-canonical-per-subscriber-multi-LLM-pre-publish-check runs per-portfolio per-canonical-multi-LLM-ensemble (per-GPT-4o + per-Claude-Sonnet + per-Gemini-Pro per-canonical-LLM) + per-canonical-per-subscriber-LLM-MRR-ARR-claim-substantiation + per-canonical-per-subscriber-LLM-churn-rate-claim-substantiation + per-canonical-per-subscriber-LLM-cohort-analysis-cross-check + per-canonical-per-subscriber-LLM-cross-platform-reconciliation-cross-check + per-canonical-per-subscriber-LLM-FTC-ROSCA-disclosure-check + per-canonical-per-subscriber-LLM-FTC-negative-option-rule-disclosure-check + per-canonical-per-subscriber-LLM-state-auto-renewal-laws-CA-NY-DC-OR-VT-CT-Florida-disclosure-check + per-canonical-per-subscriber-LLM-confidence-scoring + per-canonical-per-subscriber-LLM-self-consistency-cross-check + per-canonical-per-subscriber-LLM-chain-of-thought-extraction. Per-canonical-per-subscriber-FBC-feedback-loop runs per-portfolio per-canonical-FBC-per-platform-extraction-success-vs-failure + per-canonical-FBC-per-platform-API-rate-limit-detection + per-canonical-FBC-per-platform-API-deprecation-detection + per-canonical-FBC-per-platform-schema-drift-detection + per-canonical-FBC-per-platform-quality-score-recalibration + per-canonical-FBC-per-platform-anomaly-detection-recalibration + per-canonical-FBC-per-subscriber-cross-platform-reconciliation + per-canonical-FBC-per-subscriber-cross-platform-joining-recalibration + per-canonical-FBC-per-subscriber-pattern-learning + per-canonical-FBC-per-subscriber-emerging-platform-detection + per-canonical-FBC-per-subscriber-cannibalization-detection + per-canonical-FBC-per-subscriber-late-arriving-correction-detection.
What does per-subscriber audit-trail + per-cross-skill-handoff do?
Per-portfolio per-subscriber per-canonical-audit-trail runs per-portfolio per-canonical-per-subscriber-canonical-audit-record (per-extraction-run-ID + per-banner-pointer + per-platform-pointer + per-platform-API-version-pointer + per-platform-schema-version-pointer + per-OAuth-token-snapshot + per-rate-limit-snapshot + per-pagination-snapshot + per-quality-scoring-snapshot + per-cross-platform-joining-snapshot + per-canonical-subscriber-ID-resolution-snapshot + per-canonical-payment-method-ID-resolution-snapshot + per-canonical-plan-ID-resolution-snapshot + per-canonical-subscription-state-snapshot + per-multi-LLM-pre-publish-record + per-FBC-feedback per-canonical-audit-record) + per-canonical-OAuth-2.0-token-revocation + per-canonical-PCI-DSS-tokenization + per-canonical-PCI-DSS-Level-1-2-3-4 + per-canonical-data-residency-spec (per-US + per-EU + per-Canada + per-Brazil + per-India + per-canonical-region) + per-canonical-CCPA-CPRA-DSAR + per-canonical-GDPR-DPIA + per-canonical-LGPD-ANPD + per-canonical-DPDP-India + per-canonical-PIPEDA-OPC + per-canonical-CASL-CRTC + per-canonical-FTC-ROSCA + per-canonical-FTC-negative-option-rule + per-canonical-FTC-substantiation-doctrine + per-canonical-FTC-MARS-multi-location-substantiation + per-canonical-FDD-Item-12-Item-17-Item-19 + per-canonical-state-auto-renewal-laws-CA-NY-DC-OR-VT-CT-Florida + per-canonical-SOC-2-Type-II + per-canonical-EU-AI-Act-Article-13-transparency + per-canonical-EU-AI-Act-Article-14-human-oversight + per-canonical-NIST-AI-RMF-attestation + per-canonical-immutable-WORM-storage + per-canonical-7-year-tax-audit-IRS-retention + per-canonical-SEC-7-year-revenue-recognition-retention + per-canonical-Sarbanes-Oxley-Section-302-404-attestation. Per-canonical-per-subscriber-cross-skill-handoff runs per-portfolio per-canonical-per-subscriber-handoff-to-subscription-analytics (parent commercial pillar at /subscription-analytics) + per-canonical-per-subscriber-handoff-to-multi-stream-subscription (sibling at /multi-stream-subscription) + per-canonical-per-subscriber-handoff-to-save-flow-propensity-scoring (sibling build-pillar at /how-to-build-save-flow-with-propensity-scored-offer-selection) + per-canonical-per-subscriber-handoff-to-churn-prediction-per-subscriber + per-canonical-per-subscriber-handoff-to-lifecycle-stage-cadence (sibling build-pillar at /how-to-build-subscriber-lifecycle-cadence-for-multi-location-subscription-operators) + per-canonical-per-subscriber-handoff-to-llm-cancellation-reason-clustering + per-canonical-per-subscriber-handoff-to-per-member-monthly-clv + per-canonical-per-subscriber-handoff-to-per-member-next-best-action + per-canonical-per-subscriber-handoff-to-tier-transition-timing + per-canonical-per-subscriber-handoff-to-integration-health-monitoring (sibling build-pillar) + per-canonical-per-subscriber-handoff-to-versioned-history-regulatory-defense (sibling build-pillar) + per-canonical-per-subscriber-handoff-to-attribution-rollup (sibling build-pillar at /how-to-build-per-location-cross-channel-attribution-rollup-for-franchise-reporting) + per-canonical-per-subscriber-handoff-to-pos-receipt-integration.
What does per-customer-data-graph-agent-canonical-bundle + per-end-to-end-SLA + per-end-to-end-replay do?
Per-customer-data-graph-agent-canonical-bundle integrates the subscription-billing-ingestion skill with sibling skills on the same customer-data-graph agent: per-canonical-subscription-billing-ingestion (this skill) + per-canonical-subscription-analytics (parent commercial pillar) + per-canonical-multi-stream-subscription (sibling commercial) + per-canonical-customer-data-graph (parent agent) + per-canonical-identity-resolution (sibling) + per-canonical-canonical-customer-ID-resolution (sibling) + per-canonical-canonical-household-resolution (sibling) + per-canonical-LTV-math-primitives (sibling) + per-canonical-per-member-monthly-clv (sibling) + per-canonical-per-member-next-best-action (sibling). Per-canonical-end-to-end-SLA runs per-canonical-per-subscriber-platform-extraction-to-plan-schema-normalize-to-invoice-quality-score-to-cross-platform-join-to-pre-publish-to-present-to-FBC-SLA canonical-SLA. Per-canonical-end-to-end-replay runs per-canonical-per-subscriber-replay-spec + per-canonical-per-subscriber-replay-trace + per-canonical-per-subscriber-replay-decision + per-canonical-per-platform-extraction-replay + per-canonical-per-platform-schema-version-rewind + per-canonical-per-subscriber-cancellation-rewind canonical-replay.
Engage the customer-data-graph agent
Per-portfolio per-banner per-subscriber per-canonical-per-platform-connector-spec + per-canonical-schema-normalization-spec + per-canonical-quality-scoring-spec + per-canonical-cross-platform-joining-spec + per-canonical-multi-LLM-pre-publish-check + per-canonical-FBC-feedback-loop + per-canonical-audit-trail + per-portfolio audit-trail shipped as the orchestration layer above your existing per-subscription-billing-vendor + per-subscription-analytics-vendor + per-payment-tokenization-PCI-DSS-vendor + per-subscription-compliance-vendor primitive.
Or take the 3-question shape diagnostic first — no email required.
Related reading
- Subscription analytics (parent commercial pillar — buyer-outcome framing)
- Subscriber lifecycle cadence for multi-location subscription operators (sibling build-pillar on adjacent subscription-lifecycle agent — downstream 15-stage cadence consumer)
- Save flow with propensity-scored offer selection (sibling build-pillar on adjacent subscription-lifecycle agent — downstream cancellation save-flow consumer)