Use Upload & Extract when you want Dora to read one or more client documents and propose changes to the client file. The files are stored in Documents, and the proposed plan changes appear in a Dora conversation for advisor approval.
Uploading a document does not automatically make every detected value part of Profile. Extraction is a review workflow.
Upload only versus Upload & Extract
Open the client and choose Documents → Upload.
Upload stores the files in the document vault without asking Dora to propose plan changes.
Upload & Extract stores the files, starts a Dora extraction conversation, and asks Dora to propose warranted client updates.
Use Upload when the document is for storage or later review. Use Upload & Extract when you want structured plan updates now.
Prepare the documents
Before uploading:
use a clear, readable copy;
remove unrelated pages when practical;
confirm the file is for the open client;
unlock a password-protected PDF or provide its password when prompted; and
group related documents when they should be interpreted together.
Do not upload another client's document into the current household. Extraction follows the client context in which it was started.
Add files and instructions
Attach files by choosing them, dropping them into the upload area, or pasting long text when the interface offers that option. The pending attachment area shows what will be sent.
The upload area stages up to 15 files at a time. Each file can be up to 50 MB. Current supported upload formats include PDF, PNG, JPEG, XLSX, XLSM, CSV, plain text, Markdown, and JSON. Convert a Word document to PDF before uploading it.
Add instructions when context will improve the result. Useful instructions identify:
who owns an account or policy;
whether the document replaces or supplements an existing record;
the statement or tax year;
which pages or facts matter;
a known nickname or institution relationship; and
what you do not want changed.
Instructions should clarify the source, not dictate an unsupported result. “This is Jane's Roth IRA statement for June” is useful. “Make Retirement fully funded” is not an extraction instruction.
Start extraction
Choose Upload & Extract. Kerdora uploads the files and opens the Dora conversation created for that extraction. Dora reads the documents in the context of the current client and prepares a proposal.
Depending on the documents, a proposal can include new or updated household entities, assets, liabilities, income, insurance, holdings, Changes, Tasks, and other supported client records.
The uploaded files remain in Documents whether you approve or reject the proposal.
Review the proposal
The Dora conversation displays a proposal card with the proposed changes. Review every row before acting.
For each change, confirm:
whether the record already exists;
the owner or insured person;
the account, liability, income, or policy subtype;
amount and frequency;
dates and statement period;
tax treatment;
whether the proposed update would replace a better current value; and
any downstream Goal or planning effect.
The current proposal uses Approve and Reject for the proposal shown. Approval applies the proposed event batch. Rejection leaves the client data unchanged. Do not assume that the document-detail extraction history is a second approval surface.
If one part is wrong, reject the proposal and ask Dora for a corrected, narrower proposal or make the correct Profile edit manually. Do not approve a known duplicate merely because other rows are useful.
After approval
Approval applies the proposed client events. Then verify the result in the appropriate source workspace:
people and entities in Profile Household;
assets and liabilities in Profile Accounts;
income and cash-flow records in Profile Cash Flow;
policies in Profile Insurance;
holdings in the investment account;
Changes in Planning Changes; and
Tasks in Office Tasks.
Check amount frequency, ownership, subtype, and duplicates again in the saved record. Then review any affected Goal, Financials summary, Plan Cleanup item, or Guide.
Extract an existing stored document
Documents can be uploaded without extraction and processed later. In the Documents list, select the applicable files and choose Start Extraction. Add instructions and confirm. Kerdora starts a Dora extraction conversation using those stored documents.
You can run extraction again when the first result was incomplete or when better instructions are available. Re-extraction can propose records that already exist, so duplicate review becomes even more important.
Clients and extraction
Clients can upload documents in the portal. Their onboarding document mode can be Upload Only or AI Extract. Advisor review remains required before proposed plan changes should be trusted.
Clients do not receive the advisor's Dora conversation or proposal-approval workspace.
Best practices
Use the smallest coherent set of documents.
Include owner and date context.
Prefer source statements over screenshots when both are available.
Separate different households and unrelated years.
Review the existing Profile before approving new records.
Reject and correct a mixed-quality proposal rather than accepting known errors.
Verify applied data in Profile, not only in the conversation.
Extraction saves time when it reduces typing and preserves review. It should not reduce the advisor's responsibility to confirm the client record.
Common questions
Does Upload & Extract remove the source file after approval?
No. The uploaded file remains in Documents until an authorized user deletes it. Approval changes the proposed client records, not document retention.
Does rejecting the proposal delete the document?
No. Rejecting resolves the proposed plan changes. Keep, organize, hide, download, or delete the stored document separately.
Can I add more context after Dora finishes reading?
Yes. Reply in the extraction conversation with the missing owner, date, or correction and ask for a new, narrower proposal. Review that proposal independently; it does not inherit approval from the rejected one.
Will uploading a new budget overwrite current cash flow?
No. Upload only stores the file. Upload & Extract prepares a proposal, and current Profile data changes only if an advisor approves the displayed event batch.
Before approving a budget or cash-flow proposal, compare each income, savings, spending, debt-payment, and Giving value with Profile → Cash Flow. Reject a mixed or ambiguous proposal and ask Dora for a narrower correction instead of approving known duplicates.
Why did the account import but the holdings did not appear?
Holdings require enough document detail and a clear destination account. Open the proposal and check whether holdings were included, whether the account already existed, and whether ownership and account identity are unambiguous.
If the approved proposal did not contain holdings, give Dora the account name, owner, statement date, and pages containing positions, then request a new holdings-only proposal. If the document is incomplete or the account cannot be matched safely, enter or correct the holdings manually under Profile → Accounts.
What if a PDF fails to extract?
Confirm that the PDF opens, is readable, is no larger than 50 MB, and is not locked. Scanned pages need legible text and complete page edges. Try the smallest coherent document set with instructions that name the owner, document type, and statement date.
If extraction still fails, store the file with Upload, enter urgent facts manually, and contact Kerdora Support with the client name, document type, approximate upload time, and the error shown. Do not send the client's document through an unapproved channel.
What Upload & Extract does not do
Upload & Extract does not guarantee that every value will be detected, matched to an existing record, or free of duplicates. It does not apply a proposal without the approval action shown to the advisor, and it does not give clients access to Dora's advisor conversation.
Use manual Profile entry when a source is unclear, a proposed value cannot be verified, or a supported record cannot be matched safely.