> 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/party-wise-sales-collection-analysis.md). # Party Wise Sales/Collection Analysis Logic ERP has improved the **Party Wise Sales/Collection Analysis**. You can now compare the same period across up to three financial years. A new **GRADING DAYS** column splits collections by how many days they took. Two new options control how debit/credit notes are picked and how receipts are matched to bills. This release also fixes several figures and makes the report faster. *** ### **Step 1: Open the Report** * Navigate to **Reports/Queries** and select **Financial Analysis**. * Open the **Party Wise Sales/Collection Analysis**. *** ### **Step 2: Compare financial years side by side** * When you run the report, select up to **three** financial years. The report shows the same date range (same day and month) in each year you select. * Each party gets one row per financial year, one below the other. The new **FIN YEAR** column shows which year a row belongs to. * Totals are shown once for each financial year. * The date range must start and end inside one financial year. If it does not, or more than three years are selected, the report shows a message. *** ### **Step 3: GRADING DAYS column** * Add the **GRADING DAYS** column from the report's column settings. * In **Configuration**, under **Grading Days**, enter the day ranges in **Days-1** to **Days-6**. * The report shows one column per range. Each column shows the bill amount collected within that many days of the bill date. Headings look like **ADVANCE**, **0 TO 10**, **11 TO 20** and **MORE THAN 30**. * **ADVANCE** shows money received before the bill it settles. * With the **BRANCH NAME** column on, collections are shown against the branch that raised the bill, even if a different branch received the payment. *** ### **Step 4: New configuration options** * **Configuration > Grading Days > Collection Matching Basis**: * **Adjustments (Bill Linked)** uses the bills ticked against each receipt when the receipt was entered. * **FIFO (Oldest Bill First)** treats each receipt as paying the oldest bill still open. Choose this if receipts are not adjusted against bills. * This option decides the days shown in the grading columns and in **COLLECTION DAYS**. * **Configuration > Report Options > Debit/Credit Note Basis**: * **By Account** picks up notes posted to the accounts you select under **Accounts Selection ( Debit Note )**, **( Other Debit Note )**, **( Credit Note )** and **( Other Credit Note )**. * **By Day Book** picks up every debit note and credit note voucher. No account selection is needed. **OTHER DEBIT NOTE** and **OTHER CREDIT NOTE** stay blank in this mode. *** ### **What's corrected** * The report now runs with its default settings without an error. * **Report Order** now controls the sort order of the report. Party and branch totals now appear where they are switched on. * With the **BRANCH NAME** column on, each party's entries for a branch now print together on one row. * Selecting only **CHEQUES/PAYMENTS RETURNED** now shows its figures. * **TOTAL/PROD OUTLET(%)** now uses each party's own outlet counts. * **FIRST BILL DATE** now comes only from real bills. Opening balances brought forward and cancelled documents no longer count as bills. * **DEBIT NOTE**, **CREDIT NOTE**, **OTHER DEBIT NOTE** and **OTHER CREDIT NOTE** no longer include opening balances brought forward from the previous year. * **COLLECTION DAYS** and the grading columns now count only collections made within the report period. Figures can **fall** when receipts fall outside the period. This is intended. * **COLLECTION DAYS** no longer stops the report with an error when a party's amounts cancel out to zero. * A party whose only figure is a goods return (**G.R.**) now appears in the report. * The report now runs faster, especially on large data. --- # 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/party-wise-sales-collection-analysis.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.