> ## Documentation Index > Fetch the complete documentation index at: https://docs.trueparser.com/llms.txt > Use this file to discover all available pages before exploring further. # Plans and Billing > How subscription plans are assigned to individual applications, billing structures, and beta period policies. Subscription plans govern the document limits, allowed formats, and processing features of your Tenant Applications. In TrueParser, subscriptions are managed at the application level rather than the organizational level. *** ## Per-Application Billing Subscriptions are bound to **individual applications**, not to the tenant overall. * **Individual Plans**: Every application you create requires its own active subscription plan to obtain tokens and parse documents. * **Separate Invoices**: Because plans are assigned per application, **billing and invoicing are calculated and generated separately for each individual app**. This allows you to easily isolate and allocate costs between different projects, teams, or environments (e.g., staging vs. production). *** ## Subscription Plans Screen You can view, assign, or upgrade plans from the **Plans** tab of any application details page. Subscription Plans Card *** ## Beta Period Policies & Limitations To help you test and integrate TrueParser, the platform is currently operating in an active beta period. Special rules apply during this phase: * **Beta Free Tier**: During beta, only the **Free Tier (\$0/Month)** plan is displayed and available. No credit card or billing details are required. * **One Free App Constraint**: You can assign the Free plan to **only one application** within your organization. If you create additional applications (up to the limit of 3), they will remain unassigned and unable to process documents until paid plans are activated. **Post-Beta Limit Reductions**: The generous usage allocations (such as the 10,000 monthly document limit) displayed on the Free plan card during the beta period are temporary. Once the beta period concludes, the Free plan will be scaled back to standard, reduced usage limits. Organizations requiring higher volume capacity will need to transition their applications to paid subscription tiers. *** ## Subscription Lifecycle Status The dashboard tracks the operational state of each application subscription: | Status | Description | | :------------ | :----------------------------------------------------------------------------------- | | **Pending** | Subscription checkout has been initiated but is not yet complete. | | **Active** | The subscription is active; credentials are valid and parsing is fully enabled. | | **OnHold** | Payment method update or outstanding action is required. Token requests are blocked. | | **Failed** | The billing gateway transaction failed. | | **Cancelled** | The subscription was terminated. | | **Expired** | The subscription has run its course and expired. | *** ## Administrative Plan Rules The control plane maintains plan lifecycle policies to ensure deprecated tiers do not cause system drag: * **Active Plans**: Tiers currently available for selection. * **Draft Plans**: Under host configuration; hidden from tenants. * **Archived Plans**: Retired for new subscribers, but existing applications already carrying the plan can continue to use it. * **Retired Plans**: Completely deactivated. **Any application still carrying a retired plan is immediately blocked from token issuance** and must migrate to an active tier. *** ## Related Documentation * [Developer Onboarding](/dashboard/onboarding) * [Authentication Token Model](/dashboard/authentication) * [App Setup & Configuration](/dashboard/app-setup)