HomeModules › Subscriptions
Module · Business processes

Subscriptions

Magazines, standing orders and bundles across their whole life cycle – from creation through invoicing and renewal to cancellation, with batch billing in runs.

At a glance

Manage subscribers without a second system.

Three kinds of subscription, one of them open-ended

Magazine, bundle and standing order – the last of these with an open term. Bundles are made up of components with a price and a discount of their own.

Supplementary billing, pro rata

If quantity is added in the middle of a period, the module bills it by the remaining days – first as a preview without saving, then bindingly with an invoice.

Batch billing in runs

One run invoices many subscriptions at once – in the background, with a result status per subscription and an error count that shows where to look.

MRR and the renewal pipeline

Active subscriptions, monthly recurring revenue, renewals in the next 30 days, trial subscriptions running out and last month's cancellations.

The module

A subscription lives longer than an invoice.

Subscriptions are not one-off transactions: they begin, they run, they are billed for additions, renewed and canceled at some point. This module carries them the whole way and hands over for invoicing to the same place as any other case.

A subscription belongs to an invoice recipient from the CRM and to a work or title from title data; the price follows from the title, the tiered price type and the quantity, with a preview while it is still being entered. It knows three kinds (magazine, bundle and standing order), and the standing order may run with no fixed end. Several line items can be kept under the same contract number; they inherit invoice recipient, delivery address, tenant, currency and calculation mode from the first subscription and are given consecutive numbers.

Around the master data lie the everyday cases. Dispatch and method of payment have fields of their own, and there are additional contacts for the ordering party and the document recipient. A temporary delivery address applies only for a period, for the summer or a sabbatical, say. On activation the module checks the free-subscription block and asks rather than overriding it. And digital access hangs on the subscription as entitlements, with an add-on code, serial numbers, a number of accesses and a term, created from templates, with a marker showing whether they have already been sent.

Two paths lead to an invoice. The individual one is supplementary billing: if quantity is added in the middle of a period, the module bills pro rata by the remaining days, takes the tier for the new total quantity into account and shows the result as a preview first, without saving. The bundled one is the billing run, a job across many subscriptions, with a period policy for the case of closed periods and options for a monthly invoice, totaling, collecting or individual treatment, as well as invoicing directly. It runs in the background and logs for every subscription what became of it. The invoices themselves are created in Orders & invoices and carry the tenant's number ranges.

Renewal happens with an eye ahead. The follow-on subscription is created at the press of a button, a safeguard prevents a double renewal, and the dashboard shows what is coming up in the next 30 days. Cancellation is recorded with a reason, a date, the end of delivery and the cancellation channel, plus the notice period and the supply-until date; trial subscriptions convert themselves if you wish, or run out with a reason of their own. Every change of status is in the history, beside the billing history with period, amount and a reference to the order created.

And because a subscription base is above all a number, the dashboard sums it up: active subscriptions, monthly recurring revenue, renewals and trial subscriptions running out in the next 30 days, cancellations in the last. Anyone wanting to look deeper will find the revenue in Reporting.

A look inside

Subscriptions in the application.

Subscriptions module in open.junixx: subscription list with number, invoice recipient, work, billing start and status
Subscriptions module in open.junixx: creating an invoicing job and the list of the latest runs with status, line items and errors
Subscriptions module in open.junixx: a subscription in detail with work, invoicing period, prices and the tabs from dispatch to bundle

Every subscription at a glanceSubscription number, invoice recipient, work, billing start and status – with a favorite star per row, filters for status, invoicing status, subscription type and work, saved filters and selectable column sets.

One run for many subscriptionsType, tenant, period and invoice date, plus the period policy and the switches for a monthly invoice, dispatch, totaling and invoicing directly – beneath them the latest runs with status, the number of line items and errors.

One subscription in detailWork, invoicing period, quantity, prices, currency and subscription type in the header; beneath them the tabs for additional information and dispatch, cancellation, entitlements, history and bundle. Renew and bill for additions sit beside them as actions.

See open.junixx at work. We show you on screen how the software fits your publishing workflows – with no obligation, and with time for your questions.

Book a demo
Interface

Import and export through the API.

Subscriptions live on recurring payment and regular delivery. That is exactly where the leverage lies on the outside – in collection and in delivery.

Facing outward, everything runs today through invoicing: supplementary billing and billing runs create invoices in the orders module, and from there an e-invoice to ZUGFeRD and XRechnung as well as the DATEV batch are available platform-wide. The subscriptions module itself has no import and no export of its own; payment type and method of payment are free-text fields, and the entitlements carry their delivery channel but as yet no connection to a platform. Recurring collection through SEPA or a payment service provider, the return path of the payment events and the delivery list to distribution can be added through the central API.

More on the interfaces

Detailed overview from the interface analysis: sources for import and possible targets for export.

Import – from external services

Source (external)What is importedUse in the module
Bank or payment service providerIncoming payments, direct debit returns, dunning statusInvoicing status paid or open, control of the cancellation
Payment providerSubscription events paid, failed, canceledThe subscription status follows the payment
Distribution service providerDelivery and return reportsDelivery quality and complaints
Web shop or customer accountNew subscriptions and changes of addressCreation with no data entry

Export – to external services

Purpose / triggerExternal service (examples)What is exportedFormat / standard
Recurring collectionThe bank's SEPA direct debit, Stripe, Mollie, GoCardless, PayPalAmount, cycle, mandate and customerSEPA pain.008, provider API
Delivery of the issuesPress wholesalers, lettershop, postal serviceDelivery addresses, print run, cycleCSV, REST API
Digital license deliveryContent platform, appAccess code and serial number per entitlementREST API, e-mail
Accounting through invoicingDATEVThe invoices and postings createdDATEV EXTF
In full

Every feature of Subscriptions.

Subscription list & search

  • Search across subscription number, contract number and name
  • Filters by status, invoicing status, subscription type, work and invoicing period
  • Columns from subscription and contract number through invoice recipient, delivery address, work and title to price, billing start and end
  • The next billing start, status, invoicing status and order number as columns
  • A page-by-page display with a selectable page size
  • Create a new subscription; deleting stays recoverable in the data

Master data & price

  • Tenant, subscription type template and order type
  • Selection of work and title through a picker and a select field
  • Quantity, subscription type magazine, bundle or standing order, status
  • The invoicing period; with a standing order, with no fixed end
  • Calculation mode, tiered price type, currency, next invoicing
  • Price net and gross with a live preview from title, tier type and quantity
  • Historical start, order channel, number of users, start of calculation
  • Order number, order reference, note, line item number

Several line items per contract

  • Additional line items under the same contract number
  • Inheritance of invoice recipient, delivery address, ordering party and document recipient
  • Inheritance of tenant, currency and calculation mode
  • Consecutive line item numbers, automatically

You will find the complete list in our brochure

What you see above is an excerpt. Every feature of this module – and of all the others – is collected in the open.junixx brochure. We will gladly send it to you, in print or as a PDF. And if you would rather watch than read: we are happy to show you open.junixx live on screen.

Get the brochure
A fit for

For publishers with continuing orders.

Magazines, loose-leaf works, standing orders, digital access – anywhere the customer does not buy once but stays on.

Connected to the publishing ecosystem

Portals
  • VLB
  • IDNV
  • doctronic
  • Amazon
Distributors
  • Bookwire
  • Arvato / VVA
  • Brocom
  • Prolit
  • Zeitfracht
Shops
  • Magento
  • WordPress / WooCommerce
  • Shopify
  • Shopware
  • Wirth & Horn
Accounting
  • Diamant
  • DATEV
  • BMD
  • Abacus
Shipping
  • DHL
  • DPD
Contact

Get to know open.junixx.

Arrange an appointment with no obligation. We will show you how Subscriptions fit into your publishing routine.