Import a bank or credit-card statement by attaching a CSV or PDF to Dora and asking Dora to import the transactions. Dora matches the statement to a Kerdora account and creates a Transaction import card for review. No transactions enter the client file until an advisor selects Import and the background job finishes.
Use this workflow when an account isn't linked through account aggregation or when the statement covers history that the linked account doesn't provide.
How do I import transactions from a statement?
Open the client and start a conversation with Dora.
Attach the bank or credit-card statement as a CSV or PDF.
Ask Dora to import the transactions.
If Dora asks which Kerdora account matches the statement, confirm the correct account. Dora compares details such as institution, account type, account name or owner, and the last four digits when available.
If the account doesn't exist, let Dora prepare the account creation first. Approve that separate proposal before asking Dora to continue the transaction import.
If the statement contains its own categories or tags, answer Dora's mapping questions. Source categories must map to existing Kerdora categories. Create any needed tags or categories in a separate setup step before the import.
Review the Transaction import card.
Select Import to approve it, or Reject to cancel it.
Don't guess when more than one Kerdora account could match a statement. Confirm the institution, account type, owner, and last four digits before selecting Import.
What should I review on the Transaction import card?
The card shows:
a pending, approved, or rejected status;
the number of transactions and statement date range;
Inflows, Outflows, and Net totals;
the source document names; and
Import and Reject while the proposal is pending.
Compare the count, date range, and totals with the original statement. Kerdora expects inflows to be positive and outflows to be negative. If purchases appear as inflows or the totals don't match the statement, select Reject and ask Dora to rebuild the proposal with the corrected sign treatment.
What happens after I select Import?
The card remains in Dora and shows progress through Queued, Classifying, and Importing. It also shows the number imported out of the total. When the job finishes, open Spending → Transactions to review the imported activity.
Transactions without confirmed source mappings are classified after approval. Review merchant names and categories, hide transfers when needed, and create rules for recurring descriptions.
If the card reports failed transactions or says transactions need attention, compare the affected count with the statement and contact Kerdora Support if retrying the import doesn't resolve it.
Can I import a statement for a linked account?
Yes, but first check whether account aggregation already brought in the same period. Importing the same activity again can create duplicates. Use Spending → Transactions to compare account, date, description, and amount before approving an overlapping statement.
If duplicates are already present, follow the duplicate-transaction workflow rather than deleting an account or disconnecting its institution.
What file should I use?
Use a CSV when the institution offers one because its rows and signs are usually easier to validate. A text-based PDF statement can also work. A scan with unreadable dates, descriptions, or amounts may need a clearer export before Dora can build a reliable proposal.
For long histories, splitting files by statement period makes totals and duplicate checks easier to review. Kerdora doesn't display a fixed row limit in this workflow, so judge each proposal by its transaction count, date range, totals, and successful completion.
What doesn't this import change?
Importing transactions does not link the institution, update an account through aggregation, or create a missing account automatically. Account creation and category or tag setup are separate proposals that must be completed before the transaction import uses those records.