Running an S corporation can lower self-employment taxes by splitting pay into W-2 salary and distributions, but the IRS expects that salary to be reasonable for the work performed. This guide gives a practical, planning-first framework for a Software Engineer in Arizona, plus the official sources your CPA will want to see.
Last reviewed: January 21, 2026.
- The IRS expects shareholder-employees to take reasonable wages before distributions.
- Reasonable compensation is fact-specific: role, hours, revenue drivers, and comparable market pay matter.
If your role or income shifted this year, assume the salary range should move too.
Software engineers contribute via product delivery, architecture, and technical leadership. Compensation drivers include scope of responsibility, team leadership, and equity-linked roles.
Arizona software engineers often serve remote clients or distributed teams, which can shift time toward architecture decisions, support, and client communication. If you own delivery and also lead technical strategy, the wage narrative should reflect that seniority. Use state wage data as a baseline, then layer in how much responsibility you carry for uptime, roadmap delivery, and technical leadership.
- BLS OEWS national percentiles for Software Developers (May 2023):
Reasonable compensation is the wage you would pay someone else to do your job under similar conditions. The IRS looks at duties, experience, time spent, and what comparable roles earn, not a fixed percentage of profit. Use multiple data points to defend a range, not a single number.
-
Define the role. Capture what you actually do: client load, revenue responsibility, admin oversight, and business development.
-
Benchmark a range. Use BLS occupational wage data plus any industry surveys or local comps your CPA trusts. Focus on state-level data where possible.
-
Model the split. Pay the reasonable wage as W-2 salary; treat the remaining profit as distributions only after the wage is defensible.
-
Document the rationale. Keep your notes, sources, and calculations with the tax file so your CPA can defend the position.
Example: An Arizona software engineer who owns architecture and supports production systems should justify a wage that reflects leadership, not just implementation hours.
- Did income or services change materially this year?
- Do you have a defensible compensation range for a Software Engineer in Arizona?
- Is the documentation clear enough to share with your CPA?
- Have you documented how time is split across delivery, management, and growth?
- What compensation range is defensible for my role and hours?
- How does the Arizona PTE election change the split decision this year?
- What documentation would you want if the IRS asked for support?
Do I need a separate state S election in Arizona?
Many states require additional registration or elections beyond the federal S election. Confirm Arizona requirements with your CPA and the Arizona Department of Revenue.
Should I use national or Arizona wage data?
State or local data is typically more defensible when available. Use BLS data and any reputable industry surveys your CPA prefers.
What documents should I keep?
Time allocation notes, comparable wage sources, and written rationale for the salary range are the most common requests.
Use the S-corp Reasonable Compensation Guide to draft your range, then bring it to your CPA for validation.
This guide is for planning and coordination only. It does not provide tax or legal advice. Confirm details with a qualified professional.