2. Create or select an import profile
Open More → Import → Import CSV. In Select Import Profile, choose an existing profile that matches this export, or choose Create Profile. When profiles already exist, the add action is New Profile.
In Import Profile, name the profile and set Delimiter and Has Header. Under Column Mapping (name or index), map Date Column, Merchant Column, and the amount field or debit/credit fields your export uses. Add optional category, note, type and account mappings when those columns exist.
For the synthetic example, map Date, Merchant, Amount, and Category to their corresponding fields. Choose Negative = Expense under Sign Convention. Use Date Format (optional) or Date Interpretation when the date structure needs to be explicit. Check Default Account Name if the file has no account column, then save the profile.
3. Pick the file and check the preview
Choose Pick CSV File and select your CSV. Preview Rows shows the first 20 mapped rows, so it is a sample of the file, not proof that every row will import successfully.
Check dates, merchant names, expense versus income direction, amounts, categories and accounts. If everything appears in one column, check the delimiter. If dates or signs are wrong, edit the selected profile and rebuild the preview before continuing. Refresh Preview and Detect Delimiter are available after selecting a file.
Do not continue just because the preview contains rows. The mapping should explain the file correctly, including a known expense and a known income entry where present.
4. Import and verify what was saved
Choose Import CSV once the preview is right. Read the summary, including imported transactions, skipped duplicates and any Failed Rows. A preview can look correct while a later row fails, so inspect the final result. If you stop an import, rows already saved remain; check the summary before retrying.
Use Review This Import to examine the batch’s records, or Open Migration Center for its checklist and account links. Compare the imported date range, transaction count and amounts with the source file, allowing for skipped duplicates and failed rows. Then use Reports with the same date range to check the overall spending and income picture.
If the file or mapping was wrong
Open the affected batch in Migration Center and inspect it before using Undo Import. The confirmation explains that Penniva removes transactions and imported setup created by that batch; manual edits outside the import stay in place. Undoing is a data change, so read the confirmation carefully before proceeding.
Import history, review and undo remain accessible after Pro ends. If a failure is unclear, contact support with the error and app version. A small, redacted or synthetic example is more useful than sending your full financial history.