What does POS mean on a bank statement?

POS stands for Point of Sale. It marks an in-person card transaction where you physically used the card by swiping, inserting the chip, or tapping, as opposed to an online or electronic transfer.

What do DES, INDN, and CO ID mean on a statement?

On many US statements these are ACH tags. DES is the company entry description (the sender's label for the payment), INDN is the individual or receiver name, and CO ID is the company identification of whoever originated the transfer.

Why are bank statement abbreviations different at every bank?

There is no enforced industry standard for description text. Each bank, and even each payee feeding data into the system, can label transactions differently, which is why the same type of transaction can appear under different codes.

What does ACH DEBIT mean on my statement?

ACH stands for Automated Clearing House, the electronic bank-to-bank network. ACH DEBIT means money was pulled electronically from your account, commonly for utility bills, insurance, loan payments, or subscriptions you authorized.

How do I find out what an unknown charge is?

Split the description into its code, name, and reference tags, then copy the exact descriptor text into a search engine inside quotation marks. Match the amount and date against receipts and subscriptions. If it still cannot be identified, dispute it with the bank.

Why is the merchant name on my statement shortened or misspelled?

Statement and processor descriptor fields have character limits, so longer business names get truncated and often capitalized. The name shown may also be the merchant's legal doing-business-as entity rather than the storefront brand you recognize.

Bank Statement Descriptions: Codes & Abbreviations

Bank statement descriptions are the short, often cryptic lines next to each transaction, and they are assembled from a few predictable parts: a code for the transaction type (like POS or ACH), a merchant or sender name that is frequently truncated, and reference tags such as DES or CO ID. There is no single industry standard, so the exact wording differs from bank to bank, but the building blocks are consistent enough that once you know them, almost any line becomes readable.

Three parts: most descriptions combine a transaction-type code, a name, and one or more reference tags.
POS vs ACH: POS marks an in-person card transaction; ACH marks an electronic bank-to-bank transfer.
Tag trio: on many statements DES, INDN, and CO ID map to the ACH company description, the receiver's name, and the company ID.
No universal standard: abbreviations vary across banks and even across payees, so always read codes in context.
Tracing works: searching the exact descriptor text in quotes usually reveals the merchant behind an unfamiliar charge.

The codes you will see most often

A handful of abbreviations account for the majority of confusing lines. These mark what kind of transaction took place, a card swipe, an electronic transfer, a fee, a credit. Learn this short list and most of your statement decodes itself.

Code	Stands for	What it means on your statement
POS	Point of Sale	An in-person card transaction where you swiped, inserted the chip, or tapped
ACH	Automated Clearing House	An electronic bank-to-bank transfer; ACH DEBIT means money was pulled from your account
DEBIT / DR	Debit	Money leaving your account
CREDIT / CR	Credit	Money coming into your account, such as a deposit, refund, or interest
FEE	Fee	A bank charge such as maintenance, ATM, or non-sufficient-funds fee
OD / NSF	Overdraft / Non-Sufficient Funds	Your balance went negative, or a payment was attempted without enough funds
ATM	Automated Teller Machine	A cash withdrawal or deposit at a machine
INT	Interest	Interest paid to you, or in some contexts interest charged
WD / W/D	Withdrawal	Funds taken out of the account
TFR / XFER	Transfer	Money moved between accounts

For a fuller walkthrough of where these codes sit within the document and how the columns relate, pair this glossary with our guide to reading a bank statement.

How an electronic-payment line is built

Electronic payments carry the most reference clutter, because the ACH network attaches identifying tags to every transfer. On many US statements those tags are labeled, and once you know the labels, an intimidating line becomes a structured record. The three you will meet most are below.

Tag	Maps to	What it tells you
DES:	Company Entry Description	The label the sender chose for the payment, such as PAYROLL or BILLPAY
INDN:	Individual / Receiver Name	The name of the person or account the payment was for
CO ID:	Company Identification	A unique identifier for the company that originated the transaction

So a payroll deposit might read as an ACH credit with DES showing PAYROLL, INDN showing your name, and CO ID showing your employer's originator number. Reading the tags in that order, what kind of payment, what it was called, who it was for, who sent it, turns the line into a sentence.

Card, check, and recurring-payment shorthand

Beyond the transaction-type codes and ACH tags, a second layer of shorthand describes how the money moved and whether it repeats. These appear inside or alongside the merchant name and tell you the channel of the payment. Recognizing them helps you separate a one-time card swipe from a standing arrangement you set up months ago.

Term	Meaning	Typical context
RECUR / RECURRING	A repeating, pre-authorized payment	Subscriptions and memberships billed on a schedule
PMT / PYMT	Payment	A bill or loan payment you sent or that was pulled
DEP	Deposit	Money added to the account, by transfer, check, or cash
CHK / CHECK	Check	A paper or electronic check clearing your account, often with a check number
DD / DIR DEP	Direct Deposit	Wages or benefits paid electronically into the account
REF / TRN / SEQ	Reference / Trace / Sequence number	An identifier you can quote to the bank when querying the line
RTN / RVSL	Return / Reversal	A payment that bounced back or a transaction that was undone

The reference, trace, and sequence numbers are the most useful of these when something goes wrong. If you ever call the bank about a specific line, quoting that identifier lets the representative locate the exact transaction immediately instead of searching by amount and date. Treat it as the line's fingerprint.

The facts that explain the chaos

There is no enforced standard. Abbreviations differ across banks and even across the payees feeding data in, which is exactly why the same kind of transaction can look different on two statements.
ACH tags are structured, not random. The DES, INDN, and CO ID fields come straight from the ACH record's defined data elements, so once labeled they are reliable across institutions that use them.
Descriptor length is capped. Names get truncated and capitalized because statement and processor fields have character limits, which is why a familiar brand can appear shortened or oddly abbreviated.

Tracing a charge you do not recognize

When a line means nothing to you, work it in a fixed order before assuming fraud. Most unfamiliar charges turn out to be a known purchase wearing an unfamiliar name. Start with the description itself.

Read every segment. Separate the code, the name, and the reference tags. The name is often a doing-business-as entity rather than the storefront brand you remember.
Search the exact text. Copy the full descriptor into a search engine inside quotation marks. This frequently surfaces the merchant, the parent company, or others asking about the same line.
Match the amount and date. Line the charge up against receipts, subscriptions, and recurring bills around that date. Free trials converting to paid plans are a common culprit.
Check who else uses the card. Family members, joint account holders, and stored cards in apps account for many surprise charges.
Quote the reference number. If the line carries a trace or sequence ID and you still cannot place it, give that number to the bank so they can pull the full transaction record.

Work the steps in that order and the outcome is usually one of three: you recognize the purchase, you find a subscription you forgot, or you confirm a charge that genuinely is not yours. The first two are not fraud and need no dispute, a forgotten subscription is canceled with the merchant, not contested with the bank. Only the third warrants a formal dispute. Spending two minutes on the trace before reaching for a dispute saves the bank's time and yours, and it keeps your dispute history clean for the cases that really count.

Many puzzling lines come from payment processors that prefix the merchant name, which is a whole pattern of its own. We break that down in how purchases appear on bank statements.

Why descriptions break when you copy them out

From parsing statements across hundreds of bank templates, the description field is the messiest to extract cleanly, and that messiness is informative. Because there is no shared standard, banks pack the type code, name, and reference tags into a single free-text field in different orders and with different delimiters, so a copy-paste from a PDF often jams an ACH credit's DES, INDN, and CO ID into one unreadable run. When we normalize these into separate columns, patterns jump out: recurring subscriptions reuse the exact same descriptor month after month, which makes them trivial to spot once the field is split. The practical takeaway is that putting your descriptions into rows and columns is the fastest way to recognize what is recurring, what is one-off, and what genuinely does not belong.

From cryptic lines to a clean ledger

The reason descriptions feel impenetrable is that they live as cramped free text inside a locked PDF. Converting your statement to Excel or CSV lets you split the type code, merchant, and reference tags into their own columns, then sort and filter to see every charge from one descriptor at once. That is how recurring subscriptions, duplicate charges, and the single line that does not belong become obvious.

The payoff compounds over time. Once your descriptions sit in columns, you can carry the same structure month to month and watch your recurring charges line up in a predictable pattern, so a new or changed descriptor stands out the moment it appears. That is far easier than re-reading a fresh wall of abbreviations every cycle. Decode the codes with the glossary above, get the data into a spreadsheet, and a column of cryptic shorthand turns into a record you can actually audit, budget against, and trust.

Decoding Bank Statement Descriptions