Applying Credit Memos
A posted credit memo is a promise: the customer has $1,200 of value with you. Applying it is how that promise meets a specific invoice — NovaTech's credit lands on their March invoice, the invoice's balance drops by $1,200, and both documents' paper trails say exactly what happened. Here's how, and how the system keeps it honest.
Access you'll need. Applying credit memos requires the Accounts Receivable v2 permission set (AR clerks & managers) or Accounting Admin v2 (system administrators). The Accounting Controller v2, Accounts Payable v2, and Read Only v2 sets can view credit memos and their applications but not apply them.
Applying a credit
Open the posted Credit Memo and choose Apply Credit Memo
(In the record actions — check the ▼ dropdown.) The apply screen lists the customer's posted invoices with open balances, with an amount box per row — the same pattern as applying a cash receipt.
Allocate the credit
Enter how much of the credit goes to which invoice — all of it to one, or spread across several. You can't allocate more than the memo's Remaining Credit, and no invoice can be driven below zero: "Applied Amount … exceeds available credit" / "…exceeds the Invoice balance due" are hard stops.
Apply — and check the result anywhere
Each allocation becomes a credit application record. The invoice's Credit Applied rises and its balance due falls; the memo's Applied to Invoices rises and Remaining Credit falls. Both records link to the application on their Applications tab — auditors can walk the chain in either direction.
The NovaTech application, in numbers
Meridian's $1,200 credit (MCM001001) meeting NovaTech's $9,800 March invoice (MSI001021) looks like this on both sides:
| Before applying | After applying $1,200 | |
|---|---|---|
| Invoice MSI001021 — Balance Due | $9,800.00 | $8,600.00 |
| Invoice MSI001021 — Credit Applied | $0.00 | $1,200.00 |
| Memo MCM001001 — Applied to Invoices | $0.00 | $1,200.00 |
| Memo MCM001001 — Remaining Credit | $1,200.00 | $0.00 — FULLY UTILIZED |
NovaTech's statement now tells the whole story on two lines: an invoice for $9,800 and a credit of $1,200 against it, leaving $8,600 to pay. That's the professional version of "we fixed the bill."
What an application record holds
Each allocation is saved as its own small record — worth knowing when you audit or import:
| Field | What it is |
|---|---|
| Credit Memo Invoice | The memo giving the credit. |
| Sales Invoice | The invoice receiving it. |
| Applied Amount (required) | How much of the credit this allocation moves. |
| Application Date (required) | When the allocation was made — for the record trail. |
Notice what's missing: unlike a cash receipt application, there is no Accounting Period field — because a credit application posts nothing to the ledger, it has no period to land in. The memo's posting date already decided which period the accounting belongs to.
Letting it apply itself
- Post-and-apply from the credit screen: using Save & Post when creating the memo triggers an automatic application, Original Invoice first.
- Auto Apply Memo flag: ticking it on a posted memo applies the credit oldest-invoice-first (an Application Priority number on an invoice jumps the queue), same entity and customer only.
- Product-matched allocation: ticking Match Lines on Apply restricts the credit to invoices containing the same products as the memo's lines — useful when a specific service was over-billed across months.
- Scheduled batch: administrators can schedule a sweep that auto-applies every posted memo with remaining credit — see Auto-Apply Batches.
The auto-apply order is worth knowing precisely, because it's how the system decides where a big credit lands: invoices with an Application Priority number go first (lowest number wins), then the rest oldest-invoice-first by invoice date. If the memo carries an Original Invoice link, that invoice is settled before anything else. Only posted invoices of the same customer and entity with an open balance are candidates — and ticking Dimension Match further restricts the credit to invoices in the memo's own cost-center slice. The scheduled sweep (the Credit Memo Auto-Apply Batch card in REDA Settings) simply finds every posted memo with unapplied credit and runs this same logic on each.
The guardrails
| Rule | Why |
|---|---|
| Same customer on memo and invoice | Credit belongs to who it was issued to |
| Same entity (cross-entity application refused) | Each company's books settle their own paper; group settlement flows through cash — see Cross-Entity AR Settlement |
| Both documents Posted | Draft paper has no balances to move |
| Target is an Invoice or Receipt type | Credit can't be applied to another credit |
| Original Invoice lock | While the memo links to a specific invoice, it applies only there — "Clear the Original Invoice field on the Credit Memo to apply to other invoices." |
| Same ledger; matching dimensions where enforced | Allocation stays consistent with how your books are segmented |
The exact messages, and what to do
The guardrails above surface as these messages — on the apply screen, and identically for imports and integrations:
| The message | What to do |
|---|---|
| "Credit Memo must be in Posted status to apply credit." | Post the memo first — drafts hold no credit. |
| "Target Invoice must be in Posted status to receive credit." | Post the invoice — draft invoices have no balance to offset. |
| "Credit can only be applied to Invoice or Receipt type documents." | You picked another credit memo as the target — credit offsets charges, not other credits. |
| "Credit Memo and Invoice must have the same Customer." | NovaTech's credit can never settle a Brightline bill — no exceptions. |
| "Credit Memo and Invoice must belong to the same Entity. Cross-entity credit memo application is not supported." | Memos never cross company lines. If a group settlement is needed, it flows through cash receipts — see Cross-Entity AR Settlement. |
| "This Credit Memo is linked to a specific invoice (Original Invoice). Credit can only be applied to that invoice. Clear the Original Invoice field on the Credit Memo to apply to other invoices." | The commonest surprise — clear the lock on the memo if the credit should be free. |
| "Applied Amount ({0}) exceeds available credit on the Credit Memo ({1})." | You can't allocate more than Remaining Credit — lower the amount. |
| "Applied Amount ({0}) exceeds the Invoice balance due ({1})." | An invoice can't be driven below zero — apply the balance, keep the rest for later. |
Common mistakes to avoid
| Mistake | Why it hurts | Do this instead |
|---|---|---|
| Hunting for the application's ledger entries | There are none — the accounting happened when the memo posted; you'll conclude something is broken when it isn't | Audit the memo's posting for the ledger side; audit applications for which invoice absorbed the credit |
| Applying a correction memo to a different invoice "because it's older" | The customer reconciles their March credit against a January bill — statements stop matching their records | Respect the Original Invoice link for corrections; use free credits (no link) for oldest-first work |
| Recording the offset as a journal entry instead of an application | The ledger doubles the reduction the memo already made — AR goes wrong by the memo amount | Always use the application screen; it moves balances without touching the ledger twice |
| Auto-applying a memo meant for a disputed invoice | Oldest-first sends the credit to the wrong bill, and the dispute stays open | Keep Auto Apply Memo unticked and allocate by hand — or set the invoice's Application Priority deliberately |
| Splitting hairs to zero — refusing to leave Remaining Credit | Forcing the last cents onto an invoice that doesn't owe them triggers the balance-due guard | Leave the remainder as Remaining Credit for the next invoice, or refund it |
Changing your mind
Delete the credit application (from either document's Applications list) and the allocation reverses: the invoice's balance due returns, the memo's Remaining Credit returns. Because applications carry no ledger entries of their own, there's nothing else to clean up.
Where to go next
- Credit Memo Refund — when there's nothing left to apply it to.
- Understanding Credit Memos — the accounting that already happened.
- Applying Receipts to Invoices — the cash twin of this screen.
Frequently asked questions
Open the memo: the Credit Memo Summary shows Applied to Invoices / Refunded / Remaining Credit at a glance, and the Applications tab (Credit Applications) lists each target invoice with amount and date. From an invoice, the same tab answers the reverse question.
Check the guardrails in order — most often the memo still has an Original Invoice lock pointing at a different invoice. Clear that field on the memo and try again.
Yes — a $9,800 invoice can absorb a $1,200 credit and an $8,600 payment. The invoice's balance simply reflects both: Total − Cash Received − Credit Applied.
Apply what fits and leave the rest as Remaining Credit for future invoices — or refund the remainder in cash (Credit Memo Refund). Both together are fine too.
None — an application record has no accounting period field because it creates no ledger entries. The memo's posting carried the accounting, in the memo's own period. The Application Date on the record is a documentation date, not a books date.
Original Invoice first (if the memo links one), then any invoices with an Application Priority number (lowest first), then the rest oldest-first by invoice date — always same customer, same entity, posted, with an open balance.
Treat applications as remove-and-redo: delete the application (balances return on both sides instantly, and there are no ledger entries to clean up) and create a new one with the right amount. The audit trail stays simple that way.
Was this article helpful?