PayEx Developer Portal - Error log (BERR010)

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.

35

36

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.

37

38

= Record description =

39

40

== H - Header record ==

(% border="1" %)

|Record type|1|H|Req.|Record type

45

|Firm number|2|N(5)|Req.|You receive the firm number from PayEx.

46

|Firm name|3|X(40)|Req.|Your firm name.

47

|Process Id|4|N(10)|Req.|Process Id from process

48

|Created date|6|N(6)|Req.|YYMMDD – Same date as in the file name.

49

|Created time|7|N(4)|Req.|HHMM – Time when the file was created.

50

51

== I - Information record ==

(% border="1" %)

|Record type|1|I|Req.|Information record type

56

|Code|2|N(15)|Req.|Information code

57

|Description|3|X(1000)|Req.|Description of information code

58

|Value|4|X(300)|Req.|Value

59

60

== W - Warning record ==

(% border="1" %)

|Record type|1|W|Req.|Warning record type

65

|Code|2|N(15)|Req.|Warning code

66

|Line|3|N(15)| |Corresponding line number in file

67

|Customer number|4|X(15)| |Customer number

68

|Type|5|X(50)|Req.|Warning type (format/logic)

69

|Description|6|X(1000)|Req.|Warning description

70

71

== E - Error record ==

(% border="1" %)

|Record type|1|E|Req.|Error record type

76

|Code|2|N(15)|Req.|Error code

77

|Line|3|N(15)| |Corresponding line number in file

78

|Customer number|4|X(15)| |Customer number

79

|Type|5|X(50)|Req.|Error type (format/logic)

80

|Description|6|X(1000)|Req.|Error description

81

82

== S - Trailer record ==

(% border="1" %)

|Record type|1|S|Req.|Record type

87

|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

94

E;1001;36;cust001;Logic; Incorrect format aabbccddeeffgghhjjkkllmmnnooppqqrrssttuuvv, Exceeds max length[35] [Position 3]

95

E;1241;44;cust002;Logic; Mandatory field[Address] on position 5 is missing!

96

E;1241;55;cust003;Logic; Mandatory field[Name] on position 3 is missing!

97

E;1241;66;cust004;Logic; Mandatory field[Name] on position 3 is missing!

98

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.

104

If error occurs in PayEx billing system customer file process the customer will be rejected, not the entire file

== Result codes ==

=== Information codes ===

109

110

(% border="1" %)

111

|**Code**|**Category**|**Description**

112

|10|Parameters|KUB file name

113

114

=== Warning codes ===

115

116

Not used in this error log

=== Error codes ===

(% border="1" %)

|**Code**|**Category**|**Description**

122

|1001|Logic|Incorrect format

123

|1019|Logic|CustomerNumber is missing

124

|1024|Logic|Invalid RegistrationNumber

125

|1025|Logic|CountryCode must be the same as where debtor is nationally registered

126

|1026|Logic|Invalid ZipCode specified for CountryCode and AddressType

127

|1027|Logic|Invalid ZipCode specified for CountryCode and AddressType

128

|1238|Logic|Duplicate record

129

|1240|Logic|Invalid record sequence

130

|1241|Logic|Mandatory field is missing

131

|2500|Logic|Product code not configured

132

|2510|Logic|Product is not a valid because it is a credit product

133

|2520|Logic|Start date for product in file is incorrect in relation to product start date

134

|2540|Logic|Start date is set after end date

135

|2560|Logic|Products with shared properties cannot overlap

136

|2570|Logic|If CustomerStatus is Inactive, product needs an end date

137

|3000|Logic|Date has to be within UsagePeriod

138

|3040|Logic|Multiple pricelists overlap

139

|3050|Logic|IMSI active in multiple, overlapping, periods

140

|3060|Logic|CLICode active in multiple, overlapping, periods

141

|3080|Logic|Missing alias subscription

142

|3090|Logic|Unknown subscriber number

143

|4000|Logic|CustomerNumber has already been processed in current file

144

|4010|Logic|Reseller does not exist in DB

145

|4020|Logic|Invalid CustomerCategoryCode

146

|4030|Logic|Invalid BillingCycle

147

|4040|Logic|Invalid PaymentType for country

148

|4050|Logic|Invalid PaymentRule for country

149

|4090|Logic|Invalid EmailAddress

150

|4100|Logic|Invalid LanguageCode

151

|4110|Logic|Invalid ProductGroupDiscountCode

152

|4120|Logic|ProductGroupDiscountCode set in file, but ProductGroupDiscountRate is missing

153

|4130|Logic|ProductGroupDiscountRate set in file, but ProductGroupDiscountCode is missing

154

|4140|Logic|BuyerId missing: For InvoiceDistributionCode[52] BuyerId required

155

|4150|Logic|SellerId missing: For InvoiceDistributionCode[52] SellerId required

156

|4155|Logic|EdiInfo missing: For InvoiceDistributionCode[52] EdiInfo required

157

|4160|Logic|Card missing! This field is mandatory for PaymentMethod [AK].

158

|4170|Logic|PaymentMethod has to be AK, when Card is specified!

159

|4180|Logic|Invalid DestinationCode

160

|4190|Logic|Invalid UsageType

161

|4200|Logic|UsageType is active in multiple, overlapping, periods

162

|4210|Logic|SpecialPrice is active in multiple, overlapping, periods

163

|4220|Logic|CustomerNumber has to many leading zeros

164

|4230|Logic|CustomerNumber has already been inactivated!

165

|4240|Logic|PaymentTerms is lower than the allowed limit

166

|4250|Logic|IntercompanyCode does not exist in configuration.

167

|6000|Logic|Customer has unbilled fee(s). Customer status cannot be set to Inactive

=== ===

Wiki source code of Error log (BERR010)