What it means
ASCII defines 128 codes covering the letters A to Z in both cases, the digits 0 to 9, common punctuation and a set of invisible control characters such as line endings. What it does not include matters more in practice: no accented letters, no curly quotation marks and no currency symbol other than the dollar sign.
Finance teams run into it because banking and payroll systems are often old and strict. A bank file specification will state that the file must be plain ASCII with fixed field widths, and a single accented character in a supplier name can cause the whole payment batch to be rejected.
The same applies to data moving between systems. When a ledger exports a comma-separated file for a reporting tool, the receiving system has to interpret the bytes using the same character set, or names, addresses and reference numbers arrive scrambled.
Plain ASCII uses one byte per character, which makes file sizes easy to predict and is why fixed-width layouts were built that way in the first place. Modern systems normally use UTF-8, which represents the ASCII characters identically and adds everything else, so a pure ASCII file is already a valid UTF-8 file.
The practical control is to validate before you transmit. Agree the character set in the file specification, strip or convert anything outside the permitted range, and run a test file through the bank or the receiving system before the first live run.
In practice
Real-world examples.
Example
An accounts payable team submits a payment run of 400 invoices and the bank rejects the file. The cause is one supplier name containing an accented letter, which is outside the permitted ASCII range, and stripping the accent lets the file through.
Example
A finance analyst exports the trial balance to a comma-separated file for a reporting tool, and account descriptions arrive with odd symbols because the export used one character set and the import assumed another. Re-exporting as plain ASCII fixes every row.
Example
A company migrating from an old accounting system to a new one agrees a fixed-width ASCII layout for the opening balances file. The specification states the exact character positions for account code, description and amount, so both sides can test against the same definition.
Formula
Calculation
File size in bytes = Number of records x Characters per record, at one byte per character in plain ASCII
A payroll bureau submits a bank file containing 50,000 payment records. Each record is a fixed-width line of 120 characters plus a 2-character line ending, so 122 characters per record. The file size is 50,000 x 122 = 6,100,000 bytes, which is about 6.1 MB using 1,000,000 bytes per megabyte. If the bank caps each upload at 5 MB, the bureau must split the run, and two files of 25,000 records each come to 25,000 x 122 = 3,050,000 bytes, comfortably inside the limit.Case study
Seen in the real world.
Pellmont Logistics is an illustrative, fictional freight company that paid 1,200 suppliers each month through a bank file generated by its ledger. After a supplier database tidy-up, somebody pasted names in from a word processing document, bringing curly quotation marks and accented characters with them.
The next payment run failed validation at the bank with a single unhelpful error line. The team spent two days finding the offending records manually, and 90 suppliers were paid late, which cost one early settlement discount and a great deal of goodwill.
The illustrative fix was a short validation step added before every run: the file is scanned for any character outside the plain ASCII range, offending records are listed with the supplier code, and the run cannot be submitted until the list is empty. The problem has not recurred in the story because the check sits before the bank, not after it.
Watch out
Common mistakes.
- Pasting supplier or employee names from a word processor into a system that feeds a bank file, bringing curly quotes and accented characters with them.
- Assuming every system reads a comma-separated file the same way, when the character set and the delimiter both have to be agreed.
- Testing a new bank file only with clean sample data, so the first live run is the first time real names and addresses are validated.
Questions
People also ask.
What does ASCII stand for?
American Standard Code for Information Interchange, a scheme that assigns a number to each basic text character so computers can exchange plain text.
Why do bank files still require plain ASCII?
Because many banking and payroll platforms were built around fixed-width single-byte records and reject anything outside that range.
Is UTF-8 a replacement for ASCII?
UTF-8 is a superset, so every plain ASCII file is already valid UTF-8, but a UTF-8 file containing accented characters is not valid plain ASCII.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%Related