Skip to main content
Visionnment Estimate value
Menu

Operator Systems

Reconcile an Amazon V2 Settlement Report Before Calling It Profit

Import signed V2 settlement amounts correctly, classify unknown rows, match the bank deposit, and bridge cash to operating earnings.

A magnifier inspecting financial, traffic, technical, and ownership evidence in an acquisition dossier.

Reconcile an Amazon settlement in three stages: reproduce the report's signed amounts, match the actual bank receipt, and explain the difference between that cash and operating earnings. A deposit is not a profit figure.

Format notice checked November 4, 2026: Amazon's March 9, 2026 announcement specifies November 11, 2026 as the removal date for its old XML and Flat File settlement report types. The replacement is Flat File V2; an XML replacement is not provided. Compare your actual export and parser with the documented replacement rather than relying on an old spreadsheet name.

Identify the actual report and scope

Preserve the original export before opening it in a spreadsheet. Record the report type, account/store scope, settlement identifier, start and end dates, deposit date, and currency. Keep the export's source date with any transformed workbook.

Amazon's settlement report reference identifies GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2 and its general amount fields. Its detail structure includes amount-type, amount-description, and signed amount. Do not infer the type solely from the file extension.

Choose one settlement first. Combining several currencies and periods before understanding one report makes unexplained differences harder to locate. Exclude private customer data from any training copy shared for assistance.

Import delimiters and local numbers deliberately

Inspect how the raw file separates fields and represents decimals before accepting an automatic import. Amazon documents localized amount formatting, including comma decimals. A value such as 95,00 cannot safely become 9500 because an importer removed punctuation.

Set the appropriate delimiter and numeric locale explicitly in your spreadsheet or parser. Compare several imported values with the untouched file, including a positive amount, a negative amount, and a fractional value.

Keep identifiers as identifiers. A settlement or order reference that resembles a number should not silently lose leading characters or become scientific notation. Preserve raw and parsed values when diagnosing an import failure.

Classify observed rows and retain unknown descriptions

Keep each signed amount attached to its actual type and description. Create a documented classification table for the descriptions your report contains. Distinguish customer activity, fees, refunds, credits, and other adjustments according to the actual records and accounting policy.

Unknown rows stay visible in an “unclassified” group with their amount and source reference. Do not assign them to sales merely because the spreadsheet needs a category, and do not delete them to make a reconciliation balance.

Avoid counting summary values as additional transactions. Determine which fields are report-level totals and which rows are detail components before writing formulas. A duplicated total can produce a mathematically consistent but economically meaningless result.

Work a small signed-row example

The following is hypothetical and simplified to demonstrate arithmetic:

Component Signed amount in one currency
Customer activity +100
Fees −15
Refund activity −20
Detail sum 65

If the actual report's declared total is 65, the detail sum matches that total. The match does not establish that the bank received 65 or that the business earned 65 of profit. Those are separate checks.

If another adjustment of −5 appears, retain it and investigate its description. A revised sum of 60 is a result to explain. Changing the unknown row to +5 because the expected deposit was 65 would invent evidence.

Match the report total to bank evidence

Use the settlement identifier and relevant dates to locate the actual receipt. Record expected amount, observed amount, receipt date, currency, and any supported timing or banking difference. Keep a pending receipt pending when bank evidence is unavailable.

Reconcile reserves, prior balances, and adjustments only where the source records support them. Do not assume every variance is a reserve or that deposits follow the same timing for every account.

For a hypothetical case, the report reconciles to 65 but no matching bank transaction has yet been supplied. Mark “report reconciled; receipt unverified.” That wording preserves progress without manufacturing collection.

Bridge settlement cash to operating earnings

The settlement is one part of the financial picture. Inventory purchases and cost of goods, advertising, outside invoices, software, owner replacement labor, taxes, and other obligations may use different records and timing.

Keep an inventory purchase distinct from the cost assigned to sold units. Include an actual return or supplier recovery once in the corresponding economic view; avoid subtracting both a forecast allowance and the same realized loss. The returns reconciliation guide supplies a separate event-level method.

Use the revenue and expense verification workflow to document the wider bridge. The responsible accountant should review classification and recognition decisions for the actual business. A spreadsheet tutorial cannot establish its accounting policy.

Repair and test an old-format dependency

If a workbook expects the retired report's many price and fee columns, map its required meanings to the V2 structure. Review formulas, grouping logic, sign conventions, and unknown-description handling. Renaming the file does not migrate a parser.

Test at least these cases before reusing the template:

  • A negative amount remains negative.
  • A comma decimal imports to the intended value.
  • An unfamiliar description remains visible and classified as unresolved.
  • Detail rows do not double-count the declared total.
  • A matching report total can still leave bank receipt unverified.

Use a redacted representative export and qualified parser help when needed. This method does not require exposing API credentials, creating reports through an unsupported request, or manipulating financial records.

Retain a reproducible reconciliation packet

Save the untouched export, parsing settings, classification mapping, formulas, variances, source documents, and responsible review. A second operator should be able to reproduce the total without guessing which rows were removed.

When the packet supports a stock decision, keep settlement timing separate from the money needed for the next order. Use the FBA build-or-buy preflight to assess inventory and funding obligations. A reconciled deposit is useful evidence, followed by the separate work of understanding earnings and maintaining enough cash to operate.