An offer in compromise intake form should capture the taxpayer number, liability type, application fee and payment method, decision deadlines, and first payment date.
Key takeaways
- Check the taxpayer number against the IRS notices.
- Separate individual and business liabilities for review.
- Record the fee screening and chosen payment method.
- Assign an owner to each deadline and payment record.
A partner or operations lead often inherits a folder of tax notices, a client who is worried about the balance, and a set of dates that somebody has to track. When the intake form skips the right facts at the start, those gaps show up later as returned paperwork, a missed appeal window, or a payment schedule nobody set up.
This post sets out five fields that a standard intake form should capture for an IRS offer in compromise. The list is not the whole file. The financial disclosures, supporting records, and offer packet each need their own checklist. These five fields do a different job: they show who the offer covers, what it costs to submit, which deadlines have started, and when money is due. Each section below says what to record, why the field matters, and which official source supports the rule behind it.
Many teams build intake forms by copying whatever the last client needed. That habit leaves holes. A standard form asks the same questions in the same order for every file, so a new partner can pick up any file and find the same facts in the same place. It also gives operations leads something they can audit, because a blank field is visible on day one rather than discovered at the appeal deadline. For the wider handoff, use the client intake checklist.
Taxpayer identification number
Start with the number that identifies the taxpayer. Every intake form needs the taxpayer identification number, or TIN, copied exactly as it appears on the IRS notices in the file. For prompt-payment purposes, Treasury's glossary defines TIN as the nine digit Employer Identifying Number or Social Security Number described in Section 6109 of the Internal Revenue Code of 1986; check the offer intake number against the IRS notices. The Treasury chapter on Prompt Payment Act guidance sets out that definition.
Why does this field come first? The number is the link between your intake record and the taxpayer's account. If it is wrong, every later step, from the fee to the appeal, attaches to the wrong file. Ask for the number once, store it in one place, and mask it on any screen or report that more than one person can see. Then check it against the most recent IRS letter in the folder, not against what the client remembers.
Record the name too, exactly as it appears on the notice. A name that differs from the account name makes it harder to match the offer to the balances it is meant to resolve. Some clients also have two identifiers in play: a personal number for individual debts and an employer number for a business. Keep them in separate fields so no one copies one into the other's slot. That split leads directly into the next field.
If the number is missing or does not match the notices, do not guess and do not fill it in from a similar client. Mark the field as open, add the date, and note who will get the missing number and from which source. A file with an open identifier can still be worked on, but it should not move to submission until the number is confirmed against an IRS document.
Treat the TIN as sensitive. Limit access to the people who need it, keep it out of email subject lines, and leave it out of shared chat threads. When another team needs the number, send it through the secure channel your firm already uses, and log that it was sent.
Liability type and number of forms
The second field records whose debt the offer covers. The Taxpayer Advocate Service explains that an offer can be submitted on taxes owed individually and on business tax debts. It also notes that separate Forms 656 may be required for individual and business liabilities. The intake form should therefore make liability type a choice with three answers: individual, business, or both. Free text invites small variations that make reporting hard.
If the answer is both, flag the file for review. The reviewer should decide on the number of forms against the current IRS instructions rather than assume one submission covers everything. Record the decision and the reason next to the flag, so the person who opens the file later can see why there is one form or two.
It also helps to list each liability by tax type and period on its own row. A single line that says "federal taxes, several years" hides the individual and business pieces inside it. A row for each balance lets you match each amount to the right submission and spot a business debt that landed in an individual file.
Consider a file where one client owes personal income tax and also owes payroll tax through a business. An intake form that records only one name and one balance would hide the second liability. With separate liability rows, the reviewer sees both at intake, can decide on the form count, and can check each amount against its own notice before anything goes out.
When you ask the client about liabilities, use plain questions. Ask whether any tax debt sits in the client's own name, whether any sits in a business the client owns or runs, and whether the client is unsure about either. The answers feed the liability type field directly. An unsure answer should trigger a follow-up call rather than a default choice.
Application fee and payment method
The third field covers what the client pays to submit and how offer payments are made. The Taxpayer Advocate Service puts it this way: "You'll have to pay an application fee of $205 and make offer payments based on the payment method you choose, unless you meet the low-income certification guidelines, in the IRS OIC Booklet." The same page is the source for that wording, and the booklet it names is where the full rules sit.
Record four things. First, the application fee amount and the date it was paid. Second, whether the client was screened under the low-income certification guidelines, with yes, no, or not yet screened as the only answers. Third, the payment method the client chose, and the payment schedule that goes with it. Fourth, the version of the IRS OIC Booklet the team used, so anyone reviewing the file can see which version the figures came from.
Be careful with the word waived. Do not record the fee as waived unless the low-income certification guidelines were checked and the client met them. The source ties the fee and the offer payments to that screen, and a file that says otherwise will be hard to defend.
Fee amounts can change, so confirm the figure in the current booklet before you quote it to a client. A number copied from an old file or a forum post is not a source. Keep the booklet reference in the intake record so the check can be repeated.
Someone should own the fee record from the moment money moves. Decide whether the intake lead, the billing staff, or the partner handles the payment, and write that down on the form. When a fee or payment is made by someone other than the person who opened the file, the record should show both names and the date, so the trail stays intact.
Record the payment method in the client's own terms as well as the IRS term, so the client can recognize what they chose. If the client later asks what was agreed, the intake record should answer the question without a search through old emails.
Decision deadlines
The fourth field tracks what happens after the IRS decides. An offer can be accepted, rejected, or returned, and each outcome starts a different clock. The comparison below pairs each outcome with its follow-up work.
| Outcome | Follow-up work |
|---|---|
| Accepted | Schedule offer payments |
| Rejected | Prepare an appeal |
| Returned | Request reconsideration |
A rejection calls for an appeal decision. The Taxpayer Advocate Service explains that the client has the right to appeal, but the appeal must be filed within 30 days of the date of the IRS's rejection letter. To appeal, follow the instructions in the rejection letter and use IRS Form 13711, Request for Appeal of Offer in Compromise. Count from the date printed on the letter, not from the date the file reached your desk, and put the resulting deadline in the calendar the same day.
Returned offers are a different case, and the form should not lump them with rejections. The Taxpayer Advocate Service says the IRS will send a notice giving 30 days from the date of the notice to respond, asking for reconsideration of the decision to return the offer. Record the notice date, the reconsideration deadline, and whether a response has gone out.
Keep the reason for each outcome in the record too. A rejected offer, a returned offer, and an accepted offer each lead to different follow-up work, and a short note on what the IRS letter said saves the next reviewer from rereading the whole notice.
Watch for handoffs. Offers often move between a partner, an operations lead, and the client's own staff, and a deadline can fall between those hands. Put the rejection or return date on the shared tracker the day the letter is logged, and name one person responsible for the appeal or reconsideration step. If a deadline is at risk and the file has no clear owner, escalate it at once rather than waiting for the next review meeting.
Accepted offers also start a clock, covered in the next field. Keep all three outcomes on one tracker so a single view shows which file has a live deadline right now.
First payment date
The fifth field covers the first payment after an offer is accepted. The Taxpayer Advocate Service states that the first payment generally will be due 30 calendar days after acceptance unless another date is agreed to in an amended offer. The word generally matters.
Record two dates: the acceptance date from the IRS letter and the first payment due date. If an amended offer names another date, the form should say which amended offer it came from.
Amended offers need the same care. Keep the original acceptance record and the amended record side by side rather than overwriting one with the other. An overwritten date makes it impossible to show which date was agreed and when, and that history matters if a payment question comes up later.
Offer payments follow the payment method the client chose, so a single due-date box is not enough. Build a schedule with a row for each payment, showing the due date, the amount, the date paid, and a confirmation reference. Set a reminder ahead of each due date so the team can catch a shortfall in time.
Reconcile each payment against the schedule on a regular cycle. A payment that clears the bank but never gets matched to its row leaves the file looking late when it is not. A short regular check catches that kind of mismatch early. Use the bank reconciliation checks when reviewing the bank side of the record.
Illustrative example: matching a payment
An illustrative schedule lists a payment of $50. When it clears the bank, the reviewer matches it to its schedule row and adds the confirmation reference. If the row still looks unpaid, the reviewer resolves the mismatch. The $50 is illustrative, not a suggested offer amount.
Putting the five fields to work
A form that captures these five fields lets a reviewer answer the core questions quickly. Who owes? Which forms are expected? What has been paid, and under which method? Which clock is running? When is the next payment due? If any answer is missing, the file is not ready to move forward.
Set the form up so no file opens without the five fields filled in or marked as not yet known. Give each field one owner, usually the person who takes the call or receives the letter, and require that owner to update the field whenever a new IRS notice arrives. Review the whole form at each deadline, not only at the start. That routine costs little, and it catches the errors that intake is meant to prevent.
Training matters as much as the form. Walk each new team member through one completed file, and point to each of the five fields and the source behind it. A reviewer who understands why the deadline field exists is less likely to skip it under pressure.
Finally, review the form itself on a regular cycle. Rules, fees, and booklet versions change, and a form built around last year's wording will drift. Compare each field with the current IRS materials, update the source links, and log the date of the review at the top of the form.
Before you rely on any figure in this post, check the current IRS offer booklet and the notices that came with the file. The sources linked above are the basis for the rules here, and they are the first place to look when a detail changes.
Today, open an existing intake file and check these five fields against its notices. Assign an owner to the first missing item.
Questions and answers
What should happen when an intake detail is missing?
Mark it as not yet known and assign someone to obtain it. Keep the follow-up with the intake record.
What should a payment confirmation be matched to?
Match it to the corresponding payment schedule row. Check that the due date, amount, date paid, and confirmation reference agree.
General information, not legal or tax advice.