Security
Safe AI invoicing: keep bank details out of AI
Learn how voice-note invoices can use checked bank details and human approval without giving AI control of where customers send money.
Ben Harvie6 min read

Safe AI invoicing means turning a voice note into a draft without letting AI choose where your customer sends money. Here, AI means software that turns spoken job notes into written invoice details. I'd keep bank details outside that software, insert them from a locked verified record and require approval before sending.
Why invoice bank details need attention now
In its 28 September 2026 warning, City of London Police said invoice fraud accounted for 813 reports, or 22% of the payment-diversion reports in its analysis. Payment diversion means tricking someone into sending money to the wrong account. The warning also highlighted AI-assisted impersonation, where criminals use software to pretend to be someone else.
Those figures describe reports to police. They don't mean that 22% of invoices are fraudulent, or that AI caused all those cases. They do give a reason to examine who can change payment instructions.
Police Scotland explains that invoice scams can involve criminals intercepting supplier emails. A familiar email conversation shouldn't be your only check when someone asks you to pay a different account.
What a voice note should be allowed to do
For a joiner in Dalkeith, a voice note after a door repair could capture the work completed and materials used while the details are fresh. The useful part is avoiding another evening typing job descriptions. It isn't handing over control of the invoice.
I'd limit the recording to the job reference, completed work and relevant materials. Bank details and unrelated customer information don't belong in it. If something is unclear, the draft should flag the gap rather than fill it with a guess.
Agreed prices and any tax should come from checked records and your invoicing software, not guesses from speech. I take the same approach to turning job notes into a draft quote: help with the wording, then check it against what was agreed.
Keep payment details outside the AI
The AI should receive only what it needs to describe the completed job. That rules out feeding it whole historic invoices containing bank details just because copying them is convenient. The payment section should be added separately by the invoicing software.
I'd use a locked record containing payment details you've already checked. Locked means the AI cannot edit it, and an authorised person can change it only through a separate checked process. Telling the AI not to change bank details is not the same as removing its ability to do so.
Bank details will still appear on the finished invoice because your customer needs them. The point isn't to make them secret. It's to control which details reach the invoice and who can replace them.
I'd also block payment instructions in generated job descriptions. A protected bank-details box is little help if the text above it tells the customer to send money somewhere else. Spoken instructions must never override the payment record.
How to check AI-generated invoices before sending
Approval should mean checking the finished invoice, including the payment section, rather than a preview of the job description. I'd make these checks part of the review:
- The customer and their email address match the selected job.
- The description covers work actually completed.
- Charges and tax match the checked job records.
- The payment section matches the verified bank record.
- No extra payment instructions appear elsewhere in the invoice or covering message.
The approval should apply to that exact version. If anything changes afterwards, the invoice goes back for approval. The system should hold an incomplete or rejected draft rather than send it because a timer has run out.
This needs to be manageable on the device you actually use. If you're checking invoices on your phone between jobs, the payment section must be easy to inspect, not hidden behind a tiny preview.
Bank-detail changes need their own process
A request to change payment details is a separate task, not another edit to an invoice draft. It shouldn't be accepted because it appears in a voice note, an email reply or a message that sounds like the owner.
For your own account, confirm the replacement details against records you obtain directly from your bank. For a supplier's account, check through contact details you already trust. Don't rely on a new phone number supplied in the same message as the change request.
A familiar-sounding voice isn't enough on its own, given the police warning about impersonation. I'd record what changed, who checked it and how it was verified. If another authorised person is available, they can review the change too.
For a sole trader, that still means stepping outside the incoming request and checking independently. New details should stay out of outgoing invoices until the separate check is complete. AI should have no authority to approve that change.
When you should not buy voice-note invoicing
Completely hands-off invoicing is the wrong promise. If the requirement is that spoken notes become invoices and leave without anyone looking, I wouldn't recommend this setup. Removing typing is useful; removing responsibility is not.
If your existing invoices are accurate, go out promptly and use checked payment details, leaving the process alone is fine. A saved invoice template might solve the problem without AI. There's no reason to add another tool just because dictation looks clever in a demonstration.
Before buying anything, measure how long drafting takes and how much time corrections consume. Include the approval time when testing a replacement. A system that produces quick drafts but needs constant repairs may leave you with more work, not less.
Test the process before using real customer details
I'd start with made-up job details and test what happens when a recording is unclear, names the wrong customer or includes an instruction to change the bank account. The test should cover the whole process, including the outgoing invoice and email.
I'd check that the AI cannot alter the payment record, that extra payment instructions are blocked and that an unapproved invoice cannot be sent. I'd also test that editing an approved invoice cancels its approval. A good-looking draft is not evidence that those controls work.
Keep a record of what was approved and sent so a disputed invoice can be checked later. These controls don't make fraud impossible, but they give you something firmer than hoping the software follows instructions.
Frequently asked
What is invoice payment diversion fraud? Invoice payment diversion fraud tricks someone into paying a criminal's account instead of the intended business. The invoice or payment instructions direct the money to the wrong place.
Can criminals intercept supplier emails? Yes. Police Scotland says invoice scams can involve criminals intercepting supplier emails. An existing email conversation should not be treated as proof that changed bank details are genuine.
How common is invoice fraud? Invoice fraud accounted for 22% of payment-diversion reports in the City of London Police analysis published on 28 September 2026. That figure describes those reports, not all invoices sent by businesses.
Can AI be used to impersonate a business contact? Yes. The City of London Police warning of 28 September 2026 highlighted AI-assisted impersonation in payment diversion. That means criminals can use software to help them pretend to be someone else.
Get invoice admin under control without handing over payments
Leaving a broken invoice process in place can mean delayed payments, disputes and evenings spent chasing mistakes. That takes time away from returning enquiries and quoting jobs. Customers waiting for a reply can book a competitor who deals with their request sooner.
I map how your completed jobs become invoices, identify what can safely come from speech and keep payment details in a separate checked record. I build the approval step around how you work and test the routes that must stay blocked before anything goes to a customer.
That's the kind of controlled admin I can build through AI for your business. My work is affordable on purpose, so useful tools aren't out of reach for small businesses in Edinburgh and the Lothians. Every job starts with a free consultation and a written quote before work begins.
To talk through your invoicing, book the free consultation (opens in a new tab).


