Try our translator
Try our translator
Try our translator
Total number of new orders pr day per Organization (summarized over the last 30 days in the dashboard)
Total number of active subscriptions pr day per Organization (summarized over the last 30 days in the dashboard)
Total number of Cancelled subscription pr day per Organization (summarized over the last 30 days in the dashboard)
Incoming payments pr day pr organization (summarized over the last 30 days in the dashboard)
Low price subscriptions percent
Percentage of subscriptions on price lower than full price pr day pr organization (summarized over the last 30 days in the dashboard)
The system can contain one or several organizations. The main reason for using several organization is to separate economies.
We create organizations under Systemdata – Organizations.
In subscription plan we have the possibility to apply the accounting organization for the spesific subscription plan. If this is not set we have to manually select organization when adding subscription plan to a subscriber. If database only have one organization it will be set by default.
In the subscribers overview all of subscribers data is visible across organizations. We can still filter the economy of the subscriber by organizations.
The Infosoft text filter will show results from all of the columns in every row. If any customerdata starts, ends with or contains your search, it will be displayed. Customers are filtered in ascending order and can be changed by using the arrow beside “name” in the top title. Results can also be filtered by buttons in the top title row, and it allows you to search within the specific column.
Overview button on the right side is for directly accessing what you are looking for.
The download button top right downloads a local file of your currently displayed result.
When placing an order with Infosoft we use a customized URL that brings your customer to our salesposter for completing order and payment. URL normally looks something like this:
URL mainly contains data about what type of product is being ordered and what payment types that should be available for customer. In addition there are many other order specifications that can be done.
First page of salesposter is registrating email user and creating a password:
Second page is gathering some personal data, choosing paymenttype and completing order:
After completing order customer is sent to the provider chosen for payment. When payment is completed the paymentagreement is saved to subscribers account in your database.
Open a subscriber and click Add new.
Choose the desired subscription plan.
Copies – How many copies to add
Start date – This can be changed to a future date
Payment method – Can be chosen if already exists
Permanent Discount – Select a permanent discount price (configuration details here)
Reporting Tags – Used for report statistics purposes
Continue order – Continue order with customer as billpayer
+ Add payer – Continue order with another billpayer
When startdate is set to a future date the invoice duedate is changed from normal billing plan rules. If startdate is less then the billing plan date (normally 14 days) the duedate calculated of registration date + billing plan date. And if startdate is bigger then billing plan date the due date is equal to the startdate.
Subscription can be cancelled during period or at the end of it. If a stop is made mid-delivery the invoice is credited and subscribers and economy Ledger will be updated with the remaining amount to be paid or credited.
Subscription cancel can be done from the Subscription overview.
Subscription stop today can be done from several different subscriber situations:
A subscription stop in future time can be changed or removed from subscribers overview.
Reason for change is required.
NB. If subscription is stopped < then 14 days the invoice gets credited. If we choose to restart subscription again the subscription will be active without invoice to be paid.
Subscription stop is available through subscription overview by pressing Details – Pause subscription on the subscription plan you want to pause. Stop date is locked as renewal date of the ongoing period and you are asked to fill in Start date from when the pause ends.
When the pause ends the subscription plan is started up again automatically as it was before unless you change subscription plan to a different one. In that case it will start with the selected subscription plan on the start date chosen.
After pressing Save you will have to confirm the pause and it will begin at the end of current period.
Temporary changes is a menupoint that will only show if subscriber has a product with physical delivery. We can do two different changes for the physical product. Add new move or Add new stop.
For this subscriber we have saved a temporary stop between 15th of may – 19th of may. Subscription itself and digital access will remain active, but physical delivery will stop in period.
From 1st of June a move is registered without a enddate. This move will last until New move home is set.
The subscribers overview provides an overall picture of the subscriber. Top line contains basic customerinformation which is editable through the Edit button top right.
Subscriptions lets you edit or stop subscription. Press “Details” to see all data of the current subscription.
Invoices is a list of all invoices created for the subscriber plus a draft of the upcoming invoice.
Payments shows history of payments registered.
Economic journal contains the economic day by day transactions for the subscription.
Connect user lets you connect both main user and connected users if subscription plan is configured with additional users. For online login purposes.
Payment Agreements payment agreements connected to subscriber
Contacts other potential contacts connected to the subscriber. Billpayers are saved here.
Notes write subscriber notes for internal use
Order confirmation service for sending confirmation of subscription to customer.
In some cases, you may want to block new orders from certain subscribers. This might be due to a bad credit check or that its a former subscriber with unpaid amount. Setup of denial orders can be handled under Systemdata – Configuration > Order blockage where you can type the exact negative amount of when to deny an order for the current organization. When a subscriber obtains a negative amount equal or larger to what the configuration says system will generate a blockage on the subscriber. Web orders from subscribers with a registered order blockage will be prevented from making new orders.
When opening a subscriber we can also manually add or delete an order blockage from Order blockage tab. If you want to blacklist a subscriber you simply add a order blockage on that subscriber. Subscription cannot be started on a subscriber as long as order block is active.
To create a new product go to Subscription plan – Products – Add New.
Description will show on customers online order and receipt.
Part number and External part number is both used by third party softwares.
NB. Both Name and Description needs to be less then 45 characters when used with Vipps paymenttype.
A product needs to be included in a subscription plan for it to be available for sale.
To create a subscription plan click Subscription plan – Subscription plans – Add New.
This plan allows you to make a bundle of one or more products for a set price. Step 4 decides the bundle price and step 5 decides what will happen after the subscription plan expires.
Mypage is your customers login for managing their own subscriptions. It provides an overview over active, historical and future subscription. All personal details like name, address, email etc. Invoices are listen under economy.
Chosen payment type is shown and it can be changed to another optional payment type from Mypage.
If subscription has been passive for less then 3 months, it can be restarted by subscriber.
Group subscriptions is a feature that lets a subscriber have additional extra logins in a single subscription. Subscriber can share his additional users when logging into Mypage. This can also be done through the merchant client.
To setup a subscription containing several digital users we use p.7 in the subscription plan creation.
Select product the additional users should have access to, and how many extra users should be available:
User can go to Mypage and Admin users to manage digital users:
Actual Count = Active digital users
Allowed Count = How many available users
Adding New user:
Email/User name = Add valid email address
Organization = Select organization for subscription
Admin: Digital user can edit subscription through Mypage.
User: Digital user can not edit subscription and has no access through Mypage.
Additional user added:
This economic feature is either turned on or off for your entire system.
If turned on, the Ledger billing supports changing the payment demand based on outstanding balance (positive or negative), in case of a positive balance the price should be reduced, in case of a negative balance the price should be increased for upcoming invoice. If invoice price is changed you will see why it differs to original price under Invoice details button.
In this example of Invoice details the subscriber has overpaid 100kr from earlier. Invoice amount is therefore reduced from NOK 249 to NOK 149:
In addition the system is able to split payments and connect them to invoices with outstanding amounts. For example if a subscriber has multiple demands wich have not been settle, and a single large payment is added to one of the demands, the payment will split and settle the other demands as long as payment lasts.
Product price is basically chosen when creating a new product. However the price can be overruled when included in a subscription plan.
Both Part number and External part number can be used to link product with a CRM or third-party system.
After the product is created you can edit price by opening the product in Subscription plan – Products.
Red prices are historical, green price is the active price and the upcoming prices will show in blue text.
The Add price button lets you change price for other frequencies, while the button is used for changing price with the current frequency.
Refund can be done in two ways. Refund with and without existing payments.
To create a refund, open subscriber and og to payments > Register Refund
Choose subscription plan and amount to refund. External reference and Comment are optional fields.
To create a refund on existing payment we click details arrow button and Refund. Data will be prefilled when refunding existing payment.
Write-offs are done to delete credits or debits for upcoming invoice. These corrections are located under the subscription plan Details > Corrections. Adding or deleting transaction will inflict economic changes for this subscription plan only.
From here you are able to add new corrections and also delete them. When adding a Credit to the subscriber it will decrease upcoming invoice amount. Adding a debit will increase upcoming invoice amount.
To delete we select the transactions we want to delete by checking the boxes on the left side. Press delete button.
Transactions are now deleted and will not be included for next invoice.
If a payment is missing and the due date is passed the system will stop the subscription. The Dunning process connected to the Billing plan decides if/when the subscriber gets payment stopped. Payment stop will occur when due dates in both Billing plan and Dunning process has expired.
When subscriber is payment stopped the invoice is credited and a charge of the remaining amount gets registered in ledger.
Billing plan itself has a date of when invoice should be paid based on value set in “Minimum number of days before the due date”. If the value is set to 14 it will generate invoice 14 days before the end of the current billing plan frequency.
Dunning process also has its own date of when a reminder should be paid, in addition it has a date of how many days after that it should be payment stopped.
So we have three due dates that has to expire before payment stop occurs:
Billing plan + Dunning process + Payment stopdate = Subscriber payment stopped
If there’s no Dunning process connected to the Billing plan, it will not have any follow up reminders or payment stop.
Automatic stop can be connected to a subscription plan so that subscriber gets automatically stopped at period end. A subscriber with automatic stop will have notice of the upcoming stop in subscribers overview. The feature is intended for use in combination with offers or one-time deliveries.
Automatic stop can be chosen when creating or editing a Subscription plan. If subscriber wants to continue subscription after a period with automatic stop we have to create a new order from stopdate.
Reminders are being produced based on Dunning process connected to the subscription plan.
The reminder gets issued when duedate of billing plan is passed and dunning process issuedate has occurred.
Reminders may or may not have a reminder fee in addition to the original amount dependent on dunning process setup. Fee can be added under 2. Setup balance invoice in Dunning process setup. If multiple reminders are configurated the fee will accumulate.
Reminder invoice contains a reference to original invoice so when reminder is paid by subscriber it will settle the original invoice that is connected to delivery. If a reminder is not paid the subscriber will be stopped if payment stop is configured in dunning process. If payment stop is not configurated subscription will continue.
In addition there are scenarios where the reminder can have a decreased amount. This occurs if invoice is partially paid with default system settings.
Direct payments will exclusively decrease reminder amount and no other form of credits or corrections.
Invoice amount is 500kr and subscriber has paid 400kr, the reminder would be 100kr.
Invoice amount is 500kr and subscriber has paid 400kr, subscriber is given 100kr in credit before the reminder is produced, the reminder would still be 100kr.
Invoice for next period will include the 100kr credit.
EHF (Elektronisk Handelsformat – Electronic Trading Format)
EHF is enabled under system configuration and the setting is turned on/off on an organization level.
The configuration setup is done under Systemdata – Configuration and will have to contain:
Accesspoint Id – An optional reference to the EHF access point supplier (where the EHF file is sent after production)
Organization Number – The number/id for the selling/supplying organization, I.e. the one generating invoices (can be retrieved from Organization Identifications list in GUI and supplied during configuration).
EHF export is executed automatically through webservices and every customer with a organizationnumber will be included in EHF export. When invoice gets issued the system will generate an EHF file in addition to the regular invoice. The same procedure is for credit notes.
Generating EHF invoices will apply to invoices never exported before and exclude already exported invoices.
EHF 3.0 is a common format for EU countries, but the non-norwegian rules will not be implemented until further.
The EHF files are exported at least once a week to an FTP server and transferred directly to accesspoint.
When invoice of a subscription is being paid by someone else then the subscriber
we use invoice payer. We can add invoice payer when adding new subscription by selecting + Add payer.
Invoice payer is connected to the spesific subscription plan in subscription overview and is active from first period.
Contacts tab holds information about all invoice payers for this subscriber. Editing payer is possible from this tab.
Enterprise plan is a functionality for one customer/company to be a invoicepayer and to setup an enterprise plan for two or more subscribers. The economy is held by the enterprise plan owner but is also visible on each subscriber. Economy will show on both subscriber and invoice payer as invoicenumber, period, amount, tax and fee will be identical on the two. Subscriber can not make a stop, credit, credit note, invoice copy or send invoice copy.
If the enterprise plan owner stops or misses payment it will stop subscription according to billing plan for all of the subscribers connected to the billpayer.
In terms of enterprise plan settlement it can be set as a fixed date, a day in each month or once a year settlement that is charged according to subscription&billing plan.
If a payment does not match issued amount the payment is saved in ledger on invoicepayer and neither subscriber or invoicepayer is marked as paid. Manual match must then be performed. Payer can choose paymenttype EHF or Invoice.
When adding an enterprise plan connection to a subscriber the invoice is prepared and gets issued they day after. This gives time to attach many subscribers to the enterprise plan before invoice gets issued. Ideally as many subscribers as possible are included in the first invoice. Subscribers that are attached to enterprise plan after first invoice is issued will be issued with their own invoice and invoice period until next invoice is issued.
Invoice period startdate will be day of order + 1 day. Enddate will be set in terms of what date is set in the enteprise plan generation. The billing alignment can be either monthly or yearly.
NB. It is important to notify that paymentstop is not working with enterprise plans because of potential volumes within the plans. Make sure to manually manage enterprise plans.
Enterprise plan is created from Systemdata -> Enterprise plan
When we press + Add new a wizard will guide you with creating the Enterprise plan.
Enterprise plan can be activated when its created or its possible to activate/expire the plan when opening the enterprise plan owner.
Enterprise plan details shows plan data.
When adding a new subscription plan we can use + Add payer to add invoice payer and later on Enterprise plan. We can choose the Enterprise plan we just created and attach it to the subscription plan.
Add enterprise plan and continue order.
When managing the enterprise plan subscriber we can edit subscriptions connected to it within the invoice issued by selecting Edit invoice.
Select subscriptions you want to credit. If there are remaining subscriptions after credit it will produce a new invoice for same period for the non-credited subscriptions.
Subscriptions will be included in invoice from next period.
For stopping subscriptions, go to details on the enterprise plan.
Select the subscriptions you want to stop. You will get to choose to stop immediately or at the end of the period. This will not credit the invoice.
A credit note is issued in various situations to correct a mistake. The purpose is to return money to the customer and informing that the money has been added.
A credit note can be made by selecting the invoice you want to credit from the Subscription overview or Invoice tab and click the button next to details. After creating a credit note the system will generate a negative amount invoice of the same amount as the original invoice. Once the credit is made it will update the subscribers ledger. At this time you can only credit total invoice amount, but partial credit will be possible in near future.
Credit note can be created from an issued invoice who has not been paid. The credit will be deducted on subscribers first upcoming invoice if credit is done with a paid invoice. This means that if a subscriber has two different Subscription plans and gets a credit for one spesific Subscription plan, this will affect the upcoming invoice no matter if its a invoice concerning the spesific plan or not. If an unpaid issued invoice is credited the system will create a credit note which will zero out the amount.
If however the subscription is ending and there is no upcoming invoices, the credit will be registered in the ledger with no further action.
Credit note date and invoicenumber can be seen in subscribers overview or invoices tab
For managing Offers&discounts see Products&subscription plans
When using different kinds of discounts in the subscription plan it will only apply for the first period. Permanent discount is intended to be used when the discount is to apply until the subscription ends.
Permanent discount is maintained from Systemsetting > Configuration > Permanent discount
Type in Name, Description and Discount percent:
List of created permanent discounts are listed beneath.
When we add a new subscription plan to a subscriber we can add one of our permanent discounts by clicking Permanent discount. The list of active permanent discount will be available:
A billing plan is a set of parameters that controls how a subscription is billed. Billing plan is always mandatory in a Subscription plan. Specifically, a billing plan determines the Due Date, the Frequency, how large a fee should be added, when to send reminders etc. These properties are used when issuing new payment demands (and invoices), so that the payment demand is generated at the right time with the correct due date, and any static payment related fees are added to the Invoice. For instance, it might cost 25 NOK to have an invoice issued on paper while an e-invoicing only costs 5 NOK, that fee can be exposed on the invoice to the subscriber directly.
A billing plan is created through a step by step guide under Systemdata – Billing plan – Add new
1. Plan name.
2. Billing frequency will determine invoice regularity.
When will the invoice be produced?
– Minimum number of days the invoice should be produced before the invoice due date.
This might be more if the payment method limit is more than the minimum number of days value, but in most cases invoice will be produced on the exact day. In this case invoice will be produced 14 days before due date.
NB. For new subscriptions the invoice will be produced immediately as subscription starts and the due date will be the chosen number of days from subscription startdate. In this case due date will be in 14 days. The next invoice will be produced 14 days before next due date again, and so on.
3. Choose dunning process for this billing plan.
Dunning process is explained here
4. Summary of this billing plan before you Save and exit.
A dunning process lets you decide how unpaid invoices should be handled by the system.
Dunning process is created through a step by step guide under Systemdata – Billing Management – Dunning Process – Add new
1. Choose a name for the process
2. Setup payment request.
Sets how many extra payment request the provider should attempt. If ‘number of payment request days’ is set to 1, system will execute one extra request the day after initial payment request failed.
3. Setup reminder
Delay – How many days after invoice duedate is the reminder created
Minimum due days – Set reminder duedate
The Reminder Fee – Amount of fee on the reminder
PS. When creating several reminders the delay of the second reminder follows minimum due days of the first one.
Reminder 1 has minimum due days = 10
Reminder 2 has delay = 5
When reminder 1 gets issued it has 10 days due. Reminder 2 is produced 5 days after due date of reminder 1.
A potential reminder 3 would have followed reminder 2.
4. Subscription contract
Used if contract is configuration on subscription plan.
If subscription contract is broken it will release a invoice. Choose the billing plan this last invoice should follow.
5. Setup stop rules
To calculate when to stop a subscription we use both “Delay” and “Balance Threshold Amount”. If for instance “Delay” = 10 and “Balance Threshold Amount” = 100 the system will stop subscription if subscriber owes 100kr or more after 10 days.
Delay – How many days until system performs a stop rule check
BalanceThresholdAmount – An amount threshold that defines a lower limit on the balance of the subscriber. If the subscriber owes MORE than this limit the subscription should be stopped. If this is set to 0 and there is no registered payment, the subscriber is stopped when Delay value is passed.
CauseDescription – An administrative description of why the subscription was stopped. Typically, something like: “Stopped due to a lack of payments”.
6. Setup balance invoice
Fee – Addition to invoice price
Previous Reminder Delay – Delay after previous Invoice/Reminder
Balance Limit – Limit on when to issue balance invoices (so we don’t send out an invoice for 5 NOK for instance)
Minimum Due Days – Minimum number of days the due date should be set to in the future, this is the minimum as some payment methods might have stricter requirements
Represents the subscribers financial transactions of debits and credits. It holds a complete record of the subscribers economic history from day one. Every incoming or outgoing transaction gets registered in the ledger and details about them can be viewed.
For example if the subscriber gets a invoice for 100,- the ledger will update to -100,-. When the payment gets registered it will update a record for 100,- and ledger will be set to 0,- again.
Its important to know that Ledger operates on a subscriber level and not on a Subscription plan level. This means that if a subscriber has two different Subscription plans and gets either a credit or a debit for one spesific Subscription plan, this will affect the upcoming invoice no matter if its a invoice concerning that spesific plan or not. However, this is not the case if the two subscription plans is registered under two different organizations. Economies are hold separetely across organizations.
Latest data of the ledger can be viewed from the Subscribers overview. Historical ledger data is stored under Ledger tab.
Choose organization you want to see economy for and balance of today is shown at the top under amount.
Arvato Finance is a factoring company purchasing your invoices and managing invoice administration towards the customer.
Arvato factoring requires Arvato Invoice Export to be enabled in configuration settings and the setting is turned on/off on an organization level. To generate invoice export as Arvato files configuration needs to contain certain data like organizationnumber, ClientID, 21 digit KID number based on invoicenumber, ClientID and customernumber.
Generating Arvato invoices will apply to invoices never exported before and exclude already exported invoices. Both invoices and credit notes are exported togheter and will be issued after billing plan rules. Contactpayer is not implemented in Arvato export and invoice will be adressed to subscriber.
At this time we only export invoices and not payment reminder.
Creating Arvato files are done under Systemdata – Invoice Production and files are saved in Azure store manager.
Incoming payments are imported via OCR files under Systemdata – Upload Payments. During import the file will use KID number to match the subscriber. If the amount is equal or down to -5kr in difference, the invoice will be updated as paid. If the payment does not cover total amount the remaining will be added to ledger.
OCR is the file format used when uploading data into the system. File format is chosen based on country and uploaded under System data > Upload payments.
When file is uploaded press save to store file in your system.
OCR files are uploaded to cloud based software Azure storage and then imported to Infosoft database where payment is connected to current subscriber by KID external ID.
Get started with NETS payment services like OCR and others here: www.nets.eu
KID is a number being used to identify the customer of an incoming payment. It can be from 2 to 25 digits long and it contains additional information about the customer like invoicenumber, customernumber and control digits (MOD10/11).
If there is two or several organizations in your Infosoft database KID number will start with a prefix ID for example 001 to separate the different organizations.
To implement KID you need to stetup an agreement with your bank and define total KID length aswell as MOD10 or MOD11.
Avtalegiro is a norwegian concept and is a service for automatic account-to-account payment of recurring bills. AvtaleGiro is well suited for recurring payments, such as electricity/utilities, mobile phone service, newspaper, subscriptions, insurance, rent, municipal fees and loans.
Reliable payment: AvtaleGiro increases the chance of bills being paid on time, because the bills are sent directly to the customer’s bank for automatic charge on the due date.
Easy for the customer: The customer does not have to add each invoice manually for payment. There is no bill that needs to be approved in the online bank. The bills are automatically paid on time.
Updated account balance: All bills sent with AvtaleGiro has KID numbers, which allows payments to be registered automatically. This ensures correct payment information which ensures updated account balance.
Important things to know:
What happens if I do not have account coverage on the due date?
Most banks will try to charge the money from your account in the following 4 business days.
If you still do not have coverage, you will receive information from the bank about an alternative payment method. You will be able to see in the online bank that the payment has been stopped and in most online banks you have the option to activate the payment again.
Setting for notifications is either set to bank notification or self notification on the configured account in your system. When bank notifications is on, the subscriber will be notified by the bank before payment is captured. With self notification the subscriber gets notification from the Infosoft system. This will happen through email or sms.
Subscriber will still be able to choose to get a notification or not when avtalegiro agreement is created.
Payment management evolves around managing payments that requires handling before being imported.
This is done under Systemdata – Manage payments.
If for instance the OCR contains a payment with missing or wrong data it will be added under Systemdata – Manage payments – Not matched until payment is sorted out. After payment is connected to subscriber it will be removed from this view.
“Registered payments” is a list of registered completed payments.
“Not matched payments” contains unsuccessfully imported payments. We can correct them and import them by clicking the edit button on the right side for each payment.
Under the same menu point we can also manually register payments “Register manual payment” on subscribers by inserting subscriber number on the current subscriber. We use subscriber and invoicenumber if we want a payment connecting to an invoice. The function is ideal for registrating several payments on different subcribers.
New Payex payment method is configured under Systemdata – Configuration – Payment configuration – Credit Cards
+ Add new Payex Ecommerce configuration
All of the necessary data is given by Payex.
Account is ordered from Payex who will provide necessary details to fill out.
“Organization” must be chosen and “Friendly name” is account name for internal use.
Vipps is an application that gives the user the ability to make payments to a receiver’s telephone number instead of an account number. If the receiver has a bank account in one of the owner banks of Vipps, the money is confirmed and available for the receiver within seconds. Other receivers have to register their credit card in Vipps and will get the money the next bank day. If a payment is made to a phone number not connected to Vipps, the receiver will get an SMS instructing them to download the application. If they do not, the payment will be cancelled.
To apply Vipps as a paymenttype for a subscription it has to be chosen as paymenttype through salesposter order. The salesposter URL needs to contain a certain code to allow vipps as paymenttype. At the end of URL we can insert “&PTY=2” for Vipps. 1 = Invoice 9 = Visa/Mastercard. So salesposter URL will typically be looking something like this if we want all three paymenttypes available:
NB. When creating subscription plans for use with Vipps paymenttype it is important to notice that both productname and description has to be less then 45 characters.
Handling Vipps payment import & configuration
After a subscriber has started new subscription the invoice gets issued and is automatically being paid shortly after. This is done through constantly running services between Infosoft and Vipps.
For recurring periods the invoices are normally issued a time before the duedate. The payment will be imported once the duedate is reached.
Configuration of your vipps account is made with your data received from Vipps. The setup is done through Systemdata – Configuration – Payment configuration – Vipps.
Vipps paymenttype cannot be applied or changed by anyone else then the subscriber. Subscriber can change or cancel the vipps agreement by logging into Mypage.
When order is created with Vipps paymenttype it also creates a unique Vipps agreement attached to that subscription. This is stored in database similar to a credit card agreement and is used for recurring invoicing. Subscription and upcoming invoices are shown in the Vipps app on your mobile.
Subscribers Vipps payment details are available when opening subscribers overview under tab Payment Agreements:
All of subscribers payments are listed and status of payments is updated in real time:
NB. Vipps paymenttype is currently not supported with subscription plan containing chain (Step 6 in subscription plan creation). This is due to Vipps rule for a maximum of 5x increased price on orderagreement.
Vipps order with 0,- amount can only be done if recurring periods are being paid for. So its allowed to setup offers with first periode for free, and amount > 0,- after.
Creating an order with 0,- as standard price will provide error message.
Delivery management brings a possibility to configure physical delivery to products. Systemdata – Delivery Management presents every subscribers on their current distribution. Distribution is shown by matrices representing the different delivery intervals.
Configure what matrix to be used.
Assign what products to be included in different matrices.
Configure distribution for your organization.
Overview of exported and non-exported distribution deliveries
Export changes to xml file
First time order in Info-Subscription:
Renewals and invoice/demands works separately in Info-Subscription. Renewal of next delivery happens automatically at the end of the current delivery if there’s no subscription stop registered. New delivery will be created equally to the current one if no changes are made and it will continue renewing itself until stop or other changes are made.
The invoice however is issued on the first day of delivery. For accounting causes once the invoice gets issued the current delivery can no longer be changed until we credit invoice. The invoice duedate will differ in relative to what payment type is being used. Payex for instance will have an immediate duedate while a paper invoice obviously has a duedate further ahead.
In terms of unpaid invoices the system will issue a payment reminder and ultimately payment stop subscriber if invoice remains unsettled (this applies only if there is a dunning process created). In shorter payment frequencies (fours weeks or less) its recommended to consider having payment reminder duedate on short notice to paymentstop the subscriber. If payment reminder duedate is set to be for instance in 14 days, several deliveries might be made before paymentstop occurs and several payment reminders might get issued if payment still missing.
The importance of this increases accordingly to how short the payment frequency gets.
We consider a Payment to be a financial transaction coming from a subscriber to an organization. All payments must belong to a subscriber and an organization to be used for settlement, book keeping etc.
By this definition payments are always incoming from an organizations point of view, financial transactions going from an organization to a subscriber or account is not considered a payment.
The system operates with three states for payments:
Payment starts in a state of awaiting identification, and depending on what actions are taken it will be moved to a state of Identified, AwaitingApproval and then Completed.
When a payment has been identified and approved, it is completed. That means that from the payment service point of view, no more changes must be done, and other external systems can then start reacting to the payment’s existence.
A payment is considered identified when the following properties exists
Once a payment is updated with all the above properties, the payment is considered as Identified automatically and will transition to the AwaitingApproval state. Approval marks the payment as completed.
Triggering payment creation is done in a few different ways depending on the matching mechanism to use. Each command represents a separate matching routine.
The properties of the Create Command are:
Automatic subscriber matching
The matching routine is always OrganizationId, SubscriberId, InvoiceId and ExternalInvoiceIdentifier. And the payment is created/updated with the resulting values.
Different matching types:
The input here is OrganizationId and ExternalInvoiceIdentifier. Matching is carried out by decoding the ExternalInvoiceIdentifier into its component parts (see the invoice service).
The input here is OrganizationId, InvoiceId and SubscriberId. Matching is carried out by retrieving the Invoice and verifying that the subscriber on the invoice matches the given SubscriberId.
The input here is OrganizationId and SubscriberId this basically means the payment is not matched and the InvoiceId and ExternalInvoiceIdentifier should be left blank.
Some companies need to distribute physical goods to their subscribers, either regularly during a subscription period (newspapers), or once every interval (subscriptionboxes, magazines etc).
DI is a company that takes care of the entire value chain from order, to delivery into the hands of the consumer.
With a DI connection through Infosoft the system will export data directly to DI to make sure subscribers latest changes are updated immediately to ensure start/stop in delivery.
Integration requires customer to setup a connection with Distribution innovation.
Under Systemdata – Delivery Management we can configure what products are physical and what days they will be delivered on.
Current physical deliveries
The view shows every subscription with physical deliveries active today. When a future stop is set the enddate will appear under column “Enddate” and when its passed the subscription gets removed from the view.
Shows the different existing matrices and days of deliveries. Possibility for creating new matrices.
Shows connection between Product and Matrix. Possibility for assigning new products to matrices.
In relation to exports to DI, the frequency of the exports will be controlled by the frequency of your publications.
DI sets requirements for when a file must be delivered and this is the deadline the publisher must comply with. The export can run anything from 1 day a week to 7 days a week dependent on your physical deliveries.
A prerequisite for export to DI is that the Distribution setup, product delivery and delivery matrix are set up and that the customer has an active agreement with DI.
DI setup is done here with data given from DI:
The actual DI export has to be manually done. Export is done via Export Changes button and this can only be done 1 time each day:
DI export file is being exported directly to the URL defined under Distribution Configuration settings.
DI address helper is an automatic address register that enables lookups when typing addresses.
The service helps user finding the correct address:
Configuration is done under Systemdata > Delivery Management >Distribution Configuration > Add Distribution Configuration
Contact DI for configuration data.