Introduction
In PayEx Billing, the invoice is created for the ledger system. At Billing we compiles one-time and recurring fees and credits to a invoice basis per end customer. When creating a invoice, any debit or credit products are taken into account. The invoice is then exported to PayEx Ledger service (invoice service) and further to Distribution. Data can be received and loaded automatically all around the clock every day of the year.
This is a general step-for-step implementations guide that guide you through.....
Prerequisites
Before you start implementing PayEx Billing the following is required:
- An Agreement Invoice Service with Billing
- Obtained credentials from PayEx
- A sFTP Client
- Business Rules
- Revenue Accounting Rules
Feel free to contact us if you have any questions on how to get started.
Overview
Before getting started, have a look at the high level sequence diagram below, which will help you getting a better understanding of the whole process and the components necessary to implement Invoice Service.
All main steps of the invoice process are described below. Please note that all XML examples below are here primarily for display purposes, to help you get an understanding of the CUSIN file format and to aid you in the implementation.
If you encounter any problem during implementation, don't hesitate to contact us.
All main steps of the invoice process are described below. Please note that all XML/csv examples below are here primarily for display purposes, to help you get an understanding of the file format and to aid you in the implementation.
Overview
PayEx Billing aggregates one-time and recurring fees & credits to one invoice basis per end customer. When creating invoice documents, any submitted discounts and credit products are taken into account. The invoice documentation is then exported to PayEx ledgers and PayEx Distribution (creation of invoices and mailings in various channels).
When implementing Invoice Service Billing with Revenue Accounting, customer-specific configuration takes place
Bicus2 (Customerfile xml)
Customerfile is used to submit end-user information to the PayEx Billing System. Bicus2 contains the end customer's customer information together with all of the end customer's subscriptions and products to be processed in the PayEx Billing System.
KUB (Customerfile csv)
Customerfile to billing (KUB) is used to submit end-user information to the PayEx Billing System. KUB contains the end customer's customer information together with all of the end customer's subscriptions and products to be processed in the PayEx Billing System.
PR01 (Productfile csv)
Using PR01 files in the Payex Billing system gives possibilities to create non recurrent products on both customer and subscription level.
Communication of disposable products that will be placed at the end customer level. The productfile contains information about price (+/-), VAT rate and the product name that is communicated to the end customer.
Product Catalog
The file contains instructions how products is to be booked.
Revenue Accounting Rules
...
Receipt
When one of above files are sent to us, and after PayEx have started the file you will receive a receipt at the file and its content.
Each activity has their own set of result parameters
You can view the receipt and a detailed description here.
Costumerfile
...
Productfile
...
Product Catalog
...
Reports
...
Invoice Journal Billing
...
BillingAccounting
After every billing where we have created invoices, we create a Revenue Accounting report BillingAccounting. The report including:
Invoicenumber​
VAT code
Account
ProductCode
Group company code
Cost center
BilledInAdvanced
Once a month PayEx Billing sends a report containing billed in advanced
UnbilledProduct
Once a month PayEx Billing sends a report containing unbilled products
QueuepostReport
After billing we create report BRPT001 + BRPT002, the reports contains companys queuepost that are sent for billing, but yet not invoiced.
The BRPT001 report is ment to update your database or imported to excel.
The BRPT002 report is ment to be easy to read and understand, also easy to print but not import to a database.
Both reports consists recurring and non recurring products.
Error log
If errors are encountered during file processing an errorlog will be created. Errors may refer to insufficient customer information or format errors.