What it means
Contacts change when employees leave, companies reorganise or customers move their finance work to a shared mailbox. An old invoice address can delay approval and payment, while a wrong new address can disclose private transaction data or enable invoice fraud, so the update needs more than copying a new email address from an unsigned message.
Capture who requested the change, account identifier, new contact details, effective date and what communications the contact may receive. Check against an authorised account administrator or a known channel, especially if the request comes from an unfamiliar address, and do not let a billing-contact change silently update bank details, delivery destinations or ownership.
Tell the account team which unpaid invoices should be resent and whether historical statements may be shared, since a new employee might need only future bills. A changed billing recipient may affect historic invoices as well as future ones, so decide whether the new contact may see old statements, disputed balances and purchase orders or only bills issued after a specified date, and record the scope so a distribution-list update does not become an unplanned archive share.
Confirm the first invoice reaches the new mailbox without sending unnecessary personal or commercial records. Update the customer master record with an audit trail, remove bounced or obsolete addresses from distribution lists, and consider a second reviewer for high-value or sensitive accounts.
A secure update log can record the requester, evidence used to verify the request, reviewer, old and new fields and time of change, while avoiding unnecessary personal identification. If an invoice already went to the wrong place, handle the disclosure under the relevant privacy and contractual process rather than quietly deleting the address.
A contact change is not proof the payer changed. Keep the legal customer, purchase order, credit terms and bank-payment instructions unchanged unless separate authorised processes approve those changes, and test one new invoice and reconcile any pending one to prevent a paid bill from being chased merely because a mailbox changed.
If the old contact was an external accountant, check whether access should end. When the account has several legal entities, verify which one the contact represents, because for a multinational account billing may involve multiple tax registrations and entities, and a person authorised for one entity may not be the recipient for another.
Confirm the invoice's legal entity and service period before bulk re-sending documents. For owners, a small contact maintenance task can materially affect cash collection and privacy, so it should be quick, scoped and traceable.
In practice
Real-world examples.
Example
A customer administrator asks that future invoices go to a shared finance inbox; the vendor confirms through the existing account channel before changing it. Only after that confirmation does support update the record and note the evidence in the audit log.
Example
An invoice bounces after an employee leaves, and the collections team requests an authorised replacement rather than guessing an address. The customer's administrator supplies a new contact through the portal, and the overdue invoice is resent that day.
Example
A purported new billing contact asks for historical statements; the team checks access rights before sharing them. The request came from an unfamiliar address, so support replies to the known account owner first and releases only the documents that owner approves.
Formula
Calculation
Billing-contact update lead time = Timestamp verified change took effect - Timestamp complete authorised request was received
Worked example. An invented vendor receives a complete verified request Monday at noon and updates the customer record Tuesday at noon.
- Lead time = 24 hours.
- It checks the next invoice cycle to ensure the new contact receives the bill.
This is an operational measure, not a legal service standard.Case study
Seen in the real world.
This illustrative and entirely fictional example follows Northshore Software, an invented subscription vendor. A customer's invoices still went to a former employee. Support changed the address after a message from an unknown account, and the replacement address received a statement containing historical charges. Northshore contained the disclosure and confirmed the proper finance contact through its existing account administrator.
It then separated future-invoice recipients from historical-statement access and added a verification field to contact changes. Its billing system retained the prior address and update evidence for audit. Later customer reorganisations were handled faster because support knew which change it was allowed to make and how to check the requester.
Watch out
Common mistakes.
- Treating a new email address in an inbound message as proof that the requester controls the account.
- Sharing historical statements automatically when only future invoices were requested.
- Changing bank details or contract ownership as part of a billing contact edit.
Questions
People also ask.
Can a customer use a shared billing inbox?
Usually, if an authorised account owner chooses it and the inbox fits the agreed process.
Should old invoices be resent?
Check the request and permission; future delivery does not automatically authorise historical disclosure.
Does a contact change alter payment terms?
No. Treat terms and bank details as separate, verified changes.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%