A bank rarely files one kind of return. It files 1099-INT for depositors, 1099-B for brokerage and securities customers, and the 5498 series for the IRAs it custodies — each with its own boxes, its own validation rules, and its own deadline. The volume is the real differentiator: a single institution can generate hundreds of thousands of recipient records, which pushes most banks toward the IRIS Application-to-Application (A2A) channel rather than the manual portal. The hard parts are not the forms themselves but the things around them — matching payee TINs before filing so you avoid backup withholding and penalties, electing Combined Federal/State Filing correctly on the first submission, and correcting a wrong figure cleanly after the fact. If your filing window is already tight, a provider that holds an active IRIS Transmitter Control Code can file on your behalf today rather than after a 45-business-day wait.
In this story
Why a Bank Files Three Returns, Not One
Most businesses worry about a single 1099. A bank is, in tax terms, three different filers wearing one charter, and the form you owe depends entirely on which side of the institution the customer touched.
The deposit side of the house generates Form 1099-INT, which reports the interest you paid on checking, savings, certificates of deposit, and money-market accounts. The wealth and brokerage side generates Form 1099-B, which reports the proceeds from securities your customers sold, along with the cost basis and the holding period that determine whether a gain is short-term or long-term. And the retirement side generates the 5498 series — Form 5498 for traditional and Roth IRA contributions and fair market value, Form 5498-ESA for education savings accounts, and Form 5498-SA for health and medical savings accounts — because the bank is the custodian of record for those accounts. Each return answers a different question the IRS is asking, so each one carries its own set of boxes and its own arithmetic that IRIS will check before it accepts the file.
What unites them is the channel. The IRS Information Returns Intake System (IRIS) is the modern replacement for the legacy FIRE system, and it accepts these returns either through a manual web portal or through an Application-to-Application (A2A) connection that lets your systems transmit XML directly. For a bank, the portal is almost never the answer, because the portal is built for filers counting returns in the dozens, not the hundreds of thousands. The interesting decisions for a financial institution all live in the A2A path, in the data you feed it, and in the timing — not in the choice of form.
IRIS forms, channels, and the A2A transmission model are defined in IRS Publication 5717 (the IRIS portal and A2A guide) and Publication 5718 (the A2A specification). Read them directly at irs.gov/pub/irs-pdf/p5717.pdf and irs.gov/pub/irs-pdf/p5718.pdf.
Three Forms, Three Deadlines — and the May Surprise
The single most common scheduling mistake a bank makes is treating its information-return season as one event in January. It is not. The three forms a financial institution files are due to recipients and to the IRS on different dates, and the spread runs from the end of January all the way to the end of May. Planning your data extracts and your transmission windows around a single date is how a perfectly clean 5498 file ends up filed late.
| Form | Recipient copy due | IRS e-file due |
|---|---|---|
| 1099-INT | January 31 | March 31 |
| 1099-B | February 15 | March 31 |
| 5498 series | May 31 | May 31 |
The 5498 series is the row to circle. Because IRA contributions can be made up until the individual tax-filing deadline in April, the 5498 deadline is pushed out to the end of May — long after the rest of the season feels finished. The recipient statement and the IRS filing share that May 31 date, which means there is no early-warning gap to catch a problem before it goes federal. Teams that demobilize their filing operation in February are exactly the teams that miss the 5498 window, and a late information return carries a per-return penalty under Internal Revenue Code section 6721 that scales fast across a custodian's account base.
Build your season as three mini-projects. Work backward from March 31 for the 1099-INT and 1099-B e-file, and separately backward from May 31 for the 5498 series, leaving room in each window for a rejected transmission to come back and be corrected. The IRS does not grant relief for a late file just because an earlier form in the same season was on time.
The Volume Problem: Why Banks Live on A2A
The thing that separates a bank from almost every other IRIS filer is sheer record count. A regional institution can easily produce a six-figure 1099-INT file from its deposit base alone, and the manual portal — designed for hand-keying or uploading small batches — simply was not built for that. This is why financial institutions overwhelmingly transmit through the Application-to-Application channel, where your system sends an XML transmission and IRIS responds programmatically with a confirmation and, later, an acknowledgement.
An A2A transmission is structured as a manifest that wraps one or more submission groups, and each submission group carries the header for a form type plus the individual recipient records under it. There is a hard ceiling worth designing around: per IRS Publication 5717, a single submission payload is capped at 100 MB. A bank's full annual volume will not fit in one payload, so the practical pattern is to split the year into multiple submissions and transmit them in sequence — which is fine, until Combined Federal/State Filing enters the picture and the order of those submissions starts to matter (more on that below).
When IRIS accepts a transmission it returns a Receipt ID and a Unique Transmission ID (UTID), and these are the two values you must capture and never lose — they are how you later retrieve the acknowledgement that tells you whether every record inside was accepted, accepted with errors, or rejected. For a bank moving large batches, treating the Receipt ID and UTID as durable records in your own systems is not optional bookkeeping; it is the only way to reconcile a quarter-million returns against what the IRS actually took.
The 100 MB submission cap, the manifest-and-submission structure, and the Receipt ID / UTID response model are specified in IRS Publication 5718, the IRIS A2A specification, available at irs.gov/pub/irs-pdf/p5718.pdf.
Match Your Payee TINs Before You File, Not After
For a bank, the cheapest mistake to prevent and the most expensive to ignore is a wrong name-and-TIN combination on a recipient. When the name and Taxpayer Identification Number a customer gave you do not match the IRS database, two things happen: the return is at risk of rejection, and you may be required to apply 24% backup withholding under Internal Revenue Code section 3406 on that customer's future interest or proceeds. Multiply a single TIN error across an institution's account base and the section 6721 and 6722 penalties — which apply separately to the IRS copy and the recipient copy — stop being rounding errors.
The IRS gives you a way to check before you file. Through the e-Services TIN Matching program, described in IRS Publication 2108, you can verify a payee's name-and-TIN combination against IRS records ahead of filing season. There are two modes, and the difference matters at a bank's scale. Interactive TIN Matching accepts up to 25 name/TIN combinations per request, with a ceiling of 9,999 requests in any 24-hour period for a single User ID — useful for spot-checks but far too slow for a full deposit base. Bulk TIN Matching is the one a financial institution actually uses: it accepts up to 100,000 name/TIN combinations per file, submitted through a secure mailbox, and returns a match code for each one so you can fix the bad records long before they reach a 1099-INT or 1099-B.
The Interactive (25 per request) and Bulk (up to 100,000 per file) TIN Matching limits and the match return codes are defined in IRS Publication 2108, the TIN Matching Program guide. The program is reached through irs.gov/e-services; backup withholding obligations follow Internal Revenue Code section 3406.
Combined Federal/State Filing: One Election, One Position
Most of the forms a bank files — 1099-INT and 1099-B among them — are eligible for the IRS Combined Federal/State Filing (CF/SF) program, which forwards the federal data to participating state revenue departments so you do not have to file with each state separately. On paper this is a gift to a multi-state institution. In practice it carries one trap that has nothing to do with your data being correct and everything to do with how A2A submissions are ordered.
Because a bank's volume forces the year into multiple submissions, you have to decide which submission carries the CF/SF election. The rule, learned the hard way against the IRS testing environment, is that the system only honors a CF/SF election when it sits in the first submission group of the transmission. Elect CF/SF on a later submission and the election is silently dropped: the header is read as if no election were made, the per-state totals never forward, and the IRS reports it back against the first submission group with the rejection codes SHAREDIRFORM020 and SHAREDIRFORM022. The state filing you thought you completed simply did not happen, even though every figure in the file was valid.
There is a second nuance a bank should not over-trust: the CF/SF participant list is commonly described as 33 states, but several of those states' own revenue departments contradict the federal list — Oregon was added inadvertently, and Rhode Island and Maine have publicly said they do not rely on the combined program. For those states, treat CF/SF as a federal flag only and plan to file directly with the state. CF/SF reduces your state workload; it does not eliminate it.
Filing six figures of 1099-INT and getting the CF/SF order wrong?
e1099f orders any CF/SF-electing submission first automatically and validates every record against the IRS business rules before it transmits — so the state data forwards instead of vanishing.
Correcting a Filed Return Without Creating a Duplicate
At a bank's volume, corrections are not an exception — they are a routine part of every season, whether a customer disputes an interest figure, a brokerage cost basis is restated, or an IRA contribution is reclassified after the fact. The discipline that keeps corrections from compounding is to file them as actual corrections against the original transmission, not to re-send the record as a fresh original. IRIS tracks corrections by reference: a replacement points back to the Receipt ID of the transmission it is fixing, which is why the Receipt ID you captured at filing time becomes load-bearing months later. Re-submitting a corrected figure as a brand-new original is the fast path to a duplicate-filing rejection and a recipient who receives two conflicting statements.
This is also where TIN matching pays off a second time. A large share of corrections at financial institutions trace back to a name-and-TIN mismatch that was never caught before filing — the kind of error a pre-file bulk TIN check would have surfaced in February instead of in an IRS notice in the summer. Banks that match first correct less.
Common Rejection Reasons (and How to Avoid Them)
These are the failures that actually bite a financial institution's file, drawn from the IRIS business-rule catalog for the forms banks file most. Each one rejects records, and at volume each one rejects a lot of them at once.
Cause: in a multi-submission transmission, the CF/SF election was placed on a later submission group rather than the first, so IRIS dropped it and returned SHAREDIRFORM020 and SHAREDIRFORM022 against the first group. Fix: order the transmission so the CF/SF-electing submission is first, and confirm each electing record carries its per-state total group rather than a count-only group.
Cause: a brokerage record sets both the short-term and the long-term gain/loss indicator to 1, which rule F1099B001 forbids — a lot can be one or the other, not both. The related rule F1099B003 rejects a record where the gross-proceeds and net-proceeds indicators are both set. Fix: derive the holding-period and proceeds flags from the trade data so exactly one of each mutually exclusive pair is set before you build the XML.
Cause: on a 1099-INT, the specified private activity bond interest amount exceeds the total tax-exempt interest amount, which rule F1099INT002_001 rejects because the private-activity slice cannot be larger than the whole it belongs to. Fix: validate the relationship at extract time so the private-activity amount is always less than or equal to the tax-exempt total.
Cause: a 5498 reports a rollover contribution or a fair market value greater than zero but none of the account-type indicators (traditional IRA, SEP, SIMPLE, or Roth) is set to 1, which rule F5498001 treats as missing data. Fix: ensure every funded 5498 record carries the correct account-type indicator, since the IRS cannot post a contribution it cannot classify.
Cause: a double dash (--) appearing anywhere in a data value — an address line such as Main--Suite 4 is a classic — rejects the entire transmission, because the XML treats the sequence as the start of a comment. Fix: sanitize address and name fields to replace double dashes with a single hyphen before serializing the XML, and do it across the whole batch, not record by record.
Skip the Plumbing: The e1099f Advantage for Financial Institutions
Built for bank volume
Transmit 1099-INT, 1099-B, and the 5498 series through IRIS A2A at six-figure scale without standing up your own integration.
CF/SF in the right place
The CF/SF-electing submission is ordered first automatically, so your state data forwards instead of failing on SHAREDIRFORM020/022.
Rules checked first
Every record runs against the IRS business rules — including the 1099-B, 1099-INT, and 5498 checks — before anything is transmitted.
A Receipt ID and an acknowledgement, not a batch of rejected records — across all three filing windows.
Frequently Asked Questions
Which 1099 and 5498 forms does a bank typically file?
Are the deadlines really different for each form?
Should a bank use the IRIS portal or the A2A channel?
Is there a size limit on an IRIS submission?
Why does the order of my submissions matter for state filing?
SHAREDIRFORM020 and SHAREDIRFORM022 against the first group.How do I match recipient TINs before filing?
What happens if a customer's name and TIN don't match?
Can I just re-send a corrected record as a new original?
Does CF/SF cover all 33 listed states?
What's the most common reason a bank's file gets rejected?
F1099B001), a 1099-INT whose private-activity bond interest exceeds the tax-exempt total it belongs to (rule F1099INT002_001), and a funded 5498 that carries no account-type indicator (rule F5498001). A stray double dash in an address or name field also rejects the entire transmission, so it is worth sanitizing the whole batch before you serialize the XML.Does e1099f require my team to understand all of this?
Not tax advice. This is general information about IRS procedures for financial-institution filers and may change as the IRS updates IRIS; the published IRS publications are authoritative. Consult a qualified tax professional about your institution's specific filing obligations.