Skip to content
Workflow · Match two lists · Opening soon

Amazon India settlement reconciliation

Export your Amazon Seller Central transaction report and your Tally sales register, then match them by order ID. The workflow compares invoice and product sales, splits out Amazon-kept fees and taxes, and sets each order as Paid, Short paid, Unpaid, or Not in sales register.

Early access opens shortly. Check back soon.

Someone typed

“match the amazon seller central india transactions to our tally sales register by order id, show invoice vs product sales, amazon-kept fees and taxes, and status as Paid, Short paid, Unpaid, or Not in sales register”

The agent read it as

Match the Amazon Seller Central India transaction report to our Tally sales register by order id, show invoice vs product sales, amazon-kept fees and taxes, and status as Paid, Short paid, Unpaid, or Not in sales register, with Paid comparing gross: invoice vs product sales.

What the agent built

4 steps, each one an ordinary Mammoth step you can open and change.

  1. File
    Amazon Seller Central India transaction report
    CSV export · 28 rows
  2. File
    Tally sales register
    CSV export · 30 rows
  3. Step
    Make Amazon match key
    Step 1
  4. Step
    Make Tally match key
    Step 2
  5. Join
    Match the Tally register
    27 of 28 paired
  6. Step
    Set payment status
    Step 4
  7. Result
    Amazon Sales Match
    31 rows · 6 flagged
  8. Schedule
    Runs when you say
    Proposed

On the sample files, every step runs and the result has 31 rows.

What you get back

The result of that run, the rows to look at first.

Amazon Sales MatchSample data31 rows
25 paid3 unpaid2 short paid1 not in sales register
Order IDInvoice valueProduct salesAmazon-kept feesAmazon taxes withheldStatusVoucher numberInvoice dateAmazon dateAmazon transactions line #Tally register line #
403-1234567-1099·1,1801006Not in sales register··2026-10-2728·
403-1234567-10071,1809441154.80Short paidSR-00072026-10-042026-10-0477
403-1234567-10241,7701,652808.40Short paidSR-00242026-10-202026-10-202224
403-1234567-1012590···UnpaidSR-00122026-10-08··12
403-1234567-10211,298···UnpaidSR-00212026-10-17··21
403-1234567-10282,124···UnpaidSR-00282026-10-24··28
403-1234567-1001590590653PaidSR-00012026-10-012026-10-0111
403-1234567-1002708708803.60PaidSR-00022026-10-012026-10-0122
403-1234567-10038268261004.20PaidSR-00032026-10-022026-10-0233
403-1234567-10049449441154.80PaidSR-00042026-10-032026-10-0344
403-1234567-10051,0621,0621355.40PaidSR-00052026-10-032026-10-0355
403-1234567-10061,1801,180656PaidSR-00062026-10-042026-10-0466
31 rows in the result · 12 shown, problems first. Sample data: illustrative figures, not business results.

How it works

How to use the Amazon Sales Match workflow

  1. 1Get early accessWe invite people in small batches, job by job. You'll land on this workflow, already built and working on sample files.
  2. 2Swap in your exportsUpload your own files as they come out of your tools. The agent checks the workflow on your rows.
  3. 3Change it in words, then turn it onSay what to change and see the new result before anything saves. Then choose when it runs.

Amazon Sales Match: questions

How do you reconcile Amazon settlements against your Tally sales register?
Export your Amazon Seller Central transaction report and your Tally sales register, then match them by order ID. The workflow compares invoice and product sales, splits out Amazon-kept fees and taxes, and sets each order as Paid, Short paid, Unpaid, or Not in sales register.
Which export should you use from Amazon Seller Central?
Use the transaction report export from Amazon Seller Central India. It should include the order ID and the settlement values you want to reconcile.
What happens to rows that do not match by order ID?
Rows that do not find a match stay separate, so you can review them as missing from one file or the other. This helps you spot unpaid orders, short payments, and orders that are not in the sales register.
How do you change the matching rules?
You change the rules in words, for example by choosing a different match key or by changing how payment status is decided. You can also tell it which fields should be compared and how to label the result when values do not line up.

Get early access to this workflow

It opens already built and working on sample files. Swap in your own exports to see your result.

Early access opens shortly. Check back soon.