data.day
payments / security / finops / banking

I Am Not Manually Typing That IBAN: Why Payment Data Still Gets Re-Typed

Typing an IBAN by hand is not work; it is a security risk. One typo sends your cash to a stranger. Here is why we ban manual entry.

Klara Budget Klara Budget

The most dangerous moment in finance is not the tax audit. It is the moment a human being reads a number from a PDF and attempts to type it into a bank portal.

We call this “The Swivel Chair Interface.” You look left. You look right. You type. You hope.

This is insanity. I recently audited a firm where the Office Manager spent three hours every Friday manually paying 40 invoices. That is 40 chances to commit a typo. One wrong digit in an IBAN usually triggers a checksum error. But two wrong digits? That might be a valid account number. Someone else’s account number.

If you send €10,000 to a stranger because you mistyped a 6 for a 9, that money is gone. The bank will not refund your incompetence.

The Audit Risk: The “Fat Finger” and The Fraud

Manual entry is the playground of fraud.

If your process allows a human to type the destination account, you have no control. A dishonest employee can pay a legitimate vendor name but type in their own IBAN. An honest employee can simply be tired.

When the auditors ask, “How do you ensure the money goes to the right vendor?” and your answer is “Sarah is very careful,” you have failed. “Careful” is not a control. “Careful” is a mood. Moods change.

[TO EDITOR: Create a flow diagram. Top path (Red): “PDF Invoice” -> “Human Eye” -> “Human Brain” -> “Human Finger” -> “Bank Portal” -> “Error/Fraud”. Bottom path (Green): “PDF Invoice” -> “OCR” -> “Accounting System” -> “SEPA XML File” -> “Bank Portal” -> “Success”.]

The Control: The Batch Payment Protocol

We stop typing. We start uploading.

Modern banking relies on Structured Data. In Europe, we use the SEPA XML standard. In the US, ACH files.

The Workflow:

  1. Ingest: The invoice enters your accounting software (via OCR). The software reads the IBAN once. You verify it once.
  2. The Master Record: That IBAN is saved to the Vendor Contact. It is never typed again.
  3. The Batch: On Friday, you select all 40 approved bills in your software. You click “Create Payment File.”
  4. The Upload: You log into the bank. You upload one file. The bank populates 40 payments instantly.
  5. The Sign-Off: You authorize the total amount.

This is Data Logistics. The IBAN flows from the vendor’s invoice to the bank’s server without a human finger ever touching a keyboard.

Conclusion

Typing is for poets. Finance is for data moving.

If your “Accounts Payable” process involves a keyboard, you are doing it wrong. Generate the file. Upload the file. Meten is weten. The file does not make typos.

FAQs

How do I pay without typing?

Batch payment files (SEPA XML). Your accounting software generates a file. You upload the file to the bank. 100 invoices paid, zero typing.

Is this only for big corporations?

No. If you pay more than 5 invoices a week, manual entry is a waste of life. Most modern accounting tools support batch files.

What if the invoice has the wrong IBAN?

Then the error is on the vendor, not you. You pay what is on the document. If you re-type it, the error is yours.