The first one, at yes
The card is charged as they sign, and the invoice is issued against that charge.
BillInvoices that never drift
Invoices that never drift
from what the client signed.
Every invoice comes out of the accepted proposal: the first stage at signature, later ones when you send them, retainers on the saved card.
Start free trialAcceptance writes the first invoice. After that, stages go out when you generate them, the retainer renews itself, and an issued invoice stops moving.
Milestones, invoiced by you
Split the total at send, then generate a stage’s invoice when the work lands. Stripe emails it.
Renews on the saved card
A Stripe subscription bills the card from acceptance every cycle. Nothing to re-key each month.
Issued means finished
Line items, tax and your business details are captured at issue. Re-price the proposal later, the invoice holds.
Every invoice traces to a signature. The numbers are the ones the client approved, and the billing page ages whatever is still owed, by currency.
Schedule
Set the split once, at send
Stages have to add up to the proposal total, and the sum is checked again at acceptance.
Aging
Sorted by how late it is
Open, overdue and paid, bucketed 1-30 through 90+ days, and never two currencies in one total.
Copy
A record, not a live page
The client’s invoice renders from its own snapshot, so it reads the same in three years.
Stages, durations and deliverables are already agreed, so billing reads from the accepted document instead of a fresh form.
Stages have to add up to the proposal total, and the schedule bills itself on the dates you chose.
Each invoice renders from its own snapshot, so it reads the same in three years as it did the day it went out.
FAQ
Invoicing and records, answered.
On acceptance. Stripe charges the first stage as the client signs, and the invoice is issued against that charge. A single-payment proposal charges in full instead.