Changes for page KUB

Last modified by ang on 2024/03/28 10:31
From version 23.2
edited by ang
on 2020/10/26 15:20
To version 24.1
edited by ang
on 2020/10/26 15:32
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -27,13 +27,15 @@
27 27  
28 28  KUB_<CompanyNumber>_<DateTime>_<(% style="font-size:14px" %)SEQNO(%%)>.DAT
29 29  
30 -|=Names Component|=Description
31 -|CompanyNumber|The company number in PayEx ledger system
32 -|DateTime|Date created in format YYYYMMDDHHMMSS
33 -|SEQNO|Unbroken serial number sequence.
34 34  
35 -**For example: **KUB_1234_20161201155511_1.DAT
31 +(% border="1" %)
32 +|=(% style="width: 371px;" %)Names Component|=(% style="width: 1121px;" %)Description
33 +|(% style="width:371px" %)CompanyNumber|(% style="width:1121px" %)The company number in PayEx ledger system
34 +|(% style="width:371px" %)DateTime|(% style="width:1121px" %)Date created in format YYYYMMDDHHMMSS
35 +|(% style="width:371px" %)SEQNO|(% style="width:1121px" %)Unbroken serial number sequence.
36 36  
37 +**For example: **KUB_1234_20201001155511_1.DAT
38 +
37 37  The file is semicolon-separated.
38 38  
39 39  
... ... @@ -42,6 +42,9 @@
42 42  
43 43  * You cannot use the same serial number more than once. In case something goes wrong during CUSIN processing, **you need to supply a new serial number - the next number in the number series you are using - when transferring the rectified file to PayEx**.
44 44  
47 +(% class="wikigeneratedid" %)
48 +== ==
49 +
45 45  == Change log ==
46 46  
47 47  |**Version**|**Date**|**Description**|**Created by**
... ... @@ -69,6 +69,9 @@
69 69  
70 70  Processing KUB files can be done 24/7 and response files will be delivered immediately after processing KUB files.
71 71  
77 +(% class="wikigeneratedid" %)
78 +=== ===
79 +
72 72  === Format ===
73 73  
74 74  In the format columns below, the numerical values are called N where “n” stands for the maximum number of characters, or in some cases the obligatory number of characters. Alphanumeric characters are written as X. The decimal separator for amounts will be a point “.”. Each record has a description about which character check will be made. Some records are not obligatory but if they do occur, some fields for the record may become obligatory. See the fixed telephony record “C2” for example, or mobile telephony record “MO”. Obligatory records are described with the abbreviation “Obl.” in the type column. All records marked with a star can only be used after contacting Payex.
... ... @@ -75,10 +75,16 @@
75 75  
76 76  The customers different records have to be sent in the same order as the record description.
77 77  
86 +(% class="wikigeneratedid" %)
87 +=== ===
88 +
78 78  === Implementation ===
79 79  
80 80  Implementation of KUB requires a complete file with all customers. Otherwise it is sufficient to only send updated customers.
81 81  
93 +(% class="wikigeneratedid" %)
94 +=== ===
95 +
82 82  === GDPR (General Data Protection Regulation) ===
83 83  
84 84  Inactivating a customer can be done by using record C1, field 8 (CustomerStatus). Default is the value = 2 (Active). For inactive value 1 is used.
... ... @@ -87,8 +87,11 @@
87 87  
88 88  As soon as a customer has been send with value 1 (Inactive) no information regarding this customer will be available in any report or api. A final removal of the customers information will be made after x days, where the recommendation is to use the default of 40 days. Within this period it´s possible to reactivate the customer again.This can be done by sending value Active in the customerstatus
89 89  
90 -= Response files =
104 +(% class="wikigeneratedid" %)
105 +== ==
91 91  
107 +== Response files ==
108 +
92 92  If the file contains format errors a general error file will be produced.
93 93  
94 94  If the file format is correct and the file contains correct and incorrect customers an error file with filename (BERR010..ErrorlogKund) and a receipt file (BRCP010..ReceiptCustomerfile) will be produced.
... ... @@ -95,8 +95,11 @@
95 95  
96 96  If the file format is correct and the file contains only correct customers no error file will be produced, only a receipt file will be produced.
97 97  
98 -== Receipt and Error -files ==
115 +(% class="wikigeneratedid" %)
116 +=== ===
99 99  
118 +=== Receipt and Error -files ===
119 +
100 100  Examples of an extract from a receipt and a error -file:
101 101  
102 102  [[Receipt and Error -file example>>https://developer.payex.com/xwiki/wiki/developer/view/Main/billing/technical-reference/Costumer%20information/2%20KUB%20xml/Example%20Error%20file%20KUB/]]