Follow the transaction through states
Record the authorization time, pending description, pending amount, available-credit effect, posting date, final description, and final amount. The same purchase can look different at each stage. Restaurants can add a tip, fuel stations can place an estimate, hotels can hold deposits, and merchants can submit a final amount later.
Do not add a pending and posted row together when they represent one event. Keep a stable review identifier and link the states. If a pending row disappears, note whether it posted, reversed, expired, or remains unresolved rather than assuming the merchant never submitted it.
Follow one event through every observed state. A hotel can request a 300.00 authorization, increase the hold during the stay, post a final 224.60 charge, and release the unused portion later. Store authorization time, pending amount, preliminary descriptor, available-credit effect, posted date, final amount, and final descriptor under one review identifier. Do not add the authorization and posted charge together as completed spending. If the pending item disappears, record whether it posted, reversed, expired, or remains unresolved.
Transaction state tracker
Track one event across authorization and settlement so temporary holds do not become duplicate spending or disappear from review.
Capture the authorization
Record timestamp, preliminary descriptor, pending amount, cardholder, and available-credit effect without treating it as final spending.
Match the posted result
Link the posting date, final descriptor, final amount, and statement cycle to the original authorization using receipt and merchant context.
Resolve extra rows
Classify each additional row as a second charge, adjustment, reversal, refund, split settlement, or open exception based on evidence.
Close with proof
Keep the final statement row, receipt, refund or cancellation confirmation, and any issuer case reference needed to explain the outcome.
Handle duplicate-looking activity carefully
One pending entry beside one matching posted entry often represents a transition, but two posted entries can represent two charges. Compare amount, merchant, time, reference, cardholder, and status. Do not dismiss a second posted transaction merely because a pending version also appears.
A split shipment, adjusted restaurant charge, repeated attempt, offline terminal, or merchant correction can create several related rows. Preserve the receipt and issuer activity view. Contact the merchant or issuer through an official channel when the final posted set cannot be reconciled.
Treat two posted entries differently from one pending and one posted entry. Compare status, amount, merchant, time, reference, cardholder, and any reversal. Split shipments, adjusted tips, repeated attempts, offline terminals, and merchant corrections can produce several related rows, but two posted transactions can also be two real charges. Preserve receipts and the issuer activity view. Do not dismiss a second posted amount merely because an earlier pending version looked similar or because the merchant name is familiar.
Respect the statement cutoff
A pending purchase at the billing-cycle close can correctly be absent from that statement and post in the next cycle. Conversely, an earlier transaction can post near the close and appear on the statement with a date different from the purchase date. Use the issuer's posting date for statement inclusion unless the statement says otherwise.
When comparing a receipt, live account, and issued statement, retain all relevant dates and statuses. A statement is not incomplete merely because it excludes an authorization that had not posted by the cutoff. A live activity screen is not a replacement for the closed statement record.
Treat refunds and reversals as new states
A cancelled authorization can disappear or show a reversal, while a refund usually posts as a separate credit after the original transaction. Match the credit to the source purchase and expected amount. Processing time and description can differ from the original event.
If an expected hold release or refund remains unresolved, preserve the merchant confirmation, expected timing, original charge, account screenshots, and contact history. Escalate through the issuer's official process when appropriate rather than editing the statement to reflect an expected credit that has not posted.