Proposals and invoices
When to use this
Use this page when you need the big-picture difference between the proposal and invoice sides of an event.
Proposals
The proposal is the customer-facing document for the job. It packages the arrangements, vision, pricing, and terms so the client can review, sign and accept, decline, or ask for changes.
Important proposal behaviors:
- proposals begin in draft and are only visible to your team
- sending locks the proposal, so the client always sees exactly what you approved
- you can follow progress as the client views and responds
- changes after sending become a new version, and the older version is kept as superseded history
- an accepted proposal books the event and becomes the basis for invoicing
Invoices
Invoices are billing records. They track formal payment expectations and the payments that arrive against those expectations.
Important invoice behaviors:
- invoices are created from the event’s Finances view, usually against the accepted proposal or your payment schedule
- draft is the editable stage
- a sent invoice shows as Awaiting payment, then Partially paid and Paid as money arrives, or Overdue if the due date passes
- a sent invoice that is genuinely wrong should be voided and re-issued, not edited
Why BloomBoard keeps them separate
A proposal answers “Will the client approve this work?” An invoice answers “What is now owed and what has been paid?” Keeping both tied to the same event lets your team preserve commercial history without mixing approval and payment logic.
Treat accepted proposals and sent invoices as formal history. If the commercial situation changes, use a new version or a new billing action rather than trying to rewrite the past document in place.