Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Payments & Reconciliation 6 min read

Refund and chargeback operations: a cost model for Bangladesh

Build a defensible cost per dispute for refunds and chargebacks: fees, labour, evidence, float and write-offs, with a calculator worksheet.

E
EncryptTechBD · 0 comments
Notebook, calculator and office supplies arranged on a desk
Photo: Artsy Crafty / StockSnap

The visible cost of a chargeback is the fee on the acquirer statement. The real cost includes the hours spent collecting evidence, orders that cannot be re-sold and cash tied up while a case is open. Businesses that budget only for the fee understate the operation.

This guide builds a cost per resolved dispute that you can defend to a finance team. It uses your own contract rates and payroll, not a published price list, because both vary too much between merchants and providers.

Why cost per resolved dispute is the right unit

A refund and a chargeback are different events but they share an operational path: a customer claim, a decision, evidence, a payment instruction and a reconciliation. Measure the whole path. Divide the total monthly cost by the number of cases resolved in the same month, whether they were refunded, won, lost or withdrawn. That figure can be compared across channels, teams and months.

Do not divide by orders. A low dispute rate on a large order book can still produce a meaningful absolute cost. Cost per case exposes complexity; cost as a percentage of revenue shows materiality. Use both.

The cost stack

  • Provider fees. Chargeback, dispute, refund processing and platform charges. Take the figures from your contract and statements.
  • Case labour. Time to read the claim, find the order, contact the customer, gather evidence and follow up. Include supervisors and finance staff.
  • Evidence production. Delivery proof, signed terms, device logs, chat transcripts, photographs and courier scans, plus the time to retrieve and format them.
  • Tooling. Dispute software, fraud screening, helpdesk seats and storage, allocated by the share of cases that use the tool.
  • Write-offs and lost goods. The order value not recovered, plus products that cannot be restocked.
  • Working capital. The amount debited while a case is open, multiplied by your cost of funds and days outstanding.
  • Prevention spend. Address verification, COD confirmation, fraud rules and customer communication, with a share allocated to disputes.
  • Secondary loss. Repeat-purchase loss, marketplace penalties, reserve adjustments and management escalations. Label these as estimates.

The formula

Keep the formula visible so that every number has an owner.

Monthly dispute cost = provider fees + case labour + evidence production + tool allocation + write-offs + working capital cost + prevention allocation + secondary loss

Cost per resolved dispute = monthly dispute cost / cases resolved in the month

Net cost per dispute = cost per resolved dispute - amount recovered from representment

Recovery is not the same as winning. A won case may still consume more labour than the order was worth. A lost case may still be cheaper than a prolonged fight. The formula lets you see both.

Calculator inputs

  1. Orders per month, split by card, mobile financial service, bank transfer and cash on delivery.
  2. Refund requests per month and the share that become chargebacks or formal disputes.
  3. Average order value by channel, taken from the order system rather than a summary report.
  4. Provider fee schedule, including currency and tax treatment.
  5. Minutes per case at each stage: intake, investigation, evidence, response and reconciliation.
  6. Loaded hourly cost for each role involved, including benefits and overhead.
  7. Tool cost per month and the share of cases that use each tool.
  8. Win rate and average recovered amount, from your own case history.
  9. Days a case stays open, by provider and reason code.
  10. Write-off rate and restocking recovery rate.
  11. Cost of funds or the interest rate on working capital.
  12. Prevention spend per month, with a note on which cases it should reduce.

Budget worksheet

LineUnitSourceOwnerMonthly
Provider dispute and refund feesCases x contract rateAcquirer statementsFinanceEnter
Case labourMinutes x loaded rateTime log or sampleSupport leadEnter
Evidence productionHours x loaded rateCase sampleOperationsEnter
Tool allocationMonthly cost x usage shareSoftware invoicesITEnter
Write-offsOrders x average value x loss rateOrder systemFinanceEnter
Working capitalOpen value x rate x days / 365FinanceFinanceEnter
Prevention allocationMonthly prevention spend x shareBudgetOperationsEnter
Secondary lossEstimate with a written assumptionCustomer dataCommercialEnter

Run the worksheet for the last three months, not a forecast. A historical baseline shows whether the cost is rising because of volume, complexity or a change in provider rules.

What moves the number in Bangladesh

Card disputes follow card-scheme rules and deadlines, while mobile financial service complaints follow the provider's own process. Treating them as one queue hides different evidence and timelines. Cash-on-delivery refunds add another path, especially when the original payment was cash and the customer expects a wallet transfer.

Refund the original payment method where the rules allow it, and document the exception route when they do not. A refund sent to the wrong wallet is not resolved; it becomes a second case. Keep the provider reference, the customer confirmation and the settlement line together.

Language and channel matter. A customer who receives a Bangla message with a clear reference number is less likely to escalate than one who receives an English email with no case ID. That is a cost lever, not a courtesy.

A 90-day plan to reduce cost per case

  1. Days 1-15: build the baseline, classify cases by reason code and channel, and identify the three reason codes with the highest total cost.
  2. Days 16-30: fix the evidence pack for those three codes. Agree exactly which documents are required and where they are stored.
  3. Days 31-50: introduce a pre-dispute refund rule for low-value, high-confidence claims. Measure the change in chargeback volume and labour.
  4. Days 51-65: set approval limits and a deadline tracker. Escalate cases before the provider deadline, not after.
  5. Days 66-80: train support and finance on the same reason codes and the same refund states.
  6. Days 81-90: review the cost per case against the baseline and keep only the changes that reduced total cost without increasing repeat contacts.

Questions for the provider

  • Which fees apply to a dispute, a refund, a reversal and a representment, and how are they shown on the statement?
  • What is the response deadline for each reason code, and how is it communicated?
  • What evidence does the provider accept, in what format and through which channel?
  • How are mobile financial service disputes handled differently from card disputes?
  • What reporting is available for case ageing, win rate and recovered value?
  • Who is the escalation contact when a case is about to miss a deadline?

Metrics to review monthly

  • Cost per resolved dispute, split by channel and reason code.
  • Cases resolved within the provider deadline.
  • Win rate and recovered value, net of labour.
  • Days from claim to refund or final decision.
  • Repeat contacts per case and the share of cases reopened.
  • Write-off rate and restock recovery rate.
  • Refund accuracy: payments sent to the wrong channel or duplicated.

If the dispute queue is consuming more management time than the underlying sales justify, start with Commerce Systems. The pricing page explains how payment and operations work is scoped. For the process failures behind the numbers, read the refund and chargeback troubleshooting guide.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes