Agency billing mistakes and how to prevent them

Billing from memory instead of records

The break-even hourly rate worksheet starts from costs and realistic billable hours, providing a separate reference for pricing decisions.

Trigger: someone drafts a charge by remembering what the team did. Prevention: require dated work records before a draft reaches the billing reviewer. The delivery lead checks that each activity belongs to the correct client and project, with a useful task reference. If a record is missing, ask the person who did the work to reconstruct it transparently from reliable evidence rather than inventing precision.

ABH ties time entries to clients, projects and tasks. That structure helps the reviewer find the underlying work but cannot recover facts nobody recorded. Check the recording habit during the work period, not only on the last afternoon of the month. Keep a short missing-record list with an owner for each item. The complete billing process names the handoffs where this check belongs and keeps record capture separate from the decision to bill.

Invoicing unapproved time

Trigger: all logged time is treated as eligible simply because it exists. Prevention: the reviewer checks billable status, assignment and the agreed billing basis before using time on an invoice. Entries for internal learning, agency corrections or an unapproved extra may remain valuable operational records while being excluded from a client charge. Do not erase those entries just to make the draft match.

Illustrative fictional example, USD, excluding taxes: 10 hours are logged, but 2 relate to an agency correction. At an agreed $100 hourly rate, 8 eligible hours support $800, not $1,000. ABH supports single and bulk approval of time entries. Approval records an internal review, not client authorization for new scope. Use the timesheet review guide for the detailed checks. Leave unresolved entries pending a decision rather than bulk approving them to meet a billing deadline.

Vague line items

Trigger: the reviewer cannot match a proposed line to its agreement or work record. Prevention: require that match before sending, with a client-readable description and a source reference kept for questions. Check that a fixed deliverable is not presented as a different hourly commitment. The issue here is the review test, rather than a formula for writing every possible invoice description.

ABH proof-backed invoice lines can be traced to logged time, and invoices can be shared as a PDF or public link. Traceability still needs an intelligible commercial explanation. Ask a reviewer who did not deliver the work whether the line's period and purpose are clear. Remove private commentary before sharing supporting evidence. The invoice-writing guide covers the writing itself; this checklist focuses on making the evidence check a required step before release.

Missing change requests

Trigger: delivery begins an extra without an accepted cost or scope decision. Prevention: the project lead records the request, impact, proposed charge and client authorization before assigning the work. A client asking whether something is possible is not necessarily accepting a paid change. Separate the conversation about options from the agreement to buy one.

If the extra has already happened, mark it for clarification instead of adding a surprise line. Keep the original scope and the new decision together so the reviewer can distinguish included work from additions. Assign responsibility for resolving missing approval before the billing cutoff. The change-request billing guide covers that route. For a capacity agreement, the retainer scope checklist helps define exclusions early. Software time approval cannot substitute for the client's acceptance of an additional fee.

Unclear due dates and payment references

Trigger: the invoice says payment is due soon, or a receipt arrives without a usable reference. Prevention: confirm the due date, payment instructions and invoice reference at the agreement stage, then check them on the draft. Verify the correct billing entity and contact. A familiar delivery contact may not be the person who routes invoices through procurement.

ABH invoices include due dates and statuses. Those fields help organize the record but do not ensure that the recipient has understood the terms. Have the billing owner check whether a purchase reference or a different destination is required before sending. When the agency receives money externally, match its currency, amount and reference before recording the payment manually. A vague reference should prompt reconciliation, not a guess about which balance to close. Keep the clarification for anyone who reviews the account later.

Late first reminder

Trigger: an overdue invoice has no named follow-up owner. Prevention: assign the person and the next review date when the invoice is issued. Before each message, check for a confirmed receipt, a documented dispute or a promised action that is still within its agreed window. The aim is a useful next step, not repeated messages that ignore the client's reply.

Starter and Pro support invoice reminders to clients by email in ABH. Do not confuse those reminders with general automation rules sending budget notifications. A reminder needs a correct recipient and a reconciled balance to be useful. If the client identifies a specific concern, assign its resolution rather than continuing the same request unchanged. The late-invoice follow-up workflow provides the conversation sequence. Keep tests and internal practice away from real client inboxes.

No monthly review of unbilled work

Trigger: completed eligible work has neither an invoice nor a recorded reason to wait. Prevention: at month end, compare the reviewed work list with invoices already issued and the pending exception list. Categorize ready to bill, waiting on acceptance, deliberately deferred and non-billable items. Every deferred item needs a person responsible and a date for its next decision.

Compare periods and references so a missing charge does not become a duplicate charge when discovered later. Record the outcome of each exception, including why an item was excluded. Review open invoices against externally confirmed receipts before recording payments. ABH's payment ledger is append-only and exact, but the agency still performs that reconciliation. No client funds are collected through ABH. Run these seven checks as a standing review agenda; investigate the failed handoff instead of repeatedly correcting its symptoms on invoice day.