Split one change order into buckets, routed separately

Break a change order into named dollar buckets and send each one wherever it belongs — its own invoice, a new scheduled payment, or merged into an existing draft payment.

What it is

Free-form divisions, each with a title, description and amount, summing to the change order total. Each division carries its own routing: separate, new_schedule_payment, or merge into a specific target invoice. A four-way split can send bucket three into the schedule's third payment while the rest stand alone.

Also called: split a change order · part of the extra on this payment · divide the change order · per-division routing

See it
New Change Order — Line Items
Line Items+ Add Line
KindDescriptionSupplierQtyUnitUnit PriceTotal
Material12×12 insulated overhead doors (2)Kaufman Door Supply2ea2480.00$4,960.00×
LaborFrame openings, headers, jamb & track installUnassigned18hr68.00$1,224.00×
Credit (subtracts)Delete one 3068 walk door from base scopeUnassigned1ea640.00-$640.00×
Markup %
12
Tax %
6
Subtotal$5,544.00
Markup (12%) + Tax (6%)$1,037.84
Total$6,581.84
Schedule+3 days
The divisions builder: rows of title / description / amount with a $ or % toggle, a live 'Σ = total' badge, and a routing selector per row with one set to 'Merge into existing payment'. src/components/changeOrders/ChangeOrderEditor.tsx. The real screen, drawn from the product’s own design system. Sample data — no customer information appears here.
How it works
  1. 1Amounts are entered as dollars or percentages; the editor converts and shows a live sum-equals-total badge.
  2. 2Merge routing offers a branded picker of the project's existing schedule invoices, with ineligible targets shown disabled and the reason given.
  3. 3Divisions can be replaced freely until they are billed — the replace call refuses outright if any division is already materialised or paid.
  4. 4Every merged invoice line records both the change order and the specific division that created it, giving two-way traceability.
Why we built it

Merging a change order into a payment schedule sounds simple until the schedule is already half sent, and re-touching an invoice the customer has seen — or worse, paid — is how a bill changes after the fact. A change order is split into buckets, each aimed at one specific unsent draw, and a bucket that has already been billed is never rewritten or removed. Dropping a billed bucket would orphan its invoice and bill the customer twice the next time the split was recalculated.

The problem
  • All-or-nothing change-order billing.
  • No way to attach part of an extra to a specific upcoming payment.
  • No trace from an invoice line back to the part of the change order that produced it.
Sound familiar?
What you get
Each part of an extra is billed at the right moment.
The merged payment shows base plus change-order line, itemised — the original amount stays fully visible.
Every line traces back to its change order and its division.

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 →