US and Canada retirement planning in Salesforce
Support Social Security, Roth, CPP, and OAS conversations on the household Financial Plan record — so advisors serving US, Canadian, and cross-border books plan in one Salesforce workflow, not three disconnected tools.
US Social Security and Roth on US plans; CPP/OAS on Canada plans — same Financial Plan record in Lightning.
US benefit income sources and Canadian retirement cash flow — jurisdiction-aware planning on governed Salesforce records.
Sample household data for illustration only — not a client record.
Two countries, three tools
US tool and Canada tool
Teams bounce between products that each only know one benefit system — while the household relationship already lives in Salesforce.
Household split across files
A couple with US and Canadian accounts ends up as two planning files and a spreadsheet to reconcile before every review.
Benefit assumptions drift from CRM
Social Security, CPP, or OAS timing lives in portal exports — not on the governed Financial Plan record associates reopen.
Cross-border data in extra vendors
Each extra planning portal is another database for sensitive household data your compliance team must review.
Advisor questions this helps answer
US and Canada benefit conversations on the Financial Plan record — not separate worksheets per country.
When should a US client claim Social Security?
In Salesforce Social Security explorer strategy cards compare claiming ages and projected benefit cash flow on US tax-context plans.
Should a US household evaluate Roth conversion timing?
In Salesforce Roth explorer and tax-aware projections sit on the same US Financial Plan record advisors share with the client's CPA.
When should a Canadian client start CPP?
In Salesforce CPP/OAS explorer and income charts model benefit timing against household spending on Canada tax-context plans.
How does OAS timing affect projected retirement income?
In Salesforce CPP/OAS simulation and income-by-year views show how deferral or early start changes household cash flow.
Which households have retirement income gaps?
In Salesforce Plan health, funding gaps, and lifetime cash flow on the Financial Plan surface shortfalls before the client meeting.
Which clients need a tax-aware review before retirement?
In Salesforce Estimated taxes, tax rate, and IRMAA on US plans — or Canada federal and provincial views — flag review topics on the plan record.
How do advisors keep benefit assumptions on the household record?
In Salesforce Tax jurisdiction, benefit inputs, projection runs, and explorer outputs stay on governed Salesforce records — not exported portal files.
US and Canada benefit explorers
Jurisdiction-aware explorers on the Financial Plan — US tools for US tax context, Canada tools for Canadian tax context.
US: Social Security explorer
Claiming-strategy analysis for US tax-context plans — compare ages, projected benefits, and household cash flow in Lightning.
US: Roth conversion explorer
Model conversion timing beside tax-aware projections on US households — not a one-off spreadsheet.
Canada: CPP/OAS explorer
Benefit timing scenarios for Canadian tax-context plans — dedicated explorer instead of a US-only worksheet.
Shared household Financial Plan
Accounts, income, projections, and explorer results stay on one Salesforce record regardless of jurisdiction.
Sample household data for illustration only — not a client record.
Sample household data for illustration only — not a client record.
Sample household data for illustration only — not a client record.
Sample household data for illustration only — not a client record.
US household: Social Security at 67 vs 70
Sample household data for illustration only — not a client record.
On a US tax-context sample household, the advisor opens Social Security explorer to compare claiming at 67 versus 70. Values below are illustrative — not a client record.
Sample takeaway: Claiming at 70 raises projected monthly Social Security income — giving the advisor a concrete conversation topic before the client commits to a retirement spending path.
Note: Planning estimates only — not Social Security advice or filing instructions.
Canadian household: CPP and OAS timing
Sample household data for illustration only — not a client record.
On a Canada tax-context sample household, the advisor reviews CPP/OAS timing against projected retirement spending. Values below are illustrative — not a client record.
Sample takeaway: Deferring CPP improves projected benefit income — while OAS timing and household spending stay visible on the same governed Salesforce record.
Note: Planning estimates only — not Service Canada filing advice or cross-border treaty analysis.
Mixed household: US Social Security and Canada CPP/OAS
Sample household data for illustration only — not a client record.
On a cross-border sample household, one spouse has US Social Security and the other has CPP/OAS — with a shared retirement spending goal on one Financial Plan record. Values below are illustrative — not a client record.
Sample takeaway: Shared spending goals, benefit assumptions, and review notes stay on one governed Salesforce record — treaty and dual-filer tax questions still belong with qualified tax professionals.
Note: Retirement workflow support — not a full cross-border treaty, expat-tax, or dual-filer tax engine.
Why this data belongs in Salesforce
Benefit assumptions and projection results stay on governed records — so US, Canada, and cross-border books share one advisor workflow.
Filter households by tax jurisdiction, retirement window, benefit timing, or projected income gap from Salesforce list views and reports.
Create advisor tasks when CPP/OAS, Social Security, Roth, or tax-aware planning reviews surface on the plan record.
Identify households with outdated benefit inputs or benefit-timing opportunities before the next client review.
Planning metrics on Financial Plan records feed Salesforce reporting — not portal-only exports.
Tax jurisdiction, benefit inputs, projection results, and explorer outputs remain on the Financial Plan for the next associate or review.
Sample household data for illustration only — not a client record.
Limitations and compliance-safe positioning
Retirement planning workflow support — not a full treaty, expat-tax, or dual-filer tax engine.
- Supports US and Canada retirement planning conversations — not tax filing, treaty analysis, or expat-tax preparation.
- US explorers (Social Security, Roth) appear on US tax-context plans; CPP/OAS tools appear on Canada tax-context plans.
- Projections are estimates based on assumptions — not benefit filing instructions, tax advice, or custodian recommendations.
- Complex cross-border, dual-filer, or treaty situations require the client's qualified tax professional.
- Household planning data stays in Salesforce under your existing permissions, sharing, and audit controls.
Common questions
Is this a full cross-border tax engine?
No. Financial Planner supports US and Canada retirement planning workflows and reference tax data. Complex treaty, expat-tax, or dual-filer situations still need qualified tax advice.
Does it support US Social Security planning?
Yes. US tax-context plans include a Social Security explorer for claiming-strategy conversations alongside retirement cash flow and tax-aware projections.
Does it support CPP and OAS planning?
Yes. Canadian tax-context plans include CPP/OAS explorer tools and Canada estimated tax views on the same Financial Plan record.
Can one household include US and Canadian retirement considerations?
Financial Planner supports US and Canada planning workflows on governed Salesforce records. Mixed-household benefit modeling depends on plan jurisdiction and household setup — complex cross-border cases need qualified tax advice.
Does this replace qualified tax advice?
No. Outputs are planning estimates for advisor workflow — not tax filing, treaty analysis, or custodian instructions. Material cross-border decisions belong with the client's tax professional.
Can advisors segment households by country or benefit-planning need?
Yes. Tax jurisdiction, retirement window, benefit timing, and plan health on Salesforce records support list views, reports, and segmentation your admin defines.
Does client data leave Salesforce?
No. Household planning records, benefit assumptions, and explorer outputs stay in your org. Financial Planner is a managed package — not an external planning portal.
Can results be used in Salesforce reports and review workflows?
Yes. Financial Plan records and planning metrics can feed reports, dashboards, tasks, and review workflows — so benefit-timing conversations stay attached to the household record.
See Financial Planner in your Salesforce workflow
Request early access to evaluate household records, projections, insights, and explorers before the public AppExchange listing goes live.
- Public AppExchange listing coming soon — request early access to pilot in your org.
- Passed Salesforce AppExchange security review.
- Stratus Cloud Solutions has built Salesforce-native apps since 2009.
- Documentation is available for evaluator walkthroughs. Open docs