Name convention
When the report is ordered two files will be generated.
BRPT001_<CompanyNumber>_<DateTime>_0[Unbilled_<Term>_<BatchId>].DAT
BRPT002_<CompanyNumber>_<DateTime>_0[Unbilled_<Term>_<BatchId>].DAT
| Names Component | Description |
|---|---|
| CompanyNumber | The company number in PayEx ledger system |
| DateTime | Date created in format YYYYMMDDHHMMSS |
| Term | From witch argument the report is created by, Possible values: NRP = Non recurrent products, products from PR01-file *U = Usage, traffic or events from CDR:s *UoNRP = Usage and non recurrent products aggregated *Is not used without agreement |
| BatchId | The identification number from the creation of the InvoiceJournal creation process ID |
Examples of report files:
BRPT001_9999_20190308093539_0[Unbilled_NRP_1234567].DAT
BRPT002_9999_20190308093539_0[Unbilled_NRP_1234567].DAT
The file is semicolon-separated.
Change log
| Version | Date | Description | Created by |
|---|---|---|---|
| 1.0 | 2020-09-20 | First version. | Tomas Kristoffersson |
General information and explanation of records
After billing PayEx Billing are finished the reports BRPT001 and BRPT002 are created, the reports contains companies unbilled products and fees that are sent for billing, but for some reason not been invoiced.
The BRPT001 report is semicolon separated for updating database or import to excel.
The BRPT002 report is in text -format, easy to read and printable, the report are divided in sections based on the size of amount for each customer.
Both reports present the total amount for not invoiced products and other fees on each customer number.
Format description
BRPT001
All fields in the mentioned reports are separated with semicolons ”;”. The format field is written in the way that numerical values are written as N and alphanumerical characters are written as X. where ”n” is the maximum number of characters/digits or in certain cases number of characters that must exist.
Dot “.” is decimal separator on fields with amount. Some records are not obligatory but if they exist can some fields in the record be obligatory. Obligatory records are described with the abbreviation ” Req.” in the type column.
BRPT002
BRPT002 report is in text -format, easy to read and printable, the report are divided in sections based on the size of amount for each customer.
Record Description
H - Header record
| Field name | Field no. | Format | Type | Description |
|---|---|---|---|---|
| Recordtype | 1 | H | Req. | Header record. |
| FirmNumber | 2 | N(4) | Req. | The firm number you receive from PayEx. |
| FirmName | 3 | X(40) | Req. | Your firm name |
| Creationdate | 4 | N(6) | Req. | YYYY-MM-DD – Date when generated |
| Creationtime | 5 | N(4) | Req. | HH:MM:SS – Time when generated |
I - Headline record
| Field name | Field no. | Format | Type | Description |
|---|---|---|---|---|
| Record type | 1 | I | Req. | Record type |
| Customer No | 2 | X(1-15) | Req. | Customer number |
| Customer Name | 3 | X(1-72) | Req. | Customer name |
| Subscribernumber | 4 | X(1-15) | Subscriber number | |
| Productgroup | 5 | N(5) | Productgroup | |
| Sum | 6 | N(7),N(2-6) | Req. | Total amount |
D - Data Record
| Field name | Field no. | Format | Type | Description |
|---|---|---|---|---|
| Record type | 1 | D | Req. | Record type |
| Customer No | 2 | X(1-15) | Req. | Customer number |
| Customer Name | 3 | X(1-72) | Req. | Customer name |
| Subscribernumber | 4 | X(1-15) | Subscriber number | |
| Productgroup | 5 | N(5) | Productgroup | |
| Sum | 6 | N(7),N(2-6) | Req. | Total amount |
T - Trailer record
| Field name | Field no. | Format | Type | Description |
|---|---|---|---|---|
| Record type | 1 | T | Req. | Trailer record |
| Number of records | 2 | N | Req. | Total number of records inclusive header and trailer record. |
Examples BRPT001
BRPT001 (Customer level only)
H;9999;Firm Name;2019-04-04;09:35:34
I;Customer;Name;Amount
D;100001;Customer name;2346.23
D;100002;Customer name;2829.10
D;100003;Customer name;3226.65
D;100004;Customer name;3249.89
T;6
BRPT001 (Customer and product group code level)
H;9999;Firm Name;2019-04-04;09:35:34
I;Customer;Name;Group;Amount
D;100001;Customer name1;ProductGroupCode1;2346.23
D;100001;Customer name1;ProductGroupCode2;2829.10
D;100002;Customer name2;ProductGroupCode1;3226.65
D;100002;Customer name2;ProductGroupCode2;3249.89
T;6
BRPT001 (Customer, subscriber and product group code level)
H;9999;Firm Name;2019-04-04;09:35:34
I;Customer;Name;Subscriber;Group;Amount
D;100001;Customer name1;Subscriber1;ProductGroupCode1;2346.23
D;100001;Customer name1;Subscriber1;ProductGroupCode2;2829.10
D;100001;Customer name1;Subscriber2;ProductGroupCode1;3226.65
D;100001;Customer name1;Subscriber2;ProductGroupCode2;3249.89
T;6
Examples BRPT002
BRPT002 report is in text -format, easy to read and printable, the report are divided in sections based on the size of amount for each customer.
Header record information
Contains information about batch ID, the terms the report has been processed with, date and time, period of usage and billingcycle.
Example Header
Sections
1 First section contains customer that is missing in database with the comment DIDN´T EXIST IN DATABASE.
2 Customer with amount 0, when “Add customer with no unbilled products or traffic” is chosen.
3 Customers unbilled amount between 0 > to 50.
4 Customers unbilled amount between 50 > till 100.
5 Customers unbilled amount between 100 > till 150.
6 Customers unbilled amount between 150 > till 200.
7 Customers with unbilled amount < 200
The sort order in each section is on total amount, the section is summed at the end.
Example:
Interval >150 - 200
100001 Customer name 152.11 2019-01-29 - 2019-03-26 0
100002 Customer name 166.28 2019-02-26 - 2019-03-26 0
100003 Customer name 173.65 2018-12-28 - 2019-03-26 0
100004 Customer name 177.72 2019-01-29 - 2019-03-26 0
100005 Customer name 191.33 2018-03-03 - 2019-03-21 0
Number of customers 5 Amount 861.09