## TL;DR

Card networks post the foreign transaction fee as a separate line from the purchase, so the fee arrives as an orphan expense with no parent charge. Find the base charge (same date, same merchant, amount before the fee), link the fee to it in the expense tool or merge the two lines, and resubmit. Auditors flag orphan fees because a fee without a purchase looks like an error.

## Error

```text
foreign transaction fee expensed without the base charge flagged
```

## Steps

1. Open the flagged fee expense and note its date, amount, and card. Expected: you have the fee's details isolated.
2. Find the base charge: same card, same or adjacent date, amount consistent with the fee percentage. Expected: the purchase the fee belongs to is identified.
3. In the expense tool, link the fee to the base expense or merge the lines, adding a note that it is the FX fee. Expected: the fee is visibly attached to its purchase.
4. Ensure the base charge itself is expensed with its receipt. Expected: both the purchase and the fee are documented.
5. Resubmit. Expected: the orphan-fee flag clears.

## When to use

- A foreign transaction fee expense is flagged without its base charge.
- Card feeds import the fee as a standalone line.
- Auditors question a fee with no corresponding purchase.

## When not to use

- The fee amount itself is disputed with the bank.
- The base charge is also missing (find the charge first).
- The fee is a domestic fee miscategorized as foreign.

## Tool compatibility

Applies across expense tools importing card feeds (Expensify, Concur, Ramp, Brex; current 2026 releases).

### Variant phrasings

### "orphan fee" flagged in an expense audit

Same condition in audit wording. Link the fee to its purchase.

### fx fee without a matching purchase

The base charge may be on a different report or not yet imported. Locate it first.

### card feed split the fee from the charge

Networks post them separately. Merge or link in the expense tool.

## Why it happens

Card networks authorize the purchase and the foreign transaction fee as separate postings, often settling on different days. Expense tools import both as independent expenses, and the fee lands without context. Auditors flag it because an unexplained fee is indistinguishable from a data error. Linking restores the economic reality: one purchase, one fee.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_qBCC0-oS-z1frQHmHe5SEw
