Kerdora separates source data, proposed data, planning assumptions, and client-facing output. Understanding that separation helps you correct information in the right place and avoid duplicate records.
Profile is the source-data workspace
Open a client and choose Profile. Its four views are:
Accounts — assets, liabilities, holdings, ownership, balances, tax treatment, savings, payments, beneficiaries, and related account details;
Cash Flow — income, spending, savings, debt payments, and Giving when enabled;
Insurance — the policies the household currently owns; and
Household — adults, children, businesses, trusts, household settings, and portal access.
When a client fact is wrong, correct it in Profile. Examples include a balance, owner, birthday, income amount, payment frequency, policy benefit, or household filing status.
Choose the right intake method
Kerdora supports several ways to build the same client file. The advisor can mix them instead of forcing every household through one intake path.
Use manual entry when the advisor already knows the fact or needs precise control.
Use Upload & Extract when source documents can support a reviewed Dora proposal.
Use account aggregation when a client can connect an institution for balances, holdings, and transactions.
Use the onboarding form when the client should supply household information through a guided portal workflow.
Each method should end in the same check: open Profile, confirm ownership, amount, frequency, dates, subtype, and duplicates, then review the affected planning result. Intake method does not change which saved Profile record is the source of truth.
Documents and extraction are intake, not final truth
Documents stores uploaded files. Extraction can turn those files and written context into proposed household, account, liability, income, insurance, holding, Change, or Task records.
A proposal is not the same as an applied Profile record. Before applying extracted information:
compare it with the source;
confirm the record type and owner;
check the amount and frequency;
resolve possible duplicates; and
apply only what you want saved.
Keep the document when it is useful evidence even if you reject an extracted proposal.
Linked accounts are another data source
Account aggregation can provide balances, holdings, and transactions from a connected institution. Linked balances and holdings feed the account experience. Transactions feed the Spending experience.
Do not create a manual duplicate when the linked record already represents the same account. If linked data is stale, refresh or troubleshoot the connection. Manual records remain appropriate for assets and liabilities that are not available through aggregation.
Planning reads the reviewed data
Planning modules combine Profile facts with module-specific assumptions.
Goals uses household timing, accounts, assignments, income, spending, taxes, savings, and goal assumptions.
Spending uses transaction-level data, categories, tags, groups, and rules.
Investments uses investment accounts and holdings for allocation and portfolio analysis.
Insurance compares existing Profile policies with modeled needs.
Taxes uses household, income, and scenario-specific tax assumptions.
Estate connects estate information with the household and owned assets.
Business uses business and ownership information for business-owner planning.
Changes records recommendations derived from advisor review.
Some planning fields are derived from Profile. Others are manual scenario assumptions. Use an override only when the plan should intentionally differ from the source fact.
Assignments are not duplicates
Goal Mapping does not create a second account balance. It allocates portions of an existing account's balance and savings to Goals.
An account can appear in Profile but contribute nothing to an individual Goal until it is assigned. Conversely, the household savings comparison can include savings across available bank and investment accounts even when an amount is not assigned to a Goal. Use the individual Goal table to explain assigned amounts and Gap Analysis to explain household capacity.
Financials, Visualize, and Guides are output surfaces
Financials creates client-ready summaries from the reviewed plan data. Visualize provides advisor presentation views. Guides assembles the content you deliberately deliver to the client.
These surfaces do not become independent sources of truth. If a displayed number is wrong, trace it back to Profile, the relevant planning assumption, account assignments, or linked-data freshness.
Clients see delivered Guide content under Overview and use the portal's Profile, Documents, Tasks, Spending, and Investments areas. They do not receive the advisor's Office, Financials, full Planning workspace, Visualize, Guide editor, or Dora conversations.
Changes save into the client record
Kerdora generally saves edits as you make them or when you confirm a create/update action. Do not assume that closing a modal cancels a change that was already submitted. After a material edit, confirm the displayed value and check the downstream result you intended to change.
Dora proposals and extracted proposals use explicit review or approval behavior where shown. Read the action label before assuming a suggestion has already changed the plan.
Diagnose a number that looks wrong
Use this order:
Identify the exact displayed value and its date or frequency.
Find the Profile record that supplies the fact.
Check ownership, amount frequency, start and end timing, subtype, and tax treatment.
Check whether the value is linked, extracted, manual, derived, or overridden.
Review Goal Mapping or other module-specific scope.
Refresh linked data when institution information is stale.
Reopen the planning or output surface and confirm the result.
Avoid fixing a source-data error with a presentation label or a chain of overrides. One corrected source record should flow through the rest of the client file.
Can a new upload overwrite existing client data?
Uploading a document by itself does not overwrite Profile. Upload & Extract creates a proposed event batch for advisor review. Approval can create or update the records shown in that proposal, so compare every proposed value with the existing client file before approving it.
Account aggregation can refresh linked facts from an institution. Manual edits remain separate from the connection rules for that linked record. When a value changes unexpectedly, first identify whether it is manual, extracted, linked, derived, or overridden before correcting it.