The date 04/05 can mean April 5 or May 4. The amount 1.234,56 can represent the same numeric value as 1,234.56 under another locale's punctuation rules, but an incompatible parser may misread it.
These are not cosmetic differences. A date error can move a bill into the wrong month, and a numeric error can make a balance unusable.
Follow the documented input format
Check the current template's required date, number and currency conventions. Do not assume that the language displayed in the interface automatically determines how an imported file is parsed.
Financeia's public journal provides import resources. Use the current guide and example rather than adapting an old spreadsheet from memory. Financeia
Where a format is ambiguous, resolve it before upload. A file that looks correct in your spreadsheet application may contain underlying values or text that another system interprets differently.
Test signs with a simple calculation
Suppose an account opens at 500, receives 1,000 and pays out 300. The expected closing balance is 1,200.
If an import treats the 300 payment as positive, the result becomes 1,800. That simple test reveals a sign problem more clearly than reviewing hundreds of rows in a large account.
Check whether the template expects signed amounts, separate inflow and outflow fields or another convention. Use the actual instructions rather than guessing.
Keep currency roles distinct
A merchant purchase of EUR 100 might settle as USD 112 with a separately identified USD 2 fee. The receipt amount, settlement amount and reporting conversion should not be collapsed into one unsupported figure.
Assign the correct currency to the correct amount and account. A numeric value of 100 without a currency is incomplete evidence in a multi-currency record.
Do not assume that a currency symbol alone is unambiguous. Several currencies use similar symbols, so the supported currency identifier matters.
Inspect edge cases deliberately
Include a date after the twelfth day of the month, a decimal amount, a large amount with a thousands separator, a refund and a transfer in the test sample. These cases expose errors that a file of round numbers and unambiguous dates may hide.
Check the imported dates and amounts visually as well as through the closing balance. Two errors can occasionally offset, leaving the total correct while individual records remain wrong.
Retain the preparation rules and source files. If a later import fails, you should be able to identify what changed rather than starting the investigation from zero.
A reliable import is one whose interpretation is known. The absence of an error message does not establish that the dates, signs and currencies were understood correctly.