From the first blueprint to the next stage of growth.
Give your systems a shared picture of the business.
Give people the right NetSuite-connected experience for their work.
Focused applications for specific operational challenges.
Start with the workflows that make your industry different.
Useful answers for choosing, implementing and improving NetSuite.
What changed, why it matters, and what to review next.
Meet the people and approach behind CuriousRubik.
Use a credit memo when an approved adjustment reduces what the customer owes. Use the appropriate refund process when money must be returned from an existing customer credit or overpayment. First identify why the credit balance exists; a duplicate payment does not automatically justify another revenue adjustment.
This guide focuses on non-return billing corrections, unused credits and overpayments. Physical returns, inventory disposition and return authorizations belong to the separate returns process. Ask your accountant to approve transaction type, tax treatment, classifications and posting period before making a material correction.
Begin with the original invoice, payment history, existing credits and any deposit. Establish whether the customer was overbilled, paid twice, received an approved concession or made an advance against future work.
A customer-facing request for a “credit” can mean several things. The customer may want a document explaining a pricing correction, an amount held for its next invoice or money returned to its bank. Clarify that outcome before selecting a transaction.
Preserve the original evidence. A clear case should show the disputed charge, approved adjustment or excess receipt and the customer's requested resolution. Avoid changing the original invoice merely to make the present balance look right without a traceable correction history.
Oracle describes customer credit memos as transactions that reduce the amount a customer owes. Its documentation also warns that stand-alone credit memos can affect inventory, unlike credit memos created from return authorizations.
That warning matters for a pure billing adjustment. Do not copy inventory lines into a stand-alone credit without understanding the resulting quantity and accounting effects. Finance and the NetSuite administrator should agree the permitted item and transaction design for non-return corrections.
Oracle separately documents refunding an open balance, including selection of the transactions responsible for the overpayment. Trace the refund to that source balance rather than creating a new credit simply because the refund screen is inconvenient.
First confirm whether the original charge is wrong. If it is, obtain approval for the correction and validate the credit treatment. If the charge is correct but the receipt is excessive, investigate the payment and existing unapplied balance.
Next confirm whether the customer wants application to a current invoice, retention for an agreed future invoice or a refund. Record that instruction, subject to contract terms and applicable legal requirements.
Then verify customer, subsidiary, currency and the source transaction. A credit visible in a consolidated report may not be available for every application or refund context. Resolve the scope issue rather than moving balances between entities without approval.
Finally inspect the effect on both the customer account and the ledger. The expected result should be written before saving: which balance decreases, which cash movement is expected and which open item remains.
Customer A receives a 5,000 invoice that should have been 4,600. The business approves a 400 billing correction. Customer B receives an accurate 5,000 invoice but sends two separate 5,000 payments.
For Customer A, an approved credit may correct the charge, subject to tax and accounting review. For Customer B, the issue is the extra receipt. Issuing another 5,000 credit memo without a valid billing adjustment could introduce a second, unrelated accounting effect.
If Customer B requests a refund, the reviewer should identify the excess payment, verify the refund method and reconcile the eventual cash outflow. These cases may both create a negative customer balance, but they should not share an unexamined correction recipe.
A credit approval should state the reason, affected invoice lines, amount, currency, tax treatment and person authorizing the concession or correction. A refund approval should additionally establish recipient, method and source balance.
Keep commercial approval separate from payment release where practical. Someone authorized to negotiate a concession may not be authorized to send money. Conversely, a payment operator should not decide that a disputed charge is invalid merely to complete a refund request.
For partial refunds, document what remains and how it may be used. The case should not close with a residual that nobody owns. Set a review date if the customer has elected to retain the remainder for future business.
Use the approved payment route and verify any requested change of destination independently. A message from a familiar address does not prove that new banking instructions are genuine.
The Oracle open-balance refund procedure instructs use of the original form of payment. Confirm the supported behavior and provider requirements for your specific method before promising an alternative. A recorded refund and a payment-provider settlement are separate evidence points.
For integrated payments, identify which system submits the refund and which one records it. If both an operator and an integration can create the refund, design a shared identifier and a duplicate check. After a timeout, inspect the provider result before resubmitting.
Maintain a credit register showing original amount, applications, refunds and remaining balance. For each movement, retain the related transaction identifier and date. Reconcile the same entity, currency and as-of period.
Maintain a second view of refunds awaiting cash settlement. A refund can be recorded while a check remains outstanding or a processor still handles the request. Explain those timing items and follow unresolved cases to a terminal outcome.
Review unused credits on inactive customers, credits with no source reason and refunds linked to unexpected transactions. Obtain professional advice before treating old customer money as income or extinguishing an obligation.
In a safe test environment, exercise a price correction, a duplicate receipt, partial application, partial refund and a failed refund response. Include a foreign-currency case and a closed-period source transaction for accountant review.
Check customer statements and collection queues after each scenario. A correctly posted credit may still be applied to the wrong invoice, leaving a misleading reminder. A refund case should preserve the original customer explanation even after the balance reaches zero.
For recurring correction issues, CuriousRubik's NetSuite support services can help review the configured forms, transaction relationships and payment integration. Bring the intended business result as well as the screen where staff get stuck.
Not automatically. Identify the excess receipt and its existing balance first. A new billing credit needs a valid adjustment reason and approved accounting treatment.
Oracle warns that it can. For a non-return billing correction, validate the selected items and resulting quantity and GL effects before posting.
That may be an agreed outcome, subject to policy and applicable obligations. Record the instruction, monitor the remaining balance and confirm the later application.
No. Retain the payment-provider, bank or check-clearing evidence and distinguish recording from settlement. Investigate failed or uncertain processing before retrying.
Keep the source balance, customer instruction, approval, recipient verification, refund reference and settlement evidence. Explain any remainder and assign its next action.
