QuickBooks: "The uploaded file contains invalid transaction amount information"
Intuit's own help center lists this exact sentence — “The uploaded file contains invalid transaction amount information” — as the reason a bank-transaction upload fails in QuickBooks Online. The Amount field takes digits, one decimal point and an optional leading minus, and nothing else: no currency symbol, no thousands separator, no parentheses, no trailing minus, and — outside the point-decimal convention — no comma at all.
Built for bookkeepers, accountants and small-business owners preparing a bank, invoice or journal file for Xero or QuickBooks Online.
Read from Intuit's own help centerFix bank upload errors in QuickBooks Online — quickbooks.intuit.com/learn-support — read 13 September 2026
What this error means
QuickBooks Online's bank-transaction importer reads the Amount column as a plain number: digits, a single decimal point, an optional leading minus sign, and nothing written around or inside it. Intuit's own article names a currency symbol, a comma used for grouping or as a decimal mark, parentheses around a negative figure, and a trailing minus sign as the writing conventions that trigger this rejection — every one of them ordinary in some country's own bookkeeping, and every one of them refused here.
What causes it, and what our engine actually checks
Accounting Import Check runs five separate rules over the Amount column to match what QuickBooks actually refuses: amountCurrencySymbol for a $, €, £ or similar mark; amountThousandsSeparator for a grouping character; amountDecimalComma for a comma used as the decimal point; amountParenthesesNegative for a bracketed figure; and amountTrailingMinus for a minus sign written after the number instead of before it. QuickBooks' own severity rules make the first four blockers and the fifth a warning, which the engine matches exactly rather than treating all five the same.
What the engine found in two sample files
A sample bank-transaction file written the way a European export often is raised four blockers and a warning: “$1000” as amountCurrencySymbol, “1.000,00” as both amountThousandsSeparator and amountDecimalComma at once (QuickBooks refuses the grouping dot and the decimal comma alike), “(45,00)” as amountParenthesesNegative, and “45,00-” as amountTrailingMinus, a warning rather than a blocker. A second, otherwise unremarkable sample file — entries as plain as “1.234” and “2.500” — raised none of those five. It raised amountDecimalAmbiguous instead, because nothing in the file says whether 1.234 means one thousand two hundred thirty-four or one and a fraction. QuickBooks does not reject that file at all: it imports it, and whichever reading is wrong, the ledger is now wrong by roughly a thousandfold.
amountCurrencySymbolBlocker1“$1000” → “1000”
amountParenthesesNegativeBlocker3“(45,00)” → “-45.00”
amountTrailingMinusWarning4“45,00-” → “-45.00”
amountDecimalAmbiguousBlocker“1.234”
amountThousandsSeparatorBlocker2“1.000,00” → “1000.00”
amountDecimalCommaBlocker2, 3, 4, and 5“1.000,00” → “1000.00”
Blocker stops the import outright. Warning usually gets through but is worth checking before you trust the numbers. Notice is informational — safe to leave, safe to clear.
Reproduced from two sample files — read September 13, 2026.
Check your own file for this
Drop the file you were about to import below. It is read in this browser tab, the same engine runs the same check, and you will see immediately whether this exact problem is in it.
CSV, TSV or Excel, up to 20 MB
How to fix it by hand
Open the file in a spreadsheet program and strip every currency symbol, grouping character and set of parentheses from the Amount column, rewriting a bracketed or trailing-minus figure as a plain leading minus. If your export writes amounts the European way — a comma for the decimal point — replace every comma with a point before uploading; QuickBooks reads a point and nothing else. If a value like 1.234 could mean either a thousand or a fraction, check the original statement rather than guessing: get it wrong here and QuickBooks will neither notice nor tell you.
Frequently asked questions
- What does QuickBooks' "invalid transaction amount information" error mean?
- It means a value in your Amount column is written in a way QuickBooks Online's importer does not accept — with a currency symbol, a thousands separator, a decimal comma, parentheses around a negative, or a trailing minus sign. The field only takes digits, a single point and an optional leading minus.
- Does Intuit name any other cause for this error?
- Yes — Intuit's own article also names an amount value of twelve digits or more as a cause, which Accounting Import Check does not check for. Every other documented cause is covered by the five rules this page describes.
- Is there a version of this problem QuickBooks doesn't catch at all?
- Yes, and it is more dangerous than a rejection: a value like 1.234 parses as a number under either the point or the comma reading, so QuickBooks accepts it silently and posts whichever figure is wrong. Accounting Import Check's amountDecimalAmbiguous check is what catches that case before you import, not after.
- Can Accounting Import Check fix an invalid amount automatically?
- For a currency symbol, a thousands separator, a decimal comma, parentheses or a trailing minus, yes — each offers a one-click rewrite to the plain form QuickBooks accepts, shown before and after. Where the decimal convention itself is unsettled, the tool will not guess; it says so and leaves the cell for you to check against the original statement.
What Accounting Import Check does with this file
Accounting Import Check reads every Amount cell before you import and names exactly which writing convention QuickBooks will refuse — a symbol, a separator, a bracket, or a trailing sign — rather than one generic “invalid amount.” Each of the four blockers offers a one-click fix to the plain digits-and-point form QuickBooks accepts, shown before and after, cell by cell. Where the file's own decimal convention cannot be settled at all, the tool says so and offers no fix, because guessing the wrong one is worse than leaving it for a person to check.
The file you'd check is read in your browser tab — it is never uploaded anywhere.
What it cannot do here
Intuit's own article names one more cause our engine does not check: an amount value of twelve digits or more. Every other documented cause — currency symbols, thousands separators, decimal commas, parentheses and trailing minus signs — is covered by the rules above; a twelve-digit amount is not, and a file that fails only for that reason will show as clean here and still be rejected by QuickBooks itself.