Four rules govern the amount you enter in Stripe for a foreign-currency charge or payout. The hardest part is rarely the exchange rate. The amount you type into an invoice or a charge is the real risk. A small slip in the amount can mean a client is charged too much or too little, a refund request you did not expect, or a payout that Stripe will not accept. Operations leads often find these problems only after the money has moved, when a reconciliation report refuses to match the invoice.
Key takeaways
- Check Stripe's supported currencies page and note whether the currency is zero-decimal.
- Convert the displayed amount to the amount value using the rule for that currency, not a general formula.
- Compare your result with the examples on the page, such as 500 for 500 JPY and 500 for 5 ISK.
- For HUF and TWD payouts, request only whole-unit amounts, and record any leftover fraction.
- Round once, at the end of the calculation, using your written policy.
This post covers four currency amount rules to check before you bill in Stripe. They are simple to state, but each one trips up teams that assume every currency works the same way as their home currency. Rules 1 to 3 come from Stripe's documentation on supported currencies, which is linked wherever a specific currency or figure appears, so you can confirm them yourself. Rule 4 is your firm's own rounding policy, not a Stripe rule, so confirm it internally. Product details change, so treat the linked page as the final word.
Rule 1: Find out whether the currency is zero-decimal
Most currencies you will work with have a smaller unit than their main unit, such as cents for U.S. dollars or pence for British pounds. Some currencies do not use that subdivision in everyday life, and Stripe groups them as zero-decimal currencies. Japanese yen is the usual example. Stripe's supported currencies page states the rule for these currencies plainly: "10 to charge 10 JPY (or any other zero-decimal currency)." In other words, the number you pass to Stripe is the yen amount itself, with no conversion step. The same page gives a concrete case: "For example, to charge 500 JPY, provide an amount value of 500."
Why does this matter? Picture a bookkeeper who has spent years on dollar invoices. That habit is wrong for a zero-decimal currency, where the amount goes in as the yen figure. If the setup converts anyway, the charge will not match the invoice. The error is easy to miss because the invoice looks correct on screen, while the charge behind it is not.
The same problem shows up when a team copies a working setup into a new currency and changes only the currency label. The label changes, but the logic that builds the amount does not. Check the logic, not just the label.
Make currency lookup a step in your process rather than a memory test. Before anyone sets an amount in a new currency, they should open the supported currencies page and note whether that currency is zero-decimal. If your firm bills in only three or four currencies, write the answers in your internal billing notes, next to each currency code. Review those notes whenever Stripe's documentation changes, and once a quarter even when it does not.
A useful way to run the check is to pick one invoice for each currency family and walk it through the whole path: the invoice amount, the charge, the reconciliation line, and the payout. Doing this once for each currency shows you which step is most fragile in your own setup, and that is where your written checks should be strongest.
Rule 2: Convert to the smallest unit using each currency's own rule
Stripe's amount field expects a different number than the figure you show a client, and the page's examples show how the two differ. For zero-decimal currencies, the two are the same. For currencies that have a smaller unit, they differ, and that difference is a common source of errors. The Icelandic example on the supported currencies page shows the idea clearly: "For example, to charge 5 ISK, provide an amount value of 500." The figure the client sees is 5, and the amount value Stripe expects is 500. The lesson is not to memorize one currency's rule. It is to read the rule for each currency you bill.
This is why you should avoid one formula for the whole firm. A single formula, such as always multiplying by the same factor, may work for some currencies and fail for others. Build the conversion from a lookup table instead. For each currency code, record whether it is zero-decimal and how the amount value is formed. Then the conversion reads the table rather than relying on someone's memory.
A useful lookup table has four columns:
- The three-letter currency code, the way Stripe writes it.
- Whether the currency is zero-decimal.
- The example from Stripe's page that confirms the rule.
- The date you last checked the page.
The last column matters more than it looks. Documentation can change, and the date tells the next person when to look again.
Decide who may edit the table, too. It holds the rules your firm relies on, so it belongs in a shared, versioned place rather than in one person's inbox. When a row changes, note the change and the date, so you can explain how an older invoice was calculated if someone asks.
Test the conversion against the examples before you trust it. Enter 5 for ISK and confirm your system produces an amount value of 500. Enter 500 for JPY and confirm it produces 500. If your system gets either one wrong, fix the lookup table before you bill any client. If your billing software offers a test environment, run these checks there first.
Keep both numbers in your records. Store the figure the client saw and the amount value Stripe received. When a client disputes an invoice, the two numbers together explain the charge in seconds. Without them, you are rebuilding the calculation from memory, and memory is not evidence.
Finally, watch for fractions. A conversion from a foreign price can produce a figure with more digits than the currency's smallest unit allows. Decide in advance where rounding happens, and round once, at the end of the calculation, rather than at every intermediate step. Rounding at several points is a common source of disagreements that are only a small amount apart, and those are the hardest to explain to a client.
Rule 3: Request HUF and TWD payouts in whole units
Billing and payouts are separate steps, but the same operations lead often owns both. Once client money has landed in your Stripe balance, you move it to your bank account with a payout. The supported currencies page gives payout examples for Hungarian forints (HUF) and Taiwan dollars (TWD).
For manual payouts in forints, Stripe's page says: "When you create a manual payout in HUF, you must provide integer amounts that are evenly divisible by 100." The Taiwan dollar rule is the same: "When you create a manual payout in TWD, you must provide integer amounts that are evenly divisible by 100."
Those sentences are dense, so the page's examples help. For HUF, it says: "For example, if you have an available balance of HUF 10.45, you can pay out HUF 10 by submitting 1000 for the amount value." It also shows the failure case: "You can’t submit a payout for the full balance, HUF 10.45, because the amount value of 1045 isn’t evenly divisible by 100." The TWD example works the same way: "For example, if you have an available balance of TWD 800.45, you can pay out TWD 800 by submitting 80000 for the amount value."
Read those examples as a pattern. The balance shows a figure with a fraction. The payout you can request is the whole-unit figure below it. The amount value you submit is that whole figure written in the currency's smallest unit, and it must be evenly divisible by 100. The full balance cannot go out, because its amount value does not divide evenly.
For an accounting firm, this matters in two ways. First, the leftover fraction stays in the balance. If you sweep the balance every month and assume it is zero, the account will not match your books. Second, a payout request can fail if someone types the full balance into the payout form. Write a short note in your payout procedure: take the balance, drop the fractional part, convert the whole figure to the amount value, and confirm that the amount value is evenly divisible by 100 before you submit it.
Record the leftover in your reconciliation notes, with its currency and figure. The next person who reviews the account should not conclude that money has gone missing. A one-line note turns a confusing gap into a documented, expected balance.
Be careful about the scope of this rule. The quoted sentences describe manual payouts. If your account uses other payout types, check the same page before you assume the same rule applies. Do not treat this as a rule for every payout you will ever make, and do not apply it to currencies the page does not discuss.
Rule 4: Write down your rounding policy and test it before clients see it
Rules 2 and 3 share one problem: the amount a client sees can differ from the amount Stripe records, and the gap is often a fraction. The fraction may come from a conversion, from a payout that cannot include the full balance, or from a rate applied to a figure that does not fit the currency's smallest unit. Gaps like these add up across many clients, and they produce the reconciliation questions that eat an operations lead's week.
The fix is a written rounding policy. It should answer three questions. When an amount does not fit the smallest unit, do you round down or round up? Where in the calculation does rounding happen? Who is allowed to change the rule? Keep the answers short enough to fit on one page. Apply the same policy to invoices, charges, payouts, and your books, so that one document explains every difference.
Choose the direction with care. Rounding down and rounding up each favor one side of the transaction, so pick the direction deliberately rather than letting each spreadsheet decide for itself. Talk to your firm's accountant about how the direction affects your books and any tax treatment in your jurisdiction before you publish the policy. This post does not give tax advice, and the right answer depends on your local rules.
Test the policy with real examples before a client sees it. Choose one zero-decimal currency, one currency with a smaller unit, and one HUF or TWD payout case. Run each through the lookup table and the policy, then compare the result with what the Stripe dashboard shows. If the figures match every time, the process is ready. If they do not, the gap is in the lookup table or the policy, and you can fix it before any money moves.
Reconcile weekly rather than at year-end. Pull the list of charges and payouts for the week, match each one to its invoice, and list every difference, including the small ones. A difference found on the same week is usually a typing error or a missing rule, and it is easy to trace. The same difference found in December may have passed through several reports and become hard to explain. You can set a threshold for differences that need a second look, but log every one of them. For a related routine, see Client bank reconciliation with 4 balance checks.
Keep a short log of each reconciliation: the date, the number of items checked, the differences found, and who resolved each one. A log like this shows a new team member, or an outside reviewer, how the firm handles currency differences without anyone needing to explain it from memory.
Common mistakes to watch for
Several mistakes repeat across teams, and it helps to name them before they happen.
The first is copying a working setup into a new currency and changing only the label. The old setup still carries its old logic, so the amount is built the wrong way. Test the setup with a real example in the new currency, not just by reading the label.
The second is trusting the displayed balance. A balance with a fraction cannot go out in full as a manual payout in HUF or TWD, so a payout form that worked last month can fail this month. Check the amount value before you submit, every time.
The third is treating rounding as someone else's job. If the developer, the bookkeeper, and the client each round in a different place, the numbers will disagree by small amounts that no one owns. One person should own the policy, even if several people apply it.
The fourth is assuming an old screenshot is current. Documentation changes, and a note saved last year may no longer match the page. Date your notes and recheck them on a schedule, so the team is not relying on a snapshot of a page that has since been updated.
The fifth is leaving the payout to the end of the month without checking the balance. A fraction that was easy to see earlier in the week can be forgotten by the time the month closes. Look at the balance on the day you plan to pay out, not at a figure copied from an earlier report.
Explain the amounts to clients before they see them
Clients rarely object to a conversion they understand. They object to a surprise. When a client pays in a currency with no smaller unit in everyday use, or receives a payment that differs slightly from the invoice, a short note on the invoice can reduce the follow-up questions. Before you send the invoice, run through Invoice checks: 4 steps before sending a client bill. Say which currency the invoice is in, state the amount exactly as it will be charged, and mention the rounding rule if the rounding is visible on the page.
Keep the language plain. A client does not need to know what an amount value is. They need to know that the total they see is the total they will pay, and that any rounding follows a rule you can point to. If a client asks about a difference, answer with the rule and the figure, not with a general apology. A clear answer builds more trust than a vague one, and it closes the question faster.
Consider adding one paragraph to your engagement letter that describes how your firm handles currency conversion and rounding. Ask your firm's advisers for the wording, because this is not legal advice. The goal is that the first time the topic comes up is not in the middle of a dispute. A client who has read the policy in advance is far more likely to accept it when the first invoice arrives.
Where to confirm the details
Keep the supported currencies page open while you set up billing: Supported currencies | Stripe Documentation. It is the source for every Stripe rule in this post. Stripe can update its documentation, so if anything here conflicts with the page, follow the page and update your internal notes.
Four rules, one habit: check the currency before you type the amount. Billing problems in foreign currencies often come from skipping that step, and the four rules above make it easy to build the check into your routine.
Related guides: Stripe monthly billing dates: 3 rules for client fees · Accountable plan tests: 3 rules before a reimbursement · Beneficial ownership: 3 rules before entity intake.
Frequently asked questions
Is the amount I enter the same as the price the client sees?
Not always. For a zero-decimal currency such as JPY, the amount value is the yen figure itself. For a currency with a smaller unit, such as ISK, the amount value differs: 5 ISK is provided as 500.
Can I pay out my full HUF or TWD balance?
No. For manual payouts in HUF or TWD, the amount value must be evenly divisible by 100, so a balance with a fraction cannot go out in full.