Kerdora combines manual entry, client onboarding, reviewed document extraction, linked financial accounts, and purpose-built imports in the same household file. The key distinction is whether information has only been collected, has been saved to the plan, or continues to refresh from a connection.

For household creation and choosing an initial path, see Adding Your First Client. Combine intake methods as needed: Manually Entering and Correcting Client Data covers direct edits, Using Upload & Extract for Client Data covers document proposals, and Using the Guided Onboarding Form covers client participation.

Advisors usually correct client facts in Profile. Accounts contains assets and debts; Cash flow contains income, spending, savings, debt payments, and Giving when enabled; Insurance records existing policies; and Household contains people, entities, and household settings.

To investigate a wrong fact:

A statement and a linked feed can describe the same account. Keep 1 account record: match a new connection to the existing record and reject a Dora proposal that adds a duplicate. If both paths create included records, the account’s balance counts twice.

A linked financial account can receive recurring institution data. A file import uses the file supplied for that run and does not keep reading the source system afterward.

For a RightCapital move, see Adding Your First Client, “What do I need to import from RightCapital?”

In Documents → Upload, Upload only stores files without changing Profile records. Upload & extract stores files and starts a Dora conversation that can propose additions or updates; text without files uses Extract changes. Proposed planning changes need approval before they apply.

The Accounts import-documents modal labels its action Upload & Extract, while Plan Setup uses Extract with Dora. Use the label for the surface you opened.

Read every proposed change against the existing client file and the source. Ordinary Dora proposals are approved or rejected as a batch.

If a proposal needs correction, reject it and explain the correction before approving a replacement. Rejecting the proposal leaves the uploaded documents available and does not undo an earlier approval.

The Altruist importer has a different confirmation and replacement process: its final import replaces holdings on the selected investment accounts. Do not assume all upload screens share the same behavior. See Using Upload & Extract for Client Data and Importing Holdings from Altruist for their respective review steps, limits, and recovery instructions.

An account connection reports institution and product status; it does not guarantee that every field arrived together or that the account is complete. Balances, holdings, and transactions can have different update states. Investment account values may depend on holdings and available ticker prices, rather than a single institution balance.

Advisors inspect Profile → Accounts → Connections. Use Review accounts, or a counted label such as Review 2 accounts, to match accounts. Have the client use Reconnect when bank authentication is required. See Linking Accounts and Understanding Synced Data for matching and supported data, and Troubleshooting Linked Accounts for failures and mismatched values.

Disconnecting a connection retains its planning accounts and previously imported data. Relinking can therefore create duplicates if retained accounts are added again as new.

Inspect the existing records and available matches before creating another account. Do not rely on a generic “refresh” instruction: use the actions the current connection displays.

Entering an account records what the household owns or owes. Goal mapping separately assigns account balances and savings to Goals; an assignment refers to the existing account rather than creating another account. A balance appearing in Profile is not proof that it funds the particular Goal you are reviewing.

Planning calculations also use assumptions and timing beyond current balances. For example, income has start and end timing, and spending can be a manual estimate or a calculated amount. Review those inputs when a result differs from expectations instead of changing a correct source balance to force a result.

Financials and client-facing Guide components can display information from the household's records and planning results. A display label does not correct an underlying account.

After a material edit, check the saved source, the relevant planning result, and the output you intend to share. Use Plan Setup to continue the initial review and Plan Cleanup to investigate flagged data issues.

Yes. Client forms can save permitted facts directly to the shared household record. Those edits are different from an advisor Dora proposal awaiting approval.

For example, client account-edit dialogs submit changes with Save changes, and the guided form saves confirmed information as the client proceeds. Review material client changes before relying on the plan.

Manual-investment holdings are different: Add holdings or Edit holdings on an account's page or inside Edit account opens an editor that saves immediately. Adding the first holding replaces an entered balance with a balance calculated from holdings; clients can't switch it back.

Linked-account holdings stay read-only. Manually Entering and Correcting Client Data explains the procedure.

In guided onboarding with AI extraction, the client can also review permitted intake proposals using Use these details or Leave out. This limited intake review does not give the client the advisor's Dora workspace. A client can upload documents through the regular Documents page without triggering that guided extraction flow.

See Using the Guided Onboarding Form for how drafts, saved details, extraction, and returning to the form work. For an existing household's invitation and portal-access controls, use Inviting a Client to the Portal rather than creating a second household.

No. These features handle specific sources or destinations; they do not establish a general two-way connection with another application.

The tax-return workflow extracts a supplied PDF and can create a tax scenario after the required review and person matching. Review the year, forms, and scenario values; importing a return does not file it or fetch a later filing.

Dora's transaction-import workflow can propose transactions from a statement for approval and processing. Review the account and source period to avoid overlapping imported and linked activity.

The advisor's Calendar link setting supplies a booking destination. The client's Schedule a meeting action opens that link; it does not synchronize Google or Outlook calendar events or read availability inside Kerdora.

There is no general CRM, RightCapital, or cloud-document synchronization flow in the current product. For a connection your firm needs, tell Support the provider, data needed, and whether you need a one-time import or continuing updates. An available upload route alone is not evidence of a live integration.