Each transaction can have a receipt attached. Receipts can be uploaded from the web dashboard or captured on the mobile app, and Vergo matches them to the corresponding transaction.

This is the single most common reason a change "doesn't save": after any edit to a transaction — attaching or removing a receipt, adding a job, updating coding — you must click Apply at the bottom. If you unmatch a receipt and don't click Apply, the receipt stays attached.

⚠️ Important — Reported transactions are locked: you can only edit a transaction that hasn't synced yet. Once a transaction is in the Reported tab (synced to your ERP), you can't remove a receipt or make edits. If you need to change a Reported transaction, contact support.

First, make sure you clicked Apply, then refresh or clear your browser session and try again. If a receipt still won't go away after Unmatch + Apply, it may be a case where duplicate copies of the receipt were attached in the background — unmatching removes one while others remain. Contact support with the transaction URL and we'll clear the duplicates.

If receipts and coding vanish from transactions you'd already completed, this is usually a data issue on our end — often linked to a duplicate connected card/account (for example, a duplicate Amex connection). Contact support right away with the affected transaction URLs and we'll investigate and restore them.

Unmatch it from the wrong transaction (Unmatch Receipt, then Apply) and attach it to the correct one. If the wrong transaction is already in Reported, contact support.

Include the transaction URL(s), a screenshot, and the affected user's email so we can investigate quickly.