Use this page to understand your tenant’s contract and usage. Contact your implementation partner for amendments, renewals, or licensing restrictions.
Routty Cloud records document usage centrally and shows contracts and consumption to the tenant and implementation partner. The contract determines the licensed product area, period, document volume, and any included compliance, premium connector, or archive components.
Contract models
|
Model |
How the document volume applies |
|---|---|
|
Subscription |
A document allowance for each contract year. Usage resets at the contract-year boundary, not necessarily on 1 January. |
|
Buckets |
One document allowance for the contract period. There is no annual reset; renewal and carry-over follow the contract settings. |
|
Yearly Buckets |
A bucket allowance that resets each contract year. |
|
Pay-As-You-Go |
Usage is reported without a base-document volume cap. This does not imply that every additional license component is included. |
Use the dates, quantities, and components shown on your contract. Do not assume that every subscription or bucket has the same duration.
Contract status
-
Draft: the contract has not been activated.
-
Active: the contract has been activated. Its dates determine the period to which usage can be attributed.
-
Inactive: the contract has been deactivated; this is not an unused bucket waiting for consumption to begin.
-
Expired: an active contract is past its end date.
Reaching a volume limit and reaching the contract end date are different situations. Exhausting an allowance does not itself mean that the contract status becomes Expired.
Usage and document counting
Where processing-time licensing is enabled, Routty checks the license after routing has been determined. Usage is also updated from document changes. Dashboard figures can take time to reflect processing; they are not governed by a single nightly counter refresh.
|
Situation |
Base-document quota |
|---|---|
|
Initial processing |
An eligible document counts once. Successful delivery is not the sole condition for counting. |
|
Processing error |
A document can still count once after the company and tenant have been determined, including errors before or after the licensing check. Not every failed upload or unidentified document is therefore counted. |
|
Reprocessing |
Reprocessing runs are recorded separately and do not add another base-document quota charge for the same document. |
|
Lifecycle documents |
Lifecycle status and response documents are excluded from document metering. |
|
Test and Production |
The environment is recorded, but Test documents are not automatically exempt from document quota or assigned a separate free allowance. |
Inbound and outbound documents both contribute to base usage. Base-document volume, compliance usage, premium connector usage, and archive usage describe different license components. A connector's Free classification does not make the underlying document exempt from base-document metering.
Licensing decisions and processing
Processing can be refused when the applicable licensing policy enforces missing-contract or quota restrictions. Do not assume that overusage always continues, or that every exceeded limit is automatically blocked. Availability depends on the applicable contract and licensing policy.
A licensing refusal produces LicenseBlocked and stops the document for review. The refusal does not register the refused attempt as an additional processed document. If the original document was already counted before an earlier processing error, that earlier usage is not undone.
A temporary licensing-service failure is handled as a processing retry rather than an immediate contract-refusal decision. If the issue persists or retries are exhausted, contact your implementation partner or support.
Resolving LicenseBlocked
-
Open the document and inspect its error message and audit logs for the licensing refusal reason.
-
Ask the implementation partner or authorized licensing administrator to check the tenant and partner coverage, applicable contract dates, remaining volume, and required license components.
-
Have the contract or entitlement issue corrected. Repeatedly resubmitting the same document does not resolve a licensing restriction.
-
Resume the document where that action is available, or reprocess it after the correction. Licensing is checked again; confirm the outcome in the document status and audit trail.
Do not create a duplicate upload to work around a licensing refusal.
Viewing usage and changing contracts
Customers can inspect the contracts and usage available for their own tenant. Implementation partners can inspect their own contracts and the tenants they manage. Review the current period, used and available volume, and any warnings or notifications before requesting a renewal or amendment.
Contract creation, activation, deactivation, and amendments are performed by authorized licensing administrators in the licensing portal. Read access to a dashboard does not grant those administration permissions. Customers should contact their implementation partner for contract questions.