Review bank details by comparing the final invoice with the authorised source instruction, then checking every repeated occurrence for consistency. Confirm account identity, destination, currency suitability and payment reference through their appropriate processes. A careful transcription review is necessary, but it is not independent proof of account ownership.
The payment-information workflow separates those responsibilities. The current creator displays the values entered and makes no banking verification request. Its field checks cannot establish that the destination is genuine, current or authorised for this transaction.
Start from a confirmed instruction
Use the account holder’s approved record or other authorised source. Check that it applies to this invoice’s arrangement and currency. Do not treat an old draft or familiar account number as current evidence without the required review.
Unexpected changes should be confirmed through an established contact route. A replacement message cannot independently verify itself, and the contact details inside it may be part of the same unverified instruction. Follow your business’s appropriate authorisation process.
Retain that confirmation separately from the customer-facing invoice. The review record explains why the instruction was accepted; the invoice communicates the necessary payment facts. A professional design, matching logo or complete account block does not supply the missing authorisation evidence.
Compare identifiers accurately
Check the account name and every required identifier against the confirmed source. Review the full string, not only its opening characters. A transposed character can be hard to notice when the rest of the value is familiar.
Keep account and institution identifiers in their intended roles. An IBAN, BIC and payment reference are not interchangeable. If the source supplies several values, retain their labels and confirm how the intended payment route uses them.
The creator does not run checksum, directory or ownership checks. Even if another process performs a structural check, keep its scope explicit. Correct-looking syntax does not establish that the account belongs to the intended payee or that payment should be made there.
Review the entire document for old details
Search payment details and notes for earlier account strings or references. Replacing the primary instruction does not rewrite duplicated prose. A customer may receive two conflicting destinations unless the complete document is reviewed.
Remove unnecessary repetition rather than maintaining several copies by habit. Where repetition is useful, compare it with the confirmed primary value. Do not rely on the recipient to infer that the instruction nearest the total is more authoritative.
Check seller and payee roles if another party receives payment. Do not combine the payee’s account with an incorrect seller identity merely to make the names appear to match. The arrangement needs appropriate review and may require typed fields beyond the creator’s current model.
Check currency, amount and reference
Compare the selected invoice currency with the accepted commercial agreement and authorised account instructions. Changing the selector does not convert amounts or select a different account. A familiar numeric total can conceal an unintended relabelling.
Read the payment reference with the invoice identifier and agreed reconciliation process. Ensure a previous invoice’s reference has not survived in notes. The tool does not check historical numbering or match incoming receipts to determine which value is appropriate.
Use the foreign-currency payment review when the route or destination differs from ordinary domestic instructions. Confirm any additional provider requirements externally rather than inferring them from a sample or account format.
Inspect the intended output
Read the preview and browser print view if you intend printable output. Verify that long identifiers remain legible and associated with their labels. Do not insert arbitrary spaces merely to force alignment if that makes the value ambiguous when copied.
If application JSON is part of the handoff, compare its supported payment values with the reviewed record. A visual page does not establish that every exported field has been checked. Line-item CSV is not a complete payment instruction document.
After any correction, create a fresh export. Earlier files retain the old instruction even after the workspace changes. Keep the intended final version clear and use the appropriate process if a superseded version has already been shared.
Record what was actually checked
A useful review note distinguishes authorisation, transcription, consistency and final-format validation. State the exact file or draft version reviewed. Do not summarise those separate tasks as “bank details verified” if no ownership or banking check occurred.
You can revise the supported payment fields locally before exporting. The creator does not transfer funds, confirm receipt, authenticate the account holder or guarantee that a customer can pay successfully. Those capabilities require their own implemented process.
Retain the authorised source and final invoice version under your normal business handling. The practical result is a clear, consistent instruction whose provenance and remaining limits are visible, rather than confidence based only on a complete-looking document.
A practical final check
For a long instruction, read critical identifiers in short groups against the source, then make a second pass over the labels and currency. These separate checks can catch both mistyped characters and a correctly copied value placed beside the wrong label.
Keep the comparison record.