How are receipts handled when a charge is refunded?

On Ramp, refunds are recorded as related transactions, and the original receipt stays linked to both the charge and the refund, so finance teams do not need to re-upload or re-match receipts.

Common refund scenarios

• Partial refunds. If a vendor issues a partial refund, the original receipt stays attached to the initial charge, and the refund is shown as a related transaction.
• Full refunds. When a transaction is fully refunded, the receipt remains tied to the original charge so auditors can see proof of the original purchase.
• Multiple refunds. If multiple partial refunds are issued, they are each tied back to the same original charge and receipt.
• Refunds after close. If a refund posts in a later period, the receipt still stays with the original transaction, and the refund is tracked as a new entry for that period.

Example: A $200 conference registration is charged, and a receipt is uploaded. The vendor later refunds $100 for a canceled workshop. The $200 charge remains documented with the receipt, and the $100 refund is displayed as a related transaction in Ramp.

Handling receipts with refunds

• The receipt should always remain tied to the initial charge.
• When a refund posts, the system should link it back to the original transaction automatically.
• Refund records should include a reference to the receipt for context, even if no new receipt is provided.
• The audit log should show the relationship between the charge, the refund, and the supporting documentation.

Example: A $150 software subscription is charged, and a receipt is uploaded. The vendor later issues a $50 refund. The $150 charge remains documented with the receipt, and the $50 refund is shown as a related transaction. Auditors see both the charge and the refund tied to the same documentation.

How receipts and refunds are managed on Ramp

• Automatic linkage: receipts uploaded to the original charge remain attached if a refund posts later.
• Refund visibility: the refund appears as a separate transaction but is clearly tied to the original charge in Ramp’s dashboard.
• ERP sync: when syncing to NetSuite, QuickBooks, or another ERP, the original receipt is still visible and linked to both the charge and the refund.
• Audit trail: Ramp preserves the relationship between the charge, refund, and receipt, ensuring full visibility during audits.

Best practices

• Always attach receipts to the original charge, even if you expect a partial or full refund.
• Verify that refunds are tied to the same vendor and transaction before closing the books.
• Review refund logs during month-end close to confirm they remain linked to receipts in both Ramp and your ERP.
• Keep documentation for both sides of the transaction in case auditors need to see the entire flow.