Knowledge · Business Operations

    Invoicing and Collections Checklist

    A practical checklist for invoicing at job completion, a weekly receivables routine, and a one-page collections cadence template you can copy into your own process.

    What should an invoicing and collections checklist cover?

    It should cover three routines: what must be true before an invoice is issued, what happens at job completion the same day, and the weekly receivables review. Together they stop unbilled work, wrong balances and invoices quietly ageing past the point of collection.

    Key takeaways

    • Invoice at completion, review receivables weekly, escalate on defined triggers.
    • Every invoice traces to an approved amount plus approved change orders.
    • Delivery is recorded, not assumed.
    • One named owner per balance over your escalation threshold.
    • Copy the template, change the numbers to yours, and use the same one every week.

    Before you issue: the seven checks

    • The amount ties to an accepted estimate, contract or approved change order.
    • All change orders on the job are approved and included.
    • Deposits and progress payments already received are applied as credits.
    • Line items describe the work in the customer's language.
    • Terms, due date and payment methods are on the document.
    • The recipient is the person who actually pays, with any reference they require.
    • The invoice is attached to the job record.

    At job completion, same day

    • Completion documented — photos, notes, sign-off where applicable.
    • Any extras approved in writing before they were performed.
    • Invoice generated from the job, not retyped.
    • Invoice delivered on the customer's usual channel and delivery recorded.
    • Any payment collected on site recorded with a receipt issued immediately.

    Weekly receivables review

    • Open the aging view and work the oldest bucket first.
    • Confirm delivery evidence before treating a balance as refusal.
    • Assign one owner by name to every balance over your threshold.
    • Clear unapplied payments and duplicates.
    • List completed jobs with no invoice and fix them that day.
    • Record every promise made and the date it was promised for.

    One-page collections cadence template

    Copy this and set your own thresholds. Day 0 (delivery): confirm receipt, correct recipient, correct reference. Day −3: reminder with amount and due date. Day 0 (due): payment due today, with payment instructions. Day +3: different channel, ask what is blocking payment. Day +10: named person calls, obtain a commitment with a date. Day +21: written notice restating agreed terms. Day +30: escalation decision — payment plan, formal demand, or the path your attorney defined.

    Two rules make the template work: never skip a step because the customer is a friend, and never invent a step because you are frustrated.

    Where URBLD fits

    In URBLD these routines map to existing surfaces: invoices generated from jobs, receipts issued at the point of payment, an aging view over open balances, and escalation as a recorded step with an owner.

    Principles reinforced

    This page rests on the following foundational ideas.

    FAQ

    Frequently Asked Questions

    Straight answers about how URBLD runs the business end-to-end.

    More in Business Operations

    The daily mechanics: workflows, checklists, scheduling and handoffs.

    Browse Business Operations
    Share this page