Importing accounting data into Klyra
How to import bank statements, historical closures or accounting data into Klyra without duplicating existing entries.
Import lets you load existing accounting data in bulk, such as historical closures or statements provided by your accountant, instead of entering them one by one. A well-prepared import avoids duplicates and keeps the site’s financial history consistent.
Accepted formats
Klyra imports accounting data from structured files, typically tabular, as long as they contain at least a date, an amount and a method or category for each entry. A non-compliant format is flagged before the import completes.
Mapping the file columns
During import you specify which Klyra field each file column corresponds to, for example which column holds the date and which holds the amount. The mapping can be saved for reuse on later imports from the same accountant or system.
- Entry date column
- Amount column
- Method or category column
- Mapping can be saved for recurring imports
Avoiding duplicates
Before confirming, Klyra compares the file rows with entries already present for the stated period and flags possible overlaps, so you can choose to skip or knowingly replace them.
Checking after import
After every import it is worth checking the imported total against the expected total from the original document, to catch rows discarded due to format errors right away.
Cosa trovi in questa guida
- accounting data import
- finance CSV file
- historical closures
- accounting duplicates
- column mapping
- import period
Passaggi
- Open Finance and select "Import accounting data".
- Upload the file provided by your accountant or external system.
- Map the file columns to the fields Klyra requires.
- Specify the period the data refers to.
- Check any rows flagged as possible duplicates.
- Confirm the import after resolving duplicates.
- Check the imported total against the source document.
Problemi frequenti
- Some rows fail to import → date format not recognised in the file → fix the date format and re-import only the missing rows.
- Duplicate entries appear after import → same period imported twice without checking flagged duplicates → remove the duplicate entries and re-import with the correct mapping.
- The imported total does not match the original document → amount column mapped to the wrong field → fix the mapping and re-import the file.
- The import stops partway through the file → a row has incomplete or invalid data → fix or remove the problematic row from the source file.
Domande frequenti
Can I import several periods in one operation?
Yes, as long as the file clearly states each entry’s date; Klyra distributes them into the correct periods automatically.
Does import change cash closures already recorded?
No, import adds separate accounting data and does not overwrite manually entered closures, unless you explicitly choose to when duplicates are found.
Can I save the mapping to reuse every month?
Yes, column mapping can be saved and reused for recurring imports from the same file format.
What if my accountant uses a different format every time?
You can remap columns on each import: the process only takes a few minutes even without a saved mapping.
Guide collegate
Questa guida ti è stata utile?
Hai ancora bisogno di aiuto?
Descrivi il problema: alleghiamo in automatico pagina, sede, organizzazione e ruolo.
Contatta l’assistenza