Inventory & Cost of Goods Accounting for Amazon

Last updated: March 2026

Contents

~70–80 min read · Updated February 2026

Use this contents menu to jump directly to the section you need.

• Why Inventory and COGS Are Where Amazon Profits Break Down
• What Counts as Inventory for Amazon Sellers (UK Context)
• Understanding Cost of Goods Sold in Amazon Accounting (UK)
• Periodic vs Perpetual Inventory Systems (Amazon Reality Check)
• Inventory Inside Amazon FBA (Operational vs Accounting Reality)
• Reimbursements, Write-Downs, and Inventory Losses
• Reconciling Inventory and COGS in Xero
• VAT and Inventory Accounting for Amazon Sellers
• Common Inventory and COGS Errors Amazon Sellers Make
• Month-End Inventory & COGS Review Checklist
• Action Plan: Fixing Margins and Scaling Profitably

1. Why Inventory and COGS Are Where Amazon Profits Break Down

For many UK Amazon sellers, profit problems do not begin with sales performance or payout errors. They begin with inventory and cost of goods sold (COGS). It is common to see Amazon deposits reconcile perfectly and settlement reports import without error, yet the profit figure in Xero or QuickBooks still feels wrong.

Margins move without a pricing change. Year-end profits shift after the accountant posts adjustments. A business that appeared profitable suddenly looks weaker once inventory corrections are made. Many sellers arrive at this point after fixing reconciliation, only to discover that accurate cash does not guarantee accurate profit.

The reason is simple: Amazon payouts describe cash movement, not economic performance. Inventory sits between those two realities. When inventory accounting is incomplete, delayed, or misclassified, profit becomes distorted even when reconciliation looks flawless. This guide explains why that happens, how Amazon FBA disrupts traditional COGS logic, and what reconciliation alone cannot fix.

Why accurate payouts do not guarantee accurate profits

Amazon settlement reports show what Amazon owes you, not what your business actually earned. A reconciled payout confirms that the cash received matches Amazon’s net calculation after fees, refunds, and adjustments. It does not confirm that revenue and costs have been recorded in the correct accounting period under UK GAAP.

Goods may have shipped in one month but been paid out in the next. Inventory may have been sold without COGS being posted. Refunds may reduce cash today for revenue recognised weeks earlier. When timing and inventory are misaligned, profit becomes distorted even though reconciliation appears correct.

Note on Amazon policies and reporting:
Amazon policies, reporting formats, and invoicing or VAT practices change over time. Always check current Amazon documentation and HMRC guidance before implementing any process described here.

An Amazon FBA seller might receive a £9,000 payout and record that figure as revenue. In reality, that payout may relate to £12,000 of gross sales, £3,000 of Amazon fees, inventory sold over multiple weeks, and storage costs incurred in earlier months. The cash is accurate, but the profit position is not.

Under FRS 102, revenue is generally recognised when the significant risks and rewards of ownership have transferred to the customer, and costs are matched to the related revenue on an accrual basis. Amazon typically pays sellers on a 14 to 21 day cycle, so settlement dates will not usually align with sale dates. If accounting is driven solely by payout timing, revenue and costs can end up recorded in different periods.

This is why profit discrepancies are often identified only at year end, when accountants review inventory movements, accruals, and cost recognition in more detail.

How Amazon inventory distorts traditional COGS logic

Traditional retail accounting assumes a simple flow. You buy stock, you hold it, you sell it, and you recognise COGS at the point of sale. Amazon FBA breaks that logic in several ways.

Firstly, inventory is legally owned by the seller but operationally controlled by Amazon. Stock can be received late, moved between fulfilment centres, marked as unsellable, or lost without immediate visibility.

Secondly, Amazon charges fees that blur the boundary between COGS and operating expenses. Fulfilment fees, storage fees, removal fees, and long-term storage surcharges all affect gross margin, but they are applied on different schedules and deducted long after the economic cost is incurred.

Thirdly, inventory losses and reimbursements do not follow textbook timing. A unit can be lost in an Amazon warehouse in March, discovered in May, claimed in July, and reimbursed in November. Without inventory accounting, that loss and recovery will hit profit in the wrong periods, creating artificial volatility.

This is why applying a flat COGS percentage or relying solely on settlement data produces misleading margins for Amazon sellers. The cost of selling on Amazon is not static. It evolves as inventory ages and moves through Amazon’s system.

The gap between Amazon operations and accounting records

Amazon Seller Central is an operational platform. Xero and QuickBooks are financial systems. The two do not speak the same language.

Seller Central shows real-time stock levels, stranded inventory, aged units, and fulfilment activity. Accounting software records aggregated figures, often weeks later, based on settlement imports. When sellers rely on operational dashboards for decisions and accounting software only for tax filing, the general ledger gradually drifts away from reality.

This gap usually stays hidden until something forces reconciliation. An HMRC enquiry triggered by platform-reported sales. A statutory accounts review under FRS 102. A due diligence exercise for a business sale. At that point, inventory counts do not match the balance sheet, COGS cannot be explained clearly, and profit figures need to be restated.

The issue is not poor bookkeeping. It is that settlement data alone cannot capture inventory movement, timing differences, or valuation adjustments required under UK accounting standards.

What this guide will fix that reconciliation alone cannot

This guide is designed to close the gap between Amazon operations and UK statutory accounting. It goes beyond payout reconciliation and focuses on inventory as the missing layer in accurate profit reporting.

Specifically, it shows how to align Amazon inventory data with accrual-based accounting, how to calculate COGS based on actual units sold, and how to recognise storage costs, losses, and reimbursements in the appropriate accounting periods. It also outlines the type of documentation and support HMRC may expect to see, including inventory valuation methods, reconciliation schedules, and clear audit trails.

For Amazon FBA sellers, inventory accounting is often the difference between understanding true profitability and relying on incomplete figures. Reconciliation confirms that the money arrived. Inventory accounting explains whether you actually made it.

2. What Counts as Inventory for Amazon Sellers (UK Context)

Before inventory can be valued, reconciled, or written down, it needs to be defined clearly and consistently. For Amazon sellers, this is not as straightforward as it sounds. Inventory is rarely sitting on a shelf you can see. It moves between suppliers, freight forwarders, Amazon fulfilment centres, return processing, and disposal workflows, sometimes across multiple countries.

From an accounting perspective, the key question is simpler than the logistics: what stock does the business legally own at the reporting date? That question sits at the heart of UK Amazon accounting, as outlined in our Amazon Seller Accounting – Complete Guide, and forms the foundation for every COGS and margin decision that follows.

Under UK accounting rules, inventory is determined by ownership and economic control, not by who physically holds it. This distinction matters for Amazon sellers because Amazon stores, moves, inspects, and may even destroy stock, but the seller usually remains legally and economically responsible for it. When this boundary is misunderstood, inventory balances drift, COGS becomes unreliable, and profit figures lose credibility.

This section explains how inventory is defined under FRS 102 and relevant tax guidance, so that later discussions on COGS, VAT, reimbursements, and margin analysis rest on a clear and defensible foundation.

Owned stock vs Amazon-held stock

Under FRS 102 Section 13, inventories are assets held for sale in the ordinary course of business. The standard does not require the business to physically possess the stock. Instead, it focuses on whether the entity controls the economic benefits and bears the risks associated with the goods.

For Amazon FBA sellers, inventory stored in Amazon fulfilment centres is still owned by the seller. Amazon does not purchase this stock. It provides storage, handling, and fulfilment services under the Seller Services Agreement. The seller decides pricing, controls listings, receives the sales proceeds, and bears losses if inventory is damaged, lost, or returned. These are all indicators of ownership under UK GAAP.

HMRC guidance generally expects businesses to include all stock they own at the year end, regardless of where it is physically held. Inventory sitting in an Amazon warehouse is treated no differently to inventory sitting in a third-party logistics warehouse or a rented storage unit.

A common bookkeeping error occurs when sellers treat inventory as “used up” once it leaves their premises or supplier. Shipping stock to Amazon does not trigger an expense or COGS entry. It is simply a change in location. Derecognising inventory at this point overstates costs, understates assets, and creates timing errors that compound over time.

Situations where Amazon-held goods would not appear on the seller’s balance sheet are uncommon and typically depend on specific contractual arrangements. These include true consignment arrangements where the supplier retains ownership until sale, or inventory that has become permanently unsellable and would normally require write-off under the applicable accounting framework. Outside of these exceptions, Amazon-held stock remains the seller’s inventory under both FRS 102 and HMRC rules.

FBA inventory at fulfilment centres

From a statutory accounting perspective, inventory held across multiple Amazon fulfilment centres is reported as a single inventory balance on the balance sheet. Location does not change recognition. What matters is that the inventory is owned by the UK entity at the reporting date.

Where inventory is held across both UK and EU fulfilment centres, additional disclosure may be required if the amounts are material. Where overseas holdings are material, additional disclosure in the notes to the accounts may be appropriate under FRS 102. This does not change valuation but improves transparency for HMRC, Companies House, and lenders.

Operationally, Amazon regularly redistributes stock between fulfilment centres without seller initiation. These transfers do not change ownership or unit counts, but they can create confusion when sellers try to reconcile inventory using settlement reports alone. Amazon aggregates distribution fees, storage charges, and timing adjustments in financial reports, while unit movements are recorded separately in inventory reports. Without using the Inventory Ledger Report as the primary source of truth for quantities, accounting records slowly diverge from operational reality.

Inventory stored outside the UK introduces foreign currency considerations. Under FRS 102, foreign-currency inventory is translated at the spot exchange rate at the reporting date. Exchange gains and losses arising from retranslation are recognised in the profit and loss account, even if no units have been bought or sold. This means the sterling value of EU-held stock can fluctuate even if unit quantities do not change, something many sellers only discover during year-end accounts preparation.

VAT also intersects with inventory location. Holding stock in EU fulfilment centres will often create local VAT registration obligations. The exact position depends on how sales are structured and whether marketplace deemed supplier rules apply in that jurisdiction. From an accounting perspective, recoverable VAT should not be included in inventory valuation. If VAT is incorrectly capitalised into inventory and never reclaimed, both the balance sheet and cash flow are distorted.

Inbound shipments and goods in transit

Inventory does not suddenly appear when Amazon checks it in. Under UK GAAP, inventory becomes an asset when ownership and the significant risks and rewards transfer to the buyer. In practice, this depends on shipping terms rather than physical receipt.

Many Amazon supply chains operate under shipping terms such as FOB or CIF, though the specific terms should be confirmed in supplier contracts and commercial documentation. In these cases, ownership transfers when goods leave the supplier or are placed on the carrier. From that point onward, the goods are the seller’s asset, even if they are still in transit for weeks. These goods should be recognised as inventory, typically classified as goods in transit, until they arrive at Amazon.

Failing to recognise goods in transit is one of the most common causes of inventory understatement. Sellers often wait until Amazon checks in stock before recording it, which delays asset recognition, understates payables, and inflates profit in the interim period. At year end, this can create material misstatements that attract auditor or HMRC attention.

Where suppliers invoice after delivery, accruals are required. Where inventory has been received but not yet invoiced, it would generally be recognised with a corresponding accrued liability under accrual accounting principles. The accrual basis of accounting requires costs to be recorded when incurred, not when paperwork arrives.

Clear documentation is essential. Purchase invoices, shipping terms, bills of lading, carrier tracking, and Amazon inbound confirmations together form the audit trail that supports ownership and cutoff decisions. Without this documentation, inventory recognition becomes subjective and difficult to defend under scrutiny.

Returned inventory and unsellable stock

Returns introduce complexity because inventory condition changes after sale. Amazon classifies returned items as sellable or unfulfillable, with further distinctions such as customer damaged, defective, or warehouse damaged. Each classification has different accounting consequences.

Sellable returns are straightforward. The original sale is reversed, COGS is reversed, and inventory is restored at its original cost. No impairment is required.

Unfulfillable returns require judgement. Under FRS 102, inventory is required to be valued at the lower of cost or net realisable value. If a returned item can only be sold at a discount, an impairment is required. If it cannot be sold and has no recoverable value, it would normally be written off in accordance with the entity’s accounting policy.

Many sellers allow unsellable inventory to sit on the balance sheet indefinitely at full cost. This violates the requirement to reassess NRV at each reporting date. Indefinite carrying of unsellable or aged stock without reassessment may increase the risk of challenge in the event of an HMRC enquiry, particularly where inventory ageing is significant and no impairment has been considered.

Inventory awaiting inspection, removal, or disposal should still be recognised as inventory until ownership is extinguished. Where a present obligation exists, removal fees and disposal costs would typically be accrued when incurred rather than when deducted from a later settlement, subject to the specific facts.

The timing of returns matters for margin reporting. If returns are not accrued promptly, profits appear overstated in the period of sale and then collapse later when adjustments are finally posted. Correct return accounting smooths margins and produces figures that reflect economic reality rather than Amazon’s processing delays.

Inventory vs expenses, where sellers misclassify costs

A final boundary issue is the distinction between inventory costs and expenses. Under FRS 102, inventory cost includes expenditure incurred to bring inventory to its present location and condition. Costs that relate to holding, selling, or administering inventory are expenses, not inventory.

Purchase price, inbound freight, non-recoverable duties, customs clearance, inbound handling, and FBA prep costs form part of landed inventory cost. These costs remain on the balance sheet until the related units are sold.

Amazon storage fees, advertising, and returns processing are generally treated as period expenses rather than inventory costs. The treatment of fulfilment fees depends on the accounting policy adopted and the specific facts. Storage is a time-based carrying cost. Fulfilment is a selling activity showing how the product reaches the customer, not how it becomes inventory. Misclassifying these costs inflates inventory values, distorts gross margins, and obscures true product profitability.

In practice, inbound freight and duty costs that are incorrectly expensed, or storage fees that are inappropriately capitalised, may be subject to adjustment if reviewed during an HMRC enquiry. Both errors can lead to tax adjustments, penalties, and restated accounts.

A clear, documented classification policy is essential. Sellers should be able to explain why a cost is capitalised or expensed, apply that policy consistently, and reconcile inventory balances to Amazon reports monthly. When these controls are in place, inventory becomes a reliable foundation for COGS, margins, VAT, and profitability analysis.

3. Understanding Cost of Goods Sold in Amazon Accounting (UK)

For many UK Amazon sellers, Cost of Goods Sold is one of the most frequently misunderstood areas of ecommerce accounting. COGS sits at the intersection of inventory valuation, margin reporting, tax compliance, and commercial decision-making. When it is calculated incorrectly, sellers can reconcile Amazon payouts perfectly and still make consistently wrong decisions about pricing, advertising, and growth.

In an Amazon context, the confusion usually comes from three sources. Firstly, Amazon’s fee structure blurs the line between inventory costs and selling costs. Secondly, many sellers apply intuitive but incorrect logic to per-unit costs. Thirdly, accounting systems are often fed settlement data rather than transaction-level information.

This section breaks down what belongs in COGS for UK Amazon sellers, how Amazon-specific costs should be treated under UK accounting standards, and why errors in this area create false profitability signals.

Purchase cost and landed cost explained

COGS begins with inventory cost. Under UK GAAP, inventory is generally measured at the lower of cost and net realisable value, and “cost” is defined within FRS 102.

Purchase cost is the amount paid to acquire the goods themselves. This typically includes the supplier’s unit price, adjusted for any trade discounts or rebates. For most UK Amazon sellers, purchase cost alone does not reflect the true economic cost of inventory.

Landed cost expands this concept to include all costs required to bring inventory to its current location and condition. In an Amazon FBA context, this commonly includes inbound freight, import duties, customs clearance fees, port handling charges, and insurance while goods are in transit. Where inventory is prepared specifically for Amazon before it is available for sale, such as FBA labelling, polybagging, or compliance packaging, those costs also form part of landed cost.

The governing test is timing and purpose. If a cost is incurred to acquire inventory and make it ready for sale, it belongs in inventory and flows into COGS when the unit is sold. If it arises because a sale has occurred, or because inventory is being held rather than acquired, it does not.

For example, a UK Amazon FBA seller imports kitchen accessories from China. The supplier charges £8 per unit. Inbound freight and customs add £2 per unit. The landed cost is £10 per unit, not £8. That £10 sits on the balance sheet as inventory and moves into COGS as units are sold. Recording only £8 in COGS produces inflated margins even if bank balances and settlements reconcile.

Accurate landed cost is the foundation of meaningful margin analysis. Without it, profit reporting is structurally flawed.

Which Amazon fees belong in COGS and which do not

Amazon deducts a wide range of fees from settlements, but not all fees are treated the same for accounting purposes. A common mistake is assuming that any per-unit fee automatically belongs in COGS. Under UK accounting standards, this is incorrect.

Costs that relate to acquiring inventory and preparing it for sale belong in inventory and therefore in COGS. Costs that relate to selling, delivering, storing, or servicing inventory are generally treated as operating expenses rather than inventory costs, subject to the entity’s accounting policy.

Referral fees are commissions charged for facilitating a sale. They arise only when a sale occurs and are typically treated as selling costs for statutory reporting under UK GAAP. Advertising fees are incurred to generate demand and are also operating expenses. Storage fees are charged for holding inventory over time, regardless of whether it sells, and are operating expenses.

FBA fulfilment fees are the most contentious. They cover picking, packing, shipping to the customer, customer service, and returns processing. Although charged per unit sold, these activities occur after the sale has taken place. From a statutory accounting perspective under UK GAAP, they are generally treated as selling and delivery costs rather than inventory acquisition costs.

At the time of writing, many Amazon fees are subject to UK VAT at 20 percent. This affects cash flow and VAT reporting but does not change the underlying classification of those fees as inventory costs or selling costs. The detailed VAT treatment of referral, fulfilment, and storage fees, including when Amazon charges UK VAT and how input VAT recovery works, is explained separately in our FBA VAT for Amazon Sellers guide. VAT and cost classification often intersect in practice, but they should be analysed independently.

Why FBA fulfilment is often misclassified

FBA fulfilment is misclassified more than any other cost in Amazon accounting. The root cause is Amazon’s bundling of multiple post-sale activities into a single fee, combined with the intuitive but incorrect assumption that per-unit equals product cost.

In traditional retail, fulfilment is often internalised. Warehouse labour, packaging, and shipping may be absorbed into broader cost structures for management reporting. Amazon externalises these activities and charges them explicitly after a sale occurs. Under UK GAAP, accounting treatment is based on the substance of the transaction rather than the format of the invoice.

Under FRS 102, selling costs are excluded from inventory valuation. The fulfilment fee obligation arises at the point of sale, not when inventory is acquired. That timing is typically a key factor in determining the appropriate classification. As a general principle, costs arising only upon sale are not treated as part of inventory acquisition cost under UK GAAP.

Some sellers choose to include FBA fulfilment fees within COGS for internal reporting simplicity, particularly to analyse contribution margin after delivery. While this may be useful for management analysis, it departs from the strict definition of inventory cost under UK GAAP. Where this approach is used, it should be clearly documented, applied consistently, and disclosed. Without this, the treatment may be more difficult to defend if reviewed by auditors or HMRC.

Misclassifying fulfilment fees typically does not change total operating profit over time, but it materially distorts how that profit is presented. Gross margin appears lower than reality, inventory on the balance sheet appears overstated, and operating expenses appear artificially lean. These distortions mislead lenders, investors, and management.

Storage fees and when they distort margins

Amazon FBA storage fees are generally treated as period costs under UK accounting standards rather than included in inventory cost. They are time-based holding costs and are typically expensed in the period incurred.

Despite this, many sellers attempt to allocate storage fees to per-unit COGS. This creates significant margin distortion, particularly for slow-moving or aged inventory. Storage costs do not vary directly with units sold. Dividing monthly storage fees by units sold converts a fixed cost into an artificial variable cost, causing margins to swing based on sales volume rather than operational performance.

Long-term storage surcharges intensify the problem. As inventory ages, Amazon’s storage fees increase sharply. When these fees are capitalised or spread across units sold, they produce sudden spikes in reported COGS that appear to reflect declining product profitability. In reality, they reflect inventory management and turnover issues.

Storage fees themselves are not capitalised under UK GAAP. However, sustained storage costs on slow-moving inventory often coincide with declining selling prices or reduced demand. In those circumstances, inventory may need to be written down to net realisable value. The trigger for impairment is not the storage fee, but the inability to recover cost through sale.

UK accountants typically analyse storage separately from COGS, reviewing fees by inventory age alongside sales velocity and pricing trends. This preserves clean unit economics while supporting informed decisions about discounting, removal, or liquidation.

How incorrect COGS creates false profitability

When COGS is wrong, profitability becomes misleading. The most common outcome is understated COGS, which inflates gross margin and creates a false sense of security. Sellers believe they have more pricing flexibility, more advertising headroom, and more tolerance for inefficiency than they actually do.

A seller may see a 70 percent gross margin in Xero and assume there is room to discount aggressively or scale advertising. Once fulfilment, inbound freight, and other missing costs are included, the true margin may be closer to 45 percent. The gap does not disappear. It shows up later as cash pressure, disappointing growth returns, or unexplained losses.

Timing errors compound the issue. When costs are recorded when settlements arrive rather than when sales occur, month-end and year-end profits become volatile. December may appear unusually profitable because fulfilment and storage costs are recorded in January. January then looks weak despite strong sales.

This explains why sellers can reconcile Amazon payouts perfectly yet still report the wrong profits. Bank reconciliation confirms cash movement. It does not confirm that revenue and costs have been recognised in the correct periods or classified correctly.

From a tax perspective, incorrect COGS directly affects Corporation Tax. Understated COGS overstates taxable profit and leads to overpayment of tax. Overstated inventory defers expenses and increases audit risk when discovered. HMRC may compare reported margins to industry benchmarks and platform-reported sales data as part of risk assessment processes. Significant deviations invite scrutiny.

UK accountants diagnosing Amazon seller accounts typically start with gross margin benchmarking, followed by landed cost analysis, inventory turnover testing, and reconciliation to Amazon reports. In many cases where margins appear inconsistent, COGS is incomplete, mistimed, or inconsistently applied.

Correcting COGS does not usually change how much cash the business generates. It changes how clearly the business understands where profit is created, how fragile margins really are, and which decisions genuinely improve profitability rather than just shifting numbers between accounts.

4. Periodic vs Perpetual Inventory Systems (Amazon Reality Check)

Inventory accounting theory assumes clean data, clear timing, and known costs. Amazon does not operate in that environment. UK Amazon sellers often discover that certain inventory systems produce unstable margins or unexplained adjustments that can be difficult to explain if reviewed.

This section explains how periodic and perpetual inventory systems actually behave in an Amazon context, why neither works perfectly, and how UK sellers choose a system that is defensible rather than theoretically ideal.

What periodic inventory looks like in practice

A periodic inventory system does not attempt to update cost of goods sold or inventory balances every time a unit is sold. Instead, inventory and COGS are calculated at defined intervals, usually month-end, based on reconciled data.

For UK Amazon sellers, a periodic system typically works as follows:

• Sales and fees are recorded during the month using Amazon settlement data.
• Inventory purchases are recorded when supplier invoices are posted.
• At month-end, the seller or accountant pulls the Amazon Inventory Ledger report.
• Units on hand are reconciled to the balance sheet inventory figure.
• COGS is calculated based on units sold during the period multiplied by an agreed cost basis, often average landed cost.

This approach accepts a delay between activity and accounting certainty. That delay is intentional.

In practice, periodic inventory aligns well with Amazon’s operational reality. Amazon inventory movements are not final in real time. Returns can be initiated late in the month but completed weeks later. Lost inventory can sit under investigation for 30 to 60 days. Reimbursements may be approved in one month and paid in the next. A periodic system allows these uncertainties to resolve before the books are closed.

For example, consider a UK Amazon FBA seller with £85,000 monthly turnover. During October, Amazon reports 1,200 units sold. At month-end, the Inventory Ledger shows 3,800 units remaining. The accountant reconciles this to the balance sheet, adjusts for any inventory under investigation, and calculates COGS using the seller’s landed cost register. The result is not real-time, but it is explainable and auditable.

From a documentation perspective, a periodic inventory approach can be easier to evidence and explain if reviewed. The reconciliation process produces documentation showing how inventory balances were derived, how discrepancies were investigated, and how COGS was calculated. When HMRC asks why inventory on the balance sheet matches Amazon reports, the seller can show the workings rather than relying on automated assumptions.

What perpetual inventory promises but rarely delivers

A perpetual inventory system aims to update inventory and COGS continuously. In theory, every sale triggers an immediate accounting entry that reduces inventory and recognises COGS at the unit level.

In traditional retail, this works because stock movements are immediate, costs are known, and returns are processed quickly. Amazon FBA breaks these assumptions.

Perpetual inventory assumes certainty at the point of sale. Amazon’s reporting structure does not always provide that level of certainty at the point of sale. Settlement delays mean sales are not final for seven days after delivery. Orders can be cancelled before settlement. Returns can be initiated up to 30 days later. Inventory adjustments and reimbursements can reverse transactions months after they were first recorded.

Perpetual systems also assume a known per-unit cost at the time of sale. For Amazon sellers, true cost includes landed cost, fulfilment fees charged at sale, storage fees charged monthly, and sometimes disposal or removal costs charged later. That cost is not fully known when the order is placed.

The result is a general ledger filled with provisional entries that require later correction. Inventory balances drift away from Amazon’s operational data. Gross margins appear stable until a large adjustment is posted at month-end or year-end.

Accountants see this pattern repeatedly. A seller believes they have real-time margins, but those margins rely on assumptions that have not yet been validated by Amazon’s own reporting. When discrepancies emerge, the perpetual system becomes a black box that is difficult to explain to auditors or HMRC.

Amazon data limitations that affect both systems

Both periodic and perpetual systems are constrained by Amazon’s reporting structure. Amazon Seller Central is designed for operations, not statutory accounting.

Key limitations include:

• Settlement reports show cash movement, not transaction timing. Settlement periods do not align with calendar months, and refunds are often netted against future payouts.
• Inventory Ledger reports show unit movements but do not include per-unit cost, landed cost, or valuation adjustments.
• Inventory adjustments and reimbursements are delayed. Investigations can run beyond month-end, and reimbursements can be reversed months later.
• DD+7 reserve policies delay cash settlement, creating timing gaps between revenue recognition and bank deposits.
• Goods in transit and inventory reserved for fulfilment centre transfers are not clearly reflected in accounting cut-off dates.
• Multi-marketplace and multi-currency activity introduces foreign exchange effects that Amazon does not calculate for accounting purposes.

Because of these gaps, neither system can rely solely on Amazon data. Manual reconciliation remains necessary. The difference is when and how that reconciliation occurs.

How automation tools simulate perpetual COGS

Tools such as A2X and Link My Books attempt to bridge the gap by simulating perpetual inventory using settlement-based logic.

These tools work by:

1. Pulling Amazon settlement data via API.
2. Identifying units sold within each settlement period.
3. Applying seller-entered per-unit costs for each SKU.
4. Posting aggregated journal entries to accounting software such as Xero.
5. Reducing inventory and increasing COGS in batches rather than per transaction.

This creates the appearance of perpetual inventory. Inventory decreases and COGS increases regularly throughout the month.

However, the accuracy of this approach depends entirely on assumptions:

• That per-unit costs are correct and up to date.
• That settlement data captures all sales, including deferred transactions.
• That fulfilment and storage fees are treated consistently.
• That returns and reimbursements are handled correctly by the tool’s logic.

In reality, accountants frequently override or adjust automated entries. Cost changes mid-month, storage fees, NRV write-downs, reimbursement reversals, and return grading all require manual intervention. Automation reduces workload, but it does not eliminate the need for accounting judgement.

From a compliance perspective, automation should be supported by clear documentation and review procedures. Sellers should ensure they can explain how COGS is calculated, what assumptions are embedded in the tool, and how discrepancies are reviewed.

Choosing the “least wrong” system for your scale

For UK Amazon sellers, the question is not which system is theoretically correct. It is which system produces stable margins, accurate tax reporting, and defensible records.

In practice, most sellers use a hybrid approach:

• Periodic inventory as the control framework.
• Automation tools to reduce manual posting.
• Monthly reconciliation to Amazon Inventory Ledger reports.
• Manual adjustments for edge cases such as reimbursements, storage, and write-downs.

Smaller sellers with fewer SKUs and lower order volumes often achieve better results with a disciplined periodic system supported by spreadsheets. Larger sellers with higher volumes benefit from automation, but only when paired with regular reconciliation and documented policies. As complexity increases, the choice of automation and integration tools becomes critical, particularly where multi-marketplace selling and inventory reconciliation are involved. We break this down in detail in our guide to the best accounting software for Amazon sellers (UK).

As scale increases, system choice should be revisited. Multi-marketplace selling, high return rates, volatile supplier costs, or HMRC scrutiny are all signals that inventory accounting needs to evolve.

In practice, a system that reflects Amazon’s operational constraints is often more reliable than one based purely on textbook assumptions. For UK Amazon sellers, accuracy, auditability, and consistency matter more than the promise of real-time numbers that cannot be verified.

5. Inventory Inside Amazon FBA (Operational vs Accounting Reality)

Amazon FBA inventory data looks precise on the surface. Seller Central shows unit counts, movements, and statuses across fulfilment centres. For UK accounting purposes, that data is operational, not financial. Understanding the gap between how Amazon tracks inventory and how inventory is typically reflected under UK GAAP is important for accurate COGS, profit reporting, and audit-ready records.

This section explains how Amazon records inventory movements, why those records often do not align cleanly with accounting software like Xero, and how UK accountants commonly bridge the gap in practice.

How Amazon tracks inventory movements

Amazon tracks inventory at a unit and event level, not at a cost or valuation level. Every movement is recorded based on what happens physically inside Amazon fulfilment centres, not based on accounting recognition rules.

Amazon has consolidated much of its inventory reporting into the Inventory Ledger Report, which has replaced or superseded several legacy inventory reports over time. The Inventory Ledger records all physical inventory events, including receipts, shipments, returns, adjustments, transfers, removals, and disposals.

There are two important views:

• Detailed View, which shows individual inventory events with timestamps, fulfilment centre locations, and disposition changes. Update timing can vary and may be delayed relative to real-time events.
• Summary View, which aggregates movements by SKU and disposition over daily, weekly, or monthly periods. Refresh timing can vary and may lag behind the underlying events.

From an operational perspective, this is highly effective. Amazon can optimise stock placement, predict demand, and manage fulfilment capacity. From an accounting perspective, several problems arise.

Amazon’s inventory reporting does not typically provide:

• Landed cost per unit.
• Cost flow assumptions such as FIFO or weighted average.
• Net realisable value.
• Accrual cut off dates.
• Ownership terms such as FOB shipping point versus destination.

For example, when 100 units are received into a Manchester fulfilment centre, Amazon records the receipt immediately once scanned. Under FRS 102, the accounting treatment will depend on when ownership and risks transfer, typically evidenced by shipping terms, supplier documentation, and other supporting records. Amazon does not make that judgement.

The Inventory Ledger answers the question “Where are the units?”. Accounting needs to answer “What are they worth, and when should they be recognised?”. Those are different questions.

Inventory Ledger vs Settlement Report

Amazon provides two fundamentally different data sources that sellers often confuse.

The Inventory Ledger Report tracks physical unit movement.
The Settlement Report tracks cash movement and fees.

The Inventory Ledger shows events that never appear in the Settlement Report, including:

• Transfers between fulfilment centres.
• Inventory marked as stranded, unsellable, or under investigation.
• Customer returns before grading is complete.
• Lost inventory while reimbursement is pending.
• Expired or disposed stock before any cash adjustment.

The Settlement Report only shows transactions once there is a financial outcome, such as:

• A sale being settled.
• A refund being processed.
• A fee being charged.
• A reimbursement being paid.

This creates unavoidable timing gaps. This distinction is explored in more detail in our Amazon payout reconciliation step-by-step, which explains how settlement data should be used for cash accuracy, not inventory or margin calculation.

For example, inventory may be marked as lost in the Inventory Ledger in October, but the reimbursement does not appear in the Settlement Report until November or December. Under UK GAAP, any impairment is typically recognised when the loss (or reduction in recoverable value) becomes evident on the information available at the time, rather than when cash is received.

Tools such as A2X and Link My Books use both reports together. Settlement Reports are often used as a key evidence source for reconciling revenue and fees to bank deposits, subject to appropriate cut-off and classification checks. Inventory Ledger data is used to determine units sold and inventory status for COGS and write downs.

Relying on Settlement Reports alone can contribute to overstated inventory, delayed loss recognition, and distorted gross margins, which may be harder to explain if figures are reviewed.

Why FBA inventory never matches Xero automatically

Accounting software such as Xero is designed to track inventory as a financial asset. Amazon FBA is designed to track inventory as a physical object in motion.

The two systems rarely reconcile cleanly without additional configuration, reconciliation work, or manual adjustments.

Amazon tracks:

• Units.
• Locations.
• Status categories such as available, reserved, stranded, and unsellable.
• Real time operational events.

Xero tracks:

• Monetary value.
• Cost per unit.
• Aggregate inventory balances.
• Period end cut offs.
• Impairment and write downs under FRS 102.

Amazon does not provide per unit cost data. It does not track multiple supplier batches. It does not allocate fulfilment or storage costs to units. It does not apply NRV rules. Because of this, there is no reliable data feed that can post inventory balances directly into Xero.

Timing differences make the problem worse. Inventory events often appear in Seller Central after month end close. Settlement cycles cross accounting periods. Returns, reimbursements, and investigations can take weeks or months to resolve.

As a result, even inventory enabled accounting systems require:

• Manual journals.
• Month end accruals.
• Provisions for losses and returns.
• Reversals when outcomes change.

This is not a software failure. It is a structural mismatch between operational logistics data and statutory accounting requirements.

Timing gaps between stock movement and reimbursement

One of the most misunderstood areas of Amazon accounting is reimbursement timing.

Under Amazon’s processes (which can change and vary by case), lost or damaged inventory may be reimbursed automatically or via claims, and there is often a delay between the loss event and any reimbursement or cash settlement.

Under FRS 102, inventory is required to be measured at the lower of cost and net realisable value at each reporting date. If inventory is lost or unsellable, its NRV may be nil (or materially reduced), depending on recovery prospects and the evidence available at the reporting date, regardless of whether reimbursement has been approved.

Waiting for reimbursement before recognising the loss creates several risks:

• Inventory is overstated on the balance sheet.
• COGS is understated.
• Gross margin is artificially inflated.
• Losses and recoveries appear in the wrong accounting periods.

A commonly adopted approach among UK sellers is to:

• Recognise inventory write downs when losses occur or are probable.
• Accrue recoveries only when approval is probable.
• Reverse provisions when reimbursements are approved or denied.
• Maintain a loss and recovery register to track open cases.

For defensibility, this judgement should be documented, and approaches that defer loss recognition until cash receipt may be harder to support if reviewed.

The role of reserves and delayed adjustments

Amazon account level reserves create further confusion. These reserves affect cash timing, not inventory ownership.

A reserve is a portion of seller funds withheld by Amazon to cover refunds, chargebacks, or policy risk. It does not mean inventory is reserved or unavailable. Conversely, inventory marked as reserved or under review does not correspond to any specific cash reserve amount.

This disconnect leads to phantom inventory and phantom profits.

Common examples include:

• Stranded inventory written down in accounts but still appearing in Seller Central until disposal occurs.
• Removal orders cancelled or delayed while inventory continues to incur storage fees.
• Reimbursements approved but withheld in reserves for settlement cycles.
• Inventory found months later after a loss has already been written down and recovered.

Because reserves, investigations, and adjustments operate on different timelines, month-by-month reconciliation may not be exact and often requires documented explanations for timing differences. What matters is that:

• Inventory policies are consistent.
• Provisions are applied using clear probability thresholds.
• Adjustments are tracked and reversed correctly.
• Reconciliations are retained in line with applicable UK record-keeping requirements (often at least six years), alongside the supporting evidence used.

This approach is generally consistent with FRS 102 principles, can help support enquiry responses, and tends to improve the stability and explainability of financial statements when applied consistently.

Why this matters for UK Amazon sellers

Amazon FBA inventory accounting is not about achieving perfect alignment between Seller Central and accounting software. It is about producing defensible numbers that reflect economic reality.

UK sellers who understand this distinction:

• Make better pricing decisions.
• Avoid sudden margin shocks.
• Reduce the risk of avoidable issues if HMRC reviews the records.
• Scale without losing financial control.

Inventory inside Amazon is operationally precise but financially incomplete. The role of the accountant is to translate that operational data into compliant, explainable, and trustworthy financial records.

That translation is where good Amazon accounting lives.

6. Reimbursements, Write-Downs, and Inventory Losses

Inventory reimbursements are one of the most misunderstood areas of Amazon accounting and one of the quietest sources of margin distortion in UK ecommerce businesses.

Many sellers reconcile Amazon payouts accurately, yet still report volatile or unreliable gross margins because inventory losses and reimbursements are recognised inconsistently or in the wrong accounting period. The issue is not that reimbursements are rare. It is that they sit at the intersection of inventory valuation, cost of goods sold recognition, and Amazon’s operational delays.

This section explains how inventory losses arise within Amazon FBA, how Amazon calculates reimbursements, how reimbursements are commonly treated in UK accounting records (including Xero setups), and why timing differences can materially affect reported profitability.

Lost and damaged inventory in FBA

Under the Amazon FBA model, inventory remains legally owned by the seller, but operational control sits with Amazon. Losses arise when units are misplaced, damaged, destroyed, or rendered unsellable while in Amazon’s custody. Common scenarios include stock lost during internal warehouse transfers, damage during handling, or items returned by customers that Amazon determines cannot be resold.

From an accounting perspective, these events represent inventory losses, not fee adjustments or pricing issues. Under FRS 102, inventory should generally remain on the balance sheet only while it is expected, based on available information and reasonable judgement, to generate future economic benefit.

Once it becomes reasonably clear, using evidence and professional judgement at the reporting date, that a unit is unlikely to be recovered or sold, it may no longer meet the criteria to be carried as inventory.

At that point, the cost of the affected units is typically removed from the balance sheet and recognised as an expense, based on the entity’s policy and the evidence available. Depending on the accounting structure adopted, this may be presented through cost of goods sold or through a separate inventory loss or impairment line.

The critical point is timing and judgement. Inventory loss should be recognised when, based on available evidence, it is reasonable to conclude that recovery or sale is unlikely. This assessment is typically supported by Amazon inventory adjustment reports, investigation outcomes, ageing analysis, or removal confirmations.

Recognition is not typically deferred solely because a reimbursement has not yet been approved or paid, where the evidence indicates the inventory value is no longer recoverable. Delaying loss recognition until cash is received can overstate inventory values and defer expense recognition, which may inflate profit in the interim.

How Amazon calculates reimbursements

Amazon calculates reimbursements using its own operational and commercial logic, not accounting principles. If Amazon accepts responsibility for a lost or damaged unit, it will reimburse the seller based on an internal valuation methodology. Depending on the product, timing, and Amazon policy in force, the reimbursement is based on Amazon’s internal valuation methodology, which may not match the seller’s recorded landed cost and may be net of certain amounts.

This distinction matters because the reimbursement amount is not designed to mirror the seller’s landed cost or reverse cost of goods sold precisely. It is a compensation payment determined by Amazon, not a repayment of the original accounting cost.

As a result, reimbursement amounts frequently differ from the inventory cost recorded in Xero. In some cases, reimbursements are lower than cost. In others, they may exceed the original purchase price. Neither outcome should drive inventory accounting decisions.

Because Amazon’s reimbursement logic is operational rather than accounting-led, reimbursements should not be used as a substitute for inventory accounting. They should be recognised separately and reconciled back to inventory movements to prevent margin distortion and balance sheet misstatement.

When reimbursements reduce COGS versus create other income

Under UK accounting standards, reimbursements should be analysed based on what they are compensating for, not how they appear in Amazon settlements. A reimbursement is not revenue. It does not arise from a sale to a customer and, in most standard Amazon compensation scenarios, would not be reported as turnover.

Where a reimbursement relates to inventory that has already been written down or expensed through cost of goods sold or an inventory loss, the reimbursement represents a recovery of a previously recognised cost. This is also why reimbursements should be analysed separately from cash receipts shown in settlement reports.

In practice, there are common presentation approaches under FRS 102, provided the approach is applied consistently and documented clearly:

• Reimbursements may be recorded as other operating income, separate from revenue and cost of goods sold, making the recovery visible without distorting gross margin.
• Alternatively, reimbursements may be offset against inventory losses or cost of goods sold, but only where the original loss was recognised appropriately and within the same accounting framework.

A common defensibility risk is offsetting reimbursements against cost of goods sold in a later period where the original loss was not recognised, as this can distort period-by-period margins. That approach artificially improves gross margin and obscures the true cost of trading.

Timing mismatches between loss and reimbursement

One of the most common issues in Amazon accounting is the timing gap between inventory loss and reimbursement. A unit may be lost in March, identified in April, approved for reimbursement in June, and paid in July. If the loss is recognised only when the reimbursement arrives, several months of accounts may show overstated inventory and inflated profit.

Under accrual accounting, losses are typically recognised when, based on the information available at the reporting date, it is reasonable to conclude that the inventory will not be recovered or sold. This applies even where reimbursement remains uncertain or subject to investigation. Any reimbursement received later should be recognised in that later period as recovery income or as an offset to inventory losses, depending on the accounting policy adopted.

This timing mismatch explains why some sellers see sudden profit spikes in months with large reimbursements and unexplained margin compression in earlier months. The underlying business performance did not change. The accounting timing did.

Why reimbursements quietly inflate or suppress margins

Reimbursements are particularly problematic because they are small relative to revenue but large relative to margin. A £5,000 reimbursement in a business operating at a 20 percent gross margin can shift reported profitability by several percentage points if losses and recoveries are handled inconsistently.

When inventory losses are not recognised on a timely basis and reimbursements are netted against cost of goods sold or fees, margins appear stronger than they truly are. When losses are recognised late and reimbursements are treated as income without context, margins fluctuate unpredictably from month to month. In both cases, management accounts become unreliable, even if cash reconciliation is flawless.

For UK sellers, this can also create additional questions if records are reviewed by HMRC. Inventory write-downs, loss recognition, and reimbursements should be explainable through clear schedules showing when inventory left the balance sheet, what evidence supported the judgement at the time, and how subsequent reimbursements were treated. Without this audit trail, reimbursement-driven volatility can be difficult to explain and may raise questions about the consistency and reasonableness of accounting treatment.

Reimbursements are not an afterthought in Amazon accounting. They are a material inventory-related adjustment that is best tracked deliberately and assessed using reasonable judgement. When handled correctly, they stabilise margins and clarify true performance. When handled casually, they quietly undermine every profit figure that follows.

7. Reconciling Inventory and COGS in Xero

Reconciling inventory and cost of goods sold in Xero is one of the areas where Amazon accounting commonly breaks down in practice. Sellers can have perfectly reconciled Amazon payouts and still produce unreliable margins if inventory movements, COGS journals, and settlement timing are not handled consistently. The reason is simple. Xero records accounting logic, while Amazon operates on settlement logic. Bridging that gap requires structure.

This section explains how inventory and COGS commonly land in Xero for UK Amazon sellers, how journals are typically posted, and how to avoid common sources of duplication and timing distortion.

Inventory accounts versus expense accounts

Under FRS 102, inventory held for sale is typically recognised as a current asset until it is sold or written down, based on the entity’s accounting policies and the facts at the reporting date. This generally applies whether stock is held in your own warehouse or inside Amazon fulfilment centres. Operational control does not necessarily change who bears the key risks and rewards of ownership for accounting purposes.

A common error among Amazon sellers is expensing inventory purchases directly to a “Purchases” or “Cost of Sales” account when supplier invoices are paid. This creates immediate profit and loss volatility and breaks the matching principle. Costs appear before the related revenue, margins swing sharply from month to month, and the balance sheet understates assets.

A common structure in Xero separates three layers clearly:

• Inventory asset accounts on the balance sheet for stock held for sale.
• Cost of goods sold accounts that are only used when units are actually sold.
• Separate expense accounts for write-downs, losses, and non-inventory costs.

For FBA sellers, inventory should still sit on your balance sheet even though Amazon physically holds it. For FBM sellers, the same rules apply. For statutory accounts, limited companies typically present closing inventory as a current asset, supported by appropriate evidence such as inventory reports and/or physical counts.

If your balance sheet shows zero inventory despite ongoing sales, or if COGS closely mirrors purchase timing rather than sales volume, it can indicate that inventory is being expensed too early.

Posting COGS journals correctly

Amazon does not provide unit-level cost data. That means COGS does not automatically post itself in Xero. It typically needs to be calculated and recorded using a consistent method and supporting records.

For most UK Amazon sellers, this is done using a periodic inventory approach. At the end of each accounting period, COGS is calculated using the formula:

Opening inventory
plus purchases and landed costs
minus closing inventory

The resulting figure represents the cost of inventory consumed during that period. A single journal is then posted to move that value from the inventory asset account to cost of goods sold.

COGS is often posted monthly at period end, not per Amazon settlement. Settlement cycles do not align with accounting periods, and posting per settlement can create timing distortions unless cut-off is managed carefully. Posting monthly often helps match costs to the period in which sales are recognised, rather than to cash receipt timing, provided cut-off is applied consistently.

Supporting documentation matters. If figures are reviewed, you may be asked by HMRC for evidence on how COGS was calculated, not just the final journal.. This typically includes supplier invoices, landed cost calculations, and an Amazon inventory snapshot at period end.

Clearing inventory through settlement cycles

Amazon settlement reports are cash documents. Inventory and COGS are accrual concepts. Reconciling one does not reconcile the other.

When a sale occurs, revenue and the related costs are typically recognised when control of the goods transfers to the customer, which in many Amazon retail cases aligns closely with dispatch. Cash may not arrive for weeks due to Amazon settlement cycles and reserve holds. To manage this, many sellers use an Amazon clearing account in Xero (or a similar control account structure).

The clearing account records amounts owed by Amazon between the sale date and the payout date. When the settlement is received, the clearing balance is cleared to the bank account and fees are recorded. Inventory movement is not involved in this step.

Problems arise when sellers attempt to “clear” inventory using payout figures. Payouts are net of fees, refunds, and reserves. They bear no relationship to the cost of inventory consumed. Using them as a proxy for COGS can materially reduce margin accuracy.

Settlement reports validate sales volume and cash timing. They do not explain inventory consumption.

Handling timing differences cleanly

Timing differences are unavoidable in Amazon accounting. Goods can be in transit at month end. Inventory losses may be identified weeks before reimbursements are approved. Settlements routinely cross accounting periods.

Under FRS 102, inventory should be recognised based on ownership at the reporting date. Goods in transit should be included or excluded depending on shipping terms. Known or probable inventory losses are typically recognised when sufficient evidence exists that recovery is unlikely, rather than being driven solely by the timing of Amazon approval or payment.

When reimbursements arrive later, they may be treated as recoveries (for example as other operating income or as an offset to inventory losses), depending on the accounting policy adopted. What matters is consistency, evidence, and documentation.

Ignoring timing differences does not make them disappear. They can accumulate across periods, inflate or suppress margins unpredictably, and may lead to later corrections if cut-off is revisited.

Avoiding double-counting between inventory and fees

The final failure point is duplication. Amazon fees are already deducted from settlements, and automation tools post them into Xero. Problems arise when the same fees are also embedded into COGS calculations or manual journals.

Referral fees, fulfilment fees, storage charges, and advertising costs are generally presented in one place (either within COGS-style reporting or within operating expenses) and should not be double-counted. Fulfilment fees may be treated as a variable cost of sale or as an operating expense, provided the policy is applied consistently and the cost is not duplicated. Storage fees are typically presented below gross margin because they relate to inventory holding rather than unit-level sale activity.

Monthly controls prevent this. Fee totals from settlement reports should reconcile closely to fee expense accounts in Xero, with any differences explained (for example cut-off, corrections, or mapping issues). COGS should reconcile to inventory movement, not to payouts. If gross margins swing without a clear operational reason, duplication is usually the cause.

Reconciling inventory and COGS in Xero is not about automation alone. It is about separating cash logic from cost logic, applying UK accounting rules consistently, and maintaining an audit trail that explains every material movement. When applied consistently with a clear audit trail, this approach can stabilise margins, improve management reporting, and make queries easier to evidence.

8. VAT and Inventory Accounting for Amazon Sellers

VAT and inventory accounting cannot be treated as separate disciplines for UK Amazon sellers. Inventory movements can affect VAT recovery and VAT registration considerations. For example, holding stock in the UK or increasing taxable turnover above the statutory registration threshold can trigger mandatory VAT registration.

The mechanics of how the UK VAT threshold works are explained in more detail in our UK VAT Thresholds Explained guide. Many compliance issues arise from poor alignment between inventory records, write-downs, and Amazon operational data, rather than from VAT rate selection alone.

This section explains how VAT interacts with inventory purchases, write-offs, reimbursements, and cross-border stock holding in an Amazon FBA context, and why disciplined inventory accounting is important for VAT compliance.

VAT on purchase of inventory

Inventory purchased for resale is often acquired for taxable business supplies, depending on what the business sells and whether any exemption or partial exemption restrictions apply. Where the seller is VAT registered and holds valid documentation, input VAT is often recoverable to the extent it relates to taxable business activities and the normal recovery conditions set out in HMRC’s VAT Notice 700 are met. For accounting purposes, inventory is normally recorded exclusive of VAT on the balance sheet, with VAT posted separately to the VAT control account.

For example, if a UK Amazon seller purchases £10,000 of stock plus £2,000 VAT, the inventory asset is recorded at £10,000. The £2,000 VAT is typically claimed through the VAT return, subject to normal recovery conditions and evidence requirements. Capitalising recoverable VAT into inventory can overstate assets and may be questioned if records are reviewed.

The same principle applies to import VAT. Under HMRC’s Postponed VAT Accounting (PVA) system, import VAT is accounted for on the VAT return rather than being paid upfront at import, subject to the import process used and the supporting documentation available. Recoverable import VAT is not normally part of landed cost for accounting purposes; non-recoverable VAT may form part of cost in some cases. Only customs duty, freight, insurance, and clearance fees increase the inventory value under FRS 102.

Postponed import VAT statements should be downloaded and retained as part of the VAT evidence trail, as missing documentation can make VAT recovery harder to support if reviewed.

VAT implications of inventory write-offs

Accounting write-downs and physical disposals are distinct for VAT purposes.

Writing inventory down in the accounts, for example due to obsolescence, damage, or lower net realisable value, has no VAT impact on its own. The original VAT recovery remains valid provided the inventory was purchased for taxable business use. An impairment entry does not retrospectively invalidate input VAT already reclaimed.

VAT implications commonly arise when inventory is physically disposed of, and the treatment can depend on the specific facts and documentation. Scrap sales attract output VAT. Destruction or donation with no consideration may not give rise to output VAT in many cases, but the position depends on the facts, the nature of any deemed supply rules, and the evidence retained. Where Amazon FBA removal or destruction services are used, sellers should retain evidence showing what happened to the stock and when.

Repeated write-downs without corresponding disposal evidence can be harder to support, and consistency between accounting entries, Amazon reports, and physical outcomes is an important part of an audit trail.

Reimbursements and VAT treatment

Amazon reimbursements for lost or damaged inventory are often treated as outside the scope of VAT where they are properly characterised as compensation rather than consideration for a supply. The correct VAT treatment depends on the nature of the reimbursement and should be assessed based on what the payment is compensating for, rather than how it appears in Amazon settlement reports.

Input VAT recovered when the inventory was purchased will usually remain recoverable where the purchase related to taxable business activities and the business remains entitled to recover VAT under normal rules. A reimbursement receipt does not usually require a VAT adjustment where it is genuinely compensation and not consideration for a supply, even if it differs from the original cost.

For example, if £1,000 of inventory plus £200 VAT is written off and Amazon later reimburses £600, the full £200 VAT recovery remains valid. The £600 reimbursement is recorded in the accounts, but no VAT is charged or reclaimed on it.

This treatment differs from customer refunds, which reverse a taxable supply and may affect output VAT. Confusing these two flows is a common and costly error.

Cross-border inventory and VAT risk

Holding inventory in a country often creates a local VAT registration obligation, subject to local VAT rules, how the inventory is held, and the seller’s specific fulfilment arrangements, as explained in more detail in our VAT registration for Amazon sellers guide. In many jurisdictions, holding stock locally can trigger VAT registration requirements regardless of sales volume, but the exact rules are country-specific..

OSS and IOSS schemes simplify reporting of certain cross-border sales under EU VAT rules, but they generally do not replace local registration obligations where inventory is physically stored, subject to the rules in each country. Amazon’s automatic redistribution of stock across fulfilment centres increases this risk, particularly for UK sellers using European FBA networks.

HMRC and EU tax authorities may assess VAT retrospectively where undeclared stock movements are identified, and interest and penalties may apply depending on the facts, behaviour, and local rules. Sellers relying on a single inventory balance without location tracking are particularly exposed.

Common HMRC red flags in stock accounting

HMRC attention is often triggered by patterns rather than single errors. Common red flags include inventory appearing in the accounts without a corresponding VAT registration, reimbursements recorded without prior inventory write-downs, repeated write-offs unsupported by evidence, and discrepancies between Amazon inventory reports and accounting records.

Robust controls reduce this risk. Monthly inventory reconciliation, documented net realisable value testing, reimbursement logs, and clear separation of inventory by country can help demonstrate a disciplined approach and provide a clearer evidence trail.

VAT and inventory accounting are inseparable in Amazon businesses. Sellers who treat inventory as a compliance afterthought often inherit VAT problems later. Aligning inventory movements, write-downs, and reimbursements consistently can reduce avoidable risk, stabilise reporting, and improve the ability to respond to HMRC questions if they arise.

9. Common Inventory and COGS Errors Amazon Sellers Make

Inventory and cost of goods sold errors often do not present clearly in Amazon businesses. They can accumulate quietly, distort margins over time, and may go unnoticed until a review, audit process, or cash flow pressure prompts a closer look. By the time the issue becomes visible, it has usually been present for months or even years.

Many UK Amazon sellers assume that if payouts reconcile and VAT returns file without errors, their accounting is broadly correct. In practice, inventory and COGS mistakes sit outside the settlement cycle. They live in the balance sheet, in journal timing, and in classification decisions that never appear on Amazon dashboards.

This section surfaces the most common inventory and COGS errors seen in UK Amazon businesses, explains how they arise, and shows why they matter under UK accounting rules and HMRC scrutiny.

Margins improving for the wrong reasons

When gross margins improve, sellers naturally assume something positive has happened. Prices must have increased, supplier costs must have fallen, or operations must have become more efficient. In many Amazon businesses, however, margin improvement may reflect accounting timing or classification effects rather than commercial performance.

The most common cause is accounting timing error.

Under FRS 102, gross margin is an accounting outcome driven by revenue recognition and cost recognition. It is not the same thing as unit economics or contribution margin calculated inside Seller Central. When inventory accounting is weak, reported gross margin can move independently of pricing, landed costs, or Amazon fees.

One frequent cause is overstated closing inventory. Because cost of goods sold is calculated as opening inventory plus purchases minus closing inventory, any overstatement of closing stock directly understates COGS. That understatement flows straight into gross profit.

This often happens when obsolete or unsellable stock is left on the balance sheet at full cost, when inventory losses are reimbursed but never written off, or when physical and system counts are never reconciled. The seller sees margins rise and assumes performance has improved, when in reality costs have simply not been recognised.

Delayed COGS recognition creates a different distortion. Supplier invoices arrive after month end, inventory is sold before costs are recorded, and COGS is pushed into the following period. One month looks unusually profitable, the next unusually weak. Over time, this produces volatile margin trends that have no operational explanation.

From an audit or HMRC perspective, unexplained margin expansion can attract scrutiny. If gross margin improves year on year without an obvious commercial driver, inventory valuation and COGS timing are often areas worth reviewing first. In some cases, the apparent “improvement” reduces once inventory and COGS are adjusted for timing and valuation issues.

Inventory never tying to reality

In Amazon businesses, inventory balances rarely reconcile perfectly without adjustment. Timing differences between Amazon systems and accounting cut offs are normal. What is not normal is persistent, unexplained divergence.

Amazon inventory reports are generated on operational timelines. Accounting systems close on reporting dates. Returns, inter-fulfilment centre transfers, reimbursements, and removals all introduce delays. Small differences (for example one to two percent) can occur due to timing, and are generally easier to support where they are identified and clearly explained.

Problems arise when those differences accumulate.

When inventory is not reconciled regularly, missing losses, rejected returns, stranded stock, and delayed transfers stack up silently. The balance sheet drifts away from economic reality. At that point, COGS becomes unreliable because it is calculated using an inventory figure that no longer represents what the business actually owns.

This is not just a reporting issue. If inventory cannot be reconciled, gross margin cannot be trusted. Pricing decisions, reorder quantities, and cash planning all become guesswork.

Static or implausible inventory balances can become difficult to support if records are reviewed. If inventory appears unchanged despite ongoing sales activity, HMRC may reasonably expect a clear explanation supported by supplier invoices, inventory movement reports, and reconciliation schedules. Without that documentation, inventory valuation may be challenged and could require further analysis or adjustment.

Regular reconciliation is a strongly defensible approach. The goal is not perfection. The goal is that every difference is understood, documented, and either corrected or expected to reverse in the next period.

Reimbursements treated as sales

One of the most damaging errors Amazon sellers make is treating reimbursements as revenue.

Amazon reimbursements are compensation payments. They arise when Amazon loses inventory, damages stock, miscalculates fees, or makes operational errors. They are not consideration from a customer, and they are not revenue under FRS 102.

Customer refunds reduce revenue. Amazon reimbursements do not. Conflating the two creates serious distortion.

When reimbursements are posted to sales accounts, turnover is inflated, gross margin improves artificially, and VAT errors are introduced. Because reimbursements have no associated COGS, every pound misclassified as revenue increases reported margin.

VAT treatment of Amazon reimbursements requires careful analysis. In many cases, reimbursements are treated as outside the scope of VAT rather than as consideration for a taxable supply. Incorrectly applying output VAT to amounts that are not taxable supplies can lead to overdeclared VAT and distort VAT returns.

HMRC has access to platform-reported sales data, and discrepancies between VAT returns and marketplace activity may attract further review. For that reason, reimbursement treatment should be reviewed carefully and applied consistently.

Correct treatment depends on the nature of the reimbursement. Compensation for lost or damaged inventory is commonly recorded as other income, with the inventory loss recognised separately when it becomes evident, in line with the entity’s accounting policy. Fee adjustments would normally reverse the original expense. Customer refunds typically reduce revenue or are recorded through a contra-revenue account.

What matters most is traceability. Reimbursements are easiest to evidence where they are linked to a specific underlying event, coded consistently, and reconciled regularly to settlement reports. Without that discipline, reimbursements can inflate reported performance and weaken the integrity of financial reporting.

FBA fees buried incorrectly in COGS

Amazon fees sit at the intersection of cost of sale and operating expense, and inconsistent treatment is a common source of margin confusion.

Some sellers include fulfilment fees in COGS. Others present them below gross margin as operating costs. Both approaches can be acceptable if applied consistently and transparently. Problems arise when fees move between categories month to month, or when some fees are included in COGS and others are buried in operating expenses.

When fees are excluded from COGS, gross margin appears stronger than the underlying economics. When they are double counted, margins collapse unexpectedly. In both cases, the issue is not the chosen presentation but the lack of a coherent policy.

In reviews, the key practical issue is usually whether the treatment is consistent, documented, and reconcilable to Amazon settlement data, rather than the precise presentation line chosen. If gross margin improves while fulfilment costs spike below the line, it may prompt questions about classification and consistency.

Clear account structures and monthly fee reconciliations are essential. COGS should reconcile to inventory movement. Fee accounts should reconcile to settlement reports. When those controls are in place, margin analysis becomes meaningful rather than misleading.

Ignoring unsellable and stranded stock

Under UK GAAP, inventory is generally measured at the lower of cost and net realisable value. In Amazon businesses, this requirement is routinely ignored.

Unsellable stock, stranded listings, slow-moving SKUs, and suppressed ASINs often remain on the balance sheet at full cost long after their recoverable value has collapsed. Because Amazon continues to show unit counts, sellers assume the inventory still has value.

Under UK accounting rules, that assumption is not sufficient. Net realisable value is required to be assessed based on expected selling price less costs to sell. A defensible position is supported by evidence of the assessment, such as aged inventory reports, sell-through data, pricing history, and documented decisions to discount, remove, or destroy stock.

Failing to write down impaired inventory overstates assets and understates COGS. The effect is cumulative. Each month the adjustment is delayed, margins look slightly better than reality. Over time, the distortion becomes material.

Regular reviews of aged inventory are not an administrative burden. They are a core control that protects both reported profit and tax compliance.

Trusting Amazon inventory totals blindly

Amazon inventory reports are operational tools. They are not accounting records.

Amazon controls storage, fulfilment, and movement of stock, but the seller retains ownership and valuation responsibility. That distinction matters. Amazon reports quantities. Accounting records value.

Blindly trusting Amazon totals without reconciliation ignores timing delays, system limitations, and classification differences. It also ignores the legal requirement to present inventory fairly under UK GAAP.

Professional inventory accounting does not reject Amazon data. It reconciles to it, challenges it where necessary, and documents the outcome. That process is what transforms operational data into defensible financial reporting.

For UK Amazon sellers, inventory errors rarely come from fraud or intent. They come from assumptions. The belief that Amazon “handles inventory” is one of the most costly assumptions in e-commerce accounting.

Treating inventory and COGS as structured accounting areas (rather than as by-products of settlements) can stabilise margin reporting, improve decision-making, and reduce avoidable compliance risk.

10. Month-End Inventory & COGS Review Checklist

Month-end inventory and cost of goods sold reviews sit at the centre of reliable Amazon accounting. For UK e-commerce businesses, this process is not just about producing tidy management accounts. It can affect VAT accuracy, corporation tax exposure, cash flow forecasting, margin credibility, and the quality of records available in an HMRC review.

This process is easiest to implement using a structured control document, which is why we provide an Amazon seller bookkeeping checklist covering inventory, COGS, and reconciliation checks. Amazon Seller Central provides vast amounts of operational data, but that data does not become accounting evidence until it is reviewed, reconciled, and translated into UK GAAP-compliant journals. This checklist turns that translation into a repeatable control process.

The objective is simple. Every material movement of stock should be explainable. Every pound of COGS should be capable of being aligned with real sales. Margin movements should be understandable in light of documented operational and accounting drivers.

Review inventory movements for the month

A proper month-end review always starts with inventory movements, not with the closing balance on the balance sheet. Closing figures are the result of activity. If the activity is wrong, the balance will be wrong too.

For Amazon sellers, the underlying source data lives in Seller Central. Reports designed to reconcile inventory movements to a period-end position (for example inventory reconciliation-style reports) are commonly used as the backbone of the review. More granular inventory ledger or event-level reports are then used to investigate individual discrepancies.

As a baseline, the monthly review typically checks that the following movement categories appear complete and reasonable for the period:

• Inbound shipments received into Amazon fulfilment centres
• Units sold and shipped to customers
• Customer returns that were restocked or written off
• Inventory adjustments for loss, damage, or found units
• Removal orders and disposals
• Transfers between fulfilment centres or marketplaces

The accounting logic underpinning the review is straightforward. Closing inventory equals opening inventory plus receipts, minus units sold, plus or minus returns, minus losses, write-offs, and removals. What matters is evidencing each component.

In practice, issues often arise around timing. Goods may be physically received by Amazon in the last days of the month, but the supplier invoice has not yet arrived. Under UK accrual accounting, those goods still form part of inventory if control has passed. Excluding them understates stock and overstates margins. The review should therefore include a check for goods received but not yet invoiced, with accruals posted where appropriate.

This movement-first approach matters because inventory balances are easier to support when they are built up from underlying movements and evidence. In an enquiry, you may be asked to demonstrate how stock figures were built up from underlying transactions, supported by Amazon reports and other records. A reconciled movement schedule is far more defensible than a static closing number pulled from software.

Confirm COGS postings align with sales

Cost of goods sold is not something Amazon calculates for you. It typically needs to be calculated using a consistent method and posted with supporting working papers.

Automated feeds and integrations help, but they do not replace a proper month-end review.

Under UK GAAP, costs are required to be recognised in the same accounting period as the related revenue. For product-based e-commerce, the practical anchor is when goods are dispatched or shipped, because that is typically when control transfers to the customer. For Amazon FBA sellers, the shipment date is therefore usually the correct reference point. Order date and settlement payout date are not suitable for COGS recognition.

A robust review confirms that:

• Units shipped in the month align with the revenue recognised
• COGS has been posted for those units, once and only once
• Returns accepted into sellable inventory have had their COGS reversed
• No COGS entries exist for units still sitting unsold in fulfilment centres

The cost per unit used in COGS also needs to be supportable and applied consistently. For UK Amazon sellers, landed cost typically includes product cost, inbound freight, import duties, and directly attributable preparation or packaging costs. It does not include referral fees, fulfilment fees, storage charges, advertising spend, or software subscriptions. Those belong in operating expenses.

The accounting entry itself is simple. COGS is debited, inventory is credited. What makes it complex is volume, timing, and consistency.

Reasonableness checks are essential. Sudden shifts in COGS as a percentage of revenue should be questioned. If February sales are similar to January but COGS is materially lower, something has likely been missed. If COGS spikes without a clear change in product mix or unit costs, duplication or misposting may be the cause.

This step protects margins. It also reduces the risk of challenge where COGS cannot be evidenced or explained, because the business cannot show how figures were derived or matched to sales.

Check reimbursement activity

Amazon reimbursements are one of the most misunderstood areas of e-commerce accounting. They are not sales and do not represent operational revenue, and they should not be used as a substitute for recognising underlying inventory losses or cost adjustments.

Reimbursements are compensation payments for specific events, such as lost inventory, damaged goods, or incorrect fees. They should be reviewed alongside inventory adjustment reports, not in isolation.

A disciplined process follows a clear sequence. First, the loss or overcharge is identified. Second, the accounting loss is recognised when it occurs, not when cash arrives. Third, a claim is filed with Amazon. Finally, when the reimbursement is paid, a recovery entry is posted.

Waiting for reimbursement before recognising a loss artificially inflates inventory and margins. Equally, recognising reimbursements without first recording the underlying loss creates distorted profit figures.

From a VAT perspective, reimbursements are typically compensation rather than consideration for a supply, so they are usually outside the scope of VAT. However, classification still matters. Fee corrections, price adjustments, and inventory compensation should be analysed by type and documented, rather than treated as a single generic income stream.

Strong businesses maintain an unreimbursed loss tracking schedule. This records the date discovered, ASIN, quantity, cost, claim status, and days ageing. It ensures claims are filed within Amazon deadlines and prevents silent margin leakage when reimbursements are missed or ignored.

Review write-downs and losses

UK GAAP requires inventory to be carried at the lower of cost and net realisable value. Net realisable value means the amount the business realistically expects to recover from selling the stock, after deducting costs to complete and sell.

This assessment is typically performed at each reporting date. It is not optional, and it does not depend on physical disposal of goods.

For Amazon sellers, common triggers include stranded listings, unsellable stock, products with no sales for extended periods, and items approaching mandatory removal deadlines. Storage fees and declining market prices also affect recoverability.

A proper review identifies at-risk items using Seller Central reports, then assesses what those items could actually be sold for in the current market. The calculation should be documented. Estimated selling price, less removal fees, marketplace fees, and shipping allowances, equals NRV.

If NRV is lower than cost, a write-down is required. The accounting entry records an impairment loss and reduces inventory. COGS should not be used for this purpose, because the goods have not been sold.

Write-downs that lack evidence can be difficult to support if reviewed by HMRC. Screenshots of comparable market prices, inventory ageing reports, and clear calculations turn subjective judgement into defensible accounting.

Validate margin consistency

Margins tell a story. Month-end reviews should test whether that story makes sense.

Gross margin should be compared to prior months and to the business’s own historical range. Sudden improvements without operational change often indicate missing COGS, delayed write-downs, or large reimbursements hitting the period. Sudden collapses usually signal duplicated costs or unrecorded losses.

Effective validation uses both percentage and absolute thresholds. A two percentage point movement might be immaterial in a small business but significant in a larger one. Conversely, a modest percentage shift could represent thousands of pounds.

It is also important to distinguish operational margin from accounting noise. Reimbursements and inventory write-downs are non-recurring by nature. They should be visible and explainable, not buried inside COGS or sales.

When margins are stable and movements are explainable, management decisions improve. Pricing, purchasing, and cash flow planning all rely on credible margin data.

Retain inventory audit evidence

Every number in the month-end review should be traceable back to evidence. For UK limited companies, retaining records for at least six years is standard practice, and many businesses retain them longer due to HMRC enquiry time limits and VAT obligations.

Evidence should include Amazon inventory reports, COGS calculations, landed cost workpapers, reimbursement logs, write-down assessments, and reconciliation schedules linking Seller Central data to the general ledger.

Storage should be digital, organised by month, and searchable. Under Making Tax Digital, maintaining clean digital links between Amazon, accounting software, and supporting documents is increasingly important.

Good evidence retention does more than satisfy HMRC. It can reduce stress during audits, speed up year-end accounts preparation, and support smoother funding rounds or business exits by making numbers easier to evidence. Buyers and lenders often value businesses that can explain their numbers clearly with supporting evidence.

11. Action Plan: Fixing Margins and Scaling Profitably

This action plan is designed for UK Amazon sellers whose margins do not match commercial reality. It translates accounting accuracy into operational clarity, so margin decisions are based on facts rather than assumptions.

What to fix first if margins look wrong

When margins move unexpectedly, the root cause is rarely pricing or marketing strategy. In many cases, the issue sits inside inventory valuation, cost recognition, or timing mismatches between Amazon activity and accounting records.

The first priority is usually reconciliation, not optimisation. Before changing prices, advertising spend, or supplier terms, sellers should confirm that revenue, inventory, and cost of goods sold align with Amazon Seller Central data.

In practice, this means reconciling three areas together:

• Revenue per shipment date, not order date or settlement date
• Inventory movements, including inbound receipts, sales, returns, losses, and removals
• COGS posted for the same units and period as recognised revenue

Many margin distortions come from missing or misclassified direct costs. Common examples include inbound freight not capitalised into inventory, import duty treated as overhead instead of product cost, or returns handled inconsistently between revenue and inventory. These omissions often inflate gross margin without any real improvement in profitability.

Under UK GAAP, inventory should be measured at cost and expensed when sold. That cost normally includes product cost, inbound shipping, packaging, and import charges. Amazon referral fees, fulfilment fees, storage fees, and advertising costs are generally service costs rather than acquisition costs. Some businesses include certain Amazon fees within COGS for internal margin analysis, while others treat them as operating expenses. What matters is consistency, disclosure, and that reported margins reflect economic reality.

Timing is another frequent issue. Inventory received late in the month but expensed early, or sales recognised before COGS is posted, can cause sharp month-to-month swings. These swings can reflect accounting timing effects rather than changes in underlying trading performance.

Finally, inventory impairment is typically considered as part of the period-end review. Stock that is stranded, unsellable, slow-moving, or approaching Amazon removal deadlines may no longer be worth its original cost. If net realisable value is assessed as lower than cost, a write-down may be required under FRS 102, even if the stock has not yet been disposed of.

Until these fundamentals are fixed, margin analysis is unreliable.

When spreadsheets stop working

Spreadsheets are often adequate in the early stages of an Amazon business. As transaction volume increases, they become harder to control and easier to break.

Problems usually emerge when sellers manage:

• Hundreds of SKUs
• Frequent inbound shipments
• Daily sales and returns
• Multiple users editing the same files

At that point, spreadsheets stop acting as records and start acting as estimates.

From a compliance perspective, spreadsheets themselves are not prohibited under Making Tax Digital. The risk arises when data is manually re-keyed, adjusted outside a controlled process, or copied between systems without digital links. These practices weaken audit trails and make figures difficult to defend during an HMRC enquiry.

Operationally, spreadsheets struggle to keep pace with Amazon’s reporting cadence. Inventory adjustments, reimbursements, returns, and transfers often appear days or weeks after the original event. Manual tracking increases the risk that losses are missed, reimbursements are double-counted, or COGS is posted late.

A common warning sign is decision paralysis. When sellers no longer trust their margin reports, they delay pricing decisions, advertising changes, or reordering. At that stage, the issue is not lack of data but lack of control.

When to automate inventory and COGS

Automation should be introduced to solve specific problems, not simply because turnover has increased.

Typical triggers include:

• Repeated reconciliation differences between Amazon and the general ledger
• Missed or duplicated COGS postings
• Difficulty tracking reimbursements and inventory losses
• Increasing HMRC or investor scrutiny

Tools such as A2X and Link My Books create structured links between Amazon Seller Central and accounting software like Xero. These links support Making Tax Digital by reducing manual intervention and preserving transaction-level audit trails.

Automation also improves visibility. Reimbursements can be tracked from loss discovery to payment. Inventory movements can be tied directly to journals. Exceptions are flagged rather than hidden inside spreadsheets.

Implementation should be deliberate. A parallel run, where automated outputs are compared to existing reports for one or two months, helps validate configuration and cost mapping before relying on the system fully.

Automation improves accuracy, but it does not replace judgement.

When to involve an Amazon accountant

Software can process data, but it cannot interpret accounting standards or commercial risk.

Professional input is essential when making decisions about:

• COGS methodology and landed cost composition
• Inventory impairment and write-downs
• Reimbursement classification and timing
• VAT treatment of Amazon transactions
• Prior-period corrections

As businesses scale, small errors compound. A missed loss, an overstated inventory balance, or misclassified fees can distort margins for months before being discovered. Correcting these issues later often requires backdated adjustments and explanations to HMRC or buyers.

Ongoing advisory support prevents this accumulation. Instead of fixing problems after the fact, controls are embedded into month-end processes so issues are identified early.

If you require tailored advice, consult a qualified accountant experienced in e-commerce and UK GAAP.

Before contacting an e-commerce accountant, it is often useful to gather:

• Recent Amazon inventory and settlement reports
• Current margin reports
• A description of how COGS is currently calculated
• Any known reconciliation issues

A structured review typically identifies timing errors, missing costs, or classification problems quickly. Classification and timing issues can often be corrected within weeks. Inventory write-downs, historical reconciliations, or reimbursement backlogs may take longer, depending on data quality and volume.

The goal is not just to correct one month’s figures, but to establish a repeatable process that keeps margins accurate as the business grows.

Bottom line

When margins do not make sense, the answer is rarely to push harder on sales. It is to slow down, reconcile the numbers, and fix the accounting foundations. Accurate inventory and COGS tracking restores confidence, supports compliance, and allows profitable growth decisions to be made with clarity. For a broader framework covering VAT, reconciliation, bookkeeping, and inventory together, see our Amazon Seller Accounting – Complete Guide.