Skip to main content
J
jeffrey-d-bowman
November 18, 2023
Question

Creating a sales receipt the 'sales receipt no.' field is being populated with text ("Clover 2023 Nov18") instead of the next sequential number. Any thoughts on cause?

  • November 18, 2023
  • 1 reply
  • 0 views
Original commenter did not share additional details

    1 reply

    G
    GenmarieM
    November 18, 2023

    Welcome to the QuickBooks Community, jeffrey.

     

    I can share some information about the automatic sequence of sales receipt numbers.

     

    Whenever you turn on the Custom transaction number, the next sales receipt number will be automatically filled in when you create a new sales receipt.

     

    Please ensure to review your most recent sales receipt transaction and verify if the number has been modified. It is also possible that one of your users may have edited the sales receipt number. In that case, you can review the audit log to confirm and make any necessary changes to the transaction.

     

    Here's how you can review your audit log:

     

    1. Click the Gear icon and select Audit log from the Tools column.
    2. Use the Filter panel to choose a specific User, Date, or Event.
    3. Select Apply.

     

    The audit log displays the history of transactions, who made the changes, and what was done.

     

    Just in case you want to send the sales receipt to your customer, you can check out this article for more guidance: Email estimates, invoices, and sales receipts to customers using QuickBooks Online for mobile.

     

    Don't hesitate to leave a comment below if you need further assistance about your sales receipt. I'll be here to help. Have a good one!

    J
    jeffrey-d-bowmanAuthor
    November 18, 2023

    Thank you for your reply!

     

    Custom transaction numbers has been turned on all year and was working normally. I can pull the year's report and watch the sales receipt numbers increase incrementally. Until November 14th of this year. Suddenly, that custom number field is no longer being populated with a number but is instead being populated by text in the form of "Clover 2023 Nov18" then the next day's additions will read "Clover 2023 Nov 19".

     

    FYI, we use the Clover point of sale system but all of these transactions since the very beginning are hand entered using the New > Sales receipt navigation in the QB Online sidebar.

     

    We're at a complete loss as to why this has suddenly started.

    AlverMarkT
    AlverMarkT
    November 18, 2023

    Thank you also for providing us a quick update and further details, @Jeffrey11_2. I'm here to help you with this.

     

    By default, the sales receipt number increases incrementally when the "Custom transaction numbers" in QuickBooks Online (QBO) is enabled. Custom number field no longer being populated with a number in your sales form could be an integration issue between QBO and the Clover app. 

     

    First, I suggest temporarily turning off "Custom transaction numbers" in your sales settings and running a sample sales receipt to help us isolate the problem.

     

    Next, I recommend reviewing your linked Clover app settings for any added information about how your sales form is set up when you create one in QBO. If the problem persists, it's best to contact Clover POS system support.

     

    When this is fixed, running an audit log report would then be important in correcting the changes in your previous sales forms. Checking the sales transactions on November 14 will serve as a point of reference in correcting the transactions up to the present day. 

     

    This article on matching bank deposits in QuickBooks by combining multiple transactions into a single record might come in handy for you in the future. I'm adding this as a reference: Record and make bank deposits in QuickBooks Online.

     

    We're just a post away should you have further updates on your concern about the transaction number in your sales forms. We'll do our best to assist you. Take care. 

    Terms & ConditionsAccessibility statement