A return was approved, shipped, and signed for by the supplier’s dock three weeks ago. The credit never arrived, and AP paid the original invoice in full in the meantime. Nobody did anything wrong at any single step. The return just had no owner after it left the building.
Money that suppliers owe you (rebates, return credits, shortage claims, deposits to be applied) is easy to lose because no bill arrives to prompt anyone. Each of these needs a record that follows it from the agreement or incident to a credit you can trace in the ledger.
Credit memo or debit memo?
The terms get used loosely, so agree on them internally.
| Document | Who issues it | Effect on what you owe |
|---|---|---|
| Supplier credit memo | Supplier | Reduces your payable once recorded and applied |
| Debit memo (buyer-issued) | You | Records your claim against the supplier and reduces the payable on your side, pending the supplier’s agreement |
| Corrected invoice | Supplier | Replaces the original; make sure the original is voided or credited |
| Refund | Supplier | Cash back, usually when there’s no open payable to offset |
Whatever the document, the test is the same: the claim and its settlement should be traceable to each other, and the same amount should not be both open as a claim and available for a second application.
Shortage and damage claims
An invoice lists 100 units. Receiving counts 96 and finds two damaged. Give the buyer both facts: four units are missing and two arrived in a condition the plant may reject. The supplier may agree to a different remedy for each.
Illustrative example
Unit price is $42.
| Line | Units | Amount |
|---|---|---|
| Invoiced | 100 | $4,200 |
| Missing | 4 | $168 |
| Damaged, rejected | 2 | $84 |
| Total claim | 6 | $252 |
| Supported payable | 94 | $3,948 |
$4,200 − $252 = $3,948. Paying $3,948 now and claiming the rest, or holding the whole bill, depends on the supplier agreement and your approval policy.
Give the supplier a claim it can verify: the PO line, invoice, receipt, delivered and accepted quantities, and the inspection or delivery evidence. Say whether the disputed charge is still unpaid or already paid.
| Outcome | What AP should verify |
|---|---|
| Supplier sends a corrected bill | It covers the supported quantity and the original won’t also be paid |
| Supplier issues a credit | The amount and invoice reference match the approved claim |
| Supplier sends replacement units | Receiving can tie them to the original claim, and they aren’t billed again as new goods |
Returns to vendor
A return can be approved and shipped while the credit is still outstanding. Give purchasing and AP one shared record with the original receipt, return authorization, expected remedy, and owner.
- Authorize the return. Record the part, quantity, reason, and what the supplier agreed to provide.
- Confirm shipment. Attach the shipment reference and compare the quantity shipped with the quantity authorized.
- Check the remedy. Compare the credit, refund, or replacement with the agreement. Route differences to purchasing.
- Verify the accounting. Check where the credit was applied and that it can’t be applied twice.
In NetSuite, the vendor return authorization is a non-posting record when the feature is enabled, and Oracle describes separate authorization, shipment, and credit steps. An approved authorization alone doesn’t mean the credit posted. Oracle’s vendor return documentation
Partial returns. If the supplier authorized ten units and the warehouse shipped six, show the six shipped and four pending separately. At $55 per unit, the expected credit for what actually shipped is $330 (6 × $55), not $550. When the credit arrives, compare it with the shipped quantity before closing the return.
Vendor rebates
When a supplier says you missed a rebate threshold, ask what they counted. The agreement may count receipts or invoices rather than orders, and returns, excluded items, and the cutoff all change the answer.
Build a register buyer and AP share
| Record | What to capture |
|---|---|
| Agreement | Eligible items, earning period, calculation basis, tiers, claim deadline |
| Purchases | Source line, date, quantity or value, and any reason for exclusion |
| Returns | Original purchase line and the period in which the agreement nets the return |
| Settlement | Supplier statement, approved claim, credit memo, or cash receipt |
Illustrative example: how the tier is read changes the rebate
The agreement pays 1% on eligible purchases up to $500,000 and 2% above that. Gross eligible receipts for the year are $665,000, and $25,000 was returned, so net eligible purchases are $640,000.
| Reading of the tier | Calculation | Rebate |
|---|---|---|
| Rate applies to all purchases once the threshold is crossed | 2% × $640,000 | $12,800 |
| Higher rate applies only above the threshold | 1% × $500,000 + 2% × $140,000 | $5,000 + $2,800 = $7,800 |
The $5,000 difference comes entirely from how the tier is written. Verify which reading the signed agreement uses before calculating the accrual, then compare the supplier’s statement line by line.
Accruing and reconciling
Rebates earned but not yet received are usually accrued as a receivable from the supplier, with the offset reducing inventory cost or cost of goods sold depending on whether the goods are still on hand. Confirm the treatment with your controller or auditor.
The warning sign is an accrual that keeps growing at each close while the supplier’s credits cover less of it. When you see that, reconcile it:
- Pull the eligible transactions and explain exclusions or returns.
- Compare the accrual with the supplier’s claim or statement.
- Trace the credit to the agreement and verify how AP applied it.
- Give any remaining difference an owner, and record whether it needs a supplier response or an approved adjustment.
How ERPs handle rebate agreements
NetSuite. Oracle documents that the Rebates and Trade Promotions SuiteApp uses agreement details to define calculation criteria for purchases and sales, and can select a deal for eligible transaction lines. When agreements overlap, inspect the deal that actually applied. Oracle’s agreement setup guide · Oracle’s transaction rebate guide
Dynamics 365 Supply Chain Management. Vendor rebate deals can be based on purchase or sales orders. Check the selected basis against the agreement, which may count receipts or invoices, before using a system report to support a claim. Microsoft’s rebate deal documentation
Test an overlapping agreement and a return near cutoff. The reviewer should be able to identify which deal applied and reproduce the remaining balance.
Tooling deposits and advance payments
A toolmaker asks for a deposit before cutting a die. Months later the final invoice arrives for the full amount. Before approving it, find the deposit and check how the agreement says it should be applied.
Keep a schedule by order and milestone: supplier, PO, approved deposit, date paid, milestone evidence, and intended application.
| Situation | Check next |
|---|---|
| Final invoice shows the full charge | Whether the advance should be applied now or at a later milestone |
| Partial shipment or acceptance | Which amount is due and what stays unapplied |
| Supplier invoice already deducts the deposit | How your ERP should reflect it, so you don’t deduct it twice |
| Project canceled | Refund or forfeiture terms, and an owner to follow up |
Illustrative example
A die costs $40,000 with a 50% deposit.
- Deposit paid: debit vendor prepayment $20,000, credit cash $20,000.
- Final invoice: debit the tooling account $40,000, credit AP $40,000.
- Apply the deposit: debit AP $20,000, credit vendor prepayment $20,000.
- Pay the balance: debit AP $20,000, credit cash $20,000.
The prepayment and the payable both end at zero. Which account the tooling cost goes to depends on who owns the tool and your capitalization policy.
In NetSuite QuickStart, Oracle documents linking a prepayment to a PO and applying it to an eligible bill, which reduces both the unapplied advance and the amount due. Verify both balances after applying it. Oracle’s vendor prepayments guide
What goes wrong
- Credit counted twice. AP short-paid the bill for a shortage, then also applied the supplier’s credit memo for the same units.
- Return authorized, never credited. Nobody watches the gap between shipment and credit.
- Replacement units billed as new. Receiving doesn’t link them to the claim.
- Rebate accrued on orders, earned on receipts. The accrual and the supplier’s statement never agree.
- Deposit forgotten. The final invoice is paid in full and the prepayment sits on the balance sheet.
Most of these surface on the supplier’s statement first; see vendor statement reconciliation. A credit that was paid out twice shows up as a debit balance; see duplicate payments and vendor master controls. Freight recoveries follow the same pattern and are covered in freight invoice audit.
Open-claims checklist for the month-end review
- Every open shortage, damage, return, and rebate claim has an owner and expected settlement date
- Each claim links to its source receipt, invoice, or agreement
- Shipped-but-uncredited returns listed with days outstanding
- Rebate accrual reconciled to eligible transactions and the supplier’s latest statement
- Tier calculation checked against the signed agreement wording
- Open deposits matched to POs and expected application milestones
- Received credits applied once, to the bill they relate to
- Claims closed only when settlement is traceable in the ledger