The structured bank import expects exact amounts with up to two decimal places. A value with additional fractional digits needs source review before it can be imported through this workflow.
- Check whether the mapped column is the posted transaction amount or another value such as a rate, unit price or calculated estimate.
- Compare the movement with the bank’s posted statement amount.
- Use the supported source amount only when the evidence establishes it, then preview the corrected working file.
Do not round every row automatically just to satisfy the parser. The sum of rounded values can differ from the actual posted movement, and an unsupported currency precision requires its own accounting review.
Check the account currency
Confirm that the source account currency and file currency agree. A file containing foreign purchase values alongside settled account-currency amounts may require the settled movement column rather than a conversion calculation.
If the bank’s official posted amount itself uses unsupported precision, preserve the source and ask support about the appropriate workflow. Include the currency and example format without exposing unnecessary account details. A successful numeric parse must not come at the cost of changing the financial evidence.
Was this article helpful?
Tell us whether this answered the question you came with.