An advisor can attach a CSV or PDF statement to Dora and request a transaction import. Review the Transaction import proposal and select Import before Kerdora starts adding entries to Spending. Approval and completion are separate stages.
How do I import transactions from a statement?
Start the transaction import in Dora within the intended client's file. Use a CSV export or readable PDF statement with account identity, dates, descriptions, and amounts.
Open Dora and use the paperclip icon with the Attach files tooltip to choose the file.
Send a request such as: “Import these transactions into Jane's existing checking account ending 1234. This statement covers January 2026.” If Dora's upload card appears under your message, answer it with Send, File N & send, or Skip so your message goes to Dora.
Confirm which existing account each source account should use. Check institution, account type, owner, and account ending; ask Dora to clarify an uncertain match.
If the destination account is missing, Dora proposes its creation separately. Review and approve that account; Dora can then continue automatically to prepare the transaction-import proposal.
Review the Transaction import card, then select Import or Reject.
This is an advisor approval workflow. Clients can upload documents through their own supported document flows, but can't approve this transaction-import proposal. After import, clients can see the resulting household transactions in Spending.
What do Skip and Send do on Dora's upload card when I import transactions?
When you attach a new statement to Dora, Dora's upload card can hold your message until you decide where that file goes. That card starts “Dora sorted these. Change any before sending.”
Each file has a list, preset to Dora's read when Dora has one: a folder on this client's Documents page, Documents for the top level, or Don't file. Change any preset you disagree with. If a file shows Choose…, pick one before you can file or send with those buttons. Skip stays available.
File N & send, such as File 1 & send: files those files on this client's Filed tab, then sends your message. These files stay hidden from your client until you show them. Any file set to Don't file is kept as a record, not filed.
Send: appears when every file is set to Don't file. Kerdora keeps those files without filing them, then your message goes to Dora.
Skip: sends your message and leaves every file in this client's Inbox, for you to decide later.
All 3 send your message, and Dora can read your statement after any of them. None imports a transaction; that still waits for Import on a Transaction import card.
If you leave before answering Dora's upload card, your message isn't sent and your files stay in this client's Inbox.
How do I file a statement later after sending it to Dora for a transaction import?
Under your Dora message, select File in Documents… to file a statement you sent for a transaction import. It reads File 2 files in Documents… for 2 files, and it shows only while a file from that message isn't filed.
Find your message with that statement in that client's Dora conversation.
Select File in Documents… under it.
In Where these go, choose a folder, or Documents for the top level.
Select File, or File 2 and so on when you file more than one file.
Use this for a file you skipped, which waits in that client's Inbox, or for a file Kerdora kept without filing, which no screen lists. Filed statements stay hidden from your client until you show them on that client's Filed tab. Filing a statement doesn't import or change any transaction.
Why didn't Dora's upload card appear when I attached a CSV for a transaction import?
Dora's upload card doesn't appear when Dora reads every new file in your message as working material, as it can with a CSV export. Your message goes straight to Dora, and Kerdora keeps those files as records without filing them.
Dora can still read that file for your transaction import. No screen lists kept files. To file that CSV on this client's Documents page, select File in Documents… under your message in Dora. In Where these go, its list starts at Don't file, so choose a folder or Documents, then select File. Done keeps that file without filing it.
What should I check before selecting Import?
In Dora's Transaction import card, compare the proposed transaction count, date range, Inflows, Outflows, Net, and source filenames with the original statement. The card shows no individual rows or destination account mapping, so confirm account choices in the conversation before approval. Its date range can be the statement period Dora read rather than the first and last transaction dates.
Inflows use positive amounts and outflows use negative amounts internally; the card displays Outflows as a positive total. A purchase assigned the wrong sign can inflate income instead of spending.
If the count, period, signs, or account mapping is wrong, select Reject, then explain the correction and request a rebuilt proposal. Dora's reply box is disabled while a proposal waits for a decision.
Selecting Import has no undo control, and imported transactions have no Delete control. Reject a proposal that looks wrong. After approval, hiding can exclude entries from Spending totals while retaining their records.
The card’s totals summarize proposed rows, not an independent reconciliation against the statement. Check them even when Dora’s description sounds confident.
Can I keep categories and tags from my source file?
A Dora transaction import can carry source categories and tags when you confirm how they map to existing Kerdora records. Source labels don't automatically become matching Kerdora categories just because their names look similar.
Tell Dora whether to use the file's categories or tags and review the proposed mapping. Create missing categories or tags in a separate setup step before the import uses them; Spending Categories, Groups, and Tags explains those controls.
Rows without sufficient confirmed merchant and category information go through automatic classification after approval. Review that result in Spending rather than treating it as a verified reading of the source.
Imported categories can later be superseded by Spending rules or an individual manual category. Keep the original export so you can compare source labels with Kerdora's current display.
How do I move transactions from Monarch to Kerdora?
Export your transaction history from Monarch as a CSV, then attach that CSV to Dora within the intended client’s file and request a transaction import. Kerdora doesn't provide a dedicated Monarch migration button, and this workflow doesn't recreate a Monarch budget or guarantee that every source label maps automatically.
For a history such as 19,000 transactions, start with a manageable account and period whose totals you can reconcile. Preserve dates, descriptions, amounts, account identity, and any category/tag columns you want mapped; keep an unchanged copy of the original export.
Ask Dora to confirm account and category mappings before producing the import proposal. Check each proposal's count and totals against the corresponding portion of the export, then wait for completion before approving another portion. Use non-overlapping account/date segments.
There isn't a displayed fixed transaction-row limit in this workflow. That doesn't guarantee a 19,000-row file will parse, map, and import successfully in one attempt. Contact Kerdora Support if a large proposal is incomplete or processing stops.
What happens after I select Import?
Dora's approved Transaction import card reports background progress, with labels such as Queued, Classifying, Importing, and Imported. The imported count is separate from the approved status; entries can arrive as processing completes rather than appearing all at once.
Watch the imported count against the total on the existing card.
When processing finishes, open Planning → Spending → Transactions.
Filter to the intended account and date range, then compare the imported activity with your source.
Review categories, refunds, and transfers before interpreting Cash Flow or Analyze.
A completed import doesn't certify the source data or classification. It also doesn't update the household's Profile spending assumption. Categorizing and Filtering Transactions covers corrections; Cash Flow: Income, Savings, Spending, Debt Payments, and Giving explains the planning amount.
What should I do if an import needs attention?
Dora’s Transaction import card can show Needs attention during automatic classification retries. Check its imported and failed counts; some entries may already be saved, and the warning can clear after a retry.
Reopen the existing Dora conversation later to check progress. If failures persist or an approved card continues to show no progress, contact Kerdora Support. Include the household, filename, destination account ending, statement period, proposal count, imported and failed counts, any error, and the existing Dora conversation.
The approved card has no Retry button. Don’t submit the same file again: a new proposal can duplicate entries already imported. Keep the original source file while Support investigates.
Can I undo an approved transaction import?
Dora-imported transactions have no Delete or Undo control in Kerdora. Hiding an incorrect or duplicate entry keeps it out of Spending totals but retains its record.
For one confirmed incorrect entry, open Planning → Spending → Transactions, open the entry, and select the eye control with the Visible in spending — tap to hide tooltip. Confirm Hidden from spending appears. Categorizing and Filtering Transactions explains how to find hidden entries later.
For repeated entries, Spending Rules: Automatically Categorize Transactions in Bulk explains hiding rules. Check the rule’s matches carefully so valid activity stays included. For help with a whole import, contact Kerdora Support with the household, source filename, and Dora conversation; don’t assume bulk removal is available.
Can I import a statement for an account that's already linked?
You can request a Dora import into an existing linked account, but first compare the statement period with transactions already in Planning → Spending → Transactions. A file import and a linked feed aren't guaranteed to merge the same activity into one entry.
Use a statement to fill a verified gap rather than importing an entire overlapping period. Compare account, date, amount and sign, merchant, and source description; two similar entries can also be legitimate transactions or two sides of a transfer.
For individual suspected duplicates, see How Do I Handle Duplicate Spending Transactions? For an overlapping import, hide confirmed duplicates from Spending or contact Kerdora Support. Imported transactions have no Delete control.
Importing transactions doesn't connect an institution, replace account review, or update an account balance. Linking Accounts and Understanding Synced Data explains the connection procedure.
What if my statement won't upload or read correctly?
For Dora transaction imports, use CSV when you can inspect its rows and amount signs clearly, or a readable PDF statement. A blurred scan, missing page, or incomplete export can produce an incomplete proposal even if upload succeeds.
The document service accepts up to 20 files per upload, each 50 MB or smaller, and allows 30 upload requests per user per hour. These are upload limits, not a promised transaction count or processing time. Split a long history into non-overlapping periods that remain easy to reconcile.
For protected PDFs, follow the password prompt. For detailed upload errors and supported document formats, see Using Upload & Extract for Client Data. If a file uploads but its proposal remains incomplete, keep that source and contact Support rather than approving an unexplained count difference.
