Overview

The E-Journal feature generates a .txt file that complies with BIR (Bureau of Internal Revenue) requirements in the Philippines.

This feature is available only for the Philippines COM. Users from other countries' COMs will not be able to view or access this feature.

Prerequisites

To enable the E-Journal feature, the following system configuration must be enabled:

Classic System Configuration

• Enable Transaction Logging (must be ticked)

Once transaction logging is enabled, the system will record supported receipt transactions for E-Journal generation.

Accessing the E-Journal

Users can generate the E-Journal from the Report Printing module by selecting E-Journal.

The report allows users to select which transaction types should be included in the exported file.

Available filters:

• Sales

• Cancel Sales

• Return Sales

• X Reading (Cash Declaration)

• Z Reading (End of Day)

Export Location

After the user clicks Print, the system automatically exports the E-Journal files to the following directory:

A separate folder is created for each COM using its COM number.

File Generation

The system generates one text (.txt) file for each selected transaction type.

For example, if the user selects:

• Sales

• Cancel Sales

• Return Sales

the system will generate three separate .txt files, one for each transaction type. The .txt file name will be like the from date until end date and the modules name. May refer image below

Receipt Format

The E-Journal content is generated based on the receipt format that was originally printed by the user.

The system copies the printed receipt content from the transaction log into the corresponding E-Journal text file.

Note

The generated .txt files do not preserve the original receipt line formatting. As a result, the output may appear as continuous text without receipt separator lines or printed layout formatting.

This is the expected system behavior and is considered normal, as the E-Journal is intended to record the receipt content for BIR compliance rather than reproduce the visual receipt layout.

Supported Transaction Types

The current implementation supports the following transaction logs:

Transaction Logging

The E-Journal is generated based on the transaction logs captured when receipts are printed.

The logging follows the actual receipt output. Whenever a supported transaction is completed and its receipt is printed, the system automatically saves the transaction information into the transaction log.

Later, when the user opens Report Printing > E-Journal, the system retrieves the logged transactions that match the selected filters and exports them into the E-Journal .txt file.

Only supported transaction types are included in the exported file. Reprinted receipts are ignored and are not recorded as new E-Journal entries.