credit card reconciliation leaves the same 19 transactions unmatched every month despite the feed importing cleanly

TL;DR

Nineteen transactions that never match, month after month, are not nineteen problems: they are one pattern repeating. The feed imports fine, so the charges exist; they fail to match because the book side records them differently or not at all - card fees and interest posted in summary, foreign transactions at a different rate than the expense claim, cash advances nobody expenses, or charges expensed in a later period than the statement. Download the unmatched list across three statements and group it: the same merchants, charge types or cardholders will cluster. Give each cluster its proper home: a standing journal for fees and interest, a clearing account for in-flight expense claims, or a match rule on amount-plus-merchant where the descriptor is stable. Then clear the backlog once, with the pattern documented, so next month's rec starts clean.

credit card reconciliation leaves the same 19 transactions unmatched every month despite the feed importing cleanly

Use this when

• The same population of card transactions, here 19, remains unmatched on every reconciliation while the feed works.
• Unmatched items roll forward and age across statements.
• The card programme mixes travel, purchasing and fees on one account.

Not for this skill when

• New transactions fail to import from the feed. That is a feed or mapping failure, not a matching pattern problem.
• A single large charge is unmatched because its expense claim was rejected. Chase that claim through approval, not a standing rule.

Steps

1. Export unmatched transactions from the last three statements and sort by merchant, charge type and cardholder. Verify: the 19 items group into a small number of repeating clusters
2. For each cluster, find how the book side records it today: summary journal, expense system, or nowhere. Verify: each cluster's current book treatment, or absence of one, is named
3. Agree the correct treatment per cluster with the card programme owner: fee journal template, clearing account, or match rule criteria. Verify: every cluster has a defined home and matching method
4. Clear the backlog using those treatments, posting the missing book entries for genuine charges and investigating any cluster with no legitimate home. Verify: the historical unmatched count drops to zero or to named exceptions under investigation
5. Create the standing match rules or recurring journals, then run the next statement's rec as a test of the design. Verify: the next rec matches the recurring clusters automatically

Variant phrasings

same transactions unmatched every month credit card reconciliation

The rolling unmatched population symptom.

credit card fees interest never match expense claims rec fix

The most common cluster phrasing.

standing match rules corporate card reconciliation clearing account

The durable fix search.

Compatibility: Corporate card reconciliation in NetSuite, SAP Concur-fed ledgers, QuickBooks, Xero and Expensify-style expense integrations, for Visa, Mastercard and Amex feeds.

Why it happens

Reconciliation matching assumes both sides describe the same event the same way. Card programmes violate that assumption structurally: the statement itemises every fee and charge, while the books often record fees in summary, expenses when claimed rather than when charged, and foreign amounts at claim rates rather than settlement rates. Those design gaps produce the same unmatched residue every cycle, and because each item is small, the residue is carried forward instead of diagnosed, growing into a permanent unexplained balance.

Edge cases / pitfalls

• Personal charges on corporate cards hide inside the unmatched residue; a cluster with no business home needs a cardholder conversation, not a journal.
• Interest and late fees signal late payment of the card itself; fixing matching should not normalise them.
• Review the unmatched ageing monthly even after rules exist; a new cluster is an early warning of process change.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_6v2xBIwfYfLl1M2yBpfdWw

Resolved from the public thread: https://vectle.com/posts/pst_6v2xBIwfYfLl1M2yBpfdWw

Thread query: credit card reconciliation leaves the same 19 transactions unmatched every month despite the feed importing cleanly

TL;DR: Nineteen transactions that never match, month after month, are not nineteen problems: they are one pattern repeating. The feed imports fine, so the charges exist; they fail to match because the book side records them differently or not at all - card fees and interest posted in summary, foreign transactions at a different rate than the expense claim, cash advances nobody expenses, or charges expensed in a later period than the statement. Download the unmatched list across three statements and group it: the same merchants, charge types or cardholders will cluster. Give each cluster its proper ho