Quick answer
Quick answer
Collections is operations plus finance: clean payloads first, then tiered outreach with dispute codes so the same failure is not fought twice.
About this template
Replace ad-hoc nagging with a cadence. Customize tone by customer tier.
Always log disputes as structured notes.
Preview
Excerpt of the downloadable layout—tables and checklists match the file you can install into your ops stack.
Tier A (0–7 days)
| Channel | Script summary |
|---|---|
| Friendly reminder + pay link + references |
Tier B (8–30 days)
| Channel | Script summary |
|---|---|
| Call | Confirm receipt; ask for AP contact; offer statement |
Download
equipify-invoice-aging-follow-up-scripts.md
Structured Markdown you can version in Git, copy into policy portals, or convert to PDF.
FAQ
- Should technicians collect payments?
- Usually no—keep payment flows with finance unless your model explicitly supports it.
Run templates as live workflows
Equipify connects assets, work orders, scheduling, and billing so checklists become auditable execution—not orphaned PDFs. Start a trial to map your first PM route and dispatch triage board.
Prefer a walkthrough? Contact us with your vertical and fleet size—we will map these templates to your Equipify workspace.