Subscription-Native. Revenue-Rec Built-In
CPQ → contract → e-invoice → subscription billing → cash application → revenue recognition per ASC 606. The SaaS-flavored Q2C, with usage-based billing, mid-cycle changes, and IFRS 15 / ASC 606 compliance built in.
By the numbers
The use case
Subscription metrics live in Zuora. The GL lives in NetSuite. Revenue rec lives in Excel. That's three sources of truth and the monthly close becomes a reconciliation exercise. Mid-cycle plan changes break the billing system every release. Deferred revenue is a manual calc that the auditors hate. ASC 606 wants evidence per contract — Finance has evidence per spreadsheet.
Pre-built Q2C workflow tuned for SaaS: CPQ → contract with performance obligations captured at the line level → e-invoice → subscription billing with mid-cycle proration and usage metering → cash application at the line → revenue recognition under ASC 606 / IFRS 15 → journal entries posted in real time across every entity. One operating brain (Astral) holds the subscription, contract, and revenue-rec state. The ERP and billing system both read from it.
For who
Capabilities
Configure-Price-Quote engine wired to contract drafting. Approved quote becomes a signed contract with negotiated terms, ramp schedules, and discount waterfalls captured at the line level. No re-keying into the billing system.
Plan upgrades, downgrades, seat changes, add-ons — all prorated automatically mid-cycle. Multiple billing frequencies (monthly, quarterly, annual) per contract line. The exceptions that break every billing release become the default behavior.
Ingest usage events from any source — product telemetry, API gateway, data warehouse. Aggregate per contract line, apply tiered or volume pricing, bill on cadence. Usage anomalies flagged before they hit the invoice.
Performance obligations identified at contract signing. Standalone selling prices captured. Revenue recognized over time or at point-in-time per the obligation. Deferred revenue, contract assets, and contract liabilities tracked per contract — not in a monthly Excel exercise.
Continue exploring
Invoice arrives → AI matches against PO + receipt → policy validation → auto-post if clean, exception queue if not.
Bank statements → AI matches to GL transactions → exception queue for unmatched → escalation rules → close.
Aging trigger → customer segmentation → multi-channel cadence (email/SMS/call) → escalation paths → dispute → legal handoff.
ISO 27001:2022 · GDPR · EU-hosted · Full audit trails · Trust Center →
Start free. See your first workflow run before the next quarter close.