Amazon FBA Shipment Reconciliation with Cointab

Amazon FBA shipment reconciliation helps teams confirm that what was sent to Amazon is what was received, recorded, and reflected in internal reports. For eCommerce and marketplace businesses, that process often involves comparing shipment files, receiving reports, and inventory records across different systems.

Cointab gives finance and operations teams a structured way to run Amazon FBA shipment reconciliation without rebuilding spreadsheets every period. Users upload the required files, map fields once, review matched and unmatched records, and export audit-ready reports for follow-up and close processes.

What Amazon FBA shipment reconciliation covers

Amazon FBA shipment reconciliation is the process of matching internal shipment records with external Amazon-side records so teams can identify differences early.

In practice, the workflow may involve comparing:

• Internal shipment or dispatch records on Side A
• Amazon receiving or fulfillment-side reports on Side B
• Supporting reference files such as SKU mappings or order metadata

The goal is to confirm which units were received correctly, which were partially received, and which remain unmatched.

Why manual FBA reconciliation becomes difficult

Many teams still reconcile FBA shipments in Excel using filters, VLOOKUPs, and repeated file comparisons. That approach becomes harder as shipment volumes grow and file formats change.

Common issues include:

• Missing units in receiving records
• Partial receipts where quantities do not fully match
• Duplicate or unusable rows that need to be excluded
• Different identifiers across internal and external reports
• Repeated setup work for every period or shipment cycle
• Difficulty tracking exceptions across large files

When these items are handled manually, open exceptions can stay unresolved for too long and the review process becomes hard to audit.

How Cointab structures Amazon FBA shipment reconciliation

Cointab uses a Side A and Side B reconciliation model that keeps the workflow clear and reviewable.

Side A: your records

Side A contains the records your business expects to be correct. For Amazon FBA shipment reconciliation, this may include:

• Internal shipment export
• Dispatch report
• Inventory movement file
• SKU or order-level source file
• Other internal reference data

Side B: external records

Side B contains the records received from Amazon or another external source. This may include:

• Amazon receiving report
• Shipment acknowledgment file
• Fulfillment-side reference data
• Other marketplace-side reports

Users upload CSV, XLS, or XLSX files, map the required columns such as date, amount or quantity, and identifiers, and then run reconciliation.

Matching logic for shipment reconciliation

Cointab's reconciliation engine applies structured matching logic to compare records across both sides.

For shipment reconciliation, that can include:

• One-to-one matches for simple shipment references
• One-to-many or many-to-one matches when quantities are grouped
• Partial matches when the identifier matches but the quantities differ
• Net-to-net or contra-style comparisons where records need to be grouped before comparison
• Cross-side matching when the same reference appears in different fields

The system separates results into clear categories so users can focus on exceptions instead of reviewing every row manually.

What users review after reconciliation

Once the run is complete, Cointab presents a report dashboard with transaction-level detail.

Typical outcomes include:

• Fully matched records
• Partially matched records
• Unmatched records
• Skipped records

This makes it easier to see which shipments were received as expected and which ones need follow-up.

Fully matched

Fully matched records are rows where the identifiers and quantities align according to the configured rules.

Partially matched

Partially matched records indicate that the shipment is related, but the quantity or amount does not fully align. These rows are important because they usually point to a receiving difference, short shipment, or other exception worth reviewing.

Unmatched

Unmatched records are present on one side but not found on the other. In an FBA workflow, these rows may indicate shipments that were sent but not received, or records that were received but do not map back cleanly to internal data.

Skipped

Skipped records are excluded from reconciliation because they are incomplete, invalid, duplicated, or otherwise unusable. Cointab makes skipped rows visible so teams understand what was not included and why.

Supporting data and derived columns

Amazon FBA workflows often need more than just the two main reports. Cointab supports supporting data for lookup, merge, enrichment, or calculation before reconciliation.

Examples include:

• SKU mapping files
• Order metadata
• Product master data
• Delivery or warehouse reference files
• Files used for VLOOKUP-style enrichment

Users can also create derived columns on either side. If a file needs cleaning, normalization, or a calculated field, AI can help generate an Excel-style formula from a plain-language prompt.

This is useful for fields such as:

• Clean shipment reference
• Normalized SKU
• Net quantity
• Combined identifier
• Derived comparison field

Why reusable reconciliation setup matters

A major advantage of Cointab is that the workflow can be reused.

Once an Amazon FBA shipment reconciliation is configured, teams do not need to build the same setup again for every new period. They can:

1. Select the existing reconciliation
2. Choose the period
3. Upload the files
4. Run reconciliation
5. Review the report

This saves setup time and keeps the matching logic consistent across runs.

Manual review for unresolved exceptions

Not every shipment difference can be matched automatically. Cointab supports manual match for cases where the user has business context that the system cannot infer with confidence.

Manual matching is helpful when:

• A shipment reference is incomplete
• Partner data is late or partial
• A grouped shipment needs human review
• A one-off exception must be cleared with clear documentation

Manual matches remain auditable, and users can undo them if needed.

Reconciliation reports that support finance and audit teams

Cointab produces downloadable Excel reconciliation reports that can be used for internal review, period-end close, and follow-up with warehouse or marketplace teams.

Reports help teams answer questions such as:

• What was fully matched?
• Which shipments were only partially received?
• What remains open?
• Which rows were skipped?
• What action is needed next?

That visibility is useful for finance teams, controllers, and marketplace operations teams that need a clear record of what was compared and what remains unresolved.

Where Amazon FBA reconciliation fits in the broader workflow

Amazon FBA shipment reconciliation is often part of a wider marketplace reconciliation process. Teams may also need to compare sales, settlements, returns, deductions, or payout files across the same reporting cycle.

Cointab is designed for these recurring finance workflows, so the same platform can support shipment reconciliation alongside other internal vs external matching processes.

Reconciliation workflow summary

A typical workflow in Cointab looks like this:

1. Upload internal and external reports
2. Map required fields such as date, quantity, and reference columns
3. Add supporting data if needed
4. Create derived columns if required
5. Run reconciliation manually or on a schedule
6. Review matched, partially matched, unmatched, and skipped records
7. Use manual match where needed
8. Download the report for audit and follow-up

This gives teams a structured process for Amazon FBA shipment reconciliation without relying on repeated spreadsheet work.