Skip to main content
T
TC CKD
August 7, 2023
Question

An invalid ID value was specified.

  • August 7, 2023
  • 3 replies
  • 0 views

I am trying to input a bill to one of my vendors and keep getting the invalid I.D.  This just started happening this morning and the look of the billing page is slightly different as well. Help!!

Thanks, Tim

    3 replies

    T
    TC CKDAuthor
    August 7, 2023

    Also, none of the boxes below show red where the issue might be.  I am thinking this is some sort of glitch.

    Candice C
    Candice C
    August 7, 2023

    Hello, @TC CKD. 

     

    Welcome back to the Community! 

     

    To clarify, can you provide a screenshot of the invalid ID that you're receiving? 

     

    In the meantime, I recommend clearing your browser's cache and cookies to see if this will help resolve the issue. 

     

    You can also check out this guide about entering, managing, and paying bills in QBO. 

     

    I'll be waiting for your response! 

    A
    AngLMO
    August 14, 2023

    Having the same issue.

    T
    TC CKDAuthor
    August 14, 2023

    I went into a chat session with support and spent about 30 minutes on this issue and was able to get around this error.  There must have been an update that caused this problem but it seems this is the only way to enter a bill with an open PO. 

    First you have to open a vendor with a open PO you are applying against. Then when the add to bill window opens select the bill that references the bill.  Above the vendors name you will see in blue "1 linked bill" click it.  Next you will click purchase order and then click yes to cancel.  When the purchase order opens up go to the upper right and click copy to bill.  At that point you should be good to go.

    What ever happened they need to fix this.  Adding extra operations to a simple task has to be a mistake.

    A
    AngLMO
    August 14, 2023

    I also found out that if I deleted the information I had in the "category details" section, it saved the bill. This is inconvenient as this is information I need but it worked. This is an odd glitch. 

    Terms & ConditionsAccessibility statement