Retirement savings in Kerdora are entered on each eligible investment account. The account can use a flat amount, a percentage of linked income, or the available contribution maximum; supported workplace plans can also carry a separate employer-match formula.

These inputs feed Profile savings, Goal Mapping, retirement projections, Gap Analysis, and tax calculations in different ways. Keeping employee savings, employer match, and investment income in the correct fields prevents double counting.

Retirement savings need an investment account with the correct owner and subtype. Open the client, choose Profile → Accounts, and confirm the account's owner, subtype, balance, and whether Exclude from plan is off.

For percentage-based savings or employer match, add the owner's applicable employment income under Profile → Cash Flow → Income first. The account needs that linked income to convert a percentage into dollars.

Retirement contributions are edited in the investment-account drawer.

Kerdora saves the account contribution as an account-level savings input. Check Profile → Cash Flow → Savings to confirm the household savings view and return to the account to confirm the amount and frequency.

Flat Amount stores the stated contribution and frequency. Use it when a client saves a known dollar amount, such as $1,000 each month.

% of Income links the account to an income record and calculates the contribution from that income. Use the client's employee deferral percentage rather than a combined employee-and-employer percentage.

Max tells Kerdora to use the remaining supported limit after other accounts that share the same owner and limit group. Max is available only for account subtypes covered by Kerdora's contribution-limit model.

When a manually entered amount is above a modeled limit, Kerdora can show the entered amount and the lower amount used for projections. The warning is the signal to verify the account subtype, owner, age, and other contributions sharing the limit.

Employer match is available for supported workplace-plan subtypes, including 401(k), 403(b), 457(b), TSP, SIMPLE IRA, and Solo 401(k) variants.

For a plan that matches 100% of employee contributions up to 3% of salary, enter a 100% match and a 3% ceiling. Kerdora calculates the employer amount from the employee contribution, the linked income, and the match ceiling.

Employer match is separate from the employee contribution. Do not add the employer amount to Savings, and do not create an income record for it.

Employer match contributes to an assigned retirement account's future savings. In a Retirement Goal, Kerdora can show employee savings and employer match separately, while both help fund the projection and reduce the remaining savings gap.

Employer match does not reduce household spendable cash. Profile savings and household cash-flow calculations use the employee contribution; the employer contribution is added to the account for the goal projection instead of being treated as money paid from the household budget.

Kerdora applies current modeled limits by owner and contribution-limit group. Accounts that share an owner and limit group share the available employee limit. Age-based catch-up amounts are included where supported.

The modeled groups cover common workplace deferrals, 457(b) plans, SIMPLE IRAs, Traditional and Roth IRAs, HSAs, and health FSAs. Roth IRA eligibility can also depend on filing status and household income.

Kerdora's contribution-limit model is a planning control, not a plan-administration or tax-compliance determination. It does not model every plan document or exception. For example, the model does not handle the special 457(b) catch-up, higher SIMPLE limits available to some employers, or total annual-additions rules used for after-tax and mega-backdoor Roth contributions. Confirm unusual plan rules outside Kerdora and enter the best supported planning assumption.

An HSA account can use the same account-level savings controls. When Contributions made through payroll / W-2 Code W is selected, Kerdora treats the contribution as a payroll contribution for tax modeling. When it is not selected, Kerdora treats the amount as a direct HSA contribution.

The HSA limit uses the household information available to the model. Confirm the client's coverage tier and tax treatment outside Kerdora when the plan does not match the modeled family-coverage assumption.

Enter an employee 401(k) deferral as account savings under Profile → Accounts. Do not create a second income or savings record for the same contribution.

Tax results depend on the account subtype and the income or imported tax-return facts used by the selected tax scenario. A W-2 or tax return may already reflect a pre-tax payroll deferral in taxable wages. Before adding a manual tax adjustment, check the scenario's source values so the same deferral is not subtracted twice. Use the account contribution for planning, then use Taxes to review how the selected scenario treats it.

When retirement savings do not appear where expected, check the account in this order:

Changing a Profile contribution updates the source record. It does not replace Goal Mapping, which controls which Goal receives the account balance and savings.

An advisor can edit retirement-account savings, employer-match tiers, and Goal Mapping in the advisor workspace. A client can see account and delivered Guide information allowed by the portal, but the client does not receive the advisor's Goal Mapping or full retirement-planning controls.

After an advisor changes a contribution, review any client-visible Guide that contains retirement, savings, or cash-flow components before relying on it in a meeting.