Printing the Daily Book (R76P9003)
The Daily Book report layout is in the format prescribed by Peruvian legal reporting requirements. When you run the R76P9003 program, the system generates the Daily Book report in PDF and text file formats.
See an example of the report layout at the end of this section.
The following table lists the column names and descriptions of the reporting fields in the PDF report layout:
Column Name |
Explanation |
|---|---|
Journal Number |
Register number by journal entry. |
Date |
Operation date. |
Description |
Below this column, the report concatenates the following fields: Document Type (DCT), Document Number (DOC), and Name Explanation (EXP). |
Book Code |
Blank. |
Correlative Number |
Blank |
Document Number |
Blank. |
Code |
Indicates the account number. |
Description |
Indicates the account description. |
Movements |
Indicates credits and debits. |
The following table describes the format of the text file generated by the R76P9003 report:
Number |
Length |
Description |
Type |
|---|---|---|---|
1 |
8 |
Financial period (in the YYYYMM00 format). |
Numeric |
2 |
up to 40 |
Single Operation Code (CUO). CUO is the unique key or primary key accounting software that uniquely identifies the key or accounting entry. |
Text |
3 |
2 to 10 |
Correlative number of accounting entries identified in Field 2. |
Alphanumeric |
4 |
Up to 24 |
Accounting account code unbundled into sub-accounts at the highest level of used digits. |
Numeric |
5-6 |
Up to 24 |
These fields are not populated in the report. |
Alphanumeric |
7 |
3 |
Type of currency of origin. |
Alphanumeric |
8 |
1 |
This field is not populated in the report. |
Alphanumeric |
9 |
15 |
This field is not populated in the report. |
Alphanumeric |
10 |
2 |
Payment voucher type or corresponding document associated with the operation. |
Numeric |
11 |
Up to 20 |
This field is not populated in the report. |
Alphanumeric |
12 |
Up to 20 |
Payment voucher number or document associated with the operation. |
Alphanumeric |
13-14 |
10 |
These fields are not populated in the report. |
DD/MM/YYYY |
15 |
10 |
Date of the transaction or issue. |
DD/MM/YYYY |
16 |
Up to 200 |
Glossing or description of the nature of the recorded transaction, if applicable. |
Text |
17 |
Up to 200 |
This field is not populated in the report. |
Text |
18 |
12 integers and up to 2 decimals, without commas of thousands |
Movements. |
Numeric |
19 |
12 integers and up to 2 decimals, without commas of thousands |
Haber movements. |
Numeric |
20 |
Up to 92 |
This field is not populated in the report. |
Text |
21 |
1 |
Operations status. |
Numeric |