📌 What’s New

Currently, the system has a Bill Wise Report to view bill details. However, there was no way to check bill details based on Voucher Type — making it difficult to view the tagged value against a specific bill and track untagged bills for a particular voucher type.

🎬 Where to Find It

📷 See It in Action

📄 Voucher Wise Bill Status Report — Overview

📄 Voucher Wise Bill Status Report — Details

📌 What’s New

Currently, there was no dedicated screen to reconcile the physical stock (actual count) against the book stock (system records). Users had to manually compare quantities and values outside the system, making the stock reconciliation process tedious and error-prone.

🎬 Where to Find It

📷 See It in Action

📄 Physical vs Book Stock Reconciliation Report — Overview

📄 Physical vs Book Stock Reconciliation Report — Details

📌 What’s New

There was no dedicated screen to reconcile TDS Receivable as per Books with the 26AS statement. The 26AS statement is available in Excel format based on TAN number, but users had to manually compare TDS amounts outside the system — making the reconciliation process tedious and error-prone.

🎬 Where to Find It

📷 See It in Action

📄 26AS vs TDS Reconciliation — Upload Screen

📄 26AS vs TDS Reconciliation — Report View

📄 26AS vs TDS Reconciliation — Difference Summary

📌 What Was Needed

There was no dedicated report under Bill Status to track outstanding bills falling within a critical near-term window. Users had no quick way to identify:

• Bills due within the next 7 days — payments that need to be actioned immediately
• Bills overdue within the last 7 days — payments that have already crossed their due date

Without this view, tracking and acting on these bills required manual effort across multiple screens, and there was no built-in path to push selected bills directly into bank export processing.

🎬 Where to Find It

📷 See It in Action

📄 Pending Bills Due / Overdue Within 7 Days — report view (1)

📄 Checkbox selection for bank export processing (2)

📌 What Was Happening

Users were not allowed to create or edit back-dated entries for Sale Order and Purchase Order voucher types, even though the Back Date Entry / Edit (No. of Days) permission was configured in the Voucher Type master. The root cause was that the back date entry and edit functionality was never developed for Sale Order and Purchase Order voucher types — however, the option was available on the UI, giving the impression it should work.

🎬 Where to Find It

📷 See It in Action

📄 Back Date Edit permission in Voucher Type

📄 SO / PO back date edit now working

📌 What Was Happening

When an entry was pending for approval in the Approval Workflow, users could still generate E-Invoice and E-Way Bill for that entry. There was no mechanism to restrict E-Invoice or E-Way Bill generation based on the approval status — which could lead to compliance documents being generated for unapproved transactions.

🎬 Where to Find It

📷 See It in Action

📄 Approval Template — New checkbox options

📄 E-Invoice restricted before approval

📄 E-Way Bill restricted before approval

📄 Generation allowed after approval

📌 What Was Happening

The single apostrophe (’) symbol was previously restricted in the Ledger Master due to an internal technical glitch. This meant users could not use the apostrophe character while creating or naming ledgers — which was inconvenient for ledger names that naturally include an apostrophe (e.g., “Ram’s Enterprise”).

🎬 Where to Find It

📷 See It in Action

📄 Single apostrophe now allowed in Ledger Master

📌 What Was Happening

Two new TDS sections required for compliance were not available in the Ledger Master. Users who needed to map ledgers to Section 393(2) [Sl.No.17] or Section 392 had no option to do so within the system.

🎬 Where to Find It

📷 See It in Action

📄 New TDS sections in Ledger Master

📌 What Was Happening

In the Voucher Type Numbering screen, the Company and Group segment names were being displayed in the UI even when the “TXN Allowed” parameter was disabled in the Segment Master. Showing segments that are not permitted for transactions caused confusion during manual voucher type numbering setup.

🎬 Where to Find It

📷 See It in Action

📄 Segments shown despite TXN Allowed disabled — Before Fix

📄 Segments hidden when TXN Allowed disabled — After Fix

📌 What Was Happening

In the Ledger Master → Party Information section, after PAN verification there was no provision to capture Date of Birth or Date of Incorporation. These details are statutorily relevant and depend on the Deductee Type derived from the PAN — without dedicated fields, users had no clean way to record them against the party ledger.

🎬 Where to Find It

📷 See It in Action

📄 Date of Incorporation field for Company Deductee Type (1)

📄 Date of Birth field for Non-Company Deductee Type (2)

📌 What Was Happening

The Godown Master had no option to attach supporting documents against a godown record. The Ledger Master already supported document attachments with the ability to view them back in the edit screen, but the same capability did not exist for godowns — so any related paperwork (rental agreements, licences, location proofs, etc.) had to be kept outside the system or attached against an unrelated record.

🎬 Where to Find It

📷 See It in Action

📄 Document attachment option in Godown Master (1)

📄 Attached documents visible in Godown edit (2)

📌 What Was Needed

The Notification Master screen needed a cleaner layout and simpler multi-selection for notification channels and events.

📷 See It in Action

📄 Before — original Notification Master layout

📄 After — reordered fields & multi-select dropdowns (1)

📄 After — On Event multi-select dropdown (2)

📌 What Was Happening

When a user created a Cost Centre using the Alt + C shortcut key from the Transaction Screen, the system was taking 15–20 seconds to load the pop-up. This significant delay disrupted the workflow and slowed down transaction entry, especially for users who frequently create cost centres on the fly during voucher posting.

📷 See It in Action

📄 CC Master creation via Alt+C — Before optimization

📄 CC Master creation via Alt+C — After optimization

📌 What Was Happening

The Inventory Export in Import Format feature did not support Stock Journal entries. Users who needed to export Stock Journal vouchers in import format had no option to do so, limiting the export functionality for inventory-related transactions.

🎬 Where to Find It

📷 See It in Action

📄 Stock Journal export in import format

📌 What Was Happening

When inventory transactions contained a large number of items, opening them in edit mode would take a significant amount of time. This affected the following screens:

• Purchase
• Sale
• Purchase Return
• Sale Return
• Price Difference

The prolonged loading time made the experience frustrating for clients who had to wait for the screen to open before they could make any changes.

🎬 Where to Find It

📌 What Was Happening

When generating a template from Voucher Types where WhatsApp Integration is applicable, users were presented with two print options:

• Generate Invoice & Share with WhatsApp
• Generate Invoice

There was no way to set a default option, so users had to manually choose the WhatsApp option each time — adding extra clicks to a repetitive workflow.

🎬 Where to Find It

📷 See It in Action

📄 Default print option setting in Txn Configuration

📄 WhatsApp print option — Before

📄 WhatsApp print option — After

📌 What Was Happening

For voucher types with the nature Sale, the parameter “Allow Manual Bill No.” was only available under Configurations. It was not available under Transaction (TXN) Configurations, limiting the flexibility for users who needed to control this setting at the transaction configuration level for all Sale-type vouchers.

🎬 Where to Find It

📷 See It in Action

📄 Allow Manual Bill No. in Txn Configuration

📄 Manual Bill No. option for Sale voucher type

📌 What Was Happening

If the Business Place was not saved in any accounting transaction, there was no option available to update it after the fact. Users had to either re-create the transaction or leave the Business Place field empty — which could cause issues in compliance and reporting workflows.

📷 See It in Action

📄 Business Place update option in accounting transaction

📌 What Was Happening

The Amount Restriction feature — which prevents entries from exceeding a specified amount — was available in standard Payment and Receipt voucher types. However, this restriction was not available for IBT Receipt & Payment voucher types (IBT_PAY and IBT_REC), leaving inter-branch transactions without any amount cap enforcement.

🎬 Where to Find It

📷 See It in Action

📄 Amount restriction in IBT Receipt & Payment

📌 What Was Happening

In the Purchase Order (PO) screen, there was no provision to specify a delivery date at the item level. Users who needed different delivery timelines for individual items within the same PO had no way to capture this information directly in the system.

🎬 Where to Find It

📷 See It in Action

📄 Item-wise Delivery Date in Purchase Order

📌 What Was Happening

When transactions were created via Excel import, there was no way to trace which Excel file a particular transaction originated from. The source file ID was not being stored against the transaction, making it difficult to audit or track import history.

🎬 Where to Find It

📷 See It in Action

📄 Excel File ID tracked in imported transaction

📌 What Was Happening

In the 30-05-2026 Beta Release, the Excel File ID tracking feature was introduced for Accounting, Sale, Sale Return, Purchase, and Purchase Return transactions. However, this tracking was not yet extended to IBT (Inter-Branch Transfer) transactions — meaning transactions created via Excel import through the IBT screen had no record of their source file.

🎬 Where to Find It

📷 See It in Action

📄 Excel File ID tracked in IBT imported transaction

📌 What Was Happening

The Cheque Print option was available in the regular (non-IBT) Contra Voucher Type, but was not available in the Parent IBT Contra Voucher Type. Users creating inter-branch contra entries had no way to print cheques directly from the IBT Contra screen — forcing them to use a workaround or process the cheque separately, adding unnecessary steps to the workflow.

🎬 Where to Find It

📷 See It in Action

📄 Cheque Print option in IBT Contra Voucher Type

📌 What Was Happening

During Purchase Entry creation, selecting the Alt Unit caused the MOC to change from “W” to “P”. The equivalent setting on the Sale Entry side did not change the MOC on Alt Unit selection — because the existing settings parameter that controlled this behaviour was scoped to Sales only. As a result, the same business setup behaved differently in Sales vs Purchase, which was inconsistent for users entering Purchase vouchers.

🎬 Where to Find It

📷 See It in Action

📄 Settings parameter now applies to both Sale and Purchase

📌 What Was Happening

The Stock Journal edit screen was carrying the older inventory transaction edit logic and could be slow to open, especially for entries with multiple line items. The same performance optimisation had already been rolled out earlier for Sale, Sale Return, Purchase and Purchase Return edit screens, but Stock Journal had not yet been brought in line — leaving an inconsistent edit experience across inventory voucher types.

🎬 Where to Find It

📌 What Was Happening

Vouchers could be linked to a reference (Link Ref) for traceability, but there was no dedicated search option to look up entries by that Link Ref on the voucher screens. Users had to scroll or filter by other fields to locate vouchers tied to a particular reference, which was slow when the reference was the only handle available.

🎬 Where to Find It

📷 See It in Action

📄 Link Ref search on Voucher Entry & Edit screens

📌 What Was Happening

In an IBT (Inter-Branch Transfer) entry with two Cost Centre blocks entered, opening the corresponding child entry showed only one Cost Centre block in the Cost Centre view — even though the parent IBT entry correctly displayed both blocks. This mismatch was specific to the single cost centre configuration and caused the child entry to appear incomplete relative to the originating IBT.

🎬 Where to Find It

📷 See It in Action

📄 IBT entry showing 2 Cost Centre blocks (1)

📄 Child entry now showing correct Cost Centre block (2)

📌 What Was Happening

When a client uploads a bank statement via Bank Import and navigates to the Day Book option of Bank Import, they can update the suspense ledger, assign a customer or vendor, and tag bills. However, this split / breakup of segment functionality was not working for the following IBT voucher types:

• IBT PAY
• IBT RECEIPT
• IBT CONTRA

🎬 Where to Find It

📷 See It in Action

📄 Bank Import IBT — Day Book screen overview (1)

📄 Split blocked when both Bill & Link enabled for party (2)

📄 Split allowed when only Bill or Link enabled (3)

📄 Split blocked when neither Bill nor Link enabled (4)

📄 Vtype auto-changes to IBT Contra on Cash/Bank ledger (5)

📄 IBT Contra entry reflected correctly in Day Book (6)

📌 What Was Needed

There was no way to enforce entry of the GST Party field on transaction screens where it was applicable, leaving it optional even when a business wanted to make it compulsory.

🎬 Where to Find It

📷 See It in Action

📄 Vtype Master — GST Party Mandatory field (1)

📄 Sale Transaction Entry — warning when GST Party is empty (2)

📌 What Was Needed

The Import Upload screen used a horizontal tab layout (Excel, XML, MT940, BRS/BANK) that became harder to navigate as import options grew, and its listing screen did not default to a useful date range.

🎬 Where to Find It

📷 See It in Action

📄 Before — horizontal tab layout with Bank dropdown

📄 After — vertical panel with search, alphabetical options

📌 What Was Needed

From 1st August 2026, Ship-To GSTIN is mandatory for all Bill-to/Ship-to e-Way Bill and e-Invoice transactions. Earlier, Ship-To parties were often created without a GSTIN. Users needed a prompt while preparing a Sales Order to confirm the correct GST status of the shipping party.

🎬 Where to Find It

📷 See It in Action

📄 Shipping Party alert & GST status eye icon in Sales Order

📌 What Was Needed

While posting entries from the bank statement, the opposite ledger was automatically posted to the Suspense Account. Users needed a way to replace the Suspense Account with the correct ledger in bulk for all entries requiring the same ledger, instead of editing them one by one.

📷 See It in Action

📄 Entries posted to Suspense Account from bank statement (1)

📄 Replace Suspense ledger in bulk option (2)

📄 Suspense entries updated to the correct ledger (3)

📌 What Was Happening

In the Item Wise Profitability Details Report, only a single item could be selected at a time. Users who needed profitability data for all items had to select and export each item individually — making it time-consuming and impractical for bulk analysis.

🎬 Where to Find It

📷 See It in Action

📄 All items selection in Profitability Details

📌 What Was Happening

The Profit & Loss Account report variations under Management Reports did not have the Scale Factor option. Users had no way to view amounts in a summarized format (e.g., Crores, Lakhs) — making it difficult for higher management to quickly interpret large figures in these reports.

🎬 Report Variations & Navigation

Reports → Accounts → Management Reports → Profit & Loss Account

📷 See It in Action

📄 PNL Standard — Scale Factor

📄 PNL Monthly Columnar — Scale Factor

📄 PNL Yearly Columnar — Scale Factor

📄 PNL Segment Wise Columnar — Scale Factor

📄 PNL With Gross Profit — Scale Factor

📄 PNL Quarterly Columnar — Scale Factor

📄 PNL Segment – Month Wise — Scale Factor

📌 What Was Happening

The Trial Balance report variations under Management Reports did not have the Scale Factor option. Users had no way to view amounts in a summarized format (e.g., Crores, Lakhs) — making it difficult for higher management to quickly interpret large figures in these reports.

🎬 Report Variations & Navigation

Reports → Accounts → Management Reports → Trial Balance

📷 See It in Action

📄 TB Ledger Group — Scale Factor

📄 TB Ledger Group Details — Scale Factor

📄 TB Monthly Columnar — Scale Factor

📄 TB Segment Wise Columnar — Scale Factor

📌 What Was Happening

The Balance Sheet report variations under Management Reports did not have the Scale Factor option. Users had no way to view amounts in a summarized format (e.g., Crores, Lakhs) — making it difficult for higher management to quickly interpret large figures in these reports.

🎬 Report Variations & Navigation

Reports → Accounts → Management Reports → Balance Sheet

📷 See It in Action

📄 B/S Standard — Scale Factor

📄 B/S Segment Wise Columnar — Scale Factor

📄 B/S Monthly Columnar — Scale Factor

📌 What Was Happening

GSTR-3B displays the consolidated data of GSTR-1 & GSTR-2B, and depending on the volume of data, it takes considerable time to load and export. At the time of GSTR-1 filing, clients needed to reconcile GSTR-1 data with GSTR-3B side by side — but doing so caused slowness in GSTR-3B due to the combined data load, making the reconciliation process frustrating and time-consuming.

🎬 Where to Find It

📷 See It in Action

📄 GSTR-1 reconciliation dropdown in GSTR-3B

📌 What Was Happening

During the Bank Pay Review process, the reviewer could see the party name and account name but had no visibility of the Bank Account Number or IFSC Code from the party’s ledger master. This made it difficult to verify payment details before approving, requiring the reviewer to cross-check the master separately.

🎬 Where to Find It

📷 See It in Action

📄 Account No & IFSC columns in Bank Pay Review

📌 What Was Happening

In the Item-wise Profitability → Profitability Details report, there was no option to exclude inter-branch transactions from the results. The “Exclude Inter-Branch” filter was already available in the Batch-wise Profitability Details report, but users viewing the item-wise breakdown had no equivalent control — meaning inter-branch transfers were always included, which could skew profitability figures for companies operating across multiple branches.

🎬 Where to Find It

📷 See It in Action

📄 Exclude Inter-Branch option in Item-wise Profitability Details

📌 What Was Happening

In the Daybook Advance Search, users could search by various fields but there was no option to search by Line Narration. When entries had narration recorded at the line level, there was no way to locate them using that narration text through the advance search — making it difficult to trace specific transactions where only the line narration was known.

🎬 Where to Find It

📷 See It in Action

📄 Line Narration search option in Daybook Advance Search (1)

📄 Line Narration search results in Daybook Advance Search (2)

📌 What Was Happening

The new Date of Incorporation and Date of Birth fields being added to the Ledger Master → Party Information (see E1 / JOB-163337) were not being pulled into the TCS Report → Details. Without these party-level statutory dates in the TCS Details output, users had to cross-reference the ledger master separately when validating or filing TCS data.

🎬 Where to Find It

📷 See It in Action

📄 DOB / DOI fields shown in TCS Report Details

📌 What Was Happening

The Cheque Print option always printed the cheque date on the output — there was no way to print a cheque without the date. Users who needed to issue undated cheques (post-dated handover, manual date filling, etc.) had no setting to suppress the date from the printed cheque.

🎬 Where to Find It

📷 See It in Action

📄 Parametric setting for Cheque Print without date (1)

📄 Cheque printed without date when option disabled (2)

📌 What Was Happening

The new Date of Incorporation and Date of Birth fields being added to the Ledger Master → Party Information (see E1 / JOB-163337) were not being pulled into the TDS Details reports. Users had to cross-reference the ledger master separately when validating or filing TDS data — the same gap that existed on the TCS side (see E6 / JOB-163341).

🎬 Where to Find It

📷 See It in Action

📄 DOB / DOI fields in TDS Details Section-wise (1)

📄 DOB / DOI fields in TDS Section Details IBT (2)

📌 What Was Happening

In the Ledger Report, the Stock Details option was available when searching normal ledgers — both on the UI and in the Excel export. However, when the same report was run for Stock Accounting ledgers, the Stock Details option was not available, so users had no way to view or export the stock breakdown for those ledgers from the Ledger Report screen.

🎬 Where to Find It

📷 See It in Action

📄 Stock Details option for Stock Accounting ledgers in Ledger Report

📌 What Was Happening

In the Balance Sheet (Standard), there was no visual distinction for negative (opposite-nature) values — a Cr balance in the Assets side or a Dr balance in the Liabilities side appeared in the same colour as all other figures. Users had to manually identify these anomalous balances by reading the values, with no at-a-glance signal that a closing balance was behaving contrary to its expected nature. This problem existed across the UI view, the PDF (Standard) download, and the Excel (Standard) export.

🎬 Where to Find It

📷 See It in Action

📄 Tick box beside Search button to toggle RED highlighting (1)

📄 RED highlight on -ve values in Balance Sheet UI (2)

📄 PDF (Standard) download with highlighted -ve values (3)

📄 Excel (Standard) download with highlighted -ve values (4)

📌 What Was Happening

There was no dedicated sales report to view the quantity sold broken down by Godown or Segment across the company. Users had no single-screen view to compare sales volumes across locations or segments — making it difficult to analyse distribution performance without pulling and reconciling data from multiple sources.

🎬 Where to Find It

📷 See It in Action

📄 Sales Qty Godown / Segment Wise Report — UI view (1)

📄 Sales Qty Godown / Segment Wise Report — format detail (2)

📄 Sales Qty Godown / Segment Wise Report — additional view (3)

📌 What Was Happening

The Ledger Report → Daily Balance showed Debit and Credit amounts for each date but had no way to see how many individual transactions made up those totals. Users who needed to verify the count of entries for a particular date had to drill down or cross-check manually — the report gave amounts but no count of entries.

🎬 Where to Find It

📷 See It in Action

📄 Show Transaction Count option in Ledger Daily Report

📌 What Was Happening

The Profit & Loss (Standard) report used P&L specific terminology throughout — the export was named “Profit & Loss” and the bottom line was labelled “Profit for the Period” or “Loss for the Period”. For organisations that follow the Income & Expenditure account format (trusts, societies, non-profits, and similar entities), this terminology was not appropriate — there was no alternate report format using the correct I&E labels.

🎬 Where to Find It

📷 See It in Action

📄 Income & Expenditure A/c report — UI view (1)

📄 Excess of Income / Expenditure label at bottom line (2)

📄 Report export named Income & Expenditure A/c (3)

📄 Company Master / Acc Param marking to enable report (4)

📌 What Was Happening

The GSTR-1 Report had two data mismatch issues:

• Place of Supply mismatch — the Place of Supply value was not being handled correctly in certain scenarios, causing discrepancies in the report
• Voucher-wise details mismatch for B2Cs — the voucher-level breakdown for B2C transactions was not aligning with the expected GSTR-1 format

Additionally, RCM (Reverse Charge Mechanism) entries were appearing in the B2B drill-down and were also being counted in the B2B summary, which was incorrect — RCM entries should be tracked separately and not inflate the B2B section count.

🎬 Where to Find It

📌 What Was Needed

The Cheque Print Coordinate setup did not offer a way to adjust the font size of printed cheque text, limiting control over how the cheque printout appeared.

🎬 Where to Find It

📷 See It in Action

📄 Bank Ledger Master — Edit Cheque Print Coordinate link (1)

📄 Cheque Print Coordinate popup — Font Size field (2)

📄 Ledger Report — Cheque Print option applying the font size (3)

📌 What Was Needed

In the Trial Balance Report (Standard), there was no way to visually flag Ledger Groups showing a negative or opposite balance — an Asset group with a Credit closing balance, or a Liability group with a Debit closing balance — based purely on Closing Balance figures (not Opening).

🎬 Where to Find It

📷 See It in Action

📄 Options dropdown — Red Highlight Negative Values checkbox (1)

📄 Ledger Name & Closing Balance shown in red for reversed balances (2)

📌 What Was Needed

The GSTR-2 part of the new GSTR-3B screen was contributing to slower load times.

📷 See It in Action

📄 GSTR-3B new screen — optimized GSTR-2 part

📌 What Was Needed

The Settings screen displayed several fields that had become irrelevant to the current structure. Since verification is now handled via AWS shared on the configured mail ID, those extra fields no longer served any purpose and only cluttered the screen.

🎬 Where to Find It

📷 See It in Action

📄 Before — Settings screen with irrelevant fields

📄 After — irrelevant fields removed from Settings

📌 What Was Needed

The lock voucher date is OTP based, but locking of the Chart of Accounts was not — so COA locking could override the lock date. Chart of Accounts locking needed the same OTP protection.

📷 See It in Action

📄 Chart of Accounts locking now OTP based

📌 What Was Happening

When creating a Cost Center and saving it, the focus was getting lost on the screen instead of automatically shifting back to the Cost Center field. Users had to manually click on the Cost Center field to continue working, breaking the keyboard-driven navigation flow and slowing down the master creation process.

🛠 Where to Find It

📷 See It in Action

📄 Cost Center focus behavior after save

📌 What Was Happening

Two issues were identified in the Price List and Item Master:

• Issue 1 (Price Level Master): When deleting and adding a row at the same time during edit, the system was incorrectly throwing a duplicate error — even though the combination was not actually a duplicate.

• Issue 2 (Item Master): Users were able to save duplicate combinations from the Item Master, which should not have been allowed. The validation was missing, leading to inconsistent price list data.

🛠 Where to Find It

📷 See It in Action

📄 Pricelist Master duplicate error & validation fix

📌 What Was Happening

Even though the Batch setting was turned off for an item in the Item Master, the batch option was still visible during stock entry. This was caused by the API saving the batch enable value as null instead of 0 in some cases during item creation via API — leading the system to incorrectly treat the item as batch-enabled.

📷 See It in Action

📄 Batch setting off but batch visible in stock entry

📄 Batch option correctly hidden after fix

📌 What Was Happening

When the ledger code duplicate parameter check was enabled and a ledger was created with a specific code (e.g., L58742), disabling the visibility of that ledger caused an issue. If a user then posted an entry via API, instead of showing a duplicate check alert, the system allowed a new ledger to be created with the same ledger code — because the duplicate validation was not considering ledgers whose visibility was disabled.

📷 See It in Action

📄 Duplicate ledger code created despite check being enabled

📄 Duplicate check now works correctly with disabled visibility

📌 What Was Happening

When a new user was created and the “Allowed From” option was selected for back date entry and edit during the initial setup (first go), the back date entry and edit values were not getting saved correctly in the backend. This caused incorrect permission behaviour for the newly created user regarding back-dated transactions.

🎬 Where to Find It

📷 See It in Action

📄 Back date entry / edit saving issue in User Master

📌 What Was Happening

While creating a Cost Center Master, if the user selected the Cost Category using keyboard keys instead of the mouse, the Party field would sometimes appear even when it was not enabled for the selected Industry cost category. When this happened, the Party field became mandatory, preventing the user from saving the cost center without filling it — even though the category did not require it.

🎬 Where to Find It

📷 See It in Action

📄 Party field incorrectly appearing in Cost Center Master

📌 What Was Happening

The Cashfree verification status option was appearing on multiple screens without any parameter check. This meant the option was visible to all users regardless of whether the Cashfree feature was enabled for their company. The affected screens were:

• Approval Screen
• Ledger Master
• Ledger Master shortcut from Transaction Screen
• Ledger Master View

📌 What Was Happening

When PAN applicability was set to “Mandatory” for a ledger group, the Ledger Master was not getting saved. This prevented users from creating or updating any ledger under that group, blocking master data management entirely.

🎬 Where to Find It

📷 See It in Action

📄 Ledger Master save issue when PAN is mandatory

📌 What Was Happening

When a ledger was created directly from the transaction screen using the Alt+C shortcut key, the bank details or party details entered by the user were not being saved — even though all the necessary information had been filled in. This issue was occurring for companies where the Cashfree parameter is enabled, causing the details to silently drop without any error or indication to the user.

🎬 Where to Find It

📷 See It in Action

📄 Bank/party details saved via Alt+C — After Fix (1)

📄 Bank/party details saved via Alt+C — After Fix (2)

📌 What Was Happening

When a ledger was created via the API, the creation timestamp was being stored in 12-hour format without an AM / PM indicator. Since RealBooks displays timestamps in 24-hour format, this caused the time to be interpreted incorrectly — a ledger created at 12:34:19 PM was showing as 00:34:19 in Ledger Master → User Information → Create Dt.

🎬 Where to Find It

📷 See It in Action

📄 Create Dt showing wrong time (00:34:19) before fix (1)

📄 Create Dt showing correct time (12:34:19) after fix (2)

📌 What Was Happening

In the Party Ledger Master, address details entered in the Address tab were not getting saved. Users could enter the address, but on saving and reopening the ledger, the address fields were blank — forcing repeated re-entry with no reliable way to persist the data.

🎬 Where to Find It

📷 See It in Action

📄 Address now saved correctly in Party Ledger Master

📌 What Was Happening

In the Auto-Increment Manual Update numbering configuration, it was possible to assign the same Prefix / Suffix combination to two different Segments under the same Voucher Type. This caused duplicate voucher numbers to be generated across those segments, since both segments shared the same numbering sequence identifier — leading to numbering conflicts within the voucher type.

🎬 Where to Find It

📷 See It in Action

📄 Same prefix/suffix allowed across segments — before fix (1)

📄 Duplicate prefix/suffix now restricted within voucher type (2)

📌 What Was Happening

The Key Name under Batch Specification in Item Group Master was editable even after transactions using that batch specification already existed. If a transaction was created using a Batch Specification, and the Key Name was later modified in the Item Group and then changed back to its original value and saved, the Batch Specification shown in the existing transaction was displayed incorrectly — even though the Key Name reverted to what it originally was.

🎬 Where to Find It

📷 See It in Action

📄 Batch Specification as shown in transaction (1)

📄 Configure Batch Specification — Key Name field (2)

📄 Warning shown when reassigning a Key already in use (3)

📌 What Was Happening

When configuring the Business Place Segment List under GST Business Place and removing any segment, the change was not reflected — the removed segment continued to be displayed as if it were still assigned. The root cause was that the Segment ID and Voucher ID were the same, which caused the business place configuration to save incorrectly.

🎬 Where to Find It

📷 See It in Action

📄 GST Business Place — Segment column (1)

📄 Business Place Segment List popup (2)

📌 What Was Happening

Users were unable to set or switch the Home Page to MIS DashBoard in User Master → Permission — even after saving, the same issue persisted. The root cause: if the user’s Home Page had “Show on startup” enabled (already bookmarked) and that page got loaded, a duplicate value was inserted in the database for home_page. This duplicate param caused the user to remain unable to view the MIS DashBoard, even when it was correctly assigned in User Master.

🎬 Where to Find It

📷 See It in Action

📄 Home screen with “Show on startup” enabled (1)

📄 User Master: User List — edit permission (2)

📄 Home Page dropdown — MIS DashBoard now selectable and saved (3)

📌 What Was Happening

On the Bank Ledger, the Foreign Bank pop-up option was shown only when the ledger was grouped directly under “Bank”. If the Bank Ledger was grouped under “Bank Account”, the Foreign Bank pop-up option did not appear — because marking a foreign bank was fixed to the “Bank” group only.

📷 See It in Action

📄 Foreign Bank pop-up now shown under Bank Account

📌 What Was Happening

When a Sale entry was created by chaining from a Delivery Order (DO) to Sale, the inclusive tax of the item was not getting calculated correctly in the sale entry. This led to incorrect tax calculations in the sale voucher, causing discrepancies in the final transaction amounts.

📷 See It in Action

📄 Incorrect tax calculation in DO to Sale chaining

📄 Tax calculation corrected after fix

📌 What Was Happening

The back dated entry and edit permission defined in the User Master was not being considered when transactions were posted via API. This meant users could create or edit back-dated entries through the API without the system enforcing the configured permission restrictions — bypassing the intended access control.

📌 What Was Happening

During Bank Statement import for entry posting, even when the user selected a Business Place, it was not getting saved in the transaction screen. This meant the Business Place information was lost after posting, requiring manual correction of each affected transaction.

🎬 Where to Find It

📷 See It in Action

📄 Business Place selection during Bank Statement import

📄 Business Place now saved correctly in transaction

📌 What Was Happening

While posting a Purchase entry, when navigating through fields using the Tab key, the cursor was supposed to move sequentially through each field. However, after the Quantity field, pressing Tab was skipping the Alt Unit and Alt Qty fields entirely and jumping directly to the Rate field — even though data needed to be entered in both Alt Unit and Alt Qty.

🎬 Where to Find It

📷 See It in Action

📄 Tab key skipping Alt Unit & Alt Qty in Purchase

📌 What Was Happening

Following the recent release of the optimized inventory screen, a bug was introduced for companies where the Stock Accounting module is enabled. In such companies, the Purchase ledger must always be in Multi Purchase format — regardless of whether the Multi Purchase parameter is enabled or disabled. However, the new optimized inventory screen was not enforcing this rule, causing incorrect ledger behaviour for Stock Accounting companies.

🎬 Where to Find It

📷 See It in Action

📄 Multi Purchase format issue in Stock Accounting

📌 What Was Happening

When a user opened a Purchase Return entry in edit mode and unticked and re-checked the tagged purchase reference, the godown of the previous item line was automatically getting replaced into the newly checked item row. This caused incorrect godown values to be populated without any user input, leading to data integrity issues in the Purchase Return entry.

🎬 Where to Find It

📷 See It in Action

📄 Godown auto-replaced issue in Purchase Return edit mode

📌 What Was Happening

When opening a Customer Debit Note (Price Difference) in edit mode, adding a new item, and then navigating to the Tax tab to add a new tax line for that item, two issues were observed:

• The previous item line was getting automatically removed, prompting the user to re-select the item
• The tax ledger could not be selected in the new tax line, blocking the user from completing the entry

🎬 Where to Find It

📷 See It in Action

📄 Item removed & tax ledger issue in Price Difference edit

📌 What Was Happening

While posting a Purchase entry with PO tagging, two issues were observed related to Cost Center (CC) allocation across line items. These issues occurred only when the parameter “Allow to copy last CC row details” under Cost Center settings was enabled — disabling the param made it work correctly:

• Issue 1 — CC Split not working: After selecting a single Cost Center for the first line item, when attempting to assign a different CC to subsequent items, the split was not being applied — the same CC was being carried over regardless.

• Issue 2 — CC Removal not working: After selecting multiple Cost Centers of the same category in the first line item, when trying to remove the CC for other items, the removal was not taking effect.

🎬 Where to Find It

📷 See It in Action

📄 Cost Center split working correctly — After Fix (1)

📄 Cost Center removal working correctly — After Fix (2)

📌 What Was Happening

In an inventory entry, the system was allowing a comma to be entered in the Discount Amount field under the Discount tab. The entry was getting saved with the comma intact, resulting in an invalid numeric value being stored. This caused the invoice to not get generated for that entry.

🎬 Where to Find It

📷 See It in Action

📄 Discount amount saved with comma — Before Fix

📄 Comma rejected in discount amount — After Fix

📌 What Was Happening

In the GSTR-1 Report — B2B section, two issues were observed for certain entries:

• Issue 1 — Incorrect Exempt Amount: An entry was showing an exempt amount of ₹1,118.66 even though the ledger was already marked as taxable. The amount was incorrectly being reflected as exempt.

• Issue 2 — Blank Invoice Number: For the same transaction, despite a bill reference number being present, the Invoice Number field was showing blank in the report.

Root Cause: In the IBT parent screen, when the expense ledger was changed and the entry was saved without re-computing auto GST, the GST ledgers were not getting removed cleanly — causing the GST data to be dropped from the transaction, leading to both the exempt amount discrepancy and the missing invoice number.

🎬 Where to Find It

📷 See It in Action

📄 Exempt amount & blank invoice in GSTR-1 B2B — Before Fix

📄 Correct GST data in GSTR-1 B2B — After Fix

📌 What Was Happening

When a ledger had its Visibility disabled, the restriction was being enforced in regular entry screens but not at the Copy Accounting Transaction level. Users could still copy transactions that contained visibility-disabled ledgers — effectively bypassing the visibility control and creating fresh entries against ledgers that were meant to be restricted.

🎬 Where to Find It

📷 See It in Action

📄 Restriction message with Ledger Name in Copy Transaction

📌 What Was Happening

On the Purchase Order Approval screen, users were unable to view the full item list of the PO — the page kept buffering for a long time and never finished loading. The regression was traced back to a recent Cashfree fix, where the Cashfree parameter was inadvertently added to the approval screen as well. As a result, on sites where Cashfree was disabled, the approval screen would hang and users were unable to approve Sale Orders or Purchase Orders.

🎬 Where to Find It

📷 See It in Action

📄 PO Approval screen loading item list correctly after fix

📌 What Was Happening

The issue arose from a specific sequence of actions:

1. Assign Alt Unit details in the Item Master and create a Sales Order (SO) using that Alt Unit combination
2. Go back to the Item Master and update (change) the Alt Unit details
3. When creating the Sale transaction against that SO, the Alt Unit field appeared blank — because the system no longer recognised the original combination as valid

As a result, the Alt Qty was wrongly carried / considered in the affected SO and Sale transactions, leading to incorrect quantity data.

🎬 Where to Find It

📷 See It in Action

📄 Before: Alt Unit editable — cross & dropdown visible (1)

📄 No cross or dropdown to change Alt Unit — edit disabled (2)

📌 What Was Happening

The Stock Journal edit screen was recently optimised for better performance (see E4 / JOB-156882 in Beta Release 18-06-2026). During that optimisation, a specific edge case was not handled:

The Voucher Type Master for Stock Journal does not expose an Auto-Increment Manual Update option in the UI. However, one client had configured this numbering setting via an Excel import, and the system had accepted it. Because this configuration path was not accounted for in the optimised version, Stock Journal entries with this numbering setup could not be opened in Beta.

🎬 Where to Find It

📷 See It in Action

📄 Stock Journal entry with Excel-imported numbering config (1)

📄 Stock Journal entry opening correctly after fix (2)

📌 What Was Happening

In a Sales Order (SO), when an item was populated from a pricelist before the Party was selected, the amount reflected incorrectly — tax was calculated properly but was not included in the displayed amount. The amount only corrected itself when the user clicked the Tab key, requiring an extra manual step to trigger the recalculation.

The root cause was the order of entry: adding item details before selecting the Party meant pricelist and tax values were applied without a complete party context, resulting in an incorrect amount.

🎬 Where to Find It

📷 See It in Action

📄 Incorrect amount displayed when item added before party (1)

📄 Party-first restriction enforced — correct amount shown (2)

📌 What Was Happening

RealBooks correctly blocks manual search of an inactive godown in transaction screens. However, there was a gap when the Default Godown feature was in use:

If a godown was set as the default godown in the inventory screen via Txn Configuration → Param, it would be auto-populated into the entry. If that godown was subsequently marked inactive in Godown Master, the inactivity check was not applied to this auto-populated value — allowing the inactive godown to silently slip into new and edited entries.

🎬 Where to Find It

📷 See It in Action

📄 Default Godown configuration in Txn Param (0)

📄 Inactive godown being auto-populated in entry — before fix (1)

📄 Inactive godown blocked from auto-population — after fix (2)

📌 What Was Happening

When opening a Sales Entry in Edit mode, two issues were present in the Accounts tab:

• The tax amount was not displayed — the field appeared blank even though tax had been applied to the entry
• Any ledger added in the Accounts tab during editing was not retained when the Sales Entry was saved and reopened in Edit mode — the added ledger disappeared, requiring the user to re-enter it each time

🎬 Where to Find It

📷 See It in Action

📄 Tax amount & ledger now correctly shown in Sale Edit — Accounts Tab

📌 What Was Happening

When trying to view an attached document from the Approval List, the full image of the document was not loading in the viewer. Although the zoom in / zoom out controls were present, certain documents were failing to load completely — forcing users to download the document every time just to see its full content, which was time-consuming and disruptive to the approval workflow.

🎬 Where to Find It

📷 See It in Action

📄 Document not loading fully in viewer — before fix (1)

📄 Full document loading correctly in viewer — after fix (2)

📌 What Was Happening

In the Gate Pass tab of transaction entries, the Transportation Distance (Km) was not being fetched even when both the Party PIN Code and Godown PIN Code were provided. Additionally, when the Dispatch from: Segment option was selected, the Transportation Distance was not calculated in that case either. Entries saved during this issue retained a distance value of 0.00.

🎬 Where to Find It

📷 See It in Action

📄 Transportation Distance correctly calculated with Segment dispatch

📌 What Was Happening

When a Voucher AI–processed invoice had multiple line items taxed at different GST rates, the system combined the Purchase Ledger values into a single entry instead of posting them separately. Because the values were merged, GST was also calculated on the combined amount rather than per line item, resulting in incorrect GST posting.

Example:
• Item 1 — Taxable Value: ₹1,330 @ 5% GST → GST = ₹66.50
• Item 2 — Taxable Value: ₹180 @ 18% GST → GST = ₹32.40

Instead of keeping these separate, the Purchase Ledger was posted as a single combined entry of ₹1,510, with GST calculated on that combined logic — leading to incorrect accounting entries. This occurred only when multiple GST rates existed within a single invoice.

🎬 Where to Find It

📷 See It in Action

📄 Source Tax Invoice — items at 5% & 18% GST (1)

📄 Tax Invoice — GST breakup by HSN/SAC (2)

📄 Invoice uploaded via Voucher AI (3)

📄 Purchase Ledger & GST posted separately per rate — after fix (4)

📌 What Was Happening

While making a TDS payment, the TDS Challan Tagging pop-up screen was not reflecting newly added TDS sections in RealBooks. This left users unable to tag payments against the latest TDS sections from within the Challan Tagging popup.

🎬 Where to Find It

📷 See It in Action

📄 New TDS sections now listed in TDS Payment popup

📌 What Was Happening

In the Sale Return voucher, clicking Search under the Reference tab displayed an incorrect Gross Amount. Even when only a specific item (or subset of items) was selected, the Gross Amount shown reflected the total of all items in the voucher instead of just the selected one(s).

🎬 Where to Find It

📷 See It in Action

📄 Before — Gross Amount showing total of all items

📄 After — Gross Amount matching only the selected item

📌 What Was Happening

Ideally, Sale Order (SO) quantity can be greater than or equal to the Sale quantity, but never less. When a Sale was created by tagging an SO, and the setting to allow changing SO qty after tagging was enabled, that setting was meant only to allow increasing the SO qty. However, if the user went back to the SO, added a new row, and then edited the qty of an item already tagged to the Sale, they were able to decrease its SO qty below the tagged Sale qty — creating a discrepancy between SO qty and Sale qty.

🎬 Where to Find It

📌 What Was Happening

When a Sale entry was saved with the Fx (foreign currency) option enabled, and the Accounts tab had additional ledger data added, reopening that entry in Edit mode failed to load its Item details correctly.

🎬 Where to Find It

📷 See It in Action

📄 Sale Order with Fx enabled (1)

📄 Sale Transaction Edit — General tab (2)

📄 Accounts tab — additional ledger row with Fx Amount (3)

📌 What Was Happening

In the Cost Center (CC) view within transaction entry, it was possible to assign two different Segments across two separate CC blocks on the same ledger line — this should not have been allowed, since a single ledger line’s CC blocks are expected to stay within a consistent Segment assignment.

🎬 Where to Find It

📷 See It in Action

📄 Before — mismatched Segments allowed across CC blocks

📄 After — Segment consistency enforced across CC blocks

📌 What Was Happening

When the Cost Center hierarchy was structured with a Cost Category nested under another Cost Category (e.g. Cost Category 1 → Cost Category 2 → Cost Center A) and the Single Cost Centre feature was enabled for the company, reopening a transaction in Edit mode showed the Cost Category as blank — even though the correct Cost Category and Cost Center were already saved in the database.

🎬 Where to Find It

📷 See It in Action

📄 Cost Category List — nested hierarchy (Agro → Farm) (1)

📄 Cost Center List — Agro Man under Agro (2)

📄 Sale Transaction Edit — CC Details now showing Cost Category correctly (3)

📌 What Was Happening

Consider an item that was taxable till 30-06-2026 and marked exempt from 01-07-2026. If the user opened a Purchase Order or Sale Order with the date 15-05-2026 and entered all details, the item tax was computed as per the item master rate. But if the user then changed the voucher date to 07-07-2026 just before saving, the tax rate was not removed — the entry saved with tax even though the configuration marked the item as exempt on the entered voucher date.

🎬 Where to Find It

📷 See It in Action

📄 Item tax configuration — taxable then exempt (1)

📄 PO/SO entry with earlier date — tax computed (2)

📄 Voucher date changed to exempt period — tax removed (3)

📌 What Was Happening

For a selected ledger with a large number of link references, the Link Details pop-up — which lists all the links used for that ledger — took a long time to load on the UI, because it tried to load every reference link at once.

🎬 Where to Find It

📷 See It in Action

📄 Before — Link Details pop-up loading slowly

📄 After — From/To date filter added to pop-up

📌 What Was Happening

While passing a Foreign Exchange entry, the FX rate was not fetched correctly on the first attempt as per the Currency Master. Even though Source and Buy/Sell were already selected, an incorrect FX rate was picked up — the user had to reselect Source and Buy/Sell every time to get the correct rate.

📷 See It in Action

📄 FX rate fetched correctly on first selection (1)

📄 Correct FX rate without reselecting Source/Buy-Sell (2)

📌 What Was Happening

Even though negative stock was disabled for the company, a stock transfer entry could still be posted from a batch with no available quantity. The outward quantity (2) ended up greater than the inward quantity (1) — producing negative stock at the batch level despite the setting.

📋 Steps to Replicate

1. Copy the existing Batch Entry.
2. Change the Transaction Date to a date before the first Sale transaction.
3. Re-select the Item — the system auto-selects a batch with available quantity and pre-fills Qty as 1.
4. Open the Batch Listing using the Batch icon next to the Item field.
5. Select a batch that has no available quantity.
6. Press Ctrl + S to save the transaction.

📷 See It in Action

📄 Negative stock now blocked when disabled

📌 What Was Happening

While running the DayBook Columnar report, the Voucher Property data was not appearing on the UI or in the exported Excel file. The column header was present, but the actual data was blank in both the on-screen view and the Excel export — making it impossible to identify voucher properties from this report.

🛠 Where to Find It

📷 See It in Action

📄 Voucher Property blank on UI

📄 Voucher Property blank in Excel export

📄 Voucher Property data now displaying correctly

📌 What Was Happening

When the opening balance was updated as on 31-03-2026 and a user ran the Ledger Report from 01-04-2024, the opening balance was appearing randomly among the transaction entries instead of being displayed first. In some cases, the ledger balance was reflected in place of the opening balance — causing confusion and incorrect report interpretation.

🎬 Where to Find It

📷 See It in Action

📄 Opening balance display issue in Ledger Report

📌 What Was Happening

In the previously released Voucher Wise Bill Status Report, the From Date field was available on the report screen. However, this field had no relevance to the report output — the report logic only required a cut-off date. Having the From Date field was misleading and could cause confusion for users.

🎬 Where to Find It

📷 See It in Action

📄 Bill Status Report — From Date removed

📌 What Was Happening

When an entry was created in RealBooks in March 2026 but the corresponding entry reflected in the JSON in April 2026 (i.e., crossing the financial year boundary), the auto match was not working. This happened even though the system is configured to check and match data 3 months before and after the entry post date in JSON. The issue was specifically related to the financial year beginning logic.

📷 See It in Action

📄 2B matching issue at financial year boundary

📌 What Was Happening

In the Daybook Advance Search, the Ledger Search was not functioning correctly — when a ledger name was entered in the search field, the data was not getting filtered or returned, leaving users unable to narrow down daybook entries by ledger through the advance search screen.

🎬 Where to Find It

📷 See It in Action

📄 Ledger Search not returning data — Before Fix

📄 Ledger Search returning correct results — After Fix

📌 What Was Happening

When an Income Ledger was configured with “Nature of Supply (GST)” set to Tax Payable Under RCM, and the transaction involved a B2B party, the entry was not appearing in the GST e-Invoice screen — even though it should have been reflected there for e-invoice processing.

🎬 Where to Find It

📷 See It in Action

📄 RCM B2B entry now showing in e-Invoice screen (1)

📄 RCM B2B entry now showing in e-Invoice screen (2)

📌 What Was Happening

In the Batch-wise Profitability Details report, the Percentage (%) column was not displaying any value. The calculation logic was missing or incorrect, leaving the % field blank for all batch-wise profitability entries regardless of the data available.

🎬 Where to Find It

📷 See It in Action

📄 Percentage now showing in Batch-wise Profitability Details

📌 What Was Happening

On the BRS entry UI screen, when users selected multiple checkboxes and applied a common date, the Bank Date filter was not working correctly. As a workaround, users had to first apply the “Set Voucher Date” option and then the Bank Date filter — only then did the filter behave as expected.

🎬 Where to Find It

📷 See It in Action

📄 Bank Date filter with common date on BRS entry (1)

📄 Bank Date filter applied correctly after fix (2)

📌 What Was Happening

In the GSTR-3B (As Per Input Taken) report, entries were correctly visible in the GSTR B2B screen when drilling down from the report UI. However, when exporting the GSTR 2 B2B Report via “Excel with GST Details”, those same entries were missing from the export — creating a discrepancy between what was shown on screen and what was downloaded.

🎬 Where to Find It

📷 See It in Action

📄 B2B entry visible in GSTR-3B drill-down UI (1)

📄 Entry missing in Excel with GST Details — before fix (2)

📄 Entry now correctly included in Excel export — after fix (3)

📌 What Was Happening

In the Purchase Register, after selecting the Voucher Type from the filter, the cursor was not automatically moving to the Party field. Users who navigate primarily using the keyboard had to manually click or tab to the Party field before they could continue, breaking the natural keyboard-driven flow through the report filters.

🎬 Where to Find It

📷 See It in Action

🎥 Cursor auto-moves to Party field after Voucher Type selection

📌 What Was Happening

In the Purchase Requisition, when opening an entry that was in Partial status and changing its status to Open, the system displayed the message “Data not saved” — preventing the status update from being applied. Users were unable to revert a Partial requisition back to Open without this error blocking the save.

🎬 Where to Find It

📷 See It in Action

📄 Purchase Requisition with Partial status in edit mode (1)

📄 Status changed to Open and saved correctly (2)

📌 What Was Happening

In the Godown Report, godowns that had been marked as inactive in Godown Master were not appearing in the following report variations:

• Item Wise — inactive godowns were missing from the item-level breakdown
• Group Wise — inactive godowns were missing from the group-level breakdown

This meant that stock held in or associated with an inactive godown was silently excluded from these report views, leading to incomplete data.

🎬 Where to Find It

📷 See It in Action

📄 Inactive godown now visible in Godown Report (1)

📄 Item Wise view showing inactive godown (2)

📄 Group Wise view showing inactive godown (3)

📌 What Was Happening

An entry was not reflecting in the BRS (Bank Reconciliation Statement) screen. To correct this, the entry was fired from the Exception Report: Missing in Bank using the Rectify Voucher option — but it got refired twice by mistake due to multiple clicks on the option. As a result, the entry started reflecting twice in the BRS screen instead of once.

🎬 Where to Find It

📷 See It in Action

📄 Rectify Voucher option on Exception Report: Missing in Bank

📌 What Was Happening

Multiple items were not getting searched in Reports. These items had the Mark As Visible toggle disabled in Item Master — but visibility being off should only affect selection in transaction entry screens, not report search. Because the same restriction was incorrectly applied to report search, these items could not be found in report item filters.

🎬 Where to Find It

📷 See It in Action

📄 Item Master with Mark As Visible disabled (1)

📄 Item now searchable in Item Register Report: Item Wise (2)

📄 Item now searchable in Item Segment Wise Quantity report (3)

📌 What Was Happening

In the Batch Register search field, the text being typed automatically disappeared mid-entry, making it difficult to search for the intended batch.

🎬 Where to Find It

📷 See It in Action

📄 Batch Register search field retaining typed text

📌 What Was Happening

The Delivery Order (DO) Status Report was not working — it kept buffering indefinitely without loading results. The root cause: when a user without full Ledger / Ledger Group permission searched using the Ledger Group filter, the report threw an error instead of loading.

🎬 Where to Find It

📷 See It in Action

📄 User Permission — Ledger Permission field (1)

📄 Delivery Order Status Report loading correctly with Ledger Group search (2)

📌 What Was Happening

The Rate column in Sale Register: Item Wise and Purchase Register: Item Wise was showing the last rate of an item instead of its average rate when multiple entries existed for the same item at different rates — producing a misleading Rate figure.

🎬 Where to Find It

📷 See It in Action

📄 Sale Register: Item Wise — Rate column (1)

📄 Purchase Register: Item Wise — Rate column (2)

📌 What Was Happening

In Item Master → Item List, exporting the Item Tax Structure to Excel produced a 0 KB (empty) file. The export was built on the old Excel structure, which could not handle a large item count — for big datasets it hit the Excel column limit and errored out instead of generating the file.

🎬 Where to Find It

📷 See It in Action

📄 Item Master — Item Tax Structure Excel export option (1)

📄 Item Tax Structure Excel exported successfully for large data (2)

📌 What Was Happening

After logging in and navigating to the Mapped Excel Import screen, changing the company caused the software to automatically log out the user.

🎬 Where to Find It

📷 See It in Action

📄 Company change on Mapped Excel Import now redirects to Home

📌 What Was Happening

When generating an invoice from the Inventory Day Book screen, it showed “no template found” — even though the same invoice generated correctly from the standard Day Book screen.

🎬 Where to Find It

📷 See It in Action

📄 Invoice generation from Inventory Day Book (1)

📄 Invoice generation from Inventory Day Book (2)