Sage BusinessVision 2023 SBE Bug Report - legitimate Sales posted that do not pass Data Validation

SUGGESTED

If a sale is tendered for $0.01 or $0.02 or -$0.01 or -$0.02, and tendered with "Cash & Cheque Receipts" selected as the payment method, BusinessVision will apply penny rounding and will round the total to $0.00.

This will post a journal entry that does not include a payment method, which will fail Data Validation within BVs own Data Validation report. 

  • 0
    SUGGESTED

    Hi  ,

    Thank you for reaching out. Did you ever find an answer for this issue?

    I’ve looked into the Sage Knowledgebase for potential solutions, and here are some steps that might help:

    1. Manual Posting: If the sales are not posting correctly, you might need to manually enter the invoice in the Accounts Receivable and General Ledger modules. Make sure AutoPost is off before you proceed.
    2. Sales Analysis (SA) to AR and GL: Verify that there is no transaction number in SA and manually update the invoice under the customer's account in AR and GL. Please refer to the detailed steps provided in the article content here to ensure accuracy.
    3. Order Entry Issue : If you're also experiencing issues with invoicing an order where the option to Print and Post Invoice is grayed out, this might be due to the Hold Invoicing setting or the order status is set to Hold. Adjust the settings in the System Manager under User Details to ensure Hold Invoicing is set to No.

    If these steps do not resolve your issue or if the problem persists, please do not hesitate to reach out for further assistance or consider chatting with support for more immediate help.

    Warm Regards,
    Erzsi

  • 0 in reply to Erzsi_I

    Hi  , 

    I am not sure if you read the post correctly. Sales Analysis record(s) are posted with corresponding GL transactions. This is a bug in the way BusinessVision handles small cash transactions due to penny rounding. The inability to handle this gracefully causes a legitimate sale to fail data validation. This is a simple fix by the Sage development team.

    Currently if we want to correct these transactions, it requires manually inserting GL_TRANSACTION lines into the affected transactions. This should not be the responsibility of the end user. We pay for software support and upgrades. If we are providing the debugging information, it would be appreciated if Sage acted on this and fixed the issues that have been described.