Skip to main content
Question

Issue with setting "invoice date" as payment due date

  • April 13, 2026
  • 3 replies
  • 17 views
Joe Underbakke

Since Honeybook does not have a native “quote” feature, I create quotes using a services page and send that by itself. If the client decides to move forward, I will take that same smart file and add the contract, payment, and invoice page.

The issue I’m facing is that I would like the first payment to be due on the “Invoice Date”, as in the day I’m sending the full proposal, but Honeybook backdates the Invoice Date to whenever I originally sent the Quote, even though that smart file did not contain an invoice. If I were to send it as-is, that payment would be marked as ‘overdue’ right out of the gate. What am I missing here?

I have a feeling that the answer to this problem is that I’m not using Honeybook as intended, but if that’s the case I am then wondering what the best method is for sending a quote and then converting it into a contract without any repetition of effort.

    3 replies

    Alicia Bauer
    Forum|alt.badge.img+4

    ​@Joe Underbakke - You’re not missing anything, this is happening because HoneyBook timestamps the Smart File based on when it was originally sent, even if an invoice page wasn’t included at that time. So when you later add the invoice, the system still uses that original send date as the invoice date, which is why it appears overdue.

    One way to avoid this is to duplicate the Smart File once the client is ready to move forward and then add the contract and invoice to the duplicated version before sending it. That way the invoice date will match the new send date instead of the original quote date.

    Another option some people use is to send the services page as a separate Smart File or brochure-style file, and then send the proposal (with contract + invoice) as a new Smart File once the client confirms they want to book.

    HoneyBook’s intended flow is typically proposal → contract → invoice all together, which is why the quote-first approach can create these small hiccups.

    Your approach makes sense though, especially if you prefer letting clients review pricing first without the full proposal attached. Using a duplicated Smart File when they’re ready to book is usually the easiest way to avoid the backdating issue without having to rebuild everything.

    Alicia, Brand and Web Designer + Honeybook Pro
    Joe Underbakke

    Thanks for the thorough reply, ​@Alicia Bauer.

    Can you clarify this part?

    HoneyBook’s intended flow is typically proposal → contract → invoice all together, which is why the quote-first approach can create these small hiccups.

    Do you mean sending it all at the same time, or sending them separately/in succession?

    Let’s say I get this inquiry:

    Project: Company Party

    Date: 12/31/26 | 8pm - 12am

    What is best next-step within the structure of HB?

    I don’t have packages or brochures like a wedding photographer would have. My quotes are for corporate clients and custom for every project, so I’m just sending them the cost for what they’re asking for, not options to choose from. 

    I often feel like I’m finding backdoor ways to get Honeybook to work the way I’d like it to and that it’s more designed for the “package” model. 

     

    Alicia Bauer
    Forum|alt.badge.img+4

    ​@Joe Underbakke - I hope that I am reading this correctly and answering it in a way that is helpful. 

    You could absolutely structure this in HoneyBook as two separate Smart Files if you want to keep the quote and booking steps distinct.

    One way to do it would be:

    File 1 – Quote / Custom Package
    Create a Smart File that includes a page outlining the custom service and pricing for that specific event. The client reviews the details and essentially approves the quote.

    The key piece here is to set this up as a service/package in the Smart File rather than building it as an invoice with line items. Using a service/package allows the client to select and approve it as part of the proposal flow instead of triggering invoice behavior too early.

    Then once they approve that quote, you can automatically send a second Smart File that contains the contract and invoice for them to sign and pay.

    This lets you keep the steps separate if that fits your workflow better:

    1. Client reviews and approves the custom quote
    2. Contract + invoice are sent for signature and payment

    You can structure HoneyBook this way so it doesn’t feel like you have to force everything into a package-style proposal.

    Alicia, Brand and Web Designer + Honeybook Pro
    Terms & PrivacyAccessibility statement

    © 2025 HoneyBook Inc.