> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-version-release-notes/october-2026/reports-queries/financial-report/journal.md).

# Journal

Logic ERP has made the **Journal** much faster on large periods. Purchase return entries now show their system voucher number, and vouchers no longer split apart when extra account group columns are shown.

***

### **Step 1: Open the Report**

* Navigate to **Reports/Queries** and select **Financial Reports**.
* Open the **Journal**.

***

### **What's corrected**

* **SYSTEM VOUCHER NO.** now shows the goods receipt number on purchase return entries, as it already did on purchases.
* The extra account group columns are now for information only and do not change the order of the report. All lines of a voucher now stay together under one voucher total.
* **CREATION USER NAME** and **APPROVAL USER NAME** now show the same name every time for the same voucher.
* The report now runs much faster on large data, and no longer slows down as it goes through a long period.

***

For more detailed information, [Click Here](/logic-erp-learning-hub-tutorials-and-best-practices/reports-queries/financial-report/journal.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://kb.logicerp.com/logic-erp-version-release-notes/october-2026/reports-queries/financial-report/journal.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.