HoneyBook invoices and contracts can be used separately, but their real value appears when they are combined through Smart Files. HoneyBook defines Smart Files as interactive client documents that can range from a standalone invoice or contract to a multi-step booking experience where a client selects a service, schedules time, signs an agreement and pays within one connected file.
That makes a HoneyBook proposal fundamentally different from emailing a PDF quote and hoping the client knows what to do next.
The file can guide the action.
What Is a HoneyBook Smart File?
HoneyBook’s current Smart Files system replaces the old assumption that every client action needs a different document.
Current documentation says a Smart File may contain:
- text and branded information;
- service selections;
- questions;
- invoices;
- contracts;
- scheduling;
- other interactive client actions.
A file can be one page or a multi-step experience.
A Proposal Can Become a Booking Flow
Imagine a photographer sends a wedding proposal.
A traditional document may contain the packages and price.
A HoneyBook Smart File can potentially let the client:
review services
↓
select a package
↓
provide required details
↓
sign the contract
↓
pay the deposit
The administrative result is much stronger because acceptance, signature and payment can happen while the client is already engaged.
Combining Contract and Invoice
HoneyBook specifically documents combining invoicing and a contract inside one Smart File to make booking more continuous.
The business avoids the familiar sequence:
“Thanks for signing. I’ll send the invoice separately.”
That missing step matters because every extra email creates another opportunity for the booking to stall.
Invoices Pull From Services
HoneyBook invoices can be connected with service blocks inside the same file.
Current recurring-invoice documentation also describes automatically pulling a client’s service selections into later invoice sections in supported configurations.
That reduces manual re-entry.
If a customer selects Package B, the invoice can reflect the choice rather than requiring the business owner to build a new invoice from scratch.
Customizing an Invoice
Current HoneyBook documentation allows invoices to be inserted into Smart Files, customized and shared through desktop or mobile workflows.
The invoice can include services and payment options appropriate to the project.
The important part is that the invoice remains connected to the client and project record.
Payment Plans
Not every service should be paid in one transaction.
HoneyBook supports scheduled payments, letting businesses structure deposits and later balances around project milestones or dates.
That is particularly useful for:
- weddings;
- consulting projects;
- design work;
- event services;
- retainers;
- longer creative engagements.
The payment schedule remains tied to the invoice instead of being tracked manually in a spreadsheet.
Recurring Billing
HoneyBook also supports recurring invoices for ongoing services.
Current documentation lets users choose a recurring cadence and define when the series ends.
This can support arrangements such as monthly consulting or ongoing marketing services.
A recurring invoice is different from splitting one fixed project total into several payments.
The former repeatedly creates invoices for ongoing billing.
The latter divides a known balance.
Autopay
Autopay can automatically charge a client’s saved method according to the payment schedule, reducing the need to chase every due date manually.
Businesses can configure whether autopay is available or required according to the invoice setup.
The client still needs an authorized payment method.
Contracts and eSignatures
HoneyBook’s current U.S. plans include contract functionality with electronic signatures.
That allows the agreement to remain part of the same client record rather than being signed through an unrelated tool and manually uploaded later.
The specific legal terms of the contract are the business owner’s responsibility.
HoneyBook provides the document and signature workflow, not legal advice about what the agreement should contain.
Questionnaires Can Be Added Too
Smart Files are not restricted to sales and payment actions.
HoneyBook’s current file terminology includes questionnaires among standalone or combined file types.
That makes it possible to collect information needed for execution after or during booking.
A web designer could collect website requirements.
A photographer could gather locations and shot preferences.
A consultant could collect onboarding information.
Scheduler Inside a File
HoneyBook can insert scheduling directly inside Smart Files.
Current documentation says the client can choose from real-time availability while still inside the broader document experience.
This can be useful where booking the service should immediately lead to booking the session.
Sharing Smart Files
HoneyBook currently allows Smart Files to be shared by email, direct link or view-only link, with controls over who can access and interact with the file.
That flexibility matters when a business needs to show a pricing guide publicly but reserve contract signing or payment for a specific client.
Editing After Sharing
Current HoneyBook functionality allows Smart Files to be edited after sharing in supported circumstances.
However, modifying commercial terms after client action should be handled carefully.
A signed agreement and a draft proposal do not have the same status.
The software capability to edit something does not replace sound contract practice.
Files Become Part of the Client Portal
Shared HoneyBook files can also remain available through the client’s portal.
That gives the customer a centralized way to return to invoices, agreements and other project documents instead of relying exclusively on old email links.
Our HoneyBook Client Portal guide focuses on what the client can actually see.
Smart Files vs. Legacy Files
HoneyBook still documents distinctions between legacy files and Smart Files.
As of 2026, Smart Files support capabilities such as embedded scheduling, Lead Forms and combining multiple client actions that legacy files did not provide in the same way.
For new workflow design, current Smart Files documentation is therefore more relevant than old tutorials built around legacy HoneyBook documents.
The Booking Experience in One File
The strongest HoneyBook document workflow is not:
send proposal
then
send questionnaire
then
send contract
then
send invoice
then
send calendar link
It can instead become:
one guided Smart File
→ service selection
→ questions
→ contract
→ payment
→ scheduling
Whether combining everything makes sense depends on the business.
But HoneyBook gives the business the option to reduce those handoffs.