Fix foreign-currency amounts that look 100x too large
On this page
If amounts in Japanese yen, Korean won or another currency without cents look 100 times too large, Pennyweight has a one-time repair for them. It runs in the web app, in your own browser, and checks your transactions before it changes anything. For how Pennyweight handles more than one currency, see accounts and totals in more than one currency.
What you'll see
A transaction in a currency without cents shows an amount 100 times its real size. A ¥63,750 charge, for example, shows as ¥6,375,000. Totals that include those transactions are inflated too.
Why it happens
Some currencies have no cents: a price in yen or won is a whole number. Before Pennyweight supported more than one currency, it stored every amount as if it had cents. For a currency without cents, that made the stored amount 100 times too large.
Your transaction amounts are encrypted with a key from your passphrase. The repair runs only in the web app, once you've unlocked it with your passphrase. Your AI can't run it.
How to fix it
- Open the web app and go to Settings → Security.
- Find the Fix foreign-currency amounts card and select Open. The page opens with "A one-time repair that runs in your browser."
- Under step 1, select Check my transactions. It "Looks at every transaction and reports what would change. Nothing is changed yet."
- Read the summary. It lists each currency with how many transactions it holds, how many will be corrected and how many were already fixed, and shows examples of amounts before and after.
- Under step 2, Fix them, select Fix my transactions. The step says "This can take a few minutes on a large history — keep this tab open." A progress bar counts the transactions as they're corrected.
- Read the result. Finished means every planned change was saved. Your amounts, reports and totals show the corrected numbers.
If the page sends you to the unlock screen, your session isn't unlocked. Enter your passphrase and open the page again. If your passphrase isn't accepted, see wrong passphrase on unlock.
What the check reports
- Amounts to correct. "have the wrong amount and will be corrected", with examples from your own transactions.
- A missing currency label. Some transactions have the right amount but no currency recorded. Their amounts don't change; only the currency label is added. Step 2 can offer to correct transactions even when the summary says "No transaction amounts need correcting." Those are the label-only changes.
- Already fixed. Transactions fixed by an earlier run are counted and skipped.
- Nothing to do. "Nothing needs fixing. Your amounts are already correct." Step 2 then reads "There's nothing to fix — you're all set."
- A very large history. "Your history is larger than this check can cover in one pass. Fix what was found, then run the check again to continue."
- Unreadable transactions. Any that "couldn't be read and will be left alone" are listed by ID.
Good to know
- Safe to rerun. The page says "Safe to run more than once — anything already fixed is skipped." Each corrected transaction is marked, so a second run never rescales it again.
- Dollars, euros and pounds keep their amounts. Currencies with cents were always stored correctly. For this check, a transaction with no currency recorded on it counts as US dollars and is never rescaled. The check doesn't look at the account's currency.
- Three-decimal currencies are corrected too. Currencies such as the Kuwaiti dinar and the Bahraini dinar show "3 decimals" in the summary. Their amounts are multiplied by 10, not shrunk.
- Your whole workspace is checked. The check covers every ledger in your active workspace except demo ledgers.
- Categories don't change. The repair saves each transaction with the category it already has.
- If some transactions couldn't be updated, the result reads Finished with problems and lists them. They're left unchanged. Run the check again to pick them up.
- The work happens in your browser. Your transactions are decrypted on your device with the key that's already unlocked. Each corrected transaction is encrypted again before it's saved.
If totals still look off after the repair, see totals look wrong.