Skip to main content
B
bbealsor
December 12, 2023
Question

Stop QBO from guessing invoice numbers?

  • December 12, 2023
  • 1 reply
  • 0 views

Hello. We are using the software sync from ServiceTrade and I'm getting tired of one feature of the invoice numbers. I want every invoice created in QBO from recurring transactions, etc. to not try and slot into the invoice numbers that ServiceTrade generates and sends to QBO. So if ServiceTrade sends invoice 12345678, QBO will make an automatic 12345679 for internal accounting purposes (completely unrelated and just coincidental timing), and then QBO will reject invoice 12345679 from ServiceTrade because it already exists. Can I put an invoice sequence onto these recurring transactions that will lock in and won't get overridden by the invoice numbers coming in from ServiceTrade? 

1 reply

J
JamesM4
December 12, 2023

Hello bbealsor, 

 

Welcome to the Community. It's important you're able to have the invoice numbers added the way you intend to. Rest assured, I'll be happy to steer you in the right direction so you can get back to doing what you enjoy. 

 

In order for you to be able to us a custom sequence of invoice numbers you'd first have to enable the Custom transactions numbers feature. After turning on this feature, each invoice that's added is recorded in chronological order resulting in uniform invoice numbers. Here's how to turn on this feature: 

 

  1. Go to Settings ⚙ and select Account and settings.
  2. Select Sales, then select anywhere within the Sales form content section.
  3. Turn Custom transaction numbers on.
  4. Select Save, then select Done.

If you'd like to learn more about how to set up a number preference for your invoice numbers, check out this article here. Let me know if this info helps. I'll be a message away in case you need additional assistance. Otherwise, I wish you a great rest of the week. 

B
bbealsorAuthor
December 12, 2023

Thanks for replying, but that doesn't help the issue. That feature is working against me, currently, and I don't think turning it off solves the issue but I'm not sure.

Terms & ConditionsAccessibility statement