Billing

What this product area is for

Billing combines Kadryn SaaS billing with FinOps visibility. It manages the commercial relationship with Kadryn while clearly separating Stripe subscription billing from AI usage monitored by the product.

Who uses it

• Admins who manage the subscription.
• Finance users who need invoices and billing details.
• Owners who review plan limits and entitlements.
• Operators who need to recover failed payments.

Core workflows

• Review the current plan and subscription status.
• Subscribe, upgrade, downgrade, or cancel at period end.
• Review AI usage monitored by Kadryn.
• Open invoices and download PDFs.
• Manage payment methods through Stripe.
• Update billing details and Tax IDs.
• Review plan limits and entitlements.

What Billing owns

• Kadryn SaaS subscription billing.
• Invoices, payment methods, billing details, and Tax IDs.
• Plan entitlements and product limits.
• Monitored AI usage shown for FinOps visibility.

What Billing does not own

• Provider invoices from OpenAI, Anthropic, Gemini, or other LLM providers.
• Finance-grade provider reconciliation.
• ERP close process or revenue recognition.
• Cost allocation and chargeback, which belong in Costs.

Tabs in this area

• Overview — Understand the difference between Kadryn SaaS billing, monitored AI usage, and plan limits.
• Plans — Manage the Kadryn SaaS subscription and plan selection.
• Usage — Review AI usage monitored by Kadryn for the current month.
• Invoices — Open hosted invoices, download PDFs, and review local invoice history.
• Payment — Manage payment methods, payment recovery, billing profile, and Tax IDs.
• Limits — Review product entitlements and plan limits.

Recommended operating model

1. Start from the overview to identify the most important signal.
2. Open the tab that owns the workflow.
3. Use filters to narrow the scope before taking action.
4. Open detail drawers before changing sensitive configuration.
5. Use related links instead of duplicating workflows across product areas.
6. Confirm sensitive actions such as rotation, deletion, approval, payment changes, or revocation.
7. Preserve request IDs, trace IDs, run IDs, and audit IDs when escalating.

Product boundaries

Kadryn keeps each product area focused. Billing should provide enough context to understand the situation, but ownership of related workflows stays with the product area that is responsible for them.

For example, a page may show linked alerts, approvals, reports, integrations, or recommendations, but the full administration of those objects remains in their owning menu.

Related docs

Use the related links panel to continue into concepts, developer setup, troubleshooting, or security guidance.