A fake invoice scam can look like an ordinary supplier bill, a recurring subscription, or a routine request to update bank details. This checklist shows how to verify invoices and payment changes without relying on the email alone, with practical steps for individuals, finance staff, developers, and small teams.
Overview
Invoice fraud is a payment scam in which someone sends a false bill, alters legitimate billing information, duplicates a real invoice, or impersonates a vendor, manager, or executive. The request may arrive by email, through an accounting platform, in a shared document, or in a message that appears to continue an existing conversation.
The central rule is simple: treat payment instructions as untrusted until they are verified through a separate channel. An authentic-looking sender address, familiar logo, correct invoice number, or existing email thread is not enough. Email accounts and documents can be compromised, and criminals can copy details from genuine invoices.
Do not pay while a request is being verified, especially when it includes a new bank account, a different payment platform, an unexpected fee, or pressure to act immediately. If the bill is legitimate, a short delay for verification is usually easier to resolve than recovering a misdirected payment.
Quick stop-and-check rule
- Pause the payment and avoid replying to the suspicious message.
- Compare the invoice with your purchase order, contract, account history, or service records.
- Contact the vendor or requester using a trusted phone number, portal, or previously saved contact.
- Confirm any change to bank details with an authorized person and a second approver.
- Keep the invoice, message headers, payment details, and verification notes for your records.
Checklist by scenario
1. An unfamiliar invoice arrives
- Check whether your organization or household actually ordered the product or service.
- Look for a matching contract, purchase order, delivery record, subscription, or prior bill.
- Inspect the legal business name, physical address, tax or account reference, invoice number, dates, line items, and payment terms.
- Search your own records rather than clicking links in the invoice.
- Ask the supposed vendor to confirm the invoice through an independently located contact method.
2. A vendor requests new bank details
- Assume the change requires verification, even if the email appears to come from a familiar contact.
- Do not use the phone number, reply address, QR code, or link supplied in the change request until it has been checked.
- Call a known number from an earlier contract, prior invoice, official vendor portal, or established contact list.
- Ask the vendor to confirm both the old and new details, the effective date, and the reason for the change.
- Use a documented callback and approval process before changing a saved payee.
3. A duplicate invoice appears
- Compare invoice number, amount, date, purchase order, line items, and bank details with the original.
- Check whether the invoice has already been approved, scheduled, or paid.
- Look for small changes such as an extra digit, altered spacing, a new attachment, or a different remittance address.
- Ask the vendor to confirm whether the second invoice is a correction, replacement, or duplicate.
4. A manager or executive demands urgent payment
- Do not treat urgency, secrecy, or seniority as authorization.
- Use the organization’s normal approval route, including a second approver where required.
- Verify the request in person, by a known phone number, or through an established internal channel.
- Never bypass controls because the requester says they are traveling, in a meeting, or unable to speak.
5. A recurring subscription bill changes unexpectedly
- Sign in through a bookmarked or manually entered official website rather than an email link.
- Review the account’s billing history, renewal date, plan, payment method, and user access.
- Check whether a new service, add-on, cancellation fee, or price adjustment was actually authorized.
- Contact the provider through its verified support route if the account and invoice do not match.
What to double-check
Use the table below as a quick comparison, but remember that a convincing document can contain accurate information copied from a genuine bill.
| Invoice detail | What may be genuine | What deserves verification |
|---|---|---|
| Sender | Matches a known vendor contact or portal notification | Lookalike domain, unexpected reply-to address, or newly created contact |
| Bank information | Matches previously approved vendor records | New account, country, beneficiary, payment platform, or remittance address |
| Amount | Matches contract, quote, order, or normal recurring charge | Round amount, unexplained adjustment, overdue-fee pressure, or unusual currency |
| Invoice number | Fits the vendor’s normal sequence and account history | Duplicate number, missing reference, altered formatting, or unexplained replacement |
| Timing | Arrives near the agreed billing or delivery date | Urgent deadline, weekend request, or demand to bypass the normal cycle |
| Attachment or link | Available through the established vendor portal or expected workflow | Unexpected file, password request, macro-enabled document, QR code, or login prompt |
Verification scripts
Use neutral wording that does not disclose sensitive payment information to an unverified contact:
“We received an invoice or payment-detail change and are verifying it through our standard process. Please confirm the invoice number, amount, account reference, and effective date through our established contact channel.”
“For security, we do not approve bank-detail changes by email alone. We will call the contact on file before updating payment information.”
For a small team, record who requested the payment, who verified the details, which independent channel was used, and who approved the final release. For technical teams, consider restricting payee changes, requiring multi-person approval, and alerting on unusual beneficiary or payment-platform changes.
Common mistakes
- Trusting a familiar conversation: A real thread may have been compromised. Start a new conversation using a trusted address or phone number.
- Relying on the display name: Inspect the complete sender and reply-to addresses, but do not treat an address match as proof of legitimacy.
- Calling the number on the invoice: Verify contact details independently before discussing payment or account changes.
- Paying a small test amount: A test payment can still go to the wrong account and may signal that the process is working.
- Opening attachments before checking context: Review unexpected files cautiously and use approved security controls or a secure portal where available.
- Deleting evidence: Preserve the original message, full headers where available, invoice, payment instructions, and approval history.
- Assuming a failed payment means no loss: Check whether the transaction is pending, duplicated, or routed through an intermediary before taking further action.
If money has already been sent, contact the financial institution or payment provider immediately through an official channel and ask whether the transaction can be stopped or recalled. Notify the affected vendor and your internal security or finance contact. If credentials were entered, change them from a trusted device and review account activity. For broader identity or account exposure, use the data breach response checklist and preserve evidence for any relevant reporting process.
When to revisit
Return to this checklist whenever an unfamiliar invoice arrives, a vendor changes payment instructions, a recurring bill looks different, or a manager asks you to bypass normal controls. It is especially useful before seasonal planning cycles, fiscal year-end, staff changes, onboarding a new supplier, or switching accounting and payment tools.
Teams should revisit the workflow whenever bank accounts, approval roles, finance software, vendor portals, payment providers, or remote-work procedures change. Remove outdated contacts from vendor records, confirm who can create or edit payees, test the callback process, and make sure backup approvers understand the same controls.
Before approving the next payment, ask four final questions: Do we expect this bill? Do the details match our records? Did we verify changes independently? Has the required person approved it? If any answer is uncertain, pause and verify rather than letting urgency decide.