Main.Invoicing.billing.technical-reference.Costumer information.2 KUB xml.Example Error file KUB.Error log (BERR010) - Error log (BERR010)

Page of - last modified by Anders Göthberg on 2023/11/14 11:10

Error log (BERR010)

Anders Göthberg

2023/11/14 11:10

Table of Contents

Name convention

Change log

General information and explanation of records

Format description

Record description

H - Header record

I - Information record

W - Warning record

E - Error record

S - Trailer record

Example

Logic

Result codes

Information codes

Warning codes

Error codes

Name convention

BERR010_<CompanyNumber>_<DateTime>_0[ErrorlogKund_<BatchId>].DAT

Names Component	Description
CompanyNumber	The company number in PayEx ledger system
DateTime	Date created in format YYYYMMDDHHMMSS
ErrorlogKund	File description
BatchId	Billing process Id

For example: BERR010_12345_20220415093539_0[ErrorlogKund_1234567].DAT

Change log

Version	Date	Description	Created by
1.0	22-02-22	Document created	Daniel Olsson
1.01	23-11-14	Updated information code for "KUB file name" from 15313 to 10	Anders Göthberg

General information and explanation of records

The error log presenting format and logical errors in KUB -files.

Format description

All fields in the mentioned report are separated with semicolons ”;”. Sort order is sequence number. 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 some fields in the record can be obligatory. Obligatory records are described with the abbreviation ” Req.” in the type column.

Record description

H - Header record

Field name	Field no.	Format	Type	Description
Record type	1	H	Req.	Record type
Firm number	2	N(5)	Req.	You receive the firm number from PayEx.
Firm name	3	X(40)	Req.	Your firm name.
Process Id	4	N(10)	Req.	Process Id from process
Created date	6	N(6)	Req.	YYMMDD – Same date as in the file name.
Created time	7	N(4)	Req.	HHMM – Time when the file was created.

I - Information record

Field name	Field no.	Format	Type	Description
Record type	1	I	Req.	Information record type
Code	2	N(15)	Req.	Information code
Description	3	X(1000)	Req.	Description of information code
Value	4	X(300)	Req.	Value

W - Warning record

Field name	Field no.	Format	Type	Description
Record type	1	W	Req.	Warning record type
Code	2	N(15)	Req.	Warning code
Line	3	N(15)	Corresponding line number in file
Customer number	4	X(15)	Customer number
Type	5	X(50)	Req.	Warning type (format/logic)
Description	6	X(1000)	Req.	Warning description

E - Error record

Field name	Field no.	Format	Type	Description
Record type	1	E	Req.	Error record type
Code	2	N(15)	Req.	Error code
Line	3	N(15)	Corresponding line number in file
Customer number	4	X(15)	Customer number
Type	5	X(50)	Req.	Error type (format/logic)
Description	6	X(1000)	Req.	Error description

S - Trailer record

Field name	Field no	Format	Type	Description
Record type	1	S	Req.	Record type
Total number of records	2	N(8)	Req.	Number of records, header record, description record and trailer record included.

Example

H;12345;Name;717971;220131;1247
E;1001;36;cust001;Logic; Incorrect format aabbccddeeffgghhjjkkllmmnnooppqqrrssttuuvv, Exceeds max length[35] [Position 3]
E;1241;44;cust002;Logic; Mandatory field[Address] on position 5 is missing!
E;1241;55;cust003;Logic; Mandatory field[Name] on position 3 is missing!
E;1241;66;cust004;Logic; Mandatory field[Name] on position 3 is missing!
I;15313;Parameters;Name of processed file: KUB_12345_20220113161144_1.DAT
S;7

Logic

This error report is based on errors detected in PayEx billing system customer file process.
If error occurs in PayEx billing system customer file process the customer will be rejected, not the entire file

Result codes

Information codes

Code	Category	Description
10	Parameters	KUB file name

Warning codes

Not used in this error log

Error codes

Code	Category	Description
1001	Logic	Incorrect format
1019	Logic	CustomerNumber is missing
1024	Logic	Invalid RegistrationNumber
1025	Logic	CountryCode must be the same as where debtor is nationally registered
1026	Logic	Invalid ZipCode specified for CountryCode and AddressType
1027	Logic	Invalid ZipCode specified for CountryCode and AddressType
1238	Logic	Duplicate record
1240	Logic	Invalid record sequence
1241	Logic	Mandatory field is missing
2500	Logic	Product code not configured
2510	Logic	Product is not a valid because it is a credit product
2520	Logic	Start date for product in file is incorrect in relation to product start date
2540	Logic	Start date is set after end date
2560	Logic	Products with shared properties cannot overlap
2570	Logic	If CustomerStatus is Inactive, product needs an end date
3000	Logic	Date has to be within UsagePeriod
3040	Logic	Multiple pricelists overlap
3050	Logic	IMSI active in multiple, overlapping, periods
3060	Logic	CLICode active in multiple, overlapping, periods
3080	Logic	Missing alias subscription
3090	Logic	Unknown subscriber number
4000	Logic	CustomerNumber has already been processed in current file
4010	Logic	Reseller does not exist in DB
4020	Logic	Invalid CustomerCategoryCode
4030	Logic	Invalid BillingCycle
4040	Logic	Invalid PaymentType for country
4050	Logic	Invalid PaymentRule for country
4090	Logic	Invalid EmailAddress
4100	Logic	Invalid LanguageCode
4110	Logic	Invalid ProductGroupDiscountCode
4120	Logic	ProductGroupDiscountCode set in file, but ProductGroupDiscountRate is missing
4130	Logic	ProductGroupDiscountRate set in file, but ProductGroupDiscountCode is missing
4140	Logic	BuyerId missing: For InvoiceDistributionCode[52] BuyerId required
4150	Logic	SellerId missing: For InvoiceDistributionCode[52] SellerId required
4155	Logic	EdiInfo missing: For InvoiceDistributionCode[52] EdiInfo required
4160	Logic	Card missing! This field is mandatory for PaymentMethod [AK].
4170	Logic	PaymentMethod has to be AK, when Card is specified!
4180	Logic	Invalid DestinationCode
4190	Logic	Invalid UsageType
4200	Logic	UsageType is active in multiple, overlapping, periods
4210	Logic	SpecialPrice is active in multiple, overlapping, periods
4220	Logic	CustomerNumber has to many leading zeros
4230	Logic	CustomerNumber has already been inactivated!
4240	Logic	PaymentTerms is lower than the allowed limit
4250	Logic	IntercompanyCode does not exist in configuration.
6000	Logic	Customer has unbilled fee(s). Customer status cannot be set to Inactive