Skip down to the research record

Currency amount examples: 3 checks before a deal total

Quota Forecast Editorial Team · Published · 10 min read

Stripe asks you to provide an amount value, and its examples show the same value can stand for different amounts, depending on the currency. To charge 500 JPY, according to Stripe, you provide an amount value of 500. The same amount value of 500 is used, according to Stripe, to charge 5 ISK or 5 UGX, so the number alone does not show the money.

Key takeaways

  • Read each amount value with its currency: according to Stripe, an amount value of 500 stands for 500 JPY in one example and 5 ISK or 5 UGX in others.
  • Check each deal amount against its billing amount in the same currency before you add a total.
  • Write the currency beside every amount you copy from a billing report into a forecast sheet.

Why billing amounts and deal amounts differ

Billing records and deal records describe money in different units, so a matching number can hide a different charge. Stripe states that "You can charge customers in over 135 currencies and receive funds in your preferred currency," according to Stripe. A customer can therefore be charged in one currency while the deal sits in another. Your review starts by asking which currency each number uses before you read the number.

A useful habit is to keep a currency column beside each amount you copy from a billing report into a forecast sheet. The column does not change any figure, but it gives the forecast call a unit for each number. That keeps the comparison in one set of terms from the first line to the last.

Each billed charge can be paired with the deal it supports before any total is made. If a billing line has no clear deal, a short note can be placed beside it instead of guessing which deal amount it matches. The note also leaves a clear trail for whoever reviews the total later.

Your comparison should not assume an exchange rate unless your own billing export states one. The examples in this article show amount values, not exchange rates, so they cannot settle a conversion question. If your export does include a rate, that rate can be written beside the amount, so the conversion stays visible to the reader. The total can then be read without guessing how the two currencies were brought together.

Your notes can put the currency and the amount value on one line, then the deal amount on the next line, so the two are compared in the same units. The reference table below lists the quoted wording from each publisher used in this article, so each line can be checked against a quote rather than memory.

PublisherSourceQuoted wording
StripeSupported currencies page"For example, to charge 500 JPY, provide an amount value of 500."
ChargebeeCredit notes page"The currency code (ISO 4217 format) of the place of supply in which VAT needs to be converted and displayed."
ZohoUpdate deal solutions page"In some cases, the field may be left blank initially and updated later, reducing the reliability of your pipeline visibility."

JPY example: 500 JPY is an amount value of 500

The first example comes from Stripe's own wording, which pairs 500 JPY with an amount value of 500, according to Stripe. The wording is short, but it names the currency and gives the value as a separate number. That separation is the core of the check in this article. Each billing amount can be read as a pair of values rather than as one figure.

In plain terms, the number 500 in this example is the amount value, and JPY is the currency that the charge uses. The value without its currency does not tell a reader what was charged. When a billing line shows 500 with no currency beside it, the line is incomplete for a forecast comparison. The currency can be added before the line enters the sheet.

When a deal in your pipeline is in yen, the deal amount should use the same currency as the billing line you are comparing. If the two currencies differ, the comparison can be paused and the amount noted. A matching number in two currencies is not a match. The deal can then be set aside until both amounts share a currency.

A check row for this case can read: currency JPY, amount value 500, and the deal amount beside it read in JPY before any total is added. The row does not need a conversion step, because both amounts sit in the same currency. Adding the date of the check beside it makes the review easier to trace later.

This example can stay in your notes as the reference for yen, so a new yen deal can be checked against a known case before it enters a total. The same approach can be used for the other examples in this article, with each currency checked on its own line. A yen pattern should not be assumed for other currencies unless a source states that pattern.

ISK example: 5 ISK is an amount value of 500

The next example uses a different currency with the same amount value, as the Stripe wording shows: "For example, to charge 5 ISK, provide an amount value of 500," according to Stripe. The number is identical to the first example, but the currency is not. A reader who checks the number alone may see a match where the money differs.

Beside the first example, the contrast is plain: an amount value of 500 is 500 JPY in one case and 5 ISK in the other. If the value is read as 500 ISK, the figure is a factor of 100 higher than the 5 ISK in the example, which is the misread this article warns about. A deal total that adds 500 from a yen record and 500 from an ISK record treats two unlike figures as one unit.

Each figure can carry its currency code before the addition is made. Your total step can check the currency code on each line first. A practical check is to ask whether a deal amount of 500 in your CRM was entered as ISK or as JPY, and to confirm the currency from the source record. The same question applies to any amount that matches a billing value exactly, because an exact match is the case where the currency is most easily skipped.

Your team can agree which record is the source for currency, so the question is answered the same way each time. Keep the currency beside the amount in your record. Your notes can also mark a deal for a second look when its currency is missing from the record. That flag can stay in place until the currency is confirmed.

UGX example: 5 UGX is an amount value of 500

This example uses UGX, and the Stripe wording follows the same form: "For example, to charge 5 UGX, provide an amount value of 500," according to Stripe. The amount value is again 500, while the currency differs from both earlier examples.

The same number appears in three currencies, and none of the three can be read from the number alone. Your comparison can therefore treat the currency as the first item in each record.

A short comparison sheet can put the three examples in three rows, each with its currency code, its amount value, and the matching deal amount. The sheet is for reading, not for converting, so it needs no conversion column.

When two deals show the same number but one is in UGX, a note can say that the currency is not yet checked until a second record confirms it.

For a related check on totals, read catalog price before the software deal total before you add a deal to the forecast.

Illustrative example: matching numbers in two currencies

Suppose a forecast sheet has two rows. The first row holds a billing amount value of 500 in JPY. The second row holds a deal amount of 500 with no currency written beside it. The numbers match, but the match is not yet proven. Confirm the currency on the source record before either row enters a total. If the deal is in ISK, its 500 stands for a different amount from the yen charge, so the two rows are paired only after the currency is settled.

Payout amounts that must divide evenly by 100

Payouts follow their own rule, which is separate from the charge examples above. The Stripe wording reads, according to Stripe, "When you create a manual payout in HUF, you must provide integer amounts that are evenly divisible by 100." The rule concerns the form of the amount, not the deal.

The rule can be read as two tests: the amount must be an integer, and it must divide evenly by 100 with no remainder. Those tests check the number itself, so they can run on a payout line before any deal is touched. A payout line that fails either test deserves a closer look before it is included in a summary.

A deal amount is not a payout, so the HUF payout rule should not be applied to a deal amount without a reason. A clear label on each line keeps the payout check and the deal check apart.

When you compare a payout with a forecast line, you can write down the currency, check that the amount is a whole number, and check that it divides by 100 as the rule describes. The result can sit beside the line, so the check stays visible during the review. A payout that passes the check can still differ from a deal, so the comparison remains a separate step.

A small team that reviews deals and payouts in the same meeting can use separate headings for each check, so the rule and the line stay matched.

Blank deal amounts and the ISO 4217 currency code

A blank deal amount has a documented effect on visibility, though not a fixed one. According to Zoho, a deal amount may be left blank at first and updated later, which can reduce the reliability of pipeline visibility.

The timing words initially and later describe a gap: a field can be empty first and filled afterward. A late fill is a good moment to compare the deal against its billing amount again. For a separate look at weighted totals, see weighted deal amount rules before changing any deal amount.

Chargebee uses the ISO 4217 format for the currency code, according to Chargebee, but that wording concerns VAT. It describes a format for the code rather than a rule for deal amounts.

Your notes can use the ISO 4217 format for each currency label, so a code and its amount value sit together. The code gives a reader one fixed label to compare against a billing line, which is simpler than writing a currency name in full.

A short note of when each deal amount was first filled in can make a later update easy to find during review. The note combines the date with the currency code, which gives the review two checks in one line.

Next step before the forecast call

Your next step is to pick three recent deals in different currencies and compare the billing amount value with the amount stored on the deal. The currency can sit beside each pair, and any pair where the two figures do not share a unit can be set aside.

FAQ

How do I charge 500 JPY in Stripe?

To charge 500 JPY, according to Stripe, provide an amount value of 500. Check the currency before you compare that amount with a deal.

What amount value do I send for 5 ISK?

To charge 5 ISK, according to Stripe, you provide an amount value of 500. The value is 500 even though the charge is 5 ISK. A deal amount that reads 500 for this charge should be checked against its currency.

What does the HUF payout rule require?

The Stripe rule says that a manual payout in HUF must provide integer amounts that are evenly divisible by 100, according to Stripe. Each payout line can be checked against this requirement before it enters a summary.

What amount value do I send for 5 UGX?

To charge 5 UGX, according to Stripe, you provide an amount value of 500. The value is the same as in the ISK example, but the currency is UGX. Your notes can keep the currency next to the value, so the two stay together.

Sources