Skip to main content
December 28, 2018
Solved

We really need a space for bill date and posting date! They are many times not the same and because I need an invoice posted in a certain month, I need to put in a false invoice date.

  • December 28, 2018
  • 11 replies
  • 0 views

There should be two different date boxes when entering bills to be paid.  A bill from a vendor could have a date of 12/1 but the service was really in Nov, so I want to post it in November, but the post date is driven by the "bill date", which is very frustrating.  Why can't there be an 'invoice date" and a "posting date", with a default to the invoice date unless something is entered?  This is a basic feature of any accounting system and would be very easy to fix!

Best answer by lsefcik

Malcom Ziman,

I respectfully disagree that the vendor's bill date isn't important in an accounting system.  Say a vendor provided a service in the month of November.  I would want to "book" that expense in the month of November (the old matching principal).  However, if the vendor doesn't invoice me until 12/15 and has 30 day payment terms, that vendor bill isn't due until 1/15.  Service date and billing date are generally two different periods and people who book invoices just when the vendor bill arrives are actually more on the cash basis than on the accrual basis.  It would be a very simple fix for QB to have a service date/GL Posting date (to get the expense correct) and a bill date.  Since terms for that vendor are already set up in the vendor profile, once we enter the vendor invoice date correctly, the AP due date will automatically populate.  This is the way accrual accounting should work.  And this wouldn't be a difficult fix for QB to make!

11 replies

April 1, 2025

How disheartening to see that this thread started in 2018 and yet nothing has been done to address it.  Such a basic and necessary feature that has been brought up several times, yet continues to be overlooked.  This can't be that challenging of a programming issue.  I have added my recommendation to the programmers, which in the past I must say has been fruitful.  Keeping my fingers crossed but I won't be able to do the workaround for long.  If it isn't fixed soon, I will have to find new software.