Review / reference
Bank statement abbreviations: decode the label before changing a row
Use an abbreviation to understand the kind of entry, then verify the individual transaction. A familiar code does not establish the merchant, purpose or accounting category.
Separate a payment channel from a business purpose
A description may tell you how money moved without explaining what it purchased. A payment-network abbreviation, terminal reference and merchant text can appear in the same line. Keep these roles separate when reviewing an extracted description or deciding what question to ask the account owner.
For example, a fictional entry beginning “ACH” and ending with a supplier reference may identify an electronic transfer. It does not by itself prove whether the payment was for rent, inventory or a loan. The amount, reference and supporting records still matter.
Start with a small, reliable US glossary
ACH stands for Automated Clearing House, a system used for electronic transfers. ATM stands for automated teller machine. EFT means electronic funds transfer. These explain a channel or mechanism; they are not names for a single merchant or a single kind of expense.
The Office of the Comptroller of the Currency publishes a banking glossary for checking common terms. Use the issuing bank’s own help or the statement legend for its internal abbreviations. Do not treat a list assembled for another country or another institution as a definitive decoder for your statement.
Preserve the description before interpreting it
Keep the source wording, reference numbers and meaningful punctuation in the reviewed record. Put an explanatory note in your own workpaper if needed. Replacing an unfamiliar description with a guessed merchant name removes the text another reviewer may need to trace the transaction.
Imagine an extracted row that reads “AC H TRANSFER” because a line break interrupted the label. The PDF may support correcting that spacing. It would not support replacing the rest of the description with “office rent” simply because rent is usually paid near that date.
Use a repeatable lookup sequence
First inspect the source page at a readable size, including continuation lines. Next check the statement’s legend and the bank’s transaction detail. Compare the reference, signed amount and date with an authorized receipt or other record. If the meaning is still unclear, ask the bank or account owner a focused question.
A useful question is “What does this code refer to on the $86.40 debit posted June 12?” Include only the information required through the appropriate secure channel. Do not publish an unredacted statement in a public discussion to identify a code.
Keep review decisions grounded in the document
Two identical descriptions can represent two real transactions; different descriptions can refer to related stages of one payment. Avoid deleting a row or changing a sign based on the abbreviation alone. Check the surrounding balance movement and source detail, then document any unresolved ambiguity.
Fulla lets you review extracted rows beside their source pages before approval. It does not decide a transaction’s tax treatment, assign a verified business purpose or authenticate a merchant from an abbreviation. Use the sample files to inspect preserved descriptions and source references before preparing a real export.
Sources and documentation
Follow the source links for original definitions and current product requirements.
Questions about this article
Are abbreviations standardized across every bank?
No. Common payment terms exist, but institutions and processors also use their own labels. Check the actual bank’s explanation when a code is unfamiliar or ambiguous.
Should I expand every abbreviation in the exported description?
Keep the original wording available. An explanatory note can be useful, but an unsupported replacement can make a transaction harder to trace and can turn an interpretation into an apparent source fact.