The SECURE 2.0 Act of 2022 (SECURE 2.0) introduced significant changes to age 50 catch-up contributions for participants in 401(k), 403(b), and governmental 457(b) plans. Among those changes, Section 603 of SECURE 2.0 mandates that participants age 50 or older who meet a new high-earner threshold must make catch-up contributions on a designated Roth basis (the “Roth Catch-up Rule”). A “high earner” is someone who has FICA wages in the prior year in excess of a specified dollar limit. The Internal Revenue Service (IRS) recently published that that dollar limit is $150,000 for 2025, and that amount is to be used in determining who is a high earner for 2026. The IRS and the Department of Treasury (the “Treasury”) issued final regulations on September 15, 2025, clarifying many aspects of the Roth Catch-up Rule. These rules are discussed in our October 2, 2025, Special Bulletin titled The Roth Catch-Up Regulations are Final: What You Need to Know! These final regulations are generally effective for contributions beginning January 1, 2027, though reasonable, good-faith compliance with new rules is required before that date. The Roth Catch-up Rule itself applies to taxable years beginning January 1, 2026.
As employers, payroll providers, recordkeepers and plan administrators prepare for the 2026 Roth Catch-up Rule implementation deadline, a key plan decision is whether to adopt the optional “deemed” Roth election provision. That provision allows employers to automatically treat catch up contributions of high earners as Roth contributions, once they reach the applicable annual elective deferral limit.
The following Frequently Asked Questions address the scope and application of the deemed Roth election provision, including benefits and drawbacks of adopting this plan design provision.
Frequently Asked Questions
1. What is the deemed Roth election provision?
The deemed Roth election provision is an optional plan feature. Once a participant is subject to the Roth Catch-up Rule (i.e., the participant reaches the annual elective deferral limit under Section 401(a)(30) of the Internal Revenue Code (“Code”)), the plan may automatically treat (deem) any additional contributions (i.e., catch-up contributions) as designated Roth contributions. This provision is intended to simplify compliance with the Roth Catch-up Rule by eliminating the need for participants to affirmatively elect Roth catch-up contributions; this is especially helpful for plans that use a spillover design (explained below) and, thus, do not require a separate elections for catch-up contributions).
Under a spillover structure, the participant elects one deferral percentage or dollar amount. Once the participant reaches the annual Code Section 401(a)(30) limit, any additional elective amounts automatically become catch-up contributions. For high earners subject to the deemed Roth election provision, spillover designs funnel excess amounts into Roth catch-up contributions without requiring an additional election. As a result, the contribution flow is predictable, especially where the plan applies the deemed Roth election based on combined pre-tax and Roth elective deferrals. Applying the deemed Roth election based on pre-tax elective deferrals only may also be advantageous to participants who desire to max-out their pre-tax contributions for the year. However, this may impose more rigorous monitoring of Roth regular deferrals made throughout the year to determine if any year-end corrections of Roth contributions that will be required.
Conversely, under a separate election structure, the participant affirmatively elects a separate amount for regular elective deferrals and a separate amount for catch-up contributions. Because the catch-up is a distinct election, most plans would implement the deemed Roth election provision as of the first payroll of the year for participants who are high earners. The final regulations do not mandate this timing, but the structure creates a natural operational default. A significant advantage of keeping regular deferrals and catch-up contribution elections separate is that it reduces the likelihood of spillover-related errors, because the plan does not need to redirect contributions from pre-tax to Roth mid-year, once a participant hits the applicable deferral threshold. However, deeming based on pre-tax elective deferrals only (as opposed to both pre-tax and Roth elective deferrals) may potentially result in mismatches for participants who rely heavily on pre-tax contributions throughout the year.
Again, adopting a deemed Roth election provision is not required to comply with the Roth Catch-up Rule. Employers may instead:
Deciding whether to adopt the deemed Roth election provision requires an assessment of whether the operational simplicity gained from the deemed Roth election process outweighs any potential communication, plan amendment and/or system complexities. The ultimate decision hinges on the balance between the plan, payroll, and recordkeeper capabilities, as well as participant’s goals.
2. What is required to implement the deemed Roth election provision under the final regulations?
To comply with the final regulations, a plan must satisfy both operational and documentary requirements. Specifically, a plan must:
3. How is an “effective opportunity” provided?
A participant must have a meaningful opportunity under the plan to make an alternative election. The final regulations require participants to receive timely notice of this alternative election, because the deemed Roth election provision may change the tax nature of their contributions without any affirmative action on the part of the participant. Relevant factors include:
Because the deemed Roth election provision automatically recharacterizes catch-up contributions as Roth, payroll capabilities and participant misunderstanding are key concerns. Employers considering adopting this feature should evaluate:
Employers who lack adequate payroll–recordkeeper coordination or face recurring communication timing issues might be better served adopting a different administrative process that applies to all participants (i.e., rely on participant-initiated Roth catch-up contribution elections for high earners).
4. When must the plan document be amended to add the deemed Roth election provision?
Under Notice 2024-2, plans generally must be amended by December 31, 2026, to reflect SECURE 2.0. However, collectively bargaining plans generally have until December 31, 2028, and governmental plans have until December 31, 2029. Because adopting the deemed Roth election provision may require alignment of payroll, recordkeeping, and participant communications, employers should evaluate whether they can realistically implement this feature before deciding whether to adopt it.
5. If adopted, when must deemed Roth elections discontinue under the final regulations?
Under the final regulations, a plan must discontinue applying the deemed Roth election within a “reasonable period” after it becomes known that:
The final regulations do not define the specific number of days that constitute a “reasonable period,” leaving the determination to a facts and circumstances analysis, including how quickly the employer can reasonably update payroll and plan election systems. However, the final regulations clarify that catch-up contributions already designated as Roth contributions before the end of the reasonable-period window are not required to be recharacterized solely because the participant is later determined not to be a high earner for that year. This avoids the need for corrective recharacterizations that would otherwise arise from mid-year status changes or delayed employer wage corrections.
Employers should consider any operational constraints associated with stopping deemed Roth elections mid-year. Careful coordination between payroll and recordkeeping systems is essential to ensure that:
6. What happens to prior catch-up contributions when the deemed Roth election discontinues?
When a participant’s deemed Roth catch-up election discontinues, the change affects only future catch-up contributions. As discussed above, prior catch-up contributions that were deemed as Roth remain Roth, and are not recharacterized. Additionally, these existing Roth amounts retain their original Roth contribution date for purposes of the 5-taxable-year period under Code Section 402A(d)(2)(B). As a result, even if the participant’s status later changes, earlier Roth catch-up contributions continue to count toward the participant’s Roth holding period.
7. Does a plan’s deferral structure—spillover versus separate election—impact a plan’s ability to adopt the deemed Roth election provision?
No. The final regulations confirm that either plan design—spillover and separate election—may implement the deemed Roth election provision. To facilitate administration, the final regulations permit plans to apply the deemed Roth election by reference to:
The final regulations also provide that if a catch-up contribution is later recharacterized at year-end as a regular elective contribution because the participant did not reach the annual Code Section 401(a)(30) limit, or other applicable limit, the contribution is permitted to remain Roth. No recharacterization is required.
8. How does the deemed Roth election interact with other plan administrative requirements?
Because the deemed Roth election provision changes how age-50 catch-up contributions are administered for certain participants, it does not operate in a vacuum. It must be coordinated with existing plan administrative features to ensure contributions are correctly designated and applied to the right limits.
Below are the most common plan administrative features that interact with deemed Roth election provision:
Employer Aggregation
403(b) and 457(b) Special Catch-up Limits
Annual Contribution Limits
The deemed Roth election provision is tied to the time catch-up contributions begin. However, as described above, several plan administrative features will determine when that moment is triggered. Because each of these administrative features triggers may be at different points in the plan year and may rely on different data sources and plan provisions, employers must ensure strong coordination between payroll and the recordkeepers. Plans with manual processes or delayed data feeds may find that the deemed Roth election requires additional controls that may not be an ideal feature for their environment.
9. What are the benefits and disadvantages of the deemed Roth election provision?
Benefits:
Disadvantages:
10. How can employers reduce errors and mitigate fiduciary risks if the deemed Roth election provision is adopted?
To reduce the likelihood of misclassifying contributions and to mitigate associated fiduciary exposure, employers should ensure that their plan’s administrative systems and vendors can consistently support the following functions:
The final regulations emphasize that adopting a deemed Roth election provision is optional. Plans may fully comply with the Roth Catch-up Rule without using a deemed election framework. Therefore, employers should adopt the deemed election only if they are confident that their payroll systems, vendors, and administrative processes can support these obligations. If any aspect of the required coordination is uncertain or cannot be executed reliably, employers should reevaluate whether the deemed Roth election design is operationally practical and fiduciarily prudent for the plan participants.
Conclusion
The deemed Roth catch-up election feature is an optional mechanism that can streamline compliance with the Roth Catch-up Rule for employers whose systems support automated contribution tracking and integrated participant communications. It establishes a default treatment that reduces reliance on participant elections, particularly in plans with simple or centralized payroll designs. However, for employers with decentralized payroll processes, complex workforce structures, or limited administrative bandwidth, adopting a deemed Roth feature may increase the potential for misclassifications, mid-year adjustments, or reporting errors.
Ultimately, plan sponsors and other plan fiduciaries must approach the issue of the Roth Catch-up Rule through a process of informed decision making based on administrative feasibility, risk tolerance analysis, and fiduciary capacity, recognizing that compliance with the Roth Catch-up Rule can be achieved without adopting a deemed Roth election provision, if such an approach better aligns with the plan’s operational realities.
For guidance on implementation of the new Roth Catch-up Rule tailored to your particular needs and circumstances, please contact the author of this article or your Trucker Huss attorney.
The Internal Revenue Code’s (the “Code’s”) required minimum distribution (RMD) rules are a cornerstone of retirement plan compliance, ensuring that participants begin withdrawing benefits and paying applicable taxes once they reach their required beginning date (RBD). Maintaining compliance with the RMD rules is a core element of tax-qualified plan operations, which in practice often presents challenges for ERISA plan administrators (Plan Administrators) and their professional service providers (TPAs)—particularly when participants fail to respond, cannot be located, or ignore repeated communications. The issue of unresponsive and uncooperative participants creates significant administrative burdens, fiduciary risks and potential compliance failures for tax-qualified retirement plans. This article explores these compliance challenges, outlines relevant agency guidance and provides practical strategies for managing risk when participants due to commence distributions from a plan are unresponsive or uncooperative, for whatever reasons (the latter group is also referred to herein as “recalcitrant participants”).
Overview of Required Minimum Distribution Rules
The RMD rules establish when and how retirement plan participants must begin taking distributions. Defined contribution plans (e.g., 401(k), profit sharing, 403(b) and 457(b) plans), and defined benefit plans are subject to RMD requirements, though the operational rules differ based on plan type. Compliance with these rules is critical for plan administrators, as failure to follow RMD requirements can result in plan qualification risks and significant tax penalties for impacted participants.
When Plan Participants Must Take RMDs. A participant must begin taking RMDs by their RBD, which is typically April 1 of the year following the calendar year in which the participant reaches the applicable RMD age (currently 73 for individuals born between 1951 and 1959, and 75 for those born in 1960 or later).
Plans may, however, provide that a participant who is not a 5% owner and who has not yet retired (i.e., is still working for the plan sponsor) can delay RMDs until April 1 of the year after retirement.
How RMDs Are Calculated. For defined contribution plans, RMDs must be paid annually by December 31 after the first RMD payment. The annual RMD amount is determined by dividing the participant’s prior year-end account balance by the applicable life expectancy factor from the Internal Revenue Service (IRS) Uniform Lifetime Table.
For defined benefit plans, RMDs are generally satisfied once periodic annuity payments begin, provided those payments meet the Code’s rules for lifetime or actuarially equivalent distributions. If a participant has not yet started receiving benefits by his or her RBD, the plan must begin minimum benefit payments by that date. The plan must ensure that the annuity starting date and payment form comply with the RMD distribution standards.
Unlike defined contribution plans, RMDs under defined benefit plans typically do not require separate annual calculations once payments begin, but Plan Administrators must still confirm that benefit commencement dates and actuarial assumptions align with Code requirements.
Challenges in Complying with the RMD Rules: Unresponsive Participants
Retirement plans often experience difficulties in complying with RMD rules due to frequent participant turnover, decentralized recordkeeping and generalized participant disengagement, all of which leads to participant unresponsiveness. Plans routinely lack current contact information for terminated participants, especially those who have been separated from the company for a long period of time. Returned mail, invalid email addresses and inactive online accounts complicate communication and hinder a plan administrator’s ability to pay RMDs.
For a recalcitrant participant, a Plan Administrator may have no doubt as to the participant’s whereabouts or how to contact them. In fact, the participant may be in contact with the Plan Administrator regarding matters other than distributions, for example, to initiate a change in investment allocation or to update a mailing address or telephone number. However, this participant fails to cooperate with the plan administrator when it comes to providing consent to an RMD (e.g., fails to return distribution election forms or provide needed documentation, such as proof of age or spousal consent). Without accurate data and participant cooperation, Plan Administrators and TPAs cannot issue timely RMD notices or properly calculate RMD amounts.
Failure to make timely RMDs can subject a plan to disqualification, and participants to excise tax on missed distributions. Untimely RMDs also lead to administrative complexities, especially if a participant experiences a life event after reaching their required beginning date—such as death, disability or divorce. Additionally, if a participant in a defined benefit plan later resurfaces, the plan must determine whether missed payments require actuarial increases or retroactive lump sums. These adjustments can be costly and administratively complex.
Strategies for Plan Administrators to Demonstrate Good-Faith Compliance with Government Agency “Missing” Participant Guidance
Even when participants are unresponsive or recalcitrant, Plan Administrators are expected to act in good faith, and document all reasonable efforts to comply with the RMD rules. The IRS has acknowledged that a plan will not be treated as failing to satisfy the RMD rules merely because a participant refuses or fails to accept a required distribution, provided the plan took timely and reasonable steps to comply with the rules.
To mitigate RMD compliance risks, Plan Administrators and their TPAs should establish administrative procedures for identifying, locating and engaging with participants about their RMDs. Best practices include:
» Early Identification and Regular Data Audits. The Plan Administrators and TPAs should, on a regular basis:
» Coordination with Service Providers. Plan Administrators should coordinate with recordkeepers, TPAs and payroll providers to maintain accurate data and implement a consistent RMD compliance process (including a process for identifying participants who are nearing their RBDs, calculating RMD amounts and timely sending out distribution forms).
» Follow IRS Guidance on Missing Participants. In its Memorandum TE/GE-04-1017-0033 (Oct. 19, 2017), the IRS provided clear direction to examiners on how to address situations where retirement plans have failed to make RMDs to missing participants. Specifically, IRS examiners are directed not to challenge a plan for failing to pay RMDs to missing participants if the plan demonstrates that it has taken appropriate, reasonable search steps. These steps include:
» Follow DOL Best Practices to Locate Missing Participants. The U.S. Department of Labor (DOL)’s Field Assistance Bulletin 2021-01 outlines best practices to help plan fiduciaries locate missing participants. These best practices are designed to help fiduciaries demonstrate prudence under the Employee Retirement Income Security Act of 1974 by taking reasonable steps to locate missing participants, pay out benefits and reduce the number of uncashed checks or unclaimed accounts. Best practices include:
For more information about DOL Best Practices, see “Missing Participants: The Search Continues” (Trucker Huss, February 22, 2022).
» Adopt Default Distribution Policies. For defined contribution plans, the plan document should outline clear default procedures where a participant’s whereabouts are known, but fails to respond to, or cooperate about, the timely distribution of his or her RMD. Options may include:
For defined benefit plans, the plan document should specify a default form of benefit that can be initiated without participant election, consistent with spousal protections.
» Enhance Participant Communication Strategies. Plan Administrators should ensure communications to participants about RMD requirements are clear and frequent. This includes:
» Maintain Comprehensive Documentation. Plan Administrators should maintain written evidence of:
The strategies and procedures described above do not amount to an exhaustive list of the actions that can be taken to address unresponsive and recalcitrant participants, but it does provide an excellent framework from which to design a prudent process. Ultimately, plan administrators must take timely and reasonable approaches aimed at facilitating compliance with the Code’s RMD rules, consistent with IRS and DOL guidance.
Conclusion
Unresponsive and uncooperative participants present persistent administrative challenges in retirement plan management. While plan administrators cannot compel participant cooperation, they can implement robust administrative procedures (i.e., accurate recordkeeping and diligent search efforts) to identify, locate and engage with participants about their RMDs and inform them of the penalties they may face if the Code’s requirements in this regard are not met. And plan administrators should thoroughly document all actions taken to establish prudence and good-faith compliance with the RMD rules and agency guidance. These actions are essential to maintaining a plan’s tax-qualified status and defending against related fiduciary breach claims.
If you have questions about compliance with the Code’s RMD when participants fail to be responsive, please contact us.
On November 13, 2025, the Internal Revenue Service issued Notice 2025-67, containing the cost-of-living adjustments related to retirement plan limitations under the Internal Revenue Code (the “Code”). These changes will take effect on January 1, 2026. Below are some of the key highlights.
Adjusted Limitations
The following is a quick reference guide to key limitations for 2024-2026.
On May 28, 2025, the U.S. Department of Labor Employee Benefits Security Administration (EBSA) released its first compliance assistance bulletin under the new presidential administration, Compliance Assistance Release No. 2025-01 (the “New Guidance”), announcing and memorializing EBSA’s revocation of its 2022 guidance cautioning against 401(k) plan investments in cryptocurrencies (Compliance Assistance Release No. 2022-01 (the “Prior Guidance”).
The Prior Guidance was issued by EBSA during the last presidential administration in response to a growing number of firms marketing cryptocurrencies as potential 401(k) plan investment options. Citing concerns that cryptocurrencies may have volatile returns, are subject to an evolving regulatory environment, present unique challenges for participants in making informed investment decisions, and have unique custodial, recordkeeping and valuation concerns, EBSA cautioned plan fiduciaries to exercise “extreme care” before considering adding a cryptocurrency to a 401(k) plan investment menu. Notably, in light of EBSA’s concerns, the Prior Guidance warned plan fiduciaries that EBSA expected to conduct an investigative program aimed at plans offering participant investments in cryptocurrencies and related products. More specifically, EBSA informed 401(k) plan investment fiduciaries permitting cryptocurrency investments that they “should expect to be questioned about how they can square their actions with their duties of prudence and loyalty in light of the [associated] risks . . .” This resulted in an immediate and significant chilling effect on pursuing cryptocurrency offerings in 401(k) Plans.
It comes as little surprise that the new presidential administration is a proponent of cryptocurrency, with Vice President Vance announcing the same day as the release of the New Guidance that “crypto finally has a champion and an ally in the White House… crypto and digital assets… are part of the mainstream economy, and are here to stay.” But what does the New Guidance mean for plan fiduciaries and the prudent analysis they must undertake in considering whether cryptocurrencies are an appropriate 401(k) plan investment options?
The New Guidance focuses on the reference to “extreme care” in the Prior Guidance as a rationale for its revocation, stating that “extreme care” is not a standard found in ERISA, and differs from ordinary fiduciary principles thereunder. Under ERISA, the fiduciary principles describing standards of care are the duties of loyalty and prudence. Specifically, ERISA’s duty of loyalty provides that fiduciaries must act solely in the interest of plan participants and beneficiaries with the exclusive purpose of providing benefits and defraying reasonable plan expenses, and the duty of prudence provides that fiduciaries are to carry out their duties with the care, skill, prudence, and diligence that a prudent person familiar with such matters would use (described by the courts as an expert standard).
The New Guidance emphasizes that the Prior Guidance deviated from EBSA’s “historic neutral approach to investment types and strategies” (e.g., imposing a uniform standard of care for different investments), and that revocation of the Prior Guidance “restores [EBSA’s] historical approach by neither endorsing, nor disapproving of, plan fiduciaries who conclude that the inclusion of cryptocurrency in a plan’s investment menu is appropriate.”
For a responsible 401(k) plan fiduciary, the revocation of the Prior Guidance does not give the green light to add cryptocurrency as an investment option; rather, it simply places cryptocurrency on a level playing field with any other potential investment option. In other words, it removes EBSA’s prior heightened scrutiny of cryptocurrency as a 401(k) plan investment option. This means a potential cryptocurrency investment should be reviewed and vetted by plan fiduciaries in the same manner as any other investment, by conducting a prudent process and adhering to the duty of loyalty. Such process may include analyzing and documenting whether the investment option:
In issuing the New Guidance, EBSA did not dismiss the concerns listed in the Prior Compliance release regarding returns, regulatory development, participant comprehension, and unique custodial, recordkeeping and valuation considerations, which will still present challenges when evaluating cryptocurrencies in the same way as other investment options. However, EBSA was clear that it no longer “disapproves” of cryptocurrency as an investment consideration, and a plan fiduciary’s decision should consider all relevant facts and circumstances and will “necessarily be context specific” (referencing Fifth Third Bancorp v. Dudenhoeffer, 573 U.S. 409, 425 (2014)). In other words, the appropriateness of cryptocurrency as an investment should focus on the specific needs of the plan, the unique characteristics of the population, and the reasonableness of the fiduciaries’ judgment.
In light of these changes, those in charge of plan administration must carefully review the applicable disclosure obligations and work closely with the plan actuary and legal counsel to ensure accurate and timely compliance. Plan fiduciaries that wish to consider cryptocurrency as a potential 401(k) plan investment option should work with their investment advisor to evaluate whether such an investment option is appropriate for their plan, taking into account the relevant facts and circumstances for their plan population, and analyzing the various considerations solely in the interest of plan participants in a prudent manner with a well-documented demonstration of their decision-making process. This should include a process to appropriately monitor the cryptocurrency investment, understand and evaluate the reasonableness of its fees, and assess whether sufficient education on the investment can be provided to the participant population.
If you have questions about the New Guidance, please contact us.
The Prior Guidance was issued by EBSA during the last.
Trucker Huss, APC is pleased to announce it has again been recognized in the areas of ERISA Litigation and Employee Benefits (ERISA Law) in the 2026 edition of Best Law Firms®. The firm’s rankings are...
Trucker Huss is proud to sponsor The American College of Employee Benefits Counsel (ACEBC) Annual Dinner being held on November 8, 2025, in Charleston, South Carolina.
Trucker Huss is pleased to announce Brad Huss has been appointed to the Board of the Alameda-Contra Costa Transit District Employees’ Retirement Plan (ACTERP). ACTERP provides retirement, disability, ...
Mary Powell will present at the Southwest Benefits Association (SWBA), being held in Dallas, Texas, on November 13, 2025. The panel “Healthcare Track: Pharmacy Trends, Compliance, and Preemption Issue...
Robert Gower will present on the panel “Everything You Need to Know About Roth 401(k) Catch-Up Contributions: SECURE Act 2.0 Compliance and IRS Final Rules” on November 13, 2025. The presentation...
The firm was proud to sponsor the SacLegal Unity Bar Dinner held on Tuesday, October 21. The theme for 2025 was “Hope Will Never Be Silent” and was supported by local affinity bar associations, includ...
Scott Galbreath, is quoted in a recent PLANSPONSOR article highlighting a critical year-end deadline for 457(b) plan sponsored by tax exempt organizations. The article underscores the urgency for...
Scott Galbreath's Benefit of Benefits Blog Post: Government Re-Opens With Inflation Adjustment to Roth Catch-Up ThresholdPresident Trump signed legislation to re-open the federal government and keep it open through January of next year.
Since its founding in 1980, Trucker Huss has built its reputation on providing accurate, responsive and personal service. The Firm has grown in part through referrals from our many satisfied clients, including other law firms with which we often partner on a strategic basis to solve client challenges.
The Trucker Huss Benefits Report is published monthly to provide our clients and friends with information on recent legal developments and other current issues in employee benefits. Back issues of the Benefits Report are posted on the Trucker Huss website (www.truckerhuss.com)
Editor: Nicholas J. White, nwhite@truckerhuss.com
In response to IRS rules of practice, we inform you that any federal tax information contained in this writing cannot be used for the purpose of avoiding tax-related penalties or promoting, marketing or recommending to another party any tax-related matters in this Benefits Report.
135 Main Street, 9th Floor
San Francisco, California 94105-1815
15760 Ventura Blvd, Suite 910
Los Angeles, California 91436-3019
329 NE Couch St., Suite 200
Portland, Oregon 97232-1332
Tel: (415) 788-3111
Fax: (415) 421-2017
Email: info@truckerhuss.com
Website: www.truckerhuss.com
Copyright © 2026 Trucker Huss. All rights reserved. This newsletter is published as an information source for our clients and colleagues. The articles are current as of the date of publication, are general in nature and are not the substitute for legal advice or opinion in a particular case.
135 Main Street, 9th Floor
San Francisco, CA 94105-1815
15760 Ventura Boulevard, Suite 910
Los Angeles, CA 91436-2964
329 NE Couch Street, Suite 200
Portland, OR 97232-1332