Skip to content
  • There are no suggestions because the search field is empty.

Fix Amazon Settlement Income Mismatch From Cross-Month Settlements in Webgility Online

Understand why a Sales Income total can look short on a settlement that spans two months, and post the missing piece so the figures match.

Overview

You are seeing a Sales Income figure in QuickBooks that is lower than the product-charges total on your Amazon settlement report, and you cannot find where the rest of the amount went. This usually happens when the settlement period crosses a month end — Webgility Online splits the settlement into one journal entry per calendar month, and one of those entries has not been posted yet.

When This Applies

This applies to Webgility Online users posting Amazon settlement reports to QuickBooks whose settlement period starts in one calendar month and ends in another, and whose QuickBooks Sales Income total for the settlement does not match Amazon's product-charges total.

Why This Happens

Webgility Online records sales in the calendar month in which they actually happened. When a single Amazon settlement spans a month boundary, each of the four transaction categories the settlement carries — orders posted as invoices or sales receipts, fees, reserves and refund adjustments, and FBA inventory adjustments — is split into one journal entry per month, so a Dec 29–Jan 12 settlement becomes a Dec 29–Dec 31 part and a Jan 1–Jan 12 part. Each part has to be posted individually; the Sales Income you see in QuickBooks only reflects the parts you have already posted.

Important Note: "A settlement whose period falls entirely inside one calendar month does not split — it posts as a single journal entry, which is why your next settlement can match exactly while the cross-month one does not."

Steps to Post the Missing Journal Entry

Step 1: In Webgility Online, go to Sales > Orders, open the Settlements view for the Amazon channel, and locate the settlement whose total does not match QuickBooks.

Step 2: Expand the settlement to view the per-month parts listed inside it, and identify the part marked Not posted — this is the slice that is missing from QuickBooks (the setup walk-through for Amazon settlement posting is in How to Post Amazon Settlement Reports in Webgility Online).

Step 3: Click Post on the Not-posted part so Webgility Online creates the second journal entry in QuickBooks for the earlier or later month-slice.

Step 4: In Webgility Online, click the Refresh button on the settlement screen to download the latest QuickBooks data (full walk-through in Download the Latest Data from QuickBooks in Webgility Online), then re-open your Sales Income report in QuickBooks — the total should now equal Amazon's product-charges figure.

Key Recommendation

Before investigating a mismatch, open the settlement in Webgility Online and check whether its start and end dates fall in different calendar months — if they do, expect two journal entries and confirm both are posted before reconciling against Amazon's number.

Additional Support

If the Sales Income still does not match after posting both month-slices, contact support@webgility.com with the settlement identifier, the date range, the product-charges total from Amazon, and a screenshot of the Settlements view showing both month parts and their posted status.