Recent Answers to Arizona Law Questions

Randy M.

Answered Sep 23, 2025

If your single-member LLC’s S corporation election (Form 2553) is accepted and effective for the tax year, you don’t use Schedule C for that business. You file Form 1120-S for the entity, issue yourself a Schedule K-1 (Form 1120-S), and report the K-1 items on your Form 1040 (typically on Schedule E). If the election isn’t effective for the year in question (for example, it was filed late and not granted relief), you remain a disregarded entity for that year and would report on Schedule C instead. What this means for your filings this year File Form 1120-S by the 15th day of the third month after the end of your tax year (March 15 for a calendar-year S corp). Provide yourself a shareholder K-1. On your personal return, include K-1 income, deductions, and credits; don’t duplicate the same activity on Schedule C. Keep the IRS approval of your S election with your permanent records and verify the effective date before you prepare the return. Where Schedule C still applies (edge cases) If your 2553 wasn’t accepted or the effective date falls after the start of the year, the pre-election period is still disregarded-entity activity. In a mid-year effective-date situation, you’ll generally have two “periods”: a Schedule C period before the S election takes effect and an 1120-S period after. If your 2553 was late, consider Rev. Proc. 2013-30 relief so you can treat the election as timely and avoid an unintended Schedule C year. Payroll and “reasonable compensation” Once you’re taxed as an S corporation, you’re both owner and employee if you perform services. Pay yourself reasonable compensation through payroll and issue a W-2. That means registering for payroll, withholding and depositing employment taxes, filing Form 941 quarterly and Form 940 annually (where applicable), and following Publication 15 for rates and deposit rules. Non-wage distributions can be taken in addition to wages, but they come after paying reasonable compensation. Practical example Assume your 2553 was accepted effective January 1, 2025. For 2025 you run payroll to pay yourself reasonable wages, file 1120-S by March 17, 2026 (March 15, 2026 is a Sunday), and issue yourself a K-1. On your 2025 Form 1040 you include W-2 wages from your S corp and the Schedule E entry from your K-1. You do not file a Schedule C for that LLC. If the IRS letter shows an effective date of July 1, 2025, you’d generally report Jan–Jun activity on Schedule C and Jul–Dec on 1120-S unless you secure late-election relief aligning the election to January 1. State and local considerations Many states require separate S-corporation or franchise filings, estimated payments, or annual fees even if there’s no entity-level income tax. Check your state’s S-corp conformity, filing thresholds, and due dates. For payroll, also register with your state workforce and revenue agencies and follow state deposit and return schedules. Common pitfalls to avoid Don’t file 1120-S unless your S election is actually in effect; the IRS typically sends Notice CP261 confirming acceptance. Don’t skip payroll or set wages unreasonably low relative to your role. Don’t double-report the same activity on both Schedule C and your K-1. Finally, don’t overlook shareholder basis tracking; it affects loss deductibility and the taxability of distributions. Records and elections to keep on file Retain your filed Form 2553 and acceptance notice, EIN assignment letter, payroll registrations, quarterly and annual payroll returns, shareholder basis schedules, minutes/consents approving compensation, and any correspondence related to late-election relief. The Final Analysis Once your single-member LLC elects S corporation status, Form 1120-S becomes mandatory and Schedule C is no longer an option. Stay on top of payroll, compensation, and recordkeeping, and you’ll be in compliance. If you’re unsure about the details, a CPA experienced with small S corps can keep you on track and help you capture the full tax benefits.

Randy M.

Answered Sep 10, 2025

Yes, a licensing agreement can usually be terminated when the licensee fails to meet required quality standards, but whether you can do so depends on the language of your contract and how you handle the termination process. Courts enforce termination rights strictly, and you’ll need to show the breach is material rather than minor. Why Quality Failures Can Be a Material Breach Licensing agreements are built on protecting a brand. If the licensee’s products don’t meet agreed standards, that failure strikes at the heart of the deal. Poor quality undermines reputation, erodes consumer trust, and damages the goodwill the licensor has worked to build. Because of this, most agreements treat failure to meet quality standards as a material breach that allows the licensor to terminate if the breach isn’t corrected. Reviewing Your Agreement The first step is to examine the actual contract. Focus on provisions that describe: • Quality control obligations: These may reference specific product specifications, quality manuals, or compliance with industry standards. • Termination rights: Look for “for cause” termination language, which often lists quality failures as a trigger. • Notice and cure requirements: Many agreements require that you notify the licensee of the breach and give them a period (commonly 30 to 60 days) to correct it. • Dispute resolution procedures: Some contracts require mediation or arbitration before termination. You’ll need to comply with these provisions precisely. If you don’t, you risk a wrongful termination claim. Building the Record The burden will be on you to show the breach is real and significant. Documentation is key: • Collect product samples, photos, and inspection results that demonstrate the defects. • Keep a record of customer complaints, returns, or negative reviews linked to quality. • Maintain internal notes or reports from employees who’ve identified problems. • Save communications with the licensee where quality concerns were raised. If the licensee disputes termination, this evidence will support your position that the breach was material. Notice of Breach If the contract requires a cure period, you must send a written breach notice. That notice should: • Cite the contract provisions that have been violated. • Describe the quality issues in detail. • Attach or reference supporting evidence if possible. • Specify the time period for cure as outlined in the contract. • Make clear that failure to cure within that time will result in termination. The notice should be sent in the form specified in the contract, for example by certified mail or overnight courier. Termination if the Breach Isn’t Cured If the licensee fails to resolve the problems within the cure period, you may proceed with termination. The termination notice should: • State clearly that the agreement is being terminated under the relevant clause. • Identify the uncured quality failures as the reason. • Provide the effective termination date. • Remind the licensee of post-termination obligations, such as ceasing production and sales of your branded products. Protecting Your Interests After Termination If the licensee continues to sell after termination, you may need to seek an injunction to stop them. If you’ve lost sales or suffered reputational harm, you can consider pursuing damages. At the same time, you’ll want to secure a new licensee or manufacturing partner to maintain supply and protect your brand. In some cases, a carefully managed public statement can help maintain customer confidence. Limitations and Risks Not every defect will justify termination. Courts distinguish between minor issues and breaches that are serious enough to go to the root of the contract. Delay in taking action can also be seen as waiving the right to terminate for those particular breaches. Because wrongful termination can expose you to counterclaims, it’s best to have an attorney review your contract and prepare the necessary notices. Through Contracts Counsel, you can quickly connect with experienced contract attorneys who understand licensing disputes and can guide you through the process with confidence.

Randy M.

Answered Sep 6, 2025

Whether you need a Work For Hire Agreement really depends on the project and what both sides are trying to get out of it. You’re not automatically required to sign one, but saying yes or no to that clause can completely change who owns the work and what rights you’ll have moving forward. Just because a client calls something “work for hire” in a contract doesn’t mean it actually qualifies under the law, especially when it comes to freelance design work. Here’s the thing. Under U.S. copyright law, “work made for hire” is a specific exception to the general rule that the creator owns the work. For a freelance project to qualify, two conditions have to be met. First, both parties need to sign a written agreement that says the work is considered “made for hire.” Second, the type of work has to fall into one of nine defined categories under 17 U.S.C. § 101. These include things like contributions to collective works, audiovisual pieces, instructional texts, or compilations. The list is pretty narrow. Standard marketing materials, logos, brochures, or campaign graphics usually don’t make the cut. Courts take a strict approach here, so just checking a box in a contract doesn’t magically make it enforceable. If your project doesn’t meet both requirements, labeling it “work for hire” doesn’t hold legal weight. In that case, the default is that you, the designer, own the copyright unless there’s a separate written agreement transferring it to the client. That leads us to ownership. If there’s no valid Work For Hire clause and no assignment of rights, you retain full copyright. That gives you control over how the work is used beyond whatever license you’ve granted. So if you created a logo and the contract only licenses it for digital use, the client can’t later slap it on T-shirts or license it to a partner without getting your permission first. But if there is a valid Work For Hire clause or an explicit copyright assignment, then the client becomes the legal owner. That means they can use it, change it, resell it, or do whatever they want with it, without needing to pay you again or ask for further approval. You’d have no say over how the work is used, and unless the agreement gives you permission, you wouldn’t even be able to include it in your portfolio. If you want more flexibility, there are alternatives. You can structure the deal with a copyright assignment that still reserves certain rights for you. For example, you could keep the right to show the work in your portfolio or limit resale to direct competitors. Or you could stick with licensing. An exclusive license gives the client broad rights but you still own the work. A non-exclusive license is more limited and usually makes sense for templates or assets used with multiple clients. Portfolio rights, by the way, are often negotiable. Even in exclusive arrangements, you can add a clause that lets you show the work on your website, social profiles, or print materials. Just make sure it’s clearly spelled out. Some corporate clients won’t allow it at all unless it’s written into the agreement. From a practical standpoint, your decision should take into account how much you’re getting paid, how the work will be used, and whether you want to reuse or showcase it later. If you’re giving up all rights, price accordingly. Clients pushing for Work For Hire terms often just want clean, uncomplicated ownership, especially for branding or long-term use. But that doesn’t mean you can’t negotiate. You might agree to transfer ownership only after full payment is received. You might keep the right to use rejected drafts. You might even allow Work For Hire treatment for the final deliverables but retain some creative rights behind the scenes. Also, keep an eye out for boilerplate clauses. Some clients include Work For Hire language by default, not realizing their project doesn’t meet the legal standard. Just because it’s in the contract doesn’t make it enforceable. If the work doesn’t meet the criteria, the clause won’t hold unless there’s a separate valid assignment of rights. When in doubt, it’s smart to run the agreement by an attorney who understands copyright law and freelance creative work. Contracts Counsel connects you with attorneys who handle exactly this kind of issue.

Richard C.

Answered Sep 5, 2025

You can reach out to the employer and contest the termination, citing what you’ve mentioned above. If discrimination is a possibility of why you were terminated, you may want to consider an EEOC complaint (note time is an important factor here). However, a demand letter may be the best first step to try and reach a satisfactory resolution for all parties.

Randy M.

Answered Sep 4, 2025

When you're dealing with a technology transfer agreement, it's important to understand that you're not selling your software. You're licensing it. That might seem like a small difference, but it really isn't. Licensing means you're keeping ownership of your intellectual property while letting someone else use it under clearly defined terms. If you're based in Arizona, you've got a legal system that takes written contracts seriously and generally holds both parties to exactly what’s spelled out. So clarity matters—a lot. Be Specific About What's Being Licensed Don't just say you're licensing "software." Spell out what that includes. Are you talking about the source code? Object code? Documentation? APIs? Maybe there's configuration data, algorithms, or some embedded proprietary know-how. Lay it all out. Also, be clear on whether things like updates, bug fixes, or patches are part of the deal or if those require separate terms. Courts in Arizona won't guess what you meant. They’ll go by what’s in the document. Keep Your IP Rights Locked Down Make sure the agreement says you're not transferring ownership. You're only granting the rights specifically listed in the license. Anything not spelled out stays with you. Without that language, you could run into disputes later—especially if the licensee makes improvements. Want to avoid headaches? Clearly state that you own any enhancements unless you decide otherwise. Be Intentional About the License Structure Think through how you’re structuring the license. Is it exclusive, non-exclusive, or somewhere in between? An exclusive license can be powerful, but it limits your flexibility. If you're giving up other opportunities, it's reasonable to ask for higher compensation and make sure the licensee meets clear performance targets. On the flip side, a non-exclusive license gives you room to work with others. You can also narrow the license by geography, industry, or even specific use cases. And don’t forget to address sublicensing. If it’s allowed, include approval rights and make sure you’re compensated fairly if they sublicense to others. Choose a Payment Model That Reflects Value There’s no one-size-fits-all way to get paid. You might go with an upfront fee for past development work, ongoing royalties based on sales, or milestone payments tied to things like product launches or regulatory approval. Each has its pros and cons. Whatever you choose, protect yourself with audit rights. You want access to the licensee’s records if something seems off. That usually means giving them notice, checking things during business hours, and shifting the audit costs if the discrepancies are significant. Protect Your Work from Unintended Use If you’ve used open-source components, you need to disclose that—and understand how those licenses impact what you can legally offer. GPL code, for example, can bring in obligations that might not work with your business model. Copyright registration isn’t mandatory, but it gives you the ability to sue in federal court and can unlock statutory damages and legal fees. If you've developed novel algorithms, you might consider a patent—but only if the innovation meets the standards. It's not always worth the cost, so weigh that carefully. Make Sure the Licensee Does Something with Your Tech If you’re giving someone exclusive rights, set performance expectations. What does commercialization look like to you? It might mean releasing a product by a certain date, hitting minimum sales, or committing to a marketing budget. If those things don’t happen, you need a remedy—like converting the license to non-exclusive or ending the agreement altogether. The goal is to make sure your technology doesn’t sit unused. Clarify Support and Ongoing Involvement Are you expected to provide support? If so, spell out exactly what that means. Documentation, training, installation help, bug fixes, future updates—whatever it is, define it. Also decide whether that’s included in the license or billed separately. If you’re providing source code, put strict confidentiality and usage terms in place. In some cases, a source code escrow might be appropriate, with release conditions like your bankruptcy or failure to maintain the code. Limit Your Liability Arizona has adopted the Uniform Commercial Code, so if you don’t include specific disclaimers, you might be stuck with certain implied warranties. That includes things like fitness for a particular purpose. You’ll want to limit that while still affirming that you own the software and that it generally works as described. Also, set a cap on liability. Most developers limit it to the total fees paid under the agreement and exclude indirect or punitive damages. You don’t want to be held responsible for how someone else uses your tech. Mutual Indemnification Matters If someone accuses your software of infringing their intellectual property, you might agree to cover the licensee’s costs. But it needs to go both ways. They should indemnify you too—especially if they modify your code or use it in a regulated environment where compliance issues could come up. You don’t want to be liable for something outside your control. Don’t Skip Export Control Compliance Yes, export control rules apply even to downloadable software. If your product includes encryption or certain types of AI or analytics, it may fall under specific federal regulations. Many tools qualify for License Exception ENC, but that’s not automatic. Misclassification can lead to serious fines. If you're licensing internationally—or even just to a foreign-owned company based in the U.S.—you need to get this right before moving forward. Understand How Arizona Law Will Handle Your Agreement Arizona courts usually enforce what’s written. If it’s not in the contract, don’t expect the court to fill in the gaps. That makes detailed drafting essential. Arizona also supports reasonable non-competes and confidentiality terms, which isn’t true in every state. Just make sure any restrictions are tied to legitimate business interests and kept within reasonable limits for time and geography. Spell Out What Happens at the End Termination clauses are your safety net. Cover scenarios like breach, bankruptcy, missed milestones, or even changes in company control. Include cure periods where appropriate. Be specific about what happens when the agreement ends—does the licensee have to stop using the software immediately? Can they finish selling what’s already been produced? Make that clear. Also, specify which obligations survive termination. Usually, confidentiality and IP rights continue, even after the main agreement ends. Plan Ahead for Disputes Choose Arizona law to govern the agreement. If your licensee is in another state or country, decide where and how disputes will be handled. Arbitration can be quicker and cheaper, but it might limit your access to things like injunctive relief. Consider requiring mediation first to give both sides a shot at resolving issues early. And don’t forget a prevailing party clause—Arizona courts do enforce them, and it could help you recover attorneys’ fees if you end up in a legal fight. The Final Analysis Technology licensing isn't just about protecting your IP. It's about setting clear, enforceable expectations from the start. Arizona law gives you the tools to do that, but it only works if your agreement is well-drafted and forward looking. Define what you're licensing, retain ownership, protect your downside, and make sure the deal drives results, not just risk. If you're a software developer navigating a tech transfer deal or reviewing an agreement someone else drafted, don’t go it alone. Having the right legal language in place from day one can prevent years of headaches down the road.

Connie M.

Answered Apr 11, 2025

You usually need to get the permission of the owner of the photograph which is usually the photographer. Check the metadata or do a reverse image search to help you find the owner.