Amazon Month-End Close for FBA Sellers: How to Handle Fees, Refunds, Reserves, and Payout Mismatches

Key Takeaways

• Amazon month-end close breaks when you treat the payout as the source of truth instead of the settlement detail.
• Fees, refunds, reserves, reimbursements, and timing differences should not all flow through one net-revenue shortcut.
• A balanced close workflow separates period activity from cash timing and preserves a clear trail when Amazon totals do not tie perfectly.

Introduction

Amazon month-end close gets messy for a simple reason: the number that hits the bank is not the full story.

An Amazon payout is the net result of sales, fees, refunds, reserve holds, reimbursements, and adjustments that may have been earned or posted across different dates. If you book that deposit as if it represents one clean month of revenue, the close may look finished for a day or two, but the cleanup comes back later through unexplained margin swings, reconciliation issues, and repeated accountant corrections.

This is why Amazon close work is not just a settlement-posting problem. It is an operational accounting problem. You need a process that respects month boundaries, keeps the balance sheet clean, and leaves an audit trail for the activity that did not land neatly in cash during the same period.

Why Amazon Month-End Close Breaks

Most cleanup work comes from one of these mistakes:

1. The net payout is recorded as revenue.
2. Settlement activity that spans two calendar months is forced into one month.
3. Fees and refunds are lumped together instead of classified separately.
4. Reserve holds are treated like expenses or ignored entirely.
5. Reimbursements and later adjustments are posted wherever they happen to fit.
6. File totals and line totals do not match, so someone forces the books to tie by changing revenue.

That last point matters more than many sellers realize. Amazon data is detailed, but it is not always neat. If the header total and the line-level breakdown do not align cleanly, the answer is not to bury the difference in sales. The answer is to keep the posting balanced and make the variance visible.

The Month-End Close Checklist

Use this checklist when reviewing Amazon activity at month end.

1. Start With Settlement Detail, Not the Bank Deposit

The settlement report is the accounting source document. The bank deposit is just the cash result after Amazon has applied its math.

At close, review the settlement-level activity first:

• gross sales
• selling fees
• FBA fulfillment fees
• storage fees
• refunds
• reimbursements
• reserve movement
• adjustments

Many accounting teams use a clearing account for this bridge. MerchantLedger uses Payment Clearing as the canonical account in its posting flow, but the accounting idea is broader than the product label: separate the settlement activity from the bank timing so the books can reflect both accurately.

2. Cut Activity at the Month Boundary

Month-end close fails when one settlement crosses two reporting periods and gets dumped into whichever month received the payout.

For example, suppose a settlement covers March 25 through April 8, and the payout lands on April 10. If you book the full payout in April, March revenue and March fees are understated. If you force the whole settlement into March, then April activity is distorted instead.

The right approach is to respect the accounting period boundary. That means identifying what belongs in March, what belongs in April, and how the carry-forward balance should sit in clearing until cash arrives.

Close issue	Correct treatment	Why it matters
Settlement spans two months	Split activity by accounting period	Prevents revenue and fees from drifting into the wrong month
Payout lands after month end	Leave timing difference in clearing	Keeps cash timing separate from operating results
Later adjustment posts in next month	Record it in the month it applies	Avoids rewriting prior-month numbers without cause

This is one of the places where audit detail matters. MerchantLedger can surface month-segment detail, posting dates, and payment-clearing entries so users can inspect how a split settlement affects close accuracy.

3. Classify Fees Into the Buckets You Actually Review

If every deduction from Amazon lands in one generic expense account, the close may technically balance, but it will not be useful.

At a minimum, separate fees into categories you can review month over month, such as:

• selling fees
• fulfillment fees
• storage fees
• advertising, if included in settlement activity
• other marketplace charges and adjustments

This helps with two things. First, it keeps margin analysis from turning into guesswork. Second, it makes review faster when one category moves unexpectedly.

A workable close is not just about getting to a balanced journal entry. It is about making the P&L explainable to the person who has to sign off on it.

4. Treat Refunds as a Revenue Reduction, Not a Miscellaneous Expense

Refunds often create avoidable confusion because they touch both operations and accounting.

From a close perspective, the important question is not whether the money left the settlement. It did. The question is how that activity should be represented on the financial statements.

In many Amazon workflows, customer refunds are better treated as contra-revenue rather than buried in an expense bucket. That keeps gross sales, net sales, and refund behavior more interpretable. If refunds are mixed into general expense accounts, the P&L stops telling a clear story about what was sold versus what was reversed.

If return-related fees also appear, separate those from the refund itself. The refund reduces revenue. The fee is an expense. Combining them makes both lines less useful.

5. Keep Reserves on the Balance Sheet

Amazon reserves are another common source of distortion.

When Amazon holds back part of the settlement, that is not usually a new operating expense. It is a balance-sheet timing issue. The cash has not been released yet, but the hold still needs to be tracked somewhere visible.

This is why reserve handling should be explicit in the chart of accounts and posting logic. MerchantLedger supports reserve-related account mapping in the canonical account layer, and for Wave specifically the system validates Reserve Balance separately from Payment Clearing because those are not interchangeable concepts.

If reserves are shoved into fees, revenue, or an undifferentiated suspense account, the next release becomes harder to explain and the close gets less reliable each month.

6. Review Reimbursements and Adjustments Separately

Inventory reimbursements, corrections, and later adjustments should not be treated as normal product sales just because they increase the amount due from Amazon.

These entries often represent a different business event:

• reimbursement for lost or damaged inventory
• correction of a prior fee or charge
• manual adjustment that ties back to an operational issue

Keep these categories visible. If reimbursement activity gets blended into normal sales, you can overstate operating performance and miss the operational reason that the reimbursement existed in the first place.

7. Do Not Force Payout Mismatches Through Revenue

Sometimes the settlement header total is the most reliable number available, but the line-level activity still does not roll up exactly the way you expect. When that happens, the books still need a balanced entry.

The mistake is to make the unexplained difference disappear inside revenue or fees. That produces a tidy-looking P&L and a false accounting record.

The better approach is to preserve balance while keeping the mismatch visible in a dedicated variance or clearing line. MerchantLedger follows that logic in its reconciliation behavior by treating the settlement total as authoritative and routing mismatches into a plug line instead of silently distorting the operating accounts.

That does not mean every mismatch is magically resolved. It means the posting stays balanced and the uncertainty stays inspectable.

8. Confirm the Clearing Balance Before Closing the Month

Your clearing balance should tell a coherent story at month end.

It may be non-zero for legitimate reasons:

• a payout has not arrived yet
• a settlement was split across months
• Amazon is holding a reserve
• a visible variance is still awaiting review

What should not happen is carrying an unexplained clearing balance forward month after month with no documentation. If the balance exists, you should be able to explain what created it and what event is expected to release or resolve it.

A Simple Review Framework

If you want a practical monthly process, use this order:

1. Pull the settlement detail that affects the month.
2. Separate activity by month boundary instead of payout date alone.
3. Review fees, refunds, reimbursements, reserves, and adjustments in their own categories.
4. Post the activity through clearing so the balance sheet reflects timing differences.
5. Confirm any remaining reserve or variance balance is explainable.
6. Tie the final cash movement to the bank deposit when it actually arrives.

This is what turns Amazon close from repeated cleanup into a controlled process.

Where MerchantLedger Helps

MerchantLedger does not replace a full close-management workflow, but it does support the parts of Amazon accounting that usually create the mess.

The product can:

• track settlement line categories such as sales, fees, refunds, reimbursements, and adjustments
• surface settlement-level audit detail with month segments and posting dates
• show payment-clearing entries for split settlements
• preserve balanced posting behavior when settlement totals and line totals do not match cleanly
• show posting history in the settlement detail workflow

That matters because month-end close gets easier when the underlying settlement accounting is inspectable. You do not need less detail at close. You need better-structured detail.

Conclusion

Amazon month-end close becomes manageable when you stop treating the payout as the event and start treating the settlement detail as the source of truth.

That means respecting month boundaries, classifying fees intentionally, handling refunds as revenue reductions when appropriate, keeping reserves on the balance sheet, separating reimbursements from normal sales, and preserving balance when Amazon totals do not line up perfectly.

If your current process still turns every close into cleanup work, the next step is to review your settlement workflow and identify where timing differences and category mistakes are entering the books. MerchantLedger is built to surface the audit detail and structured posting behavior that make that review more reliable.