Skip to main content
Card class: Card
Total credit memo value issued. Includes returns refunds and goodwill credits.

​
At a glance

Total dollar value of Credit Memos posted in NetSuite over the period. Credit Memo is the GL-side refund record; the financial twin to RMA on the operations side. Sums the customer-credit dollars that posted to the GL, regardless of whether the credit was applied to a future invoice (offset) or paid out as a Customer Refund (cash). VP Finance reads it as the working-capital impact of returns and adjustments; the Controller reads it as the GL footprint that must be reconciled against the bank statement (cash refunds) and AR (applied credits).
What it countsSUM(transactions.total WHERE type='CredMemo') over the period. Includes credit memos created from RAs (return-driven), credit memos issued for adjustments (price corrections, billing errors, freight credits), and credit memos issued as goodwill / promotional refunds.
VAT / tax treatmentTax-inclusive, the credit memo total includes the original tax credit-back. UK / EU memos credit VAT; US memos credit sales tax where charged. Excluding tax requires summing subtotal instead.
ShippingIncluded where the merchant credited shipping. Memo line items show whether shipping was credited (typically yes for full returns, no for size-exchanges).
DiscountsOriginal discounts are preserved on the memo. A £100 order with £15 discount → £85 net → memo for £85.
RefundsThis IS the refund population at GL level. The memo posts when issued; the cash refund posts when the merchant runs Customer Refund against the memo (or applies it to the next invoice).
Cancelled / voided ordersVoided memos are excluded.
CurrencyPosted in customer’s transaction currency, summed in base / consolidation currency for the headline. Per-subsidiary view available.
Channels / sourcesAll sources blended: web returns, B2B credits, EDI deductions (retailer chargebacks posted as credit memos), freight/billing-error adjustments. EDI deductions are a major leakage point on B2B-heavy stores and worth tracking separately.
Time window30D vsP
Alert triggerNone on the value directly; spikes are surfaced on Margin Erosion Alerts and Returns Count.
Rolesowner, finance

​
Calculation

Calculated automatically from your NetSuite data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​
Worked example

A US wholesale distributor on NetSuite OneWorld. Reporting window 02 Apr 26 to 01 May 26. Headline credit memo value: **612,400∗∗.Prior30D:612,400**. Prior 30D: 384,200. Delta: +59%. Decomposition by reason code (custom field on the credit memo):
ReasonMemo countMemo valueAvg memo
Return (RA-driven)1,840$182,400$99
EDI deduction (retailer chargeback)142$238,000$1,676
Freight credit (carrier damage / late)64$42,800$669
Pricing adjustment38$84,000$2,210
Goodwill / discount22$14,200$645
Other / uncategorised14$51,000$3,643
Total2,120$612,400$289
Where the $228,200 increase came from:
  1. EDI deductions are 39% of the dollar value and the primary growth driver. Up from $148,000 prior period (+61%). Five large retail accounts each posted unusual deduction volumes:
    • Retailer A: $42,800 in compliance deductions (PO-line mismatch) on a single PO.
    • Retailer B: $38,200 in pricing deductions (the merchant’s order-entry team applied list pricing on a customer who had a contract-pricing override; retailer auto-deducted the difference).
    • Retailer C/D/E: $34,000 cumulative on freight chargebacks (late shipment penalties).
  2. Pricing adjustments are 14% of the value and stable in count, growing in size. Investigation: 3 of the 38 memos are in the 5kto5k to 12k range. Trace shows mass-price-update workflow misapplied the new wholesale price 1 week before the customer-contract amendment took effect; AR clerk caught it on month-end review and issued retroactive credits.
  3. **Returns (RA-driven) are stable at 182,400.∗∗Reconcilestothe[ReturnsCount](/nerve−centre/kpi−cards/netsuite/return−authorisations)population:1,840memos×182,400.** Reconciles to the [Returns Count](/nerve-centre/kpi-cards/netsuite/return-authorisations) population: 1,840 memos × 99 average = matches the RA count of 1,900 with 60 RAs still pending receipt.
  4. Action:
    • EDI deductions: open a dispute on Retailer A’s 42,800(thePO−linemismatchisthemerchant′sdata,nottheretailer′s,soitisrecoverable).Estimatedrecovery42,800 (the PO-line mismatch is the merchant's data, not the retailer's, so it is recoverable). Estimated recovery 30k to $35k.
    • Pricing adjustments: strengthen the contract-pricing override workflow; the $84,000 was avoidable. Add a sales-rep checklist before SO entry on contract-pricing customers.
    • Returns: unchanged, healthy ratio relative to revenue.
  5. Cross-channel sanity check: Stripe-side refunds for the period total $186,200 in 1,820 transactions; reconciles to the Return + Goodwill memo populations within 2% (the gap is the timing difference between memo posting and cash refund, plus partial refunds). Healthy.
  6. Working-capital impact: 612,400ofcreditmemosin30daysisroughly612,400 of credit memos in 30 days is roughly 20,400 / day of revenue clawback. Against $24m monthly revenue this is 2.55% net leakage. The healthy benchmark for a US wholesale distributor is 1.0 to 1.5%; this distributor is bleeding 1.0+ percentage points more than peers, mostly via EDI deductions. A quarterly EDI-compliance review is the highest-ROI action.

​
Sibling cards merchants should reference together

CardWhy pair it with Credit Memo Value
Returns CountThe operational twin (RA = returns request; Credit Memo = financial post). Reconciliation should be ~1:1 minus pending receipts.
Total Revenue / Invoiced RevenueThe denominator. Memo value / Invoice value = net refund rate, the operator’s leakage benchmark.
Margin by SKUHigh memo concentration on a SKU = product is structurally loss-making.
Customer Churn SignalsHigh memo volume on a single B2B account = relationship under stress.
Cash Application RateMemos applied to invoices reduce cash collection; the application rate metric reflects this.
Margin Erosion AlertsTriggers when memos cause a margin compression on specific SKUs.
stripe.stripe_refund_valueCross-connector: cash-refund memos should reconcile within ±5% to Stripe refund value.
bigcommerce.refund_valueCross-connector: web memos should reconcile within ±5% on the DTC subset.

​
Reconciling against the vendor’s own dashboard

Where to look in NetSuite’s own dashboard:
Reports > Sales > Credit Memo Register, set date range to match the period. Total at the bottom = card value.
For per-customer or per-reason-code breakdown: Saved Search > Transaction, filter by Type = Credit Memo, group by Customer or by the custom reason field. For the GL view: Reports > Financial > Income Statement, drill into the contra-revenue line Sales Returns and Allowances. Why our number may legitimately differ:
ReasonDirectionWhy
Posting period vs transaction dateEitherNetSuite memo posts to the GL by tranDate but the merchant may close period on different cadence. Vortex IQ uses tranDate.
Voided memosOurs can be lowerVoided memos drop from the Vortex IQ count but appear in some NS audit reports.
Multi-currency consolidationEitherVortex IQ converts to consolidation currency at the transaction’s exchange rate; some NS reports use period-end rate, producing FX-driven gaps.
Cross-connector reconciliation:
CardExpected relationshipNotes
stripe.stripe_refund_valueCash-refund memos ≈ Stripe refunds within ±5%Stripe sees only the cash-out events; memos applied to next invoice (no cash-out) are NS-only.
paypal.pp_refund_valueSame for PayPal-paid memosPer-gateway split.
shopify.refund_valueWeb-DTC subset onlyShould reconcile within 5%; large gap = unmapped refunds.
bigcommerce.refund_valueWeb-DTC subset onlySame logic.

​
Known limitations / merchant FAQs

Credit memo vs cash refund: what’s the difference? Credit memo = the GL document (revenue contra-entry, AR balance reduction). Cash refund = the bank-side cash-out event posted against the memo. A memo can sit unpaid (applied to the next invoice as offset, or held as unapplied customer credit on AR). On NetSuite the workflow is: Credit Memo posts → Customer Refund flows the money or memo applies to next Invoice. This card is on the memo side. My memo value is bigger than my refund-card value, why? Because not all memos result in cash refunds. Memos applied to the next invoice (offset) are not cash-out events. The gap memo - cash refund = the credit being held on AR for future invoice application. For B2B-heavy distributors, 30 to 50% of memo dollars apply to the next invoice rather than cashing out. Why are EDI deductions appearing as credit memos? Standard NetSuite practice. When a retailer (Walmart, Target, Costco, etc) pays a smaller amount than your invoice with a “deduction” (compliance penalty, freight chargeback, pricing dispute), the AR clerk posts a credit memo for the deduction amount to clear the AR. The memo contra-revenues the original sale. Tracking these separately by reason code is critical to dispute the recoverable ones. A B2B account is hitting credit memos every month. Is that normal? Possibly. Some B2B accounts use credit memos as their preferred billing-correction mechanism (rather than disputing invoices upfront). If the same account averages 10kto10k to 40k in monthly memos, look at the underlying reason: pricing disputes (your contract handling is wrong), shipping complaints (your fulfilment quality is wrong), or chronic over-invoicing (your order entry process has a recurring error). The pattern is a relationship-quality signal worth investigating. Should I include voided memos? Vortex IQ excludes voided memos from the headline, on the basis that a void undoes the financial event. If you want to track voids separately (audit / fraud detection), use the Saved Search approach in NS directly. Why is my pricing-adjustment line so high this period? Three usual causes: (1) a price-list update was misapplied to existing customers (the most common); (2) a sales rep entered list price on a contract-pricing customer (typical when sales reps rotate); (3) a programmatic-pricing engine had a bug. Pull the memos by user and group by sales rep to find the cluster. My OneWorld account: should memo value reconcile across subsidiaries? No, each subsidiary has its own memo posting. The consolidated headline is the sum. Intercompany memos (subsidiary A crediting subsidiary B) post in both books but eliminate at consolidation; Vortex IQ shows the eliminated view by default. Goodwill memos: how do I track them separately? Use the custom Reason Code on the credit memo header. NetSuite ships a standard Reason field on Customer Returns; merchants typically extend with custom values like “Goodwill”, “Warranty”, “Promotional”. Vortex IQ exposes the breakdown by Reason Code if the field is populated. A spike in memos on a single day, what should I do? Three usual causes: (1) end-of-month batch processing (memos accumulate during the month and post in a Friday batch); (2) a single large EDI chargeback batch from a major retailer; (3) a workflow / automation issue (the auto-memo on Q1 returns ran with a bug). Open the Credit Memo Register filtered to that day, sort by user; if one user did all 60 memos in 30 minutes, it is automation. If it is spread, it is end-of-month batch. Does this affect the revenue figure on Revenue Booked into GL? Yes. Credit memos are contra-revenue; they reduce the net revenue line. Revenue Booked into GL is net of credit memos by default. The gross revenue can be reconstructed by adding back this card’s value.

​
Tracked live in Vortex IQ Nerve Centre

Credit Memo Value is one of hundreds of KPI pulses Vortex IQ tracks across NetSuite and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.