Home > Aria Crescendo Documentation > AMPS (Aria Media Publishing Suite)

AMPS (Aria Media Publishing Suite)


The Aria Media Publishing Suite (AMPS) is a purchasable add-on to your out-of-the-box Aria platform instance that provides business logic for managing digital or physical publication subscriptions, customers, and finances.

AMPS Architectural Overview.png

AMPS Features

AMPS enables the following publishing-related capabilities in your Aria instance:

Account Management

An account is required for each customer holding a subscription to one or more titles. The account object holds general customer data, including name, address, VAT registration, and/or business registrations. It will always have a non-billable subscription and payment agreement assigned. The payment agreement can be used for payable subscriptions as well. 

No communication is sent to the customer directly from AMPS. All communications are via external solutions. AMPS events are available for consumption when an account is created, modified, suspended, anonymized, archived or if the permanent delivery address has changed on the account.

Accounts are tracked as either Consumer or Business Accounts.

Consumer Accounts

Consumer Accounts in AMPS manage individuals, households, families, or students. They can hold one or more billable or non-billable subscriptions at any given time. Consumer Accounts support printed, digital and/or combined products.

Business Accounts

  • Used to manage business customers, such as SMB, Enterprises, etc. 
  • May hold one or more billable or non-billable subscriptions at any given time
  • Supports printed, digital and/or combined products with tracking of individual employees or subjects

Payment Agreements

A payment agreement is the agreement between the customer and client controlling financial aspects of the engagement and defines:

  • the payment option the customer has selected for settlement of invoices and other charges
  • the brand or title used in financial documents such as invoices, credit notes, dunning notices, etc. 
  • the communication preferences of the customer with regards to financial documents
  • the dunning terms assigned to follow-up on missing payments
  • the communication with the customer on financial documents

A payment agreement is used to group subscriptions under a brand or title and manage the billing of one or more subscriptions. It comprises a billing group and a Dunning group. AMPS events are available for consumption when a payment agreement is created, modified or removed

  • Billing Groups
    • Defines the brand/title used to brand financial documents such as invoices, credit notes, dunning notices, etc. 
    • Defines the customer selected payment option
      • supported payment options include Bank Transfer, Direct Debit, Credit Card, Mobile Payment, etc.  
      • selected among supported options for brand/title
      • together with term length the payment option defines the actual payment term/method assigned to the billing group
    • Defines the customer selected payment variant (e.g., Bank Transfer with Mail, Bank Transfer with e-mail, etc.). 
      • Used to manage variants of the same payment option (e.g., controlling whether surcharge is applied or not, or use of different due date calculations)
    • The payment option and variant controls:
      • the way Aria and AMPS managed payment gateways are used;
      • how financial documents are produced and/or distributed to external document management partners; and 
      • how under and overpayments inside or outside predefined thresholds are managed.
    • The payment option and variant supports use of both Aria and AMPS managed payment gateways
      • Aria-managed payment gateways include ADYEN, DIBS, etc. Gateways support both tokenized credit cards as well as credit card details stored in Aria
      • AMPS managed payment gateways include MOBILEPAY, SPID, etc. Gateways support tokenized credit cards or identifications only
    • Defines the customer selected delivery option for financial documents
      • Managed by the external partner handling distribution of financial documents
      • Examples are delivery by mail, delivery by email, delivery by email as HTML, delivery by email as PDF, etc. 
    • Each subscription is always assigned to a single billing group
  • Dunning Groups
    • Defines the dunning process to be applied
      • The payment option and variant defined on the billing group also applies for the dunning group
      • Together with term length the payment option defines the actual dunning process assigned
    • The dunning process controls:
      • the steps dunning must go through if payment is not received in due time;
      • the fees to apply at each step, and how fees of previous steps are managed; and 
      • the production of a final invoice at time of suspension.
    • Each subscription is always assigned to a single dunning group

Back to top 

Subscription Management

Multiple recurring subscription types supported

  • Print subscriptions handling addresses and distribution of physical papers or products
  • Digital subscriptions handling digital access rights provisioning for external websites
  • Combination (digital and print) subscriptions handling both addresses and distribution of physical papers as well as digital access rights provisioning
  • Bundle subscriptions handling eligibility checks and availability of special bundle products, providing additional services and features under certain conditions

Product Sharing

  • Allows master customers to share a paid product digital product with a number of invited members
  • Allows invitees to accept or reject invitations from a master. If accepted, the member gets full access to the digital product paid for by the master


  • Allows customers to be offered one or more special campaigns for a given price covering a certain period of time
  • Campaigns automatically roll over to a recurring subscription when the campaign is completed


  • Allows the customer to automatically receive certain discounts when adding more active subscriptions (e.g., get 10% of your second and third active subscription)
  • Client can also apply other discounts at their discretion (e.g., as retention offer or incentive)

Back to top

Title Management


  • A title defines the brand that publishes one or more times during the week
  • The title defines information such as name, address, telephone numbers, business registrations, email addresses, URL’s, etc.
  • The title defines information such as mapping of identifications used when communicating with other systems (e.g., ERP, Distribution, Access, etc.)
  • The title defines what distribution system that is used, and at what times the distribution takes place
  • A single title can be defined as the master title
  • A single title can be assigned to a billing group and/or customer account
  • A title is linked to a title owner, i.e. a company that may own one or more titles (brands)

Publishing Calendar

  • The publishing calendar defines what days of the week a title publishes a newspaper or magazine.
  • The calendar is date effective, so different schedules can be supported over time
  • AMPS integrates with timeanddate.com to retrieve details on national holidays (provided the client has a user with timeanddate.com)
  • Using the publishing calendar and holiday information, AMPS generates a set of dates which defining the publishing calendar.
  • The generated calendar can be modified after it has been generated to better suit the requirements

Payment Options and Variants

  • Payment option and variant defines the configuration of how invoices and dunning notices are settled
    • Supports the following payment options
      • Bank Transfers
      • Direct Debit (Avtalegiro in Norway, Betalingsservice in Denmark and Autogiro in Sweden)
      • Electronic Delivery (eFaktura in Norway and Sweden),
      • Credit Card via AMPS gateway (Mobilepay, SPID, VIPPS, etc)
      • Credit Card via Aria gateway (ADYEN, DIBS, etc)
    • Defines how invoices, credit notes and dunning notices are distributed to external partners and eventually to end-customers
    • Defines how payment identifications are generated for an invoice
    • Defines how underpayments are treated (e.g., what to do if the customer pays NOK 950 out of an invoice of NOK 1000)
    • Defines how overpayments are treated (e.g., what to do if the customer pays NOK 2000 for an invoice of NOK 1000)
  • For each title the valid payment options and variants are configured

Back to top

Distribution Management

Delivery addresses

  • Supports the definition of one or more delivery addresses for a customer
  • Supports multiple different address types (e.g., home address, business address, cabin address, etc.)
  • Delivery addresses contains two sets of details, namely:
  • General information on the address split over 4 different address lines (similar to Aria)
  • Detailed information on the address:
    • street name
    • street or house number
    • flat number
    • entrance number
    • floor
    • apartment number
    • additional client specific information
  • Also allows the ability to attach a government defined address number uniquely identifying the address within the country.

Address Changes

  • Supports creation of one or more future address changes (e.g., moving to the mountain retreat from August 1, 2020)
  • Supports split delivery of newspapers (e.g., delivery on weekdays to the home address, while weekend delivers are sent to the cabin)
  • Supports stop and start of delivery as well.


  • Distribution of address changes are generated and distributed to the distribution partner in due time, i.e. one or two days before it is supposed to take effect
  • Distribution allows for feedback on distribution problems (e.g., delivery did not take place to a full district or route)
  • Distribution can be done via batch files or in real-time (customization)

Back to top

Access Management

  • Services in the individual products define the features to which access is given
  • Access Features can also be provided via the digital title code settings on the products
  • Integrates with external access control systems to provide end-customers with access to digital content
  • Changes are pushed out when a change in subscriptions occur (e.g., adding a new subscription or cancelling a subscription)
  • Current access details can also be requested or refreshed when required.

Product Management

  • Refreshed automatically when updates are performed in Aria
  • Refreshed on request
  • Use as a caching mechanism to improve performance – no need for Aria API calls

Back to top

Financial Management

The Financial Management module tracks financial transactions within AMPS. It links invoices, payments, credit notes and other transactions to form a history of balance changes. It also handles the integration with external ERP systems in the scenarios which AMPS is generating this information.

Back to top

Bundle Management

  • Allows client to create products acting as bundled services:
    • Providing digital access to more titles than the product purchased
    • Providing an incentive to buy more products to get more services
  • Bundle eligibility depends on
    • Sequence of bundles. Better bundles checked first; eligibility check is stopped when an eligible bundle is found.
    • Number of existing active subscriptions
    • Monetary value of active subscriptions
  • Bundle eligibility is checked when
    • Subscription is offered. Customer can chose the original offered product or the bundle, but not both
    • Subscription status is changed (e.g., becoming suspended or canceled)
  • Bundles are defined as independent products
    • With individual title codes
    • With individual access services
    • With individual pricing

Back to top

Campaign Management

  • Allows client to offer campaigns to existing and new customers during the sales process:
    • Buy access for 10 weeks for €10
    • Buy newspaper delivery for 5 weeks for €5
  • Customer is presented with first eligible campaign or all eligible campaigns, depending on configuration
  • The campaign definition defines:
    • The validity period of the campaign
    • The duration of the campaign
    • The cost of a campaign (€0 campaigns are allowed)
    • The purchase restriction to be fulfilled for a campaign
    • The titles and products for which the campaign is available
    • Whether previous purchase of the campaign prevents new purchases with a period of time.
  • Campaign automatically rolls over to a paid plan at the end of the campaign period.
  • Retractions apply during cancelation:
    • It is not possible to cancel a subscription during the campaign
    • Future cancelations are supported after the campaign is completed.
  • If Subscription is created immediately
    • As an active subscription with a first bill date to the date after the campaign ends
    • An initial order is immediately created for the campaign cost. This is a one-time purchase
    • Access rights is pushed out based on the status of the subscription, not the campaign
  • If Subscription is created in the future
    • As an inactive subscription with a first bill date to the date after the campaign ends
    • A future change is registered to activate the subscription on the start date of the campaign.
    • An initial order is created on the campaign start date for the campaign cost. This is a one-time purchase
    • Access rights is pushed out based on the status of the subscription, not the campaign, i.e. it will not be activated until the campaign is activated

Back to top

Discount Management

  • Discount configuration is matched using Aria core functionality
    • A discount rule must exist in Aria core
    • A coupon must exist in Aria core
    • The discount in AMPS is linked to the coupon defined in Aria core
    • New discounts are automatically synchronized with Aria core
  • Discounts are defined as ….
    • Percentage based discounts, i.e. 10% off the subscription value.
    • Amount based discounts, i.e. 10€ off each invoice.
  • Assigning multiple discounts to a subscription will give customer more discount off
    • Assigning a 10% discount and a 15% discount will result in 25% discount being given
  • Discounts are assigned ….
    • Automatically based on purchase volume, i.e. from third subscription you get 10% off, from fifth subscription you get 20% off and so on
    • Manually on request from client staff.
    • Existing discounts can also be removed by client staff

Back to top

Document Management

  • Handles different document types, namely:
    • Invoices
    • Credit Notes
    • Dunning Notices
  • Integrate with external document partners to ….
    • Allow partner to format documents based on information received
    • Allow partner to distribute documents based on payment option received
      • Avtalegiro/Autogiro
      • eFaktura
      • EHF
  • Payment option and variant defines
    • Format to be used
    • Destination of documents
    • Calculation of invoice references
    • Collection method to be applied, i.e. avtalegiro/autogiro, bank transfer, credit card, etc.
  • Integrate with one or more external partners
    • Selection of partner is done by payment option and variant
    • Selection of document format is done by payment option and variant
  • Support different formats such as …..
    • AMPS XML – the standard AMPS XML format which contains all relevant information including document texts and details from titles
    • OIOUBL – another XML format closely related to EDI standards

Back to top

Payment Management

  • Handle agreements for automatic collection or presentation
    • Collection via Direct Debit (Avtalegiro/Autogiro, Betalingsservice, Bankgirot, etc)
    • Presentation via electronic means (eFaktura, EHF, etc)
  • Handle incoming payments from financial institutions such as
    • Bank transfers
    • Avtalegiro/Autogiro payment confirmations
    • Credit cards
  • Handle Collection via AMPS Payment Gateways
    • Support for Mobilepay and SPID
    • Funds are requested when invoice is issued
    • Funds are received immediately or by callback from the gateway
    • Funds are confirmed on receipt of confirmation files
  • Matching payments received with invoices and accounts
    • Matching is performed on Customer Invoice Reference (KID/OCR Number). The number is provided in the document XML or defined as a previously created agreement
    • If payment cannot be matched it will be rejected and placed in the unmatched payment component.
    • If payment received is under the invoiced amount, but within a threshold, the missing payment can be written off
    • If payment received is over the invoice amount, the excess payment can be placed on the account for future invoices, or immediately refunded to the customer
  • Handling refunds
    • Registration of refunds based on previously received payments
    • Refunds over a configurable amount will require approval from another client staff member
    • Refunds are executed via the original payment method or via integration with financial institutions

Back to top

Complaint Management

  • Registration of complaints including information such as:
    • Identification of the subscription the complaint is related to
    • Information on why the complaint has been raised
    • Information on the date the complaint is for
  • Complaints apply to ….
    • Digital products
    • Print products
    • Print and Digital products
  • Checking complaint eligibility
    • Was the end-customer’s subscription active on the date of the complaint
    • Was the end-customer’s product published on the date of the complaint
    • Was the end-customer’s product configured to deliver the paper on the date of the complaint
  • Automatic compensation of the end-customer
    • Automatically compensate the customer for the missing deliveries
  • Information on complaints can be sent to distribution companies
    • Depending on the reason for the complaint information can be sent to distribution partners

Back to top

Tax Management

  • Form the foundation of tax calculations in AMPS
    • VAT is calculated based on the tax group assigned to services
    • VAT configuration is held in AMPS, but is a copy of the Aria configuration
  • Automatic replication from Aria
    • Schedule replication of the TAX configuration in Aria is available

Back to top

Solution Management

  • Handling of Aria events

    • Receives events from Aria based on the Aria format
    • Events received are logged for audit trail purposes
    • Events are forward to different processes within AMPS based on the type of event
  • Handling of AMPS events
    • Receives generated events from other parts of AMPS
    • Events received are logged for audit trail purposes
    • Events are forwarded to relevant external client systems
  • Handle receipt and sending of integration files via SFTP
    • Handles receipt of integration files from external partners
    • Logs details on the received files as an audit trail
    • Handles distribution of files generated by AMPS to the external partners
    • Logs details on the sent files as an audit trail
  • Covers general utilities and functionality of AMPS
    • Handling of translations to local languages for objects such as campaigns, discounts, bundles, complaints, etc.
    • Handling of locales defining the languages supported
    • Handling of follow-ups on different objects

Back to top

Last modified



This page has no classifications.