A commercial drone job is not done when the gallery uploads. It is done when the invoice clears. If you are hunting a past due drone invoice while trying not to torch a good client, you need a reminder cadence—not a late-night rant and not a spreadsheet you forget until quarter-end.
This is a Pilot Ledger Field Work / invoicing post: teach-first for Part 107 shops. Soft product note only—run quotes, invoices, and reminder status on the same job at Pilot Ledger. No SkyView pitch. No marketplace “find a drone pilot” framing. No Flight Hub 2.
Why drone invoices go past due
Clients get urgency when they need the ortho, the roof set, or the progress reel. After delivery, your invoice competes with every other AP email. Common failure modes:
- 1. The invoice never reached the person who codes payables
- 2. Missing PO, job number, or W-9 parked the bill
- 3. Silent scope dispute on a line item you thought was obvious
- 4. Their monthly AP cycle and your net terms never matched
- 5. You delivered, then went quiet, so the job left their mental inbox
None of those require accusing anyone of bad character. They require a ladder with dates.
Publish the ladder before you need it
Write the reminder cadence once. Put a short version on the quote and the invoice footer. Run the same ladder for GCs, roofers, agencies, ranch managers, and municipal contacts nationwide.
Day 0 — invoice sent. Confirm the channel. Include invoice ID, job name, amount, due date, and how to pay. If deliverables release on payment per your policy, say so the same way you said it on the quote.
Day +3 — receipt check. “Confirming INV-#### for [job] reached you. Due [date]. I can resend to AP if needed.” Goal: wrong inbox and missing PO discovery—not guilt.
Due-date morning. One short note: due today; ask if remit details or a cost-center split is needed.
Day +3 past due. First past-due note. Facts only: amount, original due date, job, pay link. One question: “Is this with AP, or is something blocking payment?”
Day +7 past due. Second note. Apply only consequences you already published (scheduling hold, late-fee policy you actually use, final-package hold). Do not invent new punishment in anger.
Day +14 past due. Phone or voicemail plus email. Bring SOW and delivery timestamp. Offer a short written payment plan only if you can administer it.
Day +21–30. Formal statement. Decide collections threshold, small-claims path, or write-off. Document the decision. Endless “friendly” loops train non-payment.
Shift the day counts if your niche needs it. Do not skip having a written ladder.
Tone that collects without theater
Bad: “I’ve been more than patient and this is unacceptable.” Better: “Invoice INV-1842 for the 12-Sep roof ortho package ($1,850) was due 19 Sep and remains open. Can you confirm whether AP has it, or whether a PO is missing?”
Keep these rules:
- Lead with invoice ID, job name, amount, and dates
- Assume process failure before character failure—once
- One ask per email
- Copy the field contact and AP when you have both
- Never threaten licenses, public shaming, or made-up penalties
- Keep emotion offline; keep the paper trail on the job record
Blunt is allowed. Blunt is “this invoice is 14 days past due; new flight dates stay on hold until it clears.” Cruel is a paragraph about their integrity.
Fix payability before you escalate
Half of “past due” is “never payable.” Before day +7, verify:
- Line items match the signed quote and change orders
- Correct legal entity and remit-to
- Tax or exemption docs if required
- PO number on the invoice face
- Delivery proof (link, timestamp, recipient)
- Scope disputes opened as scope threads—not mixed into collections language
If they dispute scope, pause the past-due ladder and resolve the change order. Mixing “you owe us” with “what did we agree” in one email helps nobody close.
Soft holds that feel like ops, not revenge
Holds work when disclosed early:
- No new scheduling while the balance is past your published threshold
- Final high-res package released when the invoice clears—if that was the deal
- Rush re-flights require a clear account
Holds fail when you spring them after delivery. Put the rule on the quote. Repeat it on acceptance. Then enforcement is operations.
Nationwide shops: keep hold language consistent across states. Payment norms vary; your status board should not.
What to log so October-you is not reconstructing history
For every past due drone invoice, keep on the job:
- Send timestamp and recipients
- Each reminder date and channel
- Client replies and promise dates
- Delivery or acceptance evidence
- Final outcome (paid, plan, write-off)
If that log lives in three inboxes and a notebook, you will lose the thread. One job record with invoice status beats heroic memory—that is the soft Pilot Ledger point: quotes, invoices, and reminder status in one commercial workspace at Pilot Ledger.
Copy-paste skeletons (then sound like yourself)
Day +3 past due Subject: Invoice INV-#### past due — [Job] Body: Invoice INV-#### for [Job] ($X) was due [date] and is now 3 days past due. Please confirm it is with AP or tell me what is blocking payment (PO, coding, revision). Pay link: [link].
Day +7 Same facts, plus: Per our quote, new flight scheduling stays on hold while this balance is open. Happy to jump on a five-minute call today.
Day +14 Phone first. Email summary after: Spoke with [name]; next step is [pay-by date / docs / split]. Confirming in writing.
Short beats clever. Clever reminder poetry does not get coded in their ERP.
When clarity beats endless niceness
Niceness without a ladder is how pilots finance other people’s projects. Clarity is dates, amounts, holds you already disclosed, and a decision date. You can still like the client. You do not have to keep flying unpaid work to prove it.
If the relationship matters, offer a clean close: pay the balance, or agree a short plan with dates in writing, then resume scheduling. Ambiguous “send what you can whenever” is how past due becomes permanent.
Bottom line
A past-due drone invoice reminder system is a published cadence, clean payability, and tone that stays specific. Teach the ladder before you need it. Run it the same way every time. Protect flight-day capacity with holds you wrote upfront. Keep the paper trail on the job. Soft next step if you want that habit in one place: Pilot Ledger.