Skip ahead to the main page
Partner Huddle
Pages

Reasonable basis: 3 return checks before sign-off

Partner Huddle Editorial Team · Published · 12 min read

Before signing a return position, check its supporting authority, assess its strength and resolve any Treasury regulation conflict and disclosure question.

Key takeaways

  • Write down the authority and how it fits the client's facts.
  • Assess the position's strength and record the reasoning.
  • Resolve regulation conflicts and disclosure questions before signing.
  • Escalate an unsupported position rather than signing on instinct.

Why the sign-off step carries the risk

In a small firm that routes returns through two or three preparers and one or two reviewers, that moment is easy to rush. The return is due, the client is waiting, and the position looks like something the firm has done before.

The penalty side is why the moment matters. The Tax Adviser's overview of the preparer penalties in Sections 6694 and 6695 covers the Section 6694 penalty for a position giving rise to an understatement. The practical lesson is that the penalty is tied to the position on the return. The question a reviewer should be able to answer is whether the position was supportable when the return was prepared and signed, not whether it can be defended once an examiner asks about it.

The same article notes the firm-side exposure: "6694 if one of their employees, partners, members, shareholders, or other equity holders is assessed." ( The Tax Adviser). For a partner who signs returns, that is a reason to treat every sign-off as a decision with the partner's own name on it, not a formality at the end of the workflow. Read the full section before you rely on any summary, including this one.

This post walks through three checks a reviewer can run on a return position before sign-off. They are not a substitute for reading the rules, and they do not decide the question for you. What they give you is a fixed order of questions and a record of the answers.

The audience here is partners and operations leads at small firms that route client returns through preparer review and sign-off. If you are a preparer, the checks still apply to you, because the preparer is usually the first person to see a position and the first to decide whether it needs more support. Operations leads own the workflow that makes the checks happen, and partners own the signature. Each role has a part in the record, and the record is what this post is really about.

Check 1: name the authority behind the position, in writing

Start with the simplest question: what is the position resting on? A reasonable-basis position needs support, and the support has to be something a reviewer can point to. In practice, that means the preparer names the statute, regulation, court decision, or published IRS guidance the position depends on, and writes down where it can be found. If the answer is "the client has always done it this way" or "the software defaults to it," then the position has no authority behind it yet, and the sign-off should stop there.

The article points to the regulation that lists the authorities acceptable for testing a higher standard: "1.6662-4(d)(3)(iii) provides a list of authorities that are acceptable for determining whether there is substantial authority for a position." ( The Tax Adviser). Reasonable basis sets a lower bar than substantial authority, so the list is best read as a map of what strong support looks like, not as a checklist every position must clear. A reviewer who can match the position to an item on that kind of list has a much stronger file than one who cannot. A reviewer who cannot should not sign on hope.

Be specific about the match. An authority that is real but does not fit the client's facts is not support for the position. Ask the preparer to explain, in a sentence or two, how the authority applies to this client, this year, and this transaction. If the explanation depends on facts the file does not show, the file needs those facts before the reviewer signs. Use the client intake checklist to organize the handoff when records are missing.

Put the result in the file. A short memo or a line in the review notes is enough: the authority, where it was found, and why the preparer believes it fits. Small firms often skip this step because the preparer "knows" the authority and the reviewer trusts the preparer. That works until the preparer leaves, the client changes preparers, or someone outside the firm asks what the basis was. The record is for the next person who reviews the return, and for the firm if a question comes up later.

One more practical point. Authority that changes over time needs a date. A position supported by guidance from one year may need a second look the next year. Put the year of the authority in the note, so the next reviewer does not have to guess which version the preparer relied on.

Check 2: test the position against the reasonable-basis standard

The second check is about how strong the position is, measured against the standard definition the article gives: "Reasonable basis is generally defined as a position that has a greater than 20% possibility of success but does not have substantial authority." ( The Tax Adviser).

Turn that into a question for the preparer. Ask them, in plain terms, what they think the chance is that the position holds if the question is raised, and why. A precise percentage is not required, and nobody should pretend the number is measured. A reasoned estimate is what you want. If the answer is "probably fine," ask what the risk is if the reviewer disagrees, and whether the reasoning survives that challenge. A position that only survives if nobody pushes on it is not a strong position.

It also helps to separate two questions that often get merged. The first is whether the preparer believes the position is right. The second is whether the file would hold up if the position were challenged. The first is a judgment about the merits. The second is a judgment about the record. A preparer can be sure a position is right and still have a file that cannot show why. The reviewer should ask for both answers, and should not accept one in place of the other.

Do not treat 20% as a comfort level. It is the lower edge of the general definition, not a target. A position that sits just above that line, with thin authority and a client who wants the result, is the kind of position that usually needs a second look rather than a signature. The reviewer's job is to slow that decision down, not to find a way to approve it.

The percentage is a general description from one source. Before you rely on it in a file, check the current regulation and your firm's own written policy, and note in the file which version of the standard you applied. If your firm does not have a written policy on positions, this is a good time to start one. Even a half-page statement of what the firm will and will not sign is better than none.

Check 3: resolve regulation conflicts and disclosure

The third check is about regulations. A position can have authority behind it and still conflict with a Treasury regulation, and that is a separate question. The article names the form that applies in that case: "Form 8275-R, Regulation Disclosure Statement, provides adequate disclosure for positions that are contrary to Treasury regulations." ( The Tax Adviser).

For a reviewer, the question is direct. Does this position depart from a Treasury regulation? If the answer is yes, has the preparer identified the disclosure approach, and has the reviewer confirmed that the approach is on the return? The sign-off record should show that someone considered that form and made a decision about it, even if the decision is not to use it. A blank space on the checklist is not a decision.

Do not assume a position is fine because the software accepted it. A return that the software calculates, prints, or transmits has not necessarily been checked for support. Review the authority and any regulation conflict separately.

Timing matters here too. A regulation conflict is easiest to handle while the return is being prepared, not at the end when the deadline is close. Ask the preparer to flag any position that departs from a regulation as soon as it is identified, so the disclosure question gets its own step in the workflow instead of being squeezed in at sign-off.

It also helps to ask the preparer whether the position is the kind of thing the firm has taken before on other clients. That question is not a reason to approve the position. It is a way to find out whether the firm has a consistent approach, or whether one preparer is working from a different rule than the others. Inconsistency is often the first sign that a position has not been thought through.

If the disclosure question is unclear, stop and get a second opinion from someone who handles technical questions. Do not let the return go out with the question open. An unanswered question is not a reason to sign, and it is not a reason to rush either. Take the time the answer needs, check the deadlines and the client's situation before you decide, and keep the reasons in the file either way. If the timing has to change, tell the client why.

Make the review a real review

The IRS internal manual on preparer and promoter penalties carries a line worth keeping in front of every reviewer: "Appropriate business reviews should be conducted to ensure consistency with the penalty policy statement (Policy Statement 20-1) and philosophy." ( Internal Revenue Service).

That text is written for how the IRS administers these penalties internally. It is not a rule that applies to a small firm's sign-off process, and it does not tell a firm what to do. Still, it names the thing a firm reviewer is supposed to do: conduct a review that checks for consistency. A sign-off that asks only "does this look right" is not that kind of review. A sign-off that asks the three questions in this post, and records the answers, is much closer.

Here is a simple way to build that into a small firm's workflow. Separate the preparer from the reviewer on any position that involves judgment, so the person who wants the result is not the only one who checks it. Use a one-page sign-off sheet that lists the three checks, the answer to each, and the reviewer's initials. Keep a short note of any position the reviewer rejected and why, so the firm does not relitigate the same question on the next return. For the wider review, see preparer duties before signing a return.

Escalate when the answer is "I don't know." A partner should be the person who hears that answer, and the partner should decide whether to get technical help, change the position, or leave it off the return. Do not let the preparer decide alone that an open question is fine. That is the situation the review exists to prevent.

Finally, look at patterns. Once a quarter, pull a sample of the positions that went through review and see which ones needed the most work. If one preparer keeps bringing the same type of position, that is a training issue or a policy gap, and it is much cheaper to fix in the firm than to find out about it during an examination. Keep the review log brief. The point is to see patterns, not to create paperwork.

What to do when a check fails

A failed check does not always mean the position is wrong. It means the file does not yet support the position well enough to sign. There are usually four ways forward. The preparer can find better authority that fits the facts. The team can change the position to one that the authority does support. The firm can use the disclosure approach that fits the situation. Or the position can be left off the return.

Each of those options should be recorded in the file. If the client wants a position the firm will not sign, document the advice you gave, the reason for it, and the client's decision. That record protects the firm and the client, and it keeps the conversation clear for the next person who reviews the file. Be direct with the client. A clear explanation of why a position is not supported is part of the service, and it is far easier to give at sign-off than after the return has been filed.

Sometimes the honest answer is that a position is outside what the firm is comfortable signing, even if a reasonable case can be made for it. Firms are allowed to set that line. A written policy that says so, and that the whole team follows, is worth more than any single decision made under deadline pressure.

When you explain a decision to the client, describe it in terms of the file rather than the reviewer's comfort. "We could not find authority that fits your facts" is a clearer reason than "we are not comfortable with it," and it gives the client something to act on. If the client can provide facts that change the answer, the file can be reopened and the review run again. That is a better result than a signature that nobody can explain later.

Be careful about the limits of this post. It describes how a reviewer can organize the questions. It does not set the rules for any particular position, and it does not replace the statute, regulations, or guidance themselves. When a position is large, unusual, or tied to a significant amount of tax, bring in the firm's technical resources or outside counsel before you sign.

A reviewer checks an illustrative batch of 10 returns. In one file, the preparer has named an authority but has not explained how it fits the client's transaction. The reviewer returns the file for that explanation rather than assigning a percentage from instinct. If the explanation depends on missing client records, the team requests those records before reconsidering sign-off. The review note records the gap and the action taken; the batch count says nothing about the position's strength.

Put the checks to work today

Choose a return awaiting review today. Ask someone other than the preparer to review its judgment-based position, record the answers to the three checks and identify any unresolved question before sign-off.

Questions before sign-off

Is a preparer's confidence enough?

No; confidence does not replace an explanation supported by the file. Ask how the authority fits the client's transaction.

Does software acceptance settle the review?

No; software acceptance does not establish that the position is supported. Keep the technical review separate from processing the return.

What if the disclosure question is unresolved?

Pause sign-off and seek technical help. Record the question and the decision before the return goes out.

Sources