Invoice reminders for agencies: check the project and payment path

Match the invoice to the agreed billing stage

Start with the contract or accepted quote, not the name of the client. For a retainer, identify the exact service period and the billing arrangement you agreed. For a milestone, identify the named stage and the delivery or approval evidence relevant to that stage.

Keep extra work linked to its separate approval or quote. Do not merge an unissued draft charge into an overdue request merely because it belongs to the same client. Equally, do not introduce a new client approval requirement where your agreement does not contain one.

The Small Business Commissioner recommends clear descriptions of completed work. For an agency, the practical detail is the particular month, campaign or milestone the invoice represents. “Marketing services” alone does not show that distinction.

Build an invoice map with one row per billing item

This fictional map is Harbour Studio’s internal reference, not a customer statement or a PayerPing feature. Add the agreed due dates and current checked balances to your own invoice records.

The map keeps £250 of proposed work outside the two issued invoices. A confirmation about B2 also says nothing about the retainer’s payment. Never apply an account-wide “approved” or “disputed” label from a reply concerning only one row.

Ask a different question for each billing basis

For the retainer, identify the month: “Our checked records show £900 remaining on INV-919 for November support under R-4. Could you confirm payment status?” Include an activity summary only where useful or required by the agreed process.

For a milestone held for a reference, ask the work contact about that reference: “Does BRAND-27 cover the B2 milestone on INV-920?” Once confirmed, ask accounts whether it can process the invoice. If the milestone itself is queried, handle the specific work question before routine chasing.

For unapproved extra work, clarify scope and authority through your normal project process. The next action is a commercial decision, not a payment-reminder template. Keep any resulting invoice distinct from the retainer and milestone records.

Fictional example: two invoices with different blockers

In the map, INV-919 was issued on 1 November and due on 15 November. INV-920 was issued on 15 November and is due on 30 November. At the 24 November review, both remain unpaid, but only the £900 retainer is overdue.

The owner asks Mira about the overdue retainer and separately obtains the branding reference from Chris before the milestone’s due date. The issued balance is £2,100; the £250 draft is excluded. One email demanding £2,350 overdue would get both the status and the amount wrong.

If Chris disputes B2, the owner handles that invoice’s query while checking INV-919 independently. A conversation about the branding deliverable cannot establish whether the support retainer was paid.

Keep the map under one owner’s control

Let project colleagues supply the relevant handover or scope records through the agency’s existing workflow. One owner checks the latest payment position, decides which invoice to contact about and records the result beside its row.

PayerPing’s intended service model remains single-owner: payments and replies go directly to the business, and manual invoice resolutions need owner updates. This sample map does not imply shared product access, team approval chains or project management features.