# Job finished to invoice sent, before the truck leaves — build checklist

Invoice at the kerb instead of on Friday, and get paid in days instead of weeks.

Roughly two weeks, plus however long it takes to get technicians closing jobs on site.

## Before you start, read this

Do NOT build this if any of the following is true of you:

- [ ] Your technicians do not close jobs on site. Without that event this fires days late anyway.
- [ ] You invoice on progress or retention terms. This assumes one job, one invoice.
- [ ] Your customers pay by purchase order against a contract. The pay link is meaningless to them.

If none of those apply, carry on.

## 1. Prove you can hear the trigger

- [ ] Your job management tool: A job status changes to Completed
      Find what your vendor actually calls this event before you write any code.
      We have not verified the name, and guessing it wastes an afternoon.
- [ ] Stripe: invoice.paid
- [ ] Log one real event end to end before building anything on top of it.

## 2. Build the steps, in this order

- [ ] 1. Job marked done
      The technician closes the job on their phone.
- [ ] 2. Check it is invoiceable
      Photos attached, parts logged, hours entered. Anything missing stops here and pings the technician.
- [ ] 3. Build the invoice
      Line items come from the job record, not retyped.
- [ ] 4. Office approves  (A PERSON DOES THIS — build the queue, not the decision)
      A person eyeballs anything above your threshold, or anything the check flagged.
- [ ] 5. Send with a pay link
      Email and text, both carrying the same link.
- [ ] 6. Payment reconciled
      The paid event closes the invoice and stops the reminders.

## 3. Keep these jobs with a person

If your build quietly takes any of these over, you have built something else:

- [ ] Approves invoices over whatever threshold you set. Automatic invoicing of a five-figure job is how you lose a customer over a typo.
- [ ] Chases the technician for missing photos — the check finds it, a person fixes it.
- [ ] Handles every dispute. The automation never argues about a bill.

## 4. Before you turn it on

- [ ] Run it in report-only mode for a week and read every message it WOULD have sent.
- [ ] Decide who gets paged when it stops firing, and prove the page works.
- [ ] Write down what "it is working" means as a number you can check next month.
- [ ] Confirm you have consent for any message this sends to a customer.

---

Generated from the recipe at https://ustechautomations.com/recipes/field-service-job-done-to-invoice-paid
by seo/scripts/v1-gen-recipe-checklists.js — do not edit this file by hand.