A customer system outage needs a specific payment update

The customer says its system is down

Imagine an overdue customer explains that a finance-system outage has delayed payments. Your team accepts the explanation and moves the expected receipt to next week without asking what is actually affected.

The outage may be genuine, but the cash assumption still needs a basis. Find out whether the issue concerns invoice access, approval, payment preparation or release.

Ask a narrow operational question

Request confirmation of the stage your invoice reached before the outage and whether any information must be resubmitted. Identify the person responsible for providing the next update.

Avoid demanding technical details the accounts contact cannot supply. The useful answer concerns your account and the remaining payment step, not an explanation of the customer's entire IT incident.

Check any proposed alternative carefully

The customer may have an approved contingency process. Ask its authorised accounts contact to explain the arrangement and the information required. Retain the response with the account record.

Do not bypass your own security checks or send sensitive information to an unverified address simply because an alternative process is described as urgent. Confirm unfamiliar instructions through an established contact route.

Keep the payment terms and status visible

An explanation of disruption is not itself a clear agreement about revised payment terms. Record what the customer has said and any actual proposal separately from your internal forecast assumption.

business.gov.au's unpaid-payment guidance recommends checking the agreement and following up the account. Use that approach to keep the discussion focused while recognising that the practical blockage may differ from an amount dispute.

Source: business.gov.au: What to do when you haven't been paid

Use a conditional forecast date

If the customer cannot confirm when processing will resume, label the expected receipt accordingly and test a later date. Do not turn a general hope that systems will recover into a guaranteed payment.

Set a sensible follow-up point tied to the next promised update. If the outage ends but your invoice remains stalled, ask what separate action is now outstanding.

Turn the explanation into a clear next step

For the next outage-related delay, record the affected stage, responsible contact and expected update. Confirm whether the invoice needs any action from your team and preserve the evidence already supplied.

This helps distinguish a temporary operational interruption from an account that still needs approval or another resolution after the system returns. The business can then plan from information rather than an undefined delay.