Review extracted information in the Dora conversation that Upload & Extract or Start Extraction creates. Dora shows a proposal card before ordinary client-plan changes are applied. Approve only after the complete proposal matches the source and the current client record.
Find the proposal
After starting extraction, Kerdora opens the related Dora conversation. If you return later, open the client's Dora conversations and select the extraction thread.
The document detail page can show file metadata and extraction history, but the active Dora proposal card is the approval surface for the proposed event batch.
Understand what is being proposed
Dora can propose creating or updating supported records such as:
household people or entities;
assets and liabilities;
income;
insurance;
holdings;
Changes; and
Tasks.
The proposal rows describe the before-and-after information available to the reviewer. A clean label does not prove that the underlying source was read correctly.
Check new records
For a proposed new record, ask:
Does the same person, account, policy, income, or debt already exist?
Is the proposed owner correct?
Is the subtype legally and financially correct?
Does the amount match the source?
Does the frequency match the amount?
Are dates and tax treatment correct?
Is the record for the open client?
Reject a duplicate even when its displayed balance is newer. Update the existing record instead.
Check updates
For an update, compare the proposed value with both the source document and the existing client record. Determine whether the document is newer and whether the field should actually be replaced.
Examples:
A quarter-end statement can update an account balance but should not automatically change legal ownership.
A pay stub can update current wages but may not replace a documented future pension.
An insurance declaration can update limits and premium while preserving a separately confirmed beneficiary note.
Watch for proposals that replace a current value with an older statement-period value.
Approve or reject
The current proposal card provides Approve and Reject for the proposal shown.
Approve applies the proposed event batch to the client.
Reject resolves the proposal without applying those plan changes.
Review the whole batch before approving. The ordinary proposal card does not provide a universal “approve all except this one row” workflow. If one row is materially wrong, reject and request a corrected proposal or enter the correct record manually.
There is no separate Finish Extraction step after the proposal is resolved.
Correct a close-but-wrong proposal
Use one of these approaches:
Reject and tell Dora exactly what was wrong and what evidence to use.
Ask for a narrower proposal containing only the supported records.
Enter or update the source record manually in Profile.
Re-run extraction with clearer documents or instructions.
Do not approve a wrong value with the intention of remembering to fix it later. Approval can immediately affect Goals, Financials, Plan Cleanup, Insights, and Guides.
Verify approved information
After approval, open the relevant Profile and confirm:
names and dates in Household;
account owner, subtype, balance, savings, and holdings in Accounts;
income amount, frequency, type, and timing in Cash Flow;
policy owner, coverage, premium, and dates in Insurance; and
Changes and Tasks in their respective workspaces.
Then inspect downstream results. An approved account still needs Goal assignments. An approved holding can affect Investments. An approved income can affect Taxes, Insurance, Retirement, Financials, and Guide content.
If you approved the wrong information
Correct the saved source record in Profile or delete the unintended duplicate after checking its dependencies. If ownership or relationships are involved, reassign linked data carefully.
Rejecting a later duplicate proposal does not undo an earlier approval. Review the current client record to determine what actually saved.
Review checklist
Before Approve, confirm:
correct client;
correct source period;
no duplicate record;
correct owner or insured person;
correct subtype and tax treatment;
correct amount and frequency;
correct dates;
no loss of better existing data; and
understandable downstream impact.
If any item is uncertain, reject or pause and verify the source.