Remittance Fee Calculator
The formula
What the remittance cost tells you
The World Bank tracks this exact number for 200+ corridors because remittance fees are a tax on migration: headline fees lie — the FX markup is where most of the revenue hides.
Calculation: Cost = fee + markup×amount + receiving fee; cost % vs sent. Enter your inputs and every substitution is shown below the result.
Reading the result
Compare all-in %, not fee lines; a $0.99 fee with 5% FX markup is a 5.2% transfer. SDG target is <3% — most retail corridors still miss it.
Rules of thumb: Global average ≈6.4% (2024 WB data); Africa corridors 7–9%; US→MX and EU corridors can run <2%
Limitations and best practice
Receiving-side fees and mobile-money cash-out charges close the last mile: the quoted "delivered" amount is the only number that is truly comparable.
This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Frequently asked questions
Why are corridors so expensive in Africa?
Are stablecoin rails cheaper?
What is the “no fee, bad rate” trick?
Source & methodology
World Bank Remittance Prices Worldwide database.
Remittance Fee: what this tool answers
This page was written for one job: turning your own inputs into a defensible figure, with the working shown. There are plenty of pages about Remittance Fee; almost none of them show the working. This one does: the formula, every input, a fully computed example, and a sensitivity analysis calculated live from this engine’s own defaults.
It helps to separate the mechanics from the interpretation. The mechanics are fixed: Cost = fee + markup×amount + receiving fee; cost % vs sent. Anyone, anywhere, entering the same inputs will get the same 3.24 of amount. The interpretation is where experience counts: whether 3.24 of amount is good, normal or alarming depends on comparisons covered below, and that is the part most articles about Remittance Fee never explain.
People rarely disagree about arithmetic; they disagree about assumptions that were never written down. Printing the substitution and the sensitivity ranking removes that category of disagreement for Remittance Fee.
Nothing below is stock text pasted around a number: the worked example computes all-in transfer cost = 3.24 of amount from this tool’s own defaults, and the sensitivity section ranks the inputs that move the result — FX markup first, at ≈8.6 % of the headline for a ten-percent error either way in that input. Read the sections in order and you will be able to reproduce every figure by hand.
Inside the Remittance Fee calculation: formula and every input
The engine implements a single stated model: Cost = fee + markup×amount + receiving fee; cost % vs sent. There is no hidden coefficient and no login-gated precision — the formula printed is the formula executed, which is also what makes the result citable.
Amount sent ($) (example value 1,125) is a measured number in the unit named by the label; the formula does not convert for you. If your source quotes a figure before and after some deduction, decide which one the formula wants and be consistent for every field.
Upfront fee ($) (example value 5) is a plain measured quantity — the unit shown in the label is the unit the formula expects. Use the figure exactly as the source document states it, not a rounded memory of it — an omitted line is the classic silent error.
FX markup (%) (example value 3) is a measured number in the unit named by the label; the formula does not convert for you. Check the convention first: if the source says “6.5 % per year”, type 6.5 and let the formula do the rest.
Receiving-side fee (local) (example value 0) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. Use the figure exactly as the source document states it, not a rounded memory of it — an omitted line is the classic silent error.
The default Remittance Fee calculation, written out in full
Rather than describe the calculation, here it is end to end — every substitution in order, starting from the inputs above. Starting figures: Amount sent ($), Upfront fee ($), FX markup (%), Receiving-side fee (local). The endpoint of that chain is 3.24 of amount of all-in transfer cost, sitting in the “Typical retail remittance zone: still 2–4× what the SDG 10.c target says is fair” band.
- Cost = $4.99 + 2.8% × $1,125 + 0.00 local = $36.49
- Effective price: 3.24% on a $1,125 transfer
- Twice a month at this cost = $876/yr of pure fees
Total cost — $36.49. Compare it against the main result of 3.24 of amount before drawing conclusions.
Received (value basis) — $1,088.51. Read next to the headline, this is the figure that shows the shape of the trade-off.
Flat-fee comparison: $25 + 0.6% — $31.75. This is the number experienced users quote when the headline alone would mislead.
Cost per $1,000 moved — $32.44. If your inputs change, this is usually the first companion figure to move.
Keep this worked example open while you enter your own figures: matching the shape of the substitution is the fastest way to spot a unit or convention mistake.
The Remittance Fee corridor: your result across a realistic band
Read this table as the practical error bar on the headline figure. It answers the question people actually have after seeing a single number: how wrong could this be if the main input is off by ten or twenty percent?
| FX markup setting | All-in transfer cost |
|---|---|
| 80 % of the example value | 2.68 of amount |
| 90 % of the example value | 2.96 of amount |
| example inputs | 3.24 of amount |
| 110 % of the example value | 3.52 of amount |
| 120 % of the example value | 3.80 of amount |
That spread — 2.68 of amount at the low end, 3.80 of amount at the high — is what a careful read of Remittance Fee looks like: a band you can state out loud, with the reason for each edge. Reproduce it in the form above by editing FX markup alone; the substitution steps will follow your figures exactly.
Sensitivity: which inputs change Remittance Fee the most
This list was computed for this specific engine just now: each numeric input was nudged ±10 % while every other field held its example value, and the all-in transfer cost was recalculated from scratch. Read it as a map of where Remittance Fee is fragile — drawn for the example inputs, which is the map you want when deciding what to measure carefully.
- FX markup +10 % → Remittance Fee = 3.52 of amount · −10 % → 2.96 of amount (the all-in transfer cost shifts ≈8.6 %)
- Amount sent: ten percent up gives 3.20 of amount, ten percent down gives 3.29 of amount — ≈1.5 % of the all-in transfer cost either way
- Nudge Upfront fee by ±10 % and Remittance Fee lands between 3.20 of amount and 3.29 of amount (sensitivity ≈1.4 %)
FX markup is the dominant lever here: ten percent either way moves the result by about 8.6 %, from 2.96 of amount to 3.52 of amount. Measure that input from a document rather than from memory, and treat Amount sent as the second priority (≈1.5 % per ten percent). The rest of the inputs earn only a rounding-error of attention, and that asymmetry is the practical payoff of measuring rather than asserting.
What a Remittance Fee of 3.24 of amount means in practice
Nobody acts on a bare figure — they act on a figure with a comparison attached. The default case lands in the “Typical retail remittance zone: still 2–4× what the SDG 10.c target says is fair” band, and bands are deliberately wide because real situations overlap. Before treating the band as fact, note its width: ten percent either way on FX markup already spans 2.96 of amount to 3.52 of amount. The practical reading rules: ask what would have to change to move you one band. If the answer is “a small, plausible input difference”, the band itself is not the finding — the uncertainty is.
Set Remittance Fee beside its neighbours and it usually plays a specific role: this figure establishes the size of something, and the neighbouring tools establish whether that size is acceptable. Skipping the first step makes the second one arbitrary.
How people get Remittance Fee wrong
Receiving-side fees and mobile-money cash-out charges close the last mile: the quoted "delivered" amount is the only number that is truly comparable. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Using stale inputs. Remittance Fee is only as current as the numbers behind it — an estimate carried over from a previous season, rate table or report quietly biases every output. Re-measure the inputs first; that single habit fixes more bad Remittance Fee figures than any formula change.
One mistake is specific to this engine: assuming every input matters equally. The computation above shows FX markup dominating — a careful figure there beats false precision everywhere else.
The subtlest error is answering the wrong question precisely. Confirm that all-in transfer cost is actually the quantity your decision needs — the arithmetic is flawless either way, which is what makes the mistake invisible.
Six things to confirm before acting on Remittance Fee
- Confirm the example values are plausible for your own situation before replacing them.
- Verify each input against its original source document, not memory.
- Put FX markup under a magnifier; the sensitivity table above is the reason why.
- Note the date and the inputs beside the number so the figure can be audited later.
- Compare the result with one independent method or published benchmark.
- Run the ±10 % stress on the top two levers and check that your conclusion survives both.
A routine for decision-grade Remittance Fee
The tool does the arithmetic; the routine below is what makes the arithmetic trustworthy. Five steps, a minute total — and afterwards you will know not just what the number is, but which assumption produced it.
Step 1 — one document, one pass. Open the statement, label or record that holds amount sent ($), upfront fee ($), fx markup (%), receiving-side fee (local) and transcribe straight into the form. Transcription from a single source removes the mismatch errors that appear when figures are assembled from three different places. Suspiciously tidy answers deserve the same scrutiny as untidy ones.
Step 2 — start from the case you can defend. Enter pessimistic-but-honest figures first; the optimistic run is a ceiling, not a plan. A conclusion that holds on conservative inputs holds everywhere. The inputs are the part of the work that nobody else can do for you.
Step 3 — measure what deserves measuring. The ranked levers above tell you where a careful figure pays off. Everything else can stay approximate, which is a licence to stop hunting for data you do not need. A calculation you cannot explain to somebody else is a calculation you cannot defend.
Step 4 — stress before you commit. A decision that survives a ten-percent squeeze on its two biggest inputs needs no luck to be sound. One that does not survive is a decision about hope, not about arithmetic. The test of a good estimate is not that it feels right but that it changes what you do.
Step 5 — record the context, not just the number. Note today’s date and the inputs alongside the 3.24 of amount output. Six months from now the context is what turns this figure into a trend. The fastest sanity test is to guess the answer first and see how far the calculation disagrees.
Who actually uses Remittance Fee — and when
In Currency & International the figure computed here is usually the first one somebody asks to see. Having it — with the formula behind it — changes your position in the conversation from participant to reference. Write the assumptions in the same file as the result, and future arguments take minutes instead of meetings.
Used properly this is a five-minute filter that saves weeks. Compute Remittance Fee, reject what fails, and only then bring in the expensive analysis for the survivors. One decimal place more than your data supports is one decimal place of fiction.
Nothing here is stored or transmitted, so the habit of checking is free: open the page, re-enter current figures, compare with the number you saved last time. Note the assumption you are least sure about; that is where the real risk lives.
Remittance Fee — frequently asked questions
What affects Remittance Fee the most?
Remittance Fee is driven above all by FX markup. Perturbing only that field by ten percent either way produced 3.52 of amount against the 3.24 of amount baseline — a ≈8.6 % response, while Amount sent manages ≈1.5 %.
Which matters more: amount sent or fx markup?
For Remittance Fee, FX markup wins the head-to-head (≈8.6 % against ≈1.5 % per ten-percent change). Knowing which input dominates is the difference between careful work and merely slow work.
What is a typical Remittance Fee?
With the example inputs on this page the result is 3.24 of amount, labelled “Typical retail remittance zone: still 2–4× what the SDG 10.c target says is fair”. “Typical” varies with situation, which is why every result here ships with its verdict band and its sensitivity list: they turn one figure into a range you can locate yourself inside.
How do I calculate Remittance Fee by hand?
Three steps: write the formula (Cost = fee + markup×amount + receiving fee; cost % vs sent), insert your values, and simplify. The worked example section shows exactly that chain for the default inputs; replicating it once on paper teaches you more about Remittance Fee than any number of calculator runs.
What happens to Remittance Fee if fx markup changes by 10 %?
The engine was re-run with that field moved by ten percent while everything else stayed fixed: the all-in transfer cost goes across 2.96 of amount to 3.52 of amount, a swing of roughly 8.6 % around the 3.24 of amount baseline. That ratio is the practical definition of how much this input matters.
Is the Remittance Fee result of 3.24 of amount good or bad?
Good and bad are comparisons, so the honest test is three questions: where does your own Remittance Fee sit against the 3.24 of amount reference above, how far would a plausible input error move it (≈8.6 % per ten percent on FX markup), and what does the alternative option compute to?
What affects Remittance Fee the most?
Sensitivity depends on where you start, but the inputs Amount sent ($) and Upfront fee ($) typically move Remittance Fee further than the rest because they enter the formula multiplicatively. If you can only measure two things well, measure those and hold the others at conservative defaults.
Does inflation change Remittance Fee?
Any money figure that stretches over months is an inflation-sensitive number. A Remittance Fee of 3.24 of amount today is a different real value next year; divide by the inflation factor when comparing across time.
Why are corridors so expensive in Africa?
Low volumes, few bank rails, heavy agent-network economics and FX liquidity spreads.
Are stablecoin rails cheaper?
Currently 0.5–2% end-to-end on some corridors, but cash-in/cash-out bridges re-add the spread.
Is my data private on this page?
Yes — computation happens locally in your browser, with no account, no tracking of your inputs and nothing sent to a server. The printed formula is the whole story of what happens to your figures.
Key terms on this page
- Total cost
- $36.49 in the default Remittance Fee calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Received (value basis)
- $1,088.51 for the Remittance Fee worked case; it sits next to the main result because it carries context the headline leaves out.
- Flat-fee comparison: $25 + 0.6%
- $31.75 on the example inputs — a companion figure printed beside the headline of Remittance Fee so that no result is read in isolation.
- All-in transfer cost
- The primary output of this tool: 3.24 of amount for the default inputs, computed exactly from Cost = fee + markup×amount + receiving fee; cost % vs sent.
- Worked example
- Every substitution in order, from the example inputs to 3.24 of amount — the audit trail for the headline figure.
- Verdict band
- The interpretation attached to a result (“Typical retail remittance zone: still 2–4× what the SDG 10.c target says is fair” on these inputs), which turns a bare number into a position on a scale.
- Sensitivity (±10 %)
- How far the Remittance Fee moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
Method, sources and what this tool cannot tell you
The model is published arithmetic implemented exactly as written: Cost = fee + markup×amount + receiving fee; cost % vs sent. Source of record: World Bank Remittance Prices Worldwide database. Any other implementation of this model should return the same figure for the same inputs. If one does not, the difference is in its assumptions — which this page prints and that one probably does not.
Nothing here replaces a qualified professional, and nothing here is approximate either — the arithmetic is exact, and the honesty is in the inputs you supply. The promise to the reader is narrow and testable: same inputs, same output, no silent rounding, and no figure presented without the formula that produced it.
What to do with your Remittance Fee next
Re-run the calculation with your own figures, stress the two most sensitive inputs by ±10 %, and only then act on the result.
Whoever you are (people who need one trustworthy number before their next decision), the next step is the same: replace the example inputs with your own, note the date, and re-run whenever a figure moves. In Finance & Banking, a dated figure is a trend, and an undated one is a rumour.