Accounts receivable for agencies: a weekly system for getting paid

Accounts receivable begins before the reminder

Accounts receivable, or AR, is money customers owe for invoiced goods or services supplied on credit. For an agency or consultancy, managing it means knowing what has been billed, what remains unpaid, when it is due and what must happen next. Your accountant can help determine how unbilled work, deposits and revenue recognition should be recorded; those are related questions, not interchangeable balances.

The basic sequence is familiar: agree terms, invoice, record the receivable, monitor it, collect payment and reconcile. Payoneer's guide for global service providers describes this broader process. The operational challenge for agencies is connecting it to account management and delivery. Finance cannot fix a missing milestone approval by sending a more persuasive reminder.

The workflow below is a suggested operating system for a small or growing service firm. One person may hold several roles, but each decision should still have a named owner. If you need help with a specific invoice that is already late, start with our overdue-invoice triage guide.

Capture the payment path before work starts

A signed statement of work does not always mean the client's AP system is ready to pay you. During onboarding, have the account owner confirm the procurement and invoicing path, then hand the details to finance in one place.

Client legal entity and billing address:
Tax and registration details required on invoices:
Contract / statement of work link:
Billing model: retainer / milestone / hourly / other
Currency and agreed payment terms:
Deposit or advance-payment requirement, if agreed:
Billing trigger and evidence required:
Who approves work, hours or milestones:
Purchase order reference, amount and expiry:
Supplier onboarding / portal status:
Invoice submission address or portal:
Named AP contact:
Account sponsor and escalation contact:
Client's payment-run schedule, if known:
Internal billing owner:
Who can approve credits, concessions or revised terms:
Secure payment instructions and verification process:

Confirm what the client means by 'approved.' A project manager approving a deliverable may be a different step from procurement increasing a PO or AP accepting an invoice. Note each dependency and who can unblock it. If the agreement requires a client action before billing, give the account owner responsibility for getting that action completed.

Treat any request to change bank details as a separate verification task through a trusted channel. Do not rely solely on an email thread containing new payment instructions. The onboarding record should make it easy for both teams to recognize the normal payment path.

Make the workflow fit how you sell services

Give the delivery team a clear handoff deadline that fits the billing schedule. For example, a firm billing monthly might require approved time and expense records before finance prepares the month's invoice batch. The exact day is a local decision; the useful control is that missing approval appears as an exception with an owner.

Do not put unbilled work into the overdue-invoice total simply because you wish it had been invoiced. Track billing blockers separately: work awaiting approval, missing timesheets, pending scope changes or supplier onboarding. This shows whether delayed cash is caused by late billing or late payment.

Keep one reliable record of every open invoice

Your accounting ledger should remain the financial source of truth. A task list or shared view can add collection context, but reconcile it to the ledger so it does not become a second, conflicting set of balances. Avoid tracking payments only in a founder's inbox.

• Financial fields: invoice ID, client legal entity, currency, invoice date, due date, original amount, applied payments, approved credits and open balance.
• Routing fields: AP contact, project sponsor, submission channel and invoice or portal link.
• Action fields: internal owner, reason unpaid, last meaningful contact, next action and review date.
• Exception fields: disputed amount, promised payment amount and date, expected receipt date, and any pause with its reason and review date.

For a simple invoice with no other adjustments, open balance equals invoice amount minus payments applied minus credit notes applied. A proposed credit is not an applied credit. An unmatched bank receipt is not yet proof that a particular invoice is settled. Reconcile both before updating the collection task.

Record promises separately from original due dates. If a client agrees to pay late on a new date, changing the due date casually can make the aging report look healthier without collecting cash. Formal amendments should follow your accounting policy and retain an audit trail.

Read an aging report without losing the context

For the example below, days past due is the number of calendar days between the invoice due date and the reporting date. Invoices due today or later are current. Overdue buckets are 1–30, 31–60, 61–90 and 91+ days past due. Some accounting systems use different labels or age from the invoice date, so confirm the report settings before comparing totals. The detailed aging-report guide shows how to build the snapshot and reconcile unapplied cash and credits.

These are fictional accounts, not HUNT customer results. Birch started at $9,000 and has a $3,000 payment applied, leaving $6,000. Dune started at $5,000 and has an approved $500 credit applied, leaving $4,500. The other rows have no applied payments or credits in this simplified example.

The oldest balance is not automatically the highest-priority action. Birch has the largest overdue exposure and an identifiable procurement blocker. Elm needs a delivery decision. Cedar has a future payment promise to monitor. Give these different tasks to the people who can complete them.

Run a weekly review that produces decisions

Before the meeting, finance applies known receipts and credits, refreshes aging and brings forward replies or exceptions. The account or delivery leads update their open blockers. That preparation lets the review focus on decisions instead of reconstructing the week's email history.

Review date:
Prepared by:
Ledger refreshed through:
Unmatched cash / reconciliation issues:

For each exception:
- Client and invoice:
- Open balance and currency:
- Reason / blocker:
- Decision made:
- Next action:
- Single accountable owner:
- Due date for the action:
- Client commitment, if any:
- Reminder pause and review date, if needed:

Items requiring founder or finance-lead approval:
Billing blockers to resolve before the next invoice run:
Changes to the expected-cash forecast:

In a small agency, the founder might approve commercial changes, the account manager resolve delivery questions and a bookkeeper apply cash. The important distinction is decision authority: a reminder sender should not improvise discounts, interest, payment plans or threats to suspend work.

Measure cash movement and unresolved work

Start with a few measures you can calculate consistently. Record the reporting date, currency policy and source. A rising overdue balance can reflect a billing surge as well as deteriorating collections, so read it alongside the underlying invoices and reasons.

Days sales outstanding, or DSO, can add context: a common calculation is average accounts receivable divided by net credit sales for the period, multiplied by the number of days in that period. Use comparable balances, sales and currencies, and document your method. If credit sales are zero, the formula is not meaningful. For small agencies, lumpy project billing, deposits and seasonal work can move DSO substantially even when follow-up behavior is unchanged.

Do not confuse open AR with a 13-week cash flow forecast. A due date is an obligation, not proof of receipt. In the forecast, identify whether an expected payment is supported by a client commitment, a regular payment-run pattern or only an assumption. Keep disputed and uncertain amounts visible to the person planning payroll and supplier payments.

Automate after the record and ownership are clear

A spreadsheet and accounting system can be sufficient for a small book of receivables if the data is current and ownership is clear. As volume grows, repeated balance checks, routine reminders and conversation handoffs may justify a dedicated workflow. Automation should remove repetitive work while preserving the decisions that require account context.

• Start with reviewed invoice records and a reliable way to apply payments and credit notes.
• Give any reminder workflow an explicit pause for disputes, payment investigations and human-led conversations.
• Assign who reviews replies and exceptions, including during leave or staff changes.
• Require approval for concessions, revised terms, formal recovery steps and changes to service delivery.
• Check that a new reply or payment changes the next action before another reminder goes out.

Our AI invoice follow-up guide explains how to evaluate those controls. HUNT's developing product includes persona configuration, reviewed invoice imports, invoice records with payments and credit notes, recorded conversations, and human pause or takeover controls. Live outreach and reply delivery are still in development; the scripted demo sends no messages. Early access is an opportunity to explore that workflow and share requirements, not a claim that production collection outreach is available today.

For the communication itself, use the payment-reminder email templates. Keep the ledger and decision log close at hand: the best wording still needs the correct balance, a known contact and a useful next step.