Managed Subscriptions - Article
Summary
Managed subscriptions let administrators provide a subscription under an agreement handled outside online checkout—for example invoicing, a purchase order, a negotiated customer contract or access provided without a separate fee. Eurekos manages the subscription relationship and learner access; external finance processes remain responsible for payment and invoicing.
The model separates commercial administration from day-to-day learning operations. An administrator configures the agreement, the invited owner accepts it, and that owner manages learners. Renewal configuration determines whether the agreement continues automatically or needs deliberate follow-up before expiry.
Use this article to:
- Choose Managed access for an external procurement or service arrangement
- Configure the owner, billing model, allocation and start date
- Distinguish automatic continuation from reminder-led renewal
- Understand acceptance, editing and owner capabilities
- Keep recorded financial information aligned with the external agreement
Use the model for the actual business arrangement
Online recurring payments do not suit every organization. A customer may require a purchase order, centralized invoicing or an annual agreement aligned with its financial calendar. A provider may include training in a broader product or support contract. A public institution may need its own procurement process while still delegating learner administration to a local contact.
Managed subscriptions allow those arrangements to use the same maintained subscription content rather than building a duplicate library. The recorded price, period and transaction information support operational reference and reporting. They do not mean a credit card is charged, an external invoice issued or confirmation that the customer paid it.
Example: A supplier agrees an annual service academy with a regional distributor. Finance invoices under the wider service contract; the distributor's training coordinator assigns access to technicians in Eurekos. The provider retains responsibility for the agreement, while routine learner changes do not have to become a new support request each time.
Create the agreement from Ownership and billing
Open Course administration → Subscriptions → Ownership and billing → Create managed subscription. Select the existing active subscription definition and enter the intended owner's email, first name and last name.
The selected definition supplies the learning offer and available billing periods and currencies. The managed record supplies the customer-specific arrangement. Do not create a new subscription definition solely to represent a different invoicing contact or negotiated price if the underlying offer is the same.
An owner who already has the same subscription through another type cannot simply receive a duplicate managed assignment. Review the existing relationship before replacing an arrangement. Applicable organization filtering can also restrict whom the administrator can select or invite.
In the form, the owner and access arrangement sit alongside the optional customer information. The following unsaved example uses a monthly Per user agreement with 20 seats; it is a sample configuration, not an issued invoice.

Choose Per user or Fixed billing deliberately
| Billing model | Allocation behaviour | Business implication |
|---|---|---|
| Per user | Price calculation uses the agreed seat quantity; the owner has no Add seats purchase action | Suitable when the commercial agreement depends on the licensed allocation |
| Fixed | The price is independent of the member count; supported owner Add seats does not trigger payment | Suitable for a fixed agreement where growing operational membership should not initiate online charges |
This is an important difference from describing every Managed subscription as a fixed maximum the owner can never exceed. Under Fixed billing, the supported allocation behaviour is different from Per user licensing. Reflect that choice in the customer agreement and support guidance.
Choose the billing period, currency and negotiated price. Review Cost information, including the configured tax presentation. The form explicitly identifies this as an estimate based on the settings, with no payment triggered. Agree how your finance or account team will reconcile it with the external contract.
Set the start date as the agreement's billing anchor
The Start date defaults to the creation date. The current form supports today or a past date, allowing the recurring schedule to be aligned with an existing agreement rather than always beginning on the day an administrator enters it.
For example, recording an agreement after its agreed start can align its billing calendar with the customer's established cycle. A backdated anchor is not evidence that learning took place before the record existed, and it should not be used to manufacture historical attendance or completion.
The start date is not an editable field on an existing managed record. Review the selected date and the resulting schedule before creation. Do not assume that future scheduled activation is available through this field.
Choose how renewal should be controlled
Automatic renewal is off by default. With it disabled, configure the reminder-led process and arrange an extension before the period ends if access should continue. If no continuation is arranged, the managed subscription reaches its end rather than collecting a payment and renewing itself.
With Automatic renewal enabled, the agreement continues at each period end without a manual renewal confirmation. This is continuation of a managed access arrangement, not an automatic collection of the external invoice. Renewal reminders are hidden and the managed owner/admin renewal-reminder emails are not sent for that automatic continuation.

Choose the option to match the contract. Automatic continuation can reduce routine administration for an ongoing service. A fixed-term pilot or agreement requiring an annual commercial review may be better served by reminders and an explicit extension. The checkbox should not contradict the customer's actual termination or renewal terms.
Configure reminder-led follow-up
When automatic renewal is disabled, use Who should be informed about renewal? for the relevant additional recipients and Inform for the number of days before the period ends. The owner is informed through the managed renewal workflow; the additional recipients help route the follow-up internally. The default lead time is one day, so choose a longer interval when procurement or negotiation requires it.
Use Comment for actionable context, such as “Review subscriber usage with the regional training coordinator before preparing the renewal.” Do not put unnecessary sensitive contractual information into a message distributed to a broader recipient list.
Example: A customer requires a purchase order before renewal. Notify the account team sufficiently early to review uptake, confirm the next allocation and obtain approval. A reminder starts that work; it does not itself extend access or prove that a purchase order was accepted.
Further down the same sample form, the estimate and reminder fields make these separate responsibilities visible. The displayed tax follows this example platform's configuration; it is not a universal rate.

Record the appropriate customer information
The Payment details section records the customer type and relevant contact/address details for documentation. These fields do not create an external invoicing integration merely because they are populated.
Agree who maintains the financial source of truth and how discrepancies are corrected. A fixed negotiated price and a seat allocation should describe the same agreement in the platform and in the organization's external process.
Complete owner acceptance
After reviewing the owner, billing and renewal choices, select Create to create the Managed subscription invitation. The intended owner must accept before they become the owner and can manage it. Review the invitation's pending state in Ownership and billing rather than treating a populated form as an active customer arrangement. Creation and acceptance do not collect an external payment or automatically assign a learner seat to every intended participant.
A registered recipient can accept through the invitation email or the pending Managed entry under Subscriptions. If the recipient finds the subscription's Storefront page while the managed invitation is pending, the purchase route can direct them into acceptance instead of starting a duplicate purchase. An unregistered recipient starts from the invitation and completes the required signup before management access is available.
If the recipient declines, the administrator is notified and the agreement is not established for that owner. Review the intended contact and create the appropriate invitation rather than assuming a declined invitation transfers itself to someone else. Some integration-created managed assignments follow a different activation route; coordinate those workflows with the implementation team rather than assuming every API assignment waits for the same email acceptance.
Let the owner manage the learning relationship
After acceptance, the owner can assign available seats, invite learners, unassign members and use supported seat-lifecycle actions. Transfer seat depends on the definition's Allow seat transfers between users option. Owners can also enroll eligible assigned members in included activities through the supported single or bulk routes.
Per user and Fixed allocation differences still apply. A Per user owner cannot use the self-service Team purchase route to increase the agreement. A Fixed owner's supported Add seats action does not charge a payment. The ability to see Transactions and to deactivate their own Managed subscription can depend on platform configuration; these are not universal owner controls on every platform.
The accepted Managed owner can use Go to analytics to open the read-only My subscribers progress view, with the supported Learning performance and Active users subscriber views also available through ownership. General Analytics permission is not required for this separate scope. These views concern the owner's subscriber relationship, not unrelated platform users or a permanent historical roster. Use Cases and Management Overview owns the detailed seat, enrollment and subscriber-analytics procedures.
Edit or extend the agreement deliberately
Locate the record in Ownership and billing and use the applicable More action. Editing does not make every field changeable: the underlying subscription, billing model, payment-details section and start date are not editable in the managed form.
An administrator can increase the quantity for a Per user agreement; it cannot be reduced through that field. The cost estimate changes, but no payment is collected. For an accepted agreement, the added seats are created when the edit is saved. For a pending invitation, the quantity is updated but seats are not created until acceptance. Under Fixed billing, that field is not the mechanism for changing the price-independent membership allocation.
Review changes to price, period, currency and renewal controls against the agreement. Updating a pending invitation sends a new email and invalidates the earlier one; tell the recipient to use the latest invitation. A change to the underlying offer or billing model may require a replacement agreement instead of editing the existing record.
Where available, Extend managed subscription adds one current billing period to the existing schedule. Review the resulting next date before confirming. Extending before expiry preserves the remaining time rather than beginning a replacement period on the day the account team starts the renewal discussion. Do not wait until after access has ended and assume an expired record can always be restored in place.
Worked renewal example: keep early agreement and access dates aligned
Suppose an annual Managed agreement has a displayed period end of 16 March 2027. The customer requires a purchase order, and the account team needs time to review usage and confirm the next allocation. With Automatic renewal off, a 30-day reminder lead time is a more useful planning choice than waiting until the final day. The reminder starts the follow-up; it does not confirm the purchase order or extend access.
If the annual continuation is agreed before expiry and the supported extension dialog confirms 16 March 2028 as the next date, the new period is added to the existing schedule. Do not restart the year from the earlier day on which the account manager happened to arrange the renewal. Review the actual confirmation before saving.
| Responsibility | Practical follow-up | Evidence to retain |
|---|---|---|
| Customer contact and account team | Review learning use, continuing needs and the agreed allocation before expiry | A documented decision about the service to continue |
| Finance or procurement | Complete the external purchase order, invoice or agreed settlement process | The external financial reference, not only a platform estimate |
| Authorized administrator | Apply the appropriate extension and verify the resulting date | The confirmed subscription schedule and continued access under the agreement |
An automatic-renewal agreement uses a different operating model: access can continue without this reminder-led cycle, but external finance still needs its own reliable process. Choose the model that matches the contract rather than relying on a reminder that the chosen configuration suppresses.
End access without confusing it with external settlement
Use the applicable cancellation action for the managed owner and inspect the effective expiry date. Ending access in Eurekos does not cancel an invoice in an external finance system, issue a credit or settle a contractual dispute.
Communicate the date to the customer and affected learners. Earned certificates remain visible through the documented profile, transcript and reporting routes, subject to normal retention policies. Avoid a blanket statement that every incomplete enrollment and all subscription-management data remain after every cancellation or whole-offer deactivation.
Keep communications consistent with the chosen lifecycle
Maintain templates through Settings → Email sending → Subscriptions. The important local events are the managed invitation, acceptance or decline, and reminder-led renewal. Automatic renewal changes the reminder behaviour; do not promise those reminders when the option suppresses them.
Use System Email Notification Overview for the canonical trigger and recipient matrix and Email Sending for configuration. Review recipients and dynamic dates during testing rather than maintaining another exhaustive email list or relying on an old email screenshot.
Troubleshooting
| Problem | What to check |
|---|---|
| A value is recorded but no payment arrived | Managed billing is external; the record does not collect an invoice |
| The invited owner cannot manage the agreement | Check acceptance, registration, the latest invitation and applicable organization scope |
| The recipient already has the subscription | Review the existing Personal, Team, Managed or pending relationship before creating a duplicate |
| A future start date cannot be selected | The current field supports today or a past date; it is not future activation scheduling |
| Renewal reminders disappeared | Check whether Automatic renewal is enabled |
| The subscription continued without an invoice payment | Automatic renewal continues managed access; external settlement remains separate |
| A Per user owner cannot add seats | The administrator maintains that allocation under the agreement |
| A Fixed owner can add seats without payment | That is different from Per user licensing; review the intended contract model |
| The administrator cannot reduce the seat quantity | The Per user edit field only supports increases |
| Additional seats are absent before acceptance | Pending edits update the offered quantity; seats are created upon acceptance |
| An earlier invitation fails | Editing a pending agreement invalidates the previous invitation email |
| Transactions or Deactivate is missing for the owner | Check the platform's Managed subscription configuration and applicable permissions |
FAQ
-
Does Managed automatic renewal collect the customer's external invoice?
No. Automatic renewal continues the managed access arrangement at each period end without manual renewal confirmation. It does not collect an external invoice. It also hides the renewal-reminder workflow and suppresses the managed renewal-reminder emails used for reminder-led renewal.
-
Do Per user and Fixed Managed subscriptions use the same owner seat-expansion controls?
No. Under Per user billing, the owner does not have an Add seats purchase action and the administrator maintains the agreed allocation. Under Fixed billing, the supported owner Add seats action does not trigger online payment because the price is independent of the member count. Choose the model to match the actual agreement.