IRS Offer in Compromise: Financial Disclosure, Payment Choices, and Rejection Appeals

Review the primary official source.

Confirm eligibility and the offer basis

An offer in compromise asks the IRS to settle a tax liability for less than the full balance under an authorized basis. It is not merely a proposed discount. Begin with account transcripts, assessed periods, collection-expiration information, filing compliance, estimated-tax or withholding compliance, and any open bankruptcy. Identify whether the theory is doubt as to collectibility, doubt as to liability, or effective tax administration.

Start with the operative source and the decision it controls. Record the version, effective date, service method, and relationship to other rules or orders. Agency summaries are useful orientation, but the statute, regulation, order, or current filed notice controls the particular step.

Read the governing IRS Form 656 guidance; IRS offer-in-compromise guidance with the complete record before applying this discussion to a current matter.

Build a complete financial statement

Most collectibility submissions require Form 656 and the appropriate Form 433-A(OIC) or 433-B(OIC), with supporting records. Document cash, accounts, investments, vehicles, real estate, business interests, receivables, retirement assets, income, household expenses, transfers, and special circumstances. Reconcile the forms to bank statements, tax returns, payroll, bookkeeping, and public records. Explain departures from IRS standards with evidence.

Build a chronology from contemporaneous records before drawing conclusions. Mark dates as confirmed, reported, disputed, or unknown. Preserve original envelopes, portal receipts, electronic metadata, and complete documents rather than screenshots or isolated pages.

Urgency should sharpen verification, not replace it. A short, documented chronology is more useful than a confident account that merges confirmed facts with assumptions.

Select and fund the payment option

The lump-sum and periodic-payment options carry different payment requirements. The IRS page also identifies a low-income certification that can affect the application fee and payments during review. Confirm the current booklet before filing. Track the application fee, initial payment, continuing periodic payments, refunds, levy posture, and every request for additional information. Missing a response or current tax obligation can cause return or rejection.

Map each record to the proposition it supports. A document proving notice may not prove timeliness, identity, causation, eligibility, or remedy. An issue-based index exposes gaps and prevents one favorable record from being asked to establish the entire case.

Place this issue beside our related guidance while keeping the distinct procedure and remedy analyzed here separate.

Control requests, rejection, and appeal rights

If the IRS rejects the offer, its public guidance states that an appeal generally must be requested within thirty days using Form 13711 or an equivalent written protest. Distinguish a returned offer from a rejected offer because review rights may differ. Build the appeal around disputed asset values, income, expenses, dissipated assets, special circumstances, and calculation errors, supported by a clear source index rather than a conclusory hardship statement.

Finish with an authority-and-deadline review. Identify who can act, what that decision-maker can order, the earliest event that could narrow options, and the record still missing. Assign each follow-up and verify receipt instead of assuming that transmission completed the step.

For a focused review, assemble:

• account transcripts and compliance verification
• signed Form 656 and financial statement
• asset, income, expense, and transfer support
• fee and offer-payment proof
• information requests, determination, and appeal filing

Then compare the record with our related analysis and identify the next decision, deadline, and missing document.

Integrating the record

Organize the working file in three layers. First, keep a source set containing the controlling statute, regulation, agency instruction, or filed order in the version actually reviewed. Second, maintain a dated factual chronology with links to the documents supporting each event. Third, use an issue chart that states what must be shown, which evidence supports it, which evidence cuts the other way, and what remains missing. This structure prevents an old notice, incomplete download, or later recollection from silently replacing the operative source or contemporaneous record.

Communications belong in the same system. Preserve letters, emails, portal messages, call notes, tracking records, and acknowledgments in chronological order. Record who sent each item, the destination, the method, and confirmed receipt. Where a deadline depends on service or receipt, keep the envelope or electronic metadata. Where a decision depends on discretion, preserve both favorable and unfavorable facts so counsel can evaluate the complete presentation rather than a curated fragment.

Verification before action

A useful review ends by confirming that every cited source remains current, every linked decision is the complete filed document, and the known facts actually fit the rule. Court orders may bind only the parties and posture before that court. Agency guidance may describe a process without resolving a statutory exception. Preserve the operative version and the date it was reviewed.

Identify the first event that could change the available options: a hearing, appeal deadline, transfer, levy, transaction, medical appointment, or agency action. Work backward from that event. If a key fact remains unknown, label it unknown and investigate it. That discipline turns general information into an organized record for counsel without mistaking the article for a completed case-specific analysis.