Quickbooks File Repair — Forced comma replaces decimal point in check register
"Forced comma replaces decimal point in check register" is a data-entry failure caused by mismatched Windows regional settings, where QuickBooks insists on a comma as the decimal separator and rejects the period. Users report that a restored backup saved every entry with a comma in place of the decimal point, and that new entries fail with a message that the decimal point is an invalid character -- yet typing a comma doesn't work either.
What this error means
QuickBooks reads its number formatting from the Windows regional and language settings. When those settings specify a comma as the decimal symbol (common in many European locales), QuickBooks expects amounts like 1,50 instead of 1.50. If the file was created under one format and is being used under another, every amount entry collides with the expected separator, blocking new transactions.
Symptoms you'll typically see
- The check register shows commas where decimal points should be.
- Entering a period triggers "the decimal point is an invalid character."
- New entries cannot be saved at all.
What you can safely try first
The fix is to align the Windows regional settings with the format QuickBooks expects:
- Open Control Panel (in Windows, click Start, then Control Panel).
- Double-click "Regional and Language Options."
- Under the formats/customize area, set the decimal symbol to a period and the digit-grouping symbol to a comma (or match the locale the file was built for).
- Apply the change, then close and reopen QuickBooks so it re-reads the settings.
Make a copy of the file first in case existing entries were already saved with the wrong separator.
When professional recovery is the safer path
If a batch of entries was already stored with the wrong separator and the register now shows incorrect amounts, correcting the regional setting alone may not undo the bad values. Our engineers can repair the affected transactions and return a clean, verified .QBW file. We work in-house across North America, and our no-data, no-charge policy means you owe nothing if we can't recover your data.