Yrka uses a set of defined billing statuses to communicate where your account stands in its lifecycle. Each status has real operational consequences — some statuses restrict features, some block server-side sync, and some limit what admins can do in the workspace. Understanding your current status and your plan’s capacity limits helps you avoid disruptions before they affect your team. OpenDocumentation Index
Fetch the complete documentation index at: https://docs.yrka.io/llms.txt
Use this file to discover all available pages before exploring further.
/admin/billing to see your current status, capacity posture, and any account notices that require attention.
Billing status reference
Each status describes a distinct phase in the account lifecycle. Your account moves through these states based on payment activity, plan choices, and owner actions.Demo
Your account is active but operating in a limited mode before paid activation or managed approval. Some features may be restricted or scoped to evaluation-level access. Demo accounts are intended for pre-launch review, not production use. What to do: Start checkout to move to a trialing or active state, or contact support if your account is on a managed activation path.Trialing
A trial is active. Your card has been collected and a trial period is running. Full features are typically available during trial, subject to plan limits. What to do: Review your trial end date on the billing page. Understand what happens at renewal — whether the subscription activates automatically or requires manual confirmation. If you need to cancel before renewal, do so through the Stripe billing portal before the trial ends.Active
Paid or managed access is fully active. All features within your plan limits are available. Server-side sync, provider integrations, and write operations work normally. What to do: Nothing urgent. Review capacity posture periodically as your roster grows. Use the billing portal to update payment methods or view invoices.Past due
A payment attempt failed. Your account is still accessible but is in a degraded state — new server-side sync writes may be blocked or limited depending on how long the account has been past due. What to do: Open the Stripe billing portal from/admin/billing and update your payment method or complete the outstanding payment. Resolve this promptly — continued non-payment leads to suspension.
Suspended
Access is blocked until the account is recovered. Suspension typically follows extended past-due status or a policy violation. You may still be able to reach the billing page to view options, but most workspace features are unavailable. What to do: Use the support path shown on the billing page. Do not create a new workspace or clear browser data while suspended — resolving the original account is almost always the right path.Canceled
Paid access has ended. The workspace may be in a read-limited or export-only mode. You are likely approaching or already in an export retention window. What to do: Export any data you need to preserve. If you want to reactivate, check whether reactivation is available from the billing page or contact support. Reactivation options depend on how long ago the account was canceled.Export retention
Your account is in a post-cancellation retention window. Data is still accessible for export or reactivation but no new operational work is being recorded. What to do: Download all records you need — employee data, payroll history, schedules, documents, and resources. The retention window has an end date. After it closes, reactivation may no longer be possible and data may no longer be accessible.Deletion requested
A verified owner has submitted an account deletion request. This status means the request has been recorded, not that deletion has been executed. Deletion is processed by support or an operator and may take time to complete. What to do: Wait for support or operator confirmation. Do not create a new workspace under the assumption that the old one has already been deleted. If you submitted the request in error, contact support immediately.Manual billing
Your account uses support-managed billing metadata instead of the self-serve Stripe portal. This is typically used for enterprise or managed accounts that are not on the standard self-serve path. What to do: Use the support path shown in the app for all billing actions — plan changes, capacity adjustments, and payment updates go through your support contact rather than the Stripe portal.Employee capacity limits
Your plan includes a maximum number of active employees. The capacity limit applies to employees in active, leave, and seasonal statuses — these all count as occupied seats on your plan.How capacity is counted
| Employee status | Counts toward capacity? |
|---|---|
| Active | Yes |
| Leave | Yes |
| Seasonal | Yes |
| Inactive / archived | No |
What happens when you approach the limit
As you get close to your plan’s employee limit, Yrka shows a capacity warning on the billing page. The warning appears before you actually hit the limit so you have time to act. When you reach the limit, you cannot add new active employees until you either reduce your active count or upgrade your plan.Capacity warnings do not block existing employees from using the workspace. They only prevent new active employees from being added.
Resolving a capacity warning
Review your active roster
Open the employee list and look for people who are in active, leave, or seasonal status but are no longer working at the organization. Move those employees to an inactive or archived status to free up capacity.
Move inactive employees out of capacity-counted statuses
Change the status of employees who are no longer active. This immediately frees their seat without affecting their historical records, past timecards, or payroll data.
Checking capacity and plan details
Open Billing Account
Go to
/admin/billing. The capacity section shows your current active employee count versus your plan limit.Review account notices
Any capacity warnings, past-due alerts, or lifecycle notices appear at the top of the billing page. Address these before they become blockers.
Common billing issues
The billing portal is not available
The billing portal is not available
The portal appears only when Stripe billing is attached to your account. If your account is on the managed billing path, use the support path shown in the app instead. If you expect self-serve billing but the portal is missing, contact support.
An invoice is missing or not showing
An invoice is missing or not showing
Invoice summaries appear in Yrka only after Stripe sends a verified billing event. If a recent invoice is missing, check the Stripe portal directly or contact support with your billing period and expected amount.
I cannot add employees even though I'm under the limit
I cannot add employees even though I'm under the limit
Confirm your account is in an active or trialing state. Past-due and suspended accounts may block new writes even when capacity appears available. Resolve the billing state first.
My offline queue is blocked
My offline queue is blocked
Account lifecycle state can block server-side sync even when local actions appear to succeed. Preserve your queued items and resolve the account state before attempting to sync — clearing browser data can cause queued work to be lost.