How this calculation works
A settlement can differ from gross captures even when every transaction is accounted for. Fees, refunds, chargebacks and reserves move the deposit amount in different ways. This page exposes their signed contribution before comparing the total with the bank record.
Expected settlement = captures − refunds − chargebacks − fees − fee tax − reserve held + reserve released + signed adjustmentA worked example
100,000 captures less 5,000 refunds, 1,000 chargebacks, 2,100 fees, 378 fee tax and a net 1,500 reserve hold gives an expected bank deposit of 90,022.
Good to know
One batch and currency. Refunds plus chargebacks cannot exceed this batch’s captures. No provider API, individual transaction matching, tax advice or policy inference; fee and tax rates are user-entered assumptions.
Reference: Razorpay — settlement reconciliation concepts (opens in a new tab) ↗
Revenue and a bank deposit are not the same ledger line
A settlement can differ from gross captures even when every transaction is accounted for. Fees, refunds, chargebacks and reserves move the deposit amount in different ways. This page exposes their signed contribution before comparing the total with the bank record.
All values must describe a compatible batch and currency. Reserve releases may relate to older captures, so they are entered separately rather than being treated as current-period sales.
The Marketplace return adjusted selling price calculator explores a product-level pricing assumption. It does not replace reconciliation of actual gateway fees and bank deposits.
Select the fee base explicitly
Some fee scenarios apply a percentage to gross captures; others may calculate it after specified deductions. The form makes that basis a deliberate choice. Fixed fees are a batch total and are not silently multiplied by a transaction count.
The tax input applies only to the calculated fee total in this model. It does not establish the rate, tax eligibility or recoverability. A provider may charge and credit fees differently across refund transactions, so copy the statement’s applicable totals or reconcile those details separately.
Use the difference as a reconciliation signal
Actual minus expected should be zero when the entered ledger explains the deposit. A positive difference means the bank deposit is larger, while a negative one means it is smaller. Neither sign by itself identifies an error or a missing transaction.
Investigate unexplained differences using the underlying settlement report, value dates and reserve records. This calculator does not connect to a provider or match individual transaction identifiers; it checks the arithmetic of the totals you supply.
Work through the example
100,000 captures less 5,000 refunds, 1,000 chargebacks, 2,100 fees, 378 fee tax and a net 1,500 reserve hold gives an expected bank deposit of 90,022.
Use the worked table to trace where each input enters. Then change one assumption and calculate again, leaving the others fixed. A comparison is easier to interpret when the change has one identifiable cause rather than a different set of measurements, dates and rates all at once.
What this model does not establish
One batch and currency. Refunds plus chargebacks cannot exceed this batch’s captures. No provider API, individual transaction matching, tax advice or policy inference; fee and tax rates are user-entered assumptions.
Keep the input assumptions with any exported result. Illustrative values do not become observations merely because the output is precise. For a real purchase, financial reconciliation or technical decision, check the underlying records and applicable requirements before treating this scenario as a final answer.
A few questions, answered
What formula does the calculator use?
Expected settlement = captures − refunds − chargebacks − fees − fee tax − reserve held + reserve released + signed adjustment
What should I verify before using this result?
One batch and currency. Refunds plus chargebacks cannot exceed this batch’s captures. No provider API, individual transaction matching, tax advice or policy inference; fee and tax rates are user-entered assumptions.
Are the example inputs live records?
No. They are an illustrative calculation case. Replace them with records and measurements appropriate to your situation.