Saved payment terms

Save the schedules you actually use and apply one to a new job in a click.

What it is

Named presets, each a full list of stages. The loader migrates the old three-field shape (down / delivery / final) into the modern stage array, so presets saved before the schedule became free-form still work.

Also called: payment presets · my standard terms · reusable draw schedule

See it
Saved payment terms
Apr
May
Jun
Jul
Ronan Petsch — Hobby Shop
Framing
Delia Yoder — 40×64 Shop
Concrete
Ronan Petsch — Riding Arena
Trim
Gideon Alt — 30×40 Garage
Framing
Gideon Alt — Riding Arena
Concrete
Framing crewConcrete crewTrim crew
The preset dropdown showing saved names next to a Save as preset control. src/lib/paymentSchedule.ts. Sample data — no customer information appears here.
How it works
  1. 1Presets and the active preset id are stored under payment_presets / payment_preset_active.
  2. 2loadPaymentPresets() detects a legacy record with down/delivery/final numbers and converts it into three named stages.
  3. 3Both the estimating engine and the invoice editor read the same preset list.
Why we built it

Most builders bill the same way on every job, and rebuilding the same deposit, progress and final split each time is wasted evenings. Schedules save as named presets shared across the estimating and invoicing sides, and schedules saved under the older format are carried forward rather than dropped, so nobody has to re-enter terms they already set.

The problem
  • Re-entering the same draw structure per job.
  • Losing saved terms when the schedule model changed.
Sound familiar?
What you get
Standard terms applied in one click.
Old saved presets keep working.

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →