feature
Jul 22, 2026Personal users and organization administrators can now review invoices in RCLM while managing payments securely through Stripe.
RCLM now provides billing views for personal subscriptions and enterprise organizations. Users can review their current plan, upcoming charges, and invoice history inside RCLM, while payment methods and billing changes remain in Stripe.
Personal billing is available under Settings → Billing. Organization administrators can access billing from the Billing tab in their enterprise organization.
The billing view displays:
Invoice amounts come directly from Stripe. RCLM does not independently calculate or store financial totals, which avoids discrepancies between the application and the final Stripe invoice.
When a subscription has not been configured, the billing page sends the user or organization administrator to Stripe Checkout. Existing subscribers are sent to the Stripe Customer Portal.
RCLM does not collect card or bank information directly.
Stripe Checkout handles new subscriptions. The Stripe Customer Portal handles payment methods, billing addresses, tax identifiers, purchase-order details, and subscription management. This keeps sensitive payment operations outside the RCLM frontend and reduces the amount of payment-related data handled by the application.
The RCLM billing pages are therefore primarily read-only. Their role is to show subscription and invoice information and provide an authenticated route into the appropriate Stripe-hosted workflow.
Personal users and enterprise organizations have separate billing accounts and Stripe customers.
An enterprise billing account belongs to the organization rather than to the administrator who initially created it. This means invoices, company details, and payment methods remain associated with the organization if its administrators change.
Only organization administrators can access enterprise billing routes.
Enterprise subscriptions use the organization’s accepted member count as the billable seat quantity. When membership changes, RCLM updates the desired seat count and synchronizes it with Stripe. Stripe remains responsible for calculating any resulting prorations.
If synchronization cannot complete immediately, the billing page reports that a seat update is pending instead of presenting stale data as final.
Stripe webhooks update local subscription state after checkout, renewal, cancellation, payment failure, and other subscription changes. Webhook events are recorded so duplicate deliveries can be ignored and failed processing can be retried.
The billing service also reconciles incomplete legacy records. If a historical account has a Stripe customer but is missing its subscription association, RCLM can discover the active subscription from Stripe and repair the local billing record.
Enterprise trial messaging now checks the organization’s billing entitlement. An expired promotional date no longer produces a trial-expired warning when Stripe confirms that the organization has an active, trialing, or past-due subscription.
Card-based Stripe Checkout is the supported payment flow in this release. ACH, wire transfers, invoice payment terms, and committed seat minimums are not yet part of the application workflow.
Billing pages also depend on Stripe availability for current subscription and invoice information. If Stripe cannot be reached, RCLM reports billing as temporarily unavailable rather than relying on potentially stale invoice data.
We are watching for enterprise workflows that require multiple billing accounts, contract-specific seat rules, or additional payment methods. Feedback on those cases and on invoice reconciliation edge cases is useful.