# Reversed Transactions on Bank Statements Explained - Author: AutoBankConvert (https://www.autobankconvert.com) - Published: 2026-06-08 - Updated: 2026-06-08 - Category: Transaction coding - Canonical: https://www.autobankconvert.com/blog/reversed-transactions-on-bank-statements > Reversed transactions on bank statements: why a charge appears and disappears, how to post the pair so the net is zero, and when to leave both out. Reversed transactions on bank statements are pairs: an original debit or credit and a later line that cancels it, usually because a payment failed, was entered twice or was voided by the bank. Post both lines to the same account so the pair nets to zero, or leave both out when your system allows. Never code only one half. ## Why does a reversed transaction appear on a bank statement? A reversed transaction appears on a bank statement when the bank or the other party undoes a line that already posted. The original stays on the statement, because statements record history rather than editing it, and a second line with the opposite sign cancels it. Both lines are real, and together they have no effect on the balance. Common causes: - **A payment returned unpaid.** An ACH debit that the receiving bank rejects comes back as a credit, often with words such as "RETURN" or "REVERSAL". - **A duplicate charge corrected.** A merchant that charged a card twice voids one, and the void posts as a credit. - **A bank error fixed.** A fee charged by mistake is credited back with a description such as "FEE REVERSAL". - **A deposit the bank could not complete.** A deposited item that fails comes back out as a debit. The description of the second line usually names the reason, or at least repeats a reference number from the first. Matching the two by amount and reference is the first step, before any coding. ## Posting a reversed transaction pair so it nets to zero Posting a reversed transaction pair means coding the original and the reversal to the same account, with opposite signs, so that account ends the month unchanged. The bank side matches the statement line for line, and the reconciliation includes both lines. Nothing shows up in income or expense unless only part of the amount came back. The worked example below shows three example pairs from a fictional client's checking account. The figures are illustrative. | Pair | Original line | Reversal line | Coding | Net effect | | --- | --- | --- | --- | --- | | Same-day void | 2026-08-04 OFFICE SUPPLY CO 312.40 debit | 2026-08-04 OFFICE SUPPLY CO VOID 312.40 credit | Both to office supplies | 0.00 | | Across month end | 2026-08-30 ACH PMT INSURER 980.00 debit | 2026-09-02 ACH RETURN INSURER 980.00 credit | August: prepaid insurance or a clearing account; September: the same account | 0.00 over two months | | Partial reversal | 2026-08-12 HOTEL DEPOSIT 450.00 debit | 2026-08-15 HOTEL ADJ 150.00 credit | Both to travel | 300.00 travel expense | The partial reversal is not a full reversal. Only 150.00 came back, so 300.00 is a real cost. Code both lines to the same expense, and the account carries the true amount without a separate calculation. ### Why both halves must be coded the same way Coding the original to an expense and the reversal to income is the common mistake. The account totals then show a cost and a matching income that never happened, both overstated by the same amount. Profit is right, but every report that reads sales or expenses is wrong. ## When should both lines of a reversal be left out? Both lines of a reversal can be left out only when your system lets you exclude a matched pair from the books while still reconciling the bank. Some bank feed tools let you exclude the two lines together. With converted statements, importing both and coding them alike is usually cleaner. Leaving out only one half is never acceptable. The bank reconciliation will be off by the amount of the missing line, and the error looks like a missing transaction rather than a reversal. ### Card authorizations that never posted Some statements, especially online banking printouts rather than official monthly statements, show pending card holds that later drop off. A hold that disappears without posting is not a reversed transaction. It was never a transaction, so there is nothing to code. Work from the bank's official monthly statement, which lists posted lines only. ## Reversed transactions that cross a statement month Reversed transactions that cross a statement month put the original in one month and the reversal in the next. Each month must reconcile to its own statement, so the original posts in month one and the reversal in month two. Code both to a clearing account so month one's expenses stay right. Using the insurance example from the table: the 980.00 debit on August 30 went out and came back on September 2. If it was coded to insurance expense, August would show a cost the client did not end up paying. Coding it to a clearing account, or to prepaid insurance if the payment will be retried, keeps August's expenses accurate. When the reversal posts in September, it clears the same account back to zero. A month-end check catches the stragglers: any clearing account with a balance after close should be a known item with a note. If the payment is retried in September, the retry is a new transaction coded normally. ## Reversals that look like refunds, credits or duplicate lines Reversals that look like refunds, credits or duplicate lines need a second look, because each one is coded differently. A reversal cancels a line that should not have happened. A refund returns money for something that did happen. A card reward has its own treatment, and two identical lines may be a duplicate upload. ### Refunds A refund comes days or weeks after the purchase, often for a different amount, and usually names the merchant without words like "void" or "reversal". Code it against the original expense. If the client sold something and refunded the customer, it goes against sales instead. ### Card rewards and statement credits A credit from the card issuer itself, such as cash back, has no original line to reverse. It needs its own treatment, chosen once per client. [Recording cash back rewards on business credit cards](/blog/record-cash-back-rewards) covers the options and why a consistent choice matters. ### Customer deposits returned When a customer pays a deposit and the job is cancelled, the client may send it back. That return clears a customer deposit liability, not a sale, because the deposit was never earned. The original entry and how the liability moves are covered in [recording customer deposits taken before the work is done](/blog/record-customer-deposits). ### Duplicates from the conversion, not the bank Two identical lines with no reversal between them may come from the same statement being converted twice. Check the statement period and page count before treating them as a bank event. The guide to [look-alike uploads that are not duplicates](/blog/duplicate-bank-statement-upload#look-alike-uploads-that-are-not-duplicates) shows how to tell a real repeat charge from a doubled file. AutoBankConvert checks that the opening balance plus every line equals the closing balance before a statement is marked done, so a reversal pair that was read correctly leaves the balance check intact. A statement missing one half of a pair fails that check and is flagged. [See the conversion flow](/).