Editing the invoice in a Proposal+Contract+Invoice smart file

Hey ​@Jamie Ovation Creative!

This is such a great question, and you’re definitely not the only one who’s run into this.

You're right: once you send a Proposal (which includes the contract and invoice), any edits to the invoice after it's been sent require the entire file to be resent—including the proposal and contract sections—because it's treated as a single, locked package. That’s why the client gets directed to the beginning again.

Unfortunately, HoneyBook doesn’t currently allow you to edit just the invoice section of a Proposal+Contract+Invoice file without needing to resend the entire thing. But here is what I would recommend as a Honeybook Pro

Send a Separate Invoice for Add-ons Like You Mentioned

Once the original file is signed and the base services are agreed upon, you can send a separate invoice for any additional services that come up. That way:

• Your client only receives the new items.

• They’re taken straight to the payment page.

• No need to re-review or re-sign anything they’ve already seen.

This keeps things simpler for your client and helps avoid confusion.

Include Add-On Language in the Initial Contract

I would suggest rewording the section in your contract when it comes to add-ons. Clearly stating in the original contract that add-ons will be billed separately will help set expectations when you send a separate invoice. You can also mention that separate invoices may follow for any additional work requested.

I know it’s not perfect (yet), but hopefully this helps you find a rhythm that works better for you and your clients. I’d definitely recommend adding this to the Ideas tab in the HoneyBook community, if you haven’t already—this kind of feedback is exactly what the product team needs to hear!

I know it’s probably not the answer you were hoping for, but does it help answer your question?

Thanks for the reply. I think I’m going to do what you suggested and adjust my contract to say add-ons will be invoiced separately. Or I might experiment with creating a proposal that’s just my proposal content and a contract and then create an invoice that goes out once the contract is signed. 

I also added a post about this to “Ideas.” Thanks for the suggestion! 

​@Jamie Ovation Creative 

That sounds like a great plan—and honestly, both of those adjustments can go a long way in making things smoother for you and your clients! Separating the invoice or updating your contract language gives you a lot more flexibility as your projects evolve.

Also, in case it helps as you experiment—when building a Proposal, you can choose to include a Service Recap and Payment Recap in the contract. That way if the client decided to include any add-ons there in the proposal, the invoice and contract will update automatically. These automatically pull from the itemized services and payment schedule you've set up!

However, if 3 months later in the project they decide they decide they would like an add-on, then it would be beneficial to send a separate invoice.

I’m so glad you added it to the Ideas tab too! The more context and real-life use cases the product team sees, the more likely they are to prioritize it.

You’ve got this! 💪✨