Check the billing identity first

Confirm the legal entity, billing name, address, and tax identifier against an approved source. The source might be a signed contract, a completed tax form, or a verified customer portal record. Do not rely on the name that appears in an email signature. A small identity error can send an invoice to the wrong entity or create a tax problem that takes weeks to correct.

Check whether the account is part of a parent or subsidiary structure that changes the billing relationship. A purchase order may be issued by one entity while the invoice must go to another. Record the relationship and the evidence in the account note. The billing team should not have to rediscover it when the next order arrives.

Verify terms and currency

Read the payment terms, discount rules, and currency from the contract rather than from the last invoice. A copied invoice can carry an outdated discount or a term that was renegotiated. Confirm the effective date and the approver for any change. If the terms are ambiguous, route the question before the cycle starts.

Check the rounding and tax settings that the billing system will apply. A currency mismatch or a missing tax rule can produce an invoice that looks correct in one system and wrong in another. Test one sample invoice from the account before the batch runs. The test is cheaper than a credit memo and a customer conversation.

Confirm the delivery and contact fields

Verify the invoice delivery address, the accounts payable contact, and the preferred channel. A portal-only customer should not receive a PDF by email unless the contract allows it. A contact who has left the company should be replaced through the approved change process, not by editing the record from memory. Keep the evidence for the change.

Check for role-based contacts rather than personal names. An accounts payable mailbox is more durable than one employee's address. If the customer requires a named contact, record a backup role. The goal is to reduce the chance that a routine invoice bounces because one person changed jobs.

Explore the related specialist service to define scope, ownership, and evidence.

Look for duplicate customer records

Search for the same tax identifier, billing address, and remittance reference across the customer master. Duplicates often appear after an acquisition, a portal migration, or a sales representative creating a new record instead of using an existing one. Two records can split payments and make the aging report look worse than the underlying relationship. Record the search fields and the result so the duplicate check can be repeated next cycle.

Do not merge records without a documented review. A merge can move open invoices, contacts, and payment history, and it is difficult to reverse. Identify the surviving record, list the items to move, and get approval from the account owner. Keep a before-and-after reference so a later reviewer can follow the change.

Test change requests against evidence

Every change to bank details, billing identity, or tax status should follow a verified path. Use a known contact and a callback to a number on file, not a number supplied in the request. Record who verified the change and when. Bank-detail fraud often starts with a convincing email that asks for a quiet update before the next payment.

Keep the old value and the new value in the audit history. Do not overwrite a field without a trace. If the change is urgent, complete the verification first and document the urgency separately. A fast change that cannot be explained later is a risk to the customer and to the finance team.

IRS Publication 583, Starting a Business and Keeping Records provides public guidance that can inform a documented review.

Freeze a clean copy for billing

Once the audit is complete, freeze the approved fields used by the billing run. Any later change should go through the same review rather than being edited during the run. A frozen copy gives the billing team a stable reference and makes exceptions easier to spot. It also prevents a last-minute edit from affecting invoices already in progress.

Compare the frozen copy with the live record before the batch starts. If they differ, resolve the difference before proceeding. Record the comparison time and the reviewer. The freeze is not a permanent lock; it is a control that separates approved data from changes that still need evidence.

Schedule the next audit window

Set the next review date based on the account's risk and activity. A high-volume account with frequent changes may need a quarterly check, while a stable account may need only an annual one. Put the date in the account record so it does not depend on someone remembering. The audit should happen before the cycle, not after a failure.

Review the exceptions found in the last audit to see whether the same fields fail again. A repeated failure is a process problem, not a data-entry accident. Fix the intake form, the verification step, or the field ownership. The purpose of the audit is a cleaner billing cycle, not a longer checklist.

Continue with a related workflow guide.

Common questions answered

What should a pre-billing customer audit check first?

Legal identity, billing name, address, and tax identifier against an approved source.

How should duplicate customer records be handled?

Identify the surviving record, list the items to move, and get account-owner approval before merging.

Why freeze the customer record before billing?

To separate approved data from unverified edits and give the billing run a stable reference.

Trace a partial customer short-pay to the deduction codeReconcile an unapplied cash suspense balance at week endAudit a customer credit limit override before order release

Define one reviewable receivables workflow.

Bring the queue, owner, source records, and exceptions you need to make visible.

Book a free consultation