> 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-analysis/periodic-performance-report.md). # Periodic Performance Report Logic ERP has improved the **Periodic Performance Report** so that every sales figure in the analysis sections is now worked out the same way: the sale value (without tax and after returns). Area, party, agent and party-count figures now agree with the Net Sales shown in the report. *** ### **Step 1: Open the Report** * Navigate to **Reports/Queries** and select **Financial Analysis**. * Open the **Periodic Performance Report**. *** ### **What's corrected** * **Area Wise Sales Analysis** now shows each area's sale value, without tax and after sales returns. The area total now equals **Net Sales** in the report, or **Net Sales After Inter Branch Transfers** when inter-branch transfers are left out. Area amounts will be **lower than before**, because tax is no longer included. This is intended. * In **Area Wise Sales Analysis**, each area's percentage is now its share of the area total, so the area rows (with **(Ungrouped)**) add up to 100. The **(Ungrouped)** percentage now matches **Area Wise - Ungrouped Sales % of Area Total**. The **Total** row no longer shows a percentage. * **Top Selling Parties** are now ranked by sale value instead of the invoice amount with tax. Parties may change places in the list. Amounts will be lower than before. This is intended. * **Parties By Growth** and **Parties By Decline** now compare sale values on the same basis as Top Selling Parties. * **Top Agents** and **Sales Through Agents** now use sale value. Agent amounts will be lower than before. This is intended. * **Total Parties, Goods Sold to During the Period**, **Average Sale per Party** and **New / Repeat / Lapsed Parties** now count every party the business sold to, including customers billed through a book other than the sales book. New Parties plus Repeat Parties now equals Total Parties. * **No. Of Parties Being Sold Above** the set amount now compares each party's sale value with the limit, not the amount with tax. The count can **fall** for parties that went over the limit only because of tax. This is intended. *** For more detailed information, [Click Here](/logic-erp-learning-hub-tutorials-and-best-practices/reports-queries/financial-analysis/periodic-performance-report.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-analysis/periodic-performance-report.md?ask=&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.