Name convention
BRCP010_<CompanyNumber>_<DateTime>_0[ReceiptCustomerfile_<BatchId>].DAT
Names Component | Description |
---|---|
CompanyNumber | The company number in PayEx ledger system |
DateTime | Date created in format YYYYMMDDHHMMSS |
ReceiptCustomerfile | File description |
BatchId | Billing process Id |
For example: BRCP010_12345_20220109110841_0[ReceiptCustomerfile_2746770].DAT
Change log
Version | Date | Description | Created by |
---|---|---|---|
1.0 | 2022-02-22 | Created document | Daniel Olsson |
General information and explanation of records
Receipt file for KUB include number of processed customers, number of accepted and number of rejected customer.
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 |
Description | 3 | X(1000) | Req. | Description of warning code |
Value | 4 | X(300) | Req. | Value |
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 |
Description | 3 | X(1000) | Req. | Description of error code |
Value | 4 | X(300) | Req. | Value |
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;7717842;220118;1804
I;10;Name of processed file;KUB_12345_20220118161144_1.DAT
I;11;Total number of processed customers;4
I;12;Number of correct customers;3
W;13;Number of incorrect customers;1
S;6
Logic
This receipt is based on receipt values resulting from Billing customer import process.
Result codes
Information codes
Code | Description |
10 | Name of processed file |
11 | Total number of processed customers |
12 | Number of correct customers |
Warning codes
Code | Description |
30 | Number of incorrect customers |
Error codes
Not used in this receipt