## TL;DR

A credit memo applied twice reduces the payable twice, which vendors eventually dispute or which hides in write-offs. Track memo application state explicitly: each memo links to the invoices it offsets, and the applied total can never exceed the memo amount. Reconcile open memos against vendor statements monthly.

## Error

```text
Credit memo CM-2041 applied to INV-100 ($500) and INV-101 ($500); memo was $500
```

## Steps

1. Model each credit memo with an applied-amount ledger.
   Expected: Explicit application state.
2. Block applications that would exceed the memo total.
   Expected: No double application.
3. Link memos to their source invoices.
   Expected: Traceable netting.
4. Reconcile open memos to vendor statements monthly.
   Expected: External confirmation.
5. Age unapplied memos and follow up.
   Expected: Memos do not linger.

## When to use

- Credit memo processing
- Vendor statement reconciliation
- Payable balance disputes

## When not to use

- Invoice duplicates
- Payment duplicates
- Write-off handling

## Compatibility

ERP-agnostic.

## Variant phrasings

### credit memo double applied

### duplicate credit memo application

### memo applied twice

## Root cause

Memos are applied manually or by matching routines that do not track state. Without an application ledger, the same memo can offset two invoices.

## Edge cases

- Partial applications need line-level tracking
- Memos in foreign currency need rate consistency
- Vendor disputes over memo validity pause application

## Provenance

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