Bank Statement Transaction Codes: ACH, POS, ATM, DR, and CR Explained

Read the whole transaction row

ACH, POS, and ATM identify a payment network or transaction channel. DR and CR can identify direction under the institution's account convention. None of those codes identifies the business purpose, expense category, or owner of the activity by itself.

Current Regulation E guidance prescribes no single terminology for transaction types. A bank may rely on a debit or credit column plus a merchant name or terminal location. Read the code as one field in the row, then test the row against the statement's account type and balance movement.

Use the six-part row interpretation worksheet

Copy the source row without editing it. Separate the information into six evidence fields, leaving any absent field blank. This preserves the printed description while giving you a repeatable way to decide whether the amount represents money in or money out.

Interpret ACH credit and ACH debit rows

Nacha describes an ACH credit as an instruction that places funds into the receiving account, with payroll Direct Deposit as a common example. An ACH debit instructs the receiving institution to withdraw funds, such as an authorized utility payment. The originator name and entry description tell you who sent the instruction; they do not assign a bookkeeping category.

Extra ACH fragments can include PPD for a prearranged consumer entry, WEB for an internet- or mobile-authorized debit, a company ID, or another reference. Keep those fragments attached to the transaction. They can distinguish two entries that share a date and amount.

Interpret POS rows without guessing the merchant category

POS marks a point-of-sale transaction under common US statement usage. The rest of the description may show a merchant or processor name, location, store number, date fragment, and card suffix. Regulation E permits several terms for a POS transfer, and the transaction documentation does not have to distinguish cash back from a purchase.

A POS debit on a deposit account points to money out. A POS reversal or refund can point back into the account. Keep the original charge and later reversal as separate rows when both posted; removing one as a duplicate breaks the transaction history.

Interpret ATM rows and fees

ATM identifies a machine transaction, while the next word should identify a withdrawal, deposit, or transfer. A terminal code, operator name, street, city, or branch can follow. Match those details with your receipt when the description is unfamiliar.

An ATM fee can appear as its own row or within a disclosed transfer amount, depending on the operator and statement presentation. Do not create a second fee from the receipt if the statement amount already includes it. Use the printed rows and balance change to determine whether the statement separated the fee.

Resolve DR and CR before assigning a sign

On checking and savings statements, CR often adds funds and DR often removes them. Credit-card statements describe an amount owed: purchases and fees increase that balance, while payments and refunds reduce it. A spreadsheet built for cash-flow analysis can still show purchases as negative and payments as positive.

StatementMint uses that portable money-flow convention. Purchases, withdrawals, and fees receive negative signed Amount values. Deposits, payments, refunds, and credits receive positive values. The export does not turn a statement code into a journal-entry debit or credit.

Test the sign against a running balance

A printed running balance provides a local arithmetic test. For a deposit account using money-in-positive signed amounts, prior balance plus signed Amount should equal the new balance. A checking purchase of $64.27 changes $1,840.35 to $1,776.08: $1,840.35 + (-$64.27) = $1,776.08.

A credit-card amount owed moves in the opposite direction from the portable signed Amount. Subtract the signed Amount from the prior amount owed. A $72.40 purchase changes $980.12 to $1,052.52: $980.12 - (-$72.40) = $1,052.52. A $500.00 payment then changes it to $552.52: $1,052.52 - $500.00 = $552.52.

Catch common transaction-code sign errors

Check the statement section and one known transaction in each direction before converting a full table. A payroll deposit and a card purchase make useful controls for checking. A card purchase and payment make useful controls for a credit-card statement.

• Do not assume an unsigned printed amount is positive cash flow.
• Do not treat DR and CR as accounting journal instructions.
• Do not assign a sign from ACH, POS, or ATM without the action text.
• Do not merge a charge with its posted reversal or refund.
• Do not count an ATM fee twice when the transfer amount includes it.
• Do not give both sides of an account transfer the same sign.
• Do not discard a reference that links a return or reversal to its source row.
• Do not accept a net total when individual row signs fail the running-balance test.

Preserve the complete description in Excel and CSV

A short export such as ACH DEBIT or POS hides the originator, merchant, entry class, location, and reference that make the row useful. Keep continuation lines joined to the correct transaction, even when the final Description looks long.

StatementMint exports Date, the complete extracted Description, and signed Amount for entitled pages. Compare those rows with the issued PDF before relying on them. Add merchant normalization or bookkeeping categories in separate columns so the source description remains available for matching and dispute research.

Escalate an unexplained transaction through the bank

Search receipts and invoices by amount and date, compare transfers across your own accounts, and ask other authorized account holders. If the code, entity text, and balance movement still do not identify the item, contact the institution through the number printed on the statement or its authenticated website.

Report suspected unauthorized activity without waiting for a category decision. The CFPB says notice deadlines can affect federal protections for some electronic transfers and describes a 60-day statement-notice period in several unauthorized-transfer situations. The institution can research references and terminal details that a public code list cannot resolve.

Frequently asked questions