So basically click on an older invoice and then duplicate it? Will it assign the next invoice number? 

I spoke with someone yesterday because I saw that we were changed back to the old layout and that our price rules are working. They informed me that they will not be forcing anyone into the new layout until price rules are available on it. If you are not back in the old layout and can't see where to switch back to it, you can call or chat with them and they can change you back. Hope this helps!

yes, that's correct.

@RickMeister It's true that they delayed the new invoicing due to customer feedback. And then decided to forge ahead anyway a couple weeks later without implementing any of the features customers told them would be essential.

It's almost like Intuit wants to push its customers to find different software that actually works.

@JanbonN "In light of this, we would greatly appreciate it if you could share your valuable suggestions with our product development team."

Except THIS IS THE FEEDBACK. IT'S RIGHT HERE IN THIS FORUM. We've known for months that the new invoicing would not work for our company and we made it known here and through the feedback feature. Quickbooks WAS AWARE. We know this because the feedback was so loud that they even delayed removing the old layout. Can anyone at Quickbooks please explain why we should spend our time leaving even more feedback on a problem that QUICKBOOKS HAS BEEN AWARE OF SINCE 2023? @JanbonN can you explain why Quickbooks forged ahead with the new invoicing despite all the complaints we submitted??

I think it's time to demand a full RCA (Root Cause Analysis) on this change to the environment AND make it publicly available for all to see.  There must be far more transparency between QB and the user community and far better communications when things do not go well.  Electronic accounting is a requirement these days, not a nice to have.  Our collective lively hoods rest in QB hands and that trust should not be taken lightly.  Bluntly stated, this latest event will be the poster child for how NOT to do a rollout and hopefully there will be lessons learned and fundamental changes applied to future releases.  While I applaud the roll back to the "known workable solution", it's clear the "Feedback loop" is broken or at a bare minimum, misused.  There are a lot of things that need attention, and the challenge is to be able to respond with real answers, not just a thanks for the feedback.