Pending or posted? Why your app and statement don't match

A hold reserves money; a posted purchase records the final charge

A pending card transaction has been authorized but hasn't finished processing. It becomes posted once the bank or card issuer processes it, as described in Capital One's explanation, dated February 3, 2026. Posted doesn't mean you've confirmed the purchase is correct. It describes the processing status, not the outcome of a dispute.

The amount can change between those stages. Capital One's debit-card help page gives three examples: a restaurant adding the tip, a pay-at-the-pump authorization, and a hotel or rental-car company estimating incidentals. That's why the final receipt is the amount to compare with the posted charge, rather than the first notification on your phone.

The balance labels matter too. For a bank account, a hold can reduce the available balance before the purchase posts. For a credit card, Capital One says pending purchases reduce available credit without yet increasing the account balance. Those are different measures. Chase also cautions that the way pending charges appear in balances varies by issuer, so don't apply one app's labels to every bank.

One fictional meal, not two purchases

Suppose a fictional checking account starts with $1,000.00, with no other transactions, fees or holds. A debit-card restaurant authorization is $120.00. The final receipt includes an $18.00 tip, so the posted purchase is $138.00. All amounts below are USD. This is a simplified illustration, not a captured bank screen or a promised posting schedule.

While the hold is present, the available balance in this example is 1,000.00 - 120.00 = 880.00. After posting, the account balance is 1,000.00 - 138.00 = 862.00. The $18.00 difference is the tip, not a second unexplained purchase. March 30 to April 1 is two calendar days, crossing the assumed March 31 statement cut-off. That's not a two-business-day service promise.

There's no separate $120.00 refund when the hold is released, because the $120.00 never became a posted debit in this example. Recording both a $120.00 expense and a $138.00 expense would produce a false $258.00 purchase total. An invented $120.00 credit would hide that mistake rather than preserve what the statement says.

But if the bank actually shows both $120.00 and $138.00 as posted debits, you're looking at a different, unresolved case. They total $258.00 and leave $742.00 under the same starting assumptions. Keep both source rows and ask the merchant and issuer to investigate, because the arithmetic can't establish that one is merely a hold or that either should be deleted.

The purchase date and posting date answer different questions

The purchase date describes when you bought something. The posting date describes when the processed transaction was recorded to the account. There can be a gap: Capital One's debit-card guidance says the transaction moves from pending to posted when it receives the final purchase from the merchant. Chase describes its own nightly posting process, including exceptions where a transaction was not shown as pending first. An app notification is not a complete posting history.

A statement is a period record, not today's live balance. Chase's statement guide describes the opening and closing balances and completed transactions for that period, noting that pending transactions may be absent. For credit cards, Capital One's balance explanation, dated July 7, 2026, says new activity after the billing cycle ends does not change that statement balance.

In the fictional timeline, the March statement has no posted restaurant purchase and closes at $1,000.00. The $138.00 belongs in the following period's posted activity, giving $862.00 if nothing else happens. That doesn't contradict the March 30 receipt: the dates describe different stages. Keep both dates in your review copy when the bank provides them, and check which date its export filter uses. Rewriting the posting date to fit a preferred month would lose that distinction.

Check whether the CSV includes pending entries

The bank's own transaction download is the place to start, but its columns matter. Dates, descriptions and amounts are the useful core. Look at the file for status, separate debit and credit fields, reference numbers or balances rather than assuming they're present. For example, U.S. Bank's download instructions document CSV and a selected date range. The page does not specify whether pending entries are included or promise a status column. Its metadata is marked modified March 6, 2024; no editorial date is displayed in the body.

A posted-transaction export can therefore have fewer rows than the live activity screen without losing a completed purchase. But CSV doesn't mean posted-only. Compare a recent pending entry with the file and check the export description to find out what was included. If status is missing and the bank's help doesn't explain the selection, confirm it with the bank or use the completed statement rows as your reference. A downloaded row isn't necessarily posted.

For reconciliation, you need posted rows, so use a posted-only export if the bank offers one. Otherwise, preserve the untouched download and make a working copy that excludes confirmed pending entries from the statement total, with a separate note of what you excluded. Keep every posted movement for the period, including fees, credits and adjustments. Selecting only purchases you recognize would leave the statement comparison incomplete.

Here is the fictional restaurant's posted row as a review CSV, not a bank's actual export layout or an accounting-app import template. It contains one transaction; the pending authorization belongs in the timeline, not in this posted-activity file.

Transaction date,Posted date,Description,Status,Amount,Currency
2026-03-30,2026-04-01,Fictional restaurant including tip,Posted,-138.00,USD

Here, the negative amount means money leaving this checking account. A credit-card export needs its own sign-convention check; don't carry this assumption across. When you standardize fields, keep the bank's original descriptions and dates alongside them so you can still compare with the source.

Reconcile to the statement, not the available balance

A posted-activity check compares like with like: the statement's opening balance, its posted movements and its closing balance. Mixing in a live hold changes the basis of the calculation. In the example, using $880.00 as the March closing balance would create a $120.00 difference even though no restaurant debit has posted.

Once you've chosen the correct rows and sign convention, the statement balance checker can do the arithmetic. For the fictional April period, opening $1,000.00 plus the single -$138.00 movement equals closing $862.00. Even when that total matches, you still need to compare each row with its source: the total doesn't prove that the bank charged correctly, that your books match, or that the document is authentic.

Your ledger may already record the meal on March 30. If so, keep that record visible as an outstanding item until it matches the posted purchase. Leaving the pending bank row out of a statement CSV doesn't mean pretending the purchase never happened. A household spending report across bank and card accounts has a separate double-counting problem: the card purchase and the payment that pays the card bill. The guide to counting purchases without counting card payments twice handles that separate problem.

A disappearing pending row is not proof of a refund

A canceled or voided pending transaction can disappear without ever posting. Capital One's debit-card help says the available balance is restored in that case and the transaction is not included in the transaction list. That is a release of reserved funds, not evidence of a separately posted refund credit.

The word reversal doesn't settle this either. Ask whether it refers to a pending authorization or an already-posted purchase, and keep any actual posted correction or refund exactly as the bank records it. A changed available balance isn't a reason to create an extra credit. Nor should you assume that a disappearing authorization settles a complaint about a posted charge. If a merchant has promised a refund, the refund-matching checklist can help you organize the evidence while following your issuer's instructions.

A missing pending row doesn't guarantee that nothing will be collected, either. Chase's posting guidance says an authorized transaction that isn't displayed as pending may still post. So if a hold or charge is unresolved, ask the issuer rather than treating a particular number of days as a universal expiry deadline.

Keep the evidence, and use the right support route

When you recognize a purchase but the amount looks wrong, compare the receipt, the pending entry and the posted detail, then contact the merchant for an explanation or correction. Note when you contacted them and what they said, because Chase's dispute page asks for that information if you open a dispute later. You still need to check the issuer's reporting instructions and deadlines; a merchant conversation doesn't replace them.

There's no safe blanket rule to wait until every charge posts. Chase says a credit-card charge must post before a dispute can be opened, but it permits a pending debit-card dispute by phone. It separately directs immediate contact for suspected unauthorized use. Capital One's credit-card help also says not to wait for posting when a charge was unauthorized. Those differences are why you need the guidance for your issuer and account type.

If the name is unfamiliar, the unfamiliar statement description guide helps you compare the details without treating a search result as proof of identity. Keep your original statement, receipt and dated status notes so you have the evidence to compare. Two similar rows are a reason to investigate, not permission for a duplicate finder to delete one.

What we checked

We opened the linked issuer pages on October 17, 2026. The Chase pages and Capital One help-center pages showed no editorial update dates; the two Capital One explainers and U.S. Bank metadata are dated inline. We checked the fictional balances with Python Decimal, parsed the sample CSV and checked the timeline with calendar-date arithmetic. We did not test a live card authorization, bank download, dispute process or spreadsheet import. The example shows how to compare records, not how long your transaction will take or what your issuer will decide.