The Complete Guide to IRS 1099 Reporting in Business Central (2025+)

Posted on by

By Ivan Labrador — Dynamics 365 Senior Developer

If you’ve been working with Business Central for a while, you probably remember the old 1099 process — the one based on the 1099 Form Boxes page, the FIRE system, and preprinted forms. Starting with version 24.0 (and mandatory from version 27.0), Microsoft completely redesigned IRS 1099 reporting in Business Central. The new system integrates directly with the IRS’s Information Returns Intake System (IRIS) via API, eliminates preprinted forms, and introduces a period-based configuration model.

This guide walks you through the entire process from start to finish, including the setup, vendor configuration, document generation, electronic filing, corrections, and — just as importantly — the real-world troubleshooting lessons I’ve learned from production deployments.

What Changed and Why It Matters

The IRS retired the legacy FIRE (Filing Information Returns Electronically) system and replaced it with IRIS (Information Returns Intake System). IRIS uses XML format instead of the old fixed-length text files from Publication 1220, and it validates transmissions with stricter rules around name formatting, TIN structure, and schema compliance.

Business Central now supports IRIS through two channels:

  • A2A (Application to Application): Available only for SaaS/Cloud tenants. Business Central sends the XML directly to IRIS using Microsoft’s security certificate. This is the recommended approach.
  • Magnetic Media (FIRE): Optional for cloud users and the only option for on-premises environments. This generates a file you manually upload to the FIRE portal.

The key architectural change is that the old IRS 1099 Code field on the Vendor Card is now replaced by a period-based configuration model. Each reporting year has its own setup, its own vendor mappings, and its own form box definitions. This means you can prepare next year’s configuration without affecting the current year’s reporting.

Part 1: Initial Setup

Step 1 — Enable the Feature

  1. Search for Feature Management.
  2. Find “Feature Update: Enable using 1099 forms to transmit the tax data to the IRS in the United States”.
  3. Set Enabled for to All Users and confirm.
  4. Follow the IRS Forms Guide wizard:
    • Select the Reporting Year (e.g., 2025).
    • If this is your first time, choose Create New Setup.
    • If upgrading from the old system, choose Transfer Existing Data.
    • Enable Collect Details For Line if you want drill-down capability on calculated amounts (recommended, but uses more database space).
    • Configure Protect TIN to mask taxpayer identification numbers on printed forms.
    • Enter your Business Name Control — this must match your registration in the IRS’s National Account Profile (NAP) database.

Important: The automatic upgrade only migrates data for the year 2025. If you need previous years, migrate them manually.

Step 2 — Configure IRS Forms Setup

Search for IRS Forms Setup to review or adjust global settings:

  • Collect Details For Line: Enables drill-down from the 1099 Form Document amounts to individual vendor ledger entries.
  • Protect TIN: Controls whether TINs are masked when printing (shows only last 4 digits: XXXXX1234).
  • Business Name Control (IRIS FastTab): Must match the IRS NAP database.
  • Setup IRIS User ID: Each BC user who sends transmissions needs their own IRIS User ID. Use this action to register the ID from the IRS Consent App.
  • Email Content Setup: Customize the subject and body for emailed 1099 forms.

Step 3 — Create the Reporting Period

  1. Search for IRS Reporting Periods.
  2. Create a new period with:
    • Starting Date: 01/01/2025
    • Ending Date: 12/31/2025
  3. If you already have a previous year configured, use Copy Setup From to copy forms, form boxes, vendor setup, and adjustments.

Tip: You must create a new reporting period for each year. Never skip this step — the entire 1099 process is period-dependent.

Step 4 — Configure Forms and Form Boxes

From the IRS Reporting Periods page:

  1. Use the Forms action to open IRS 1099 Forms.
  2. Verify that the form types you need are present (MISC, NEC, INT, DIV, etc.).
  3. For each form, use Form Boxes to review the box definitions.
  4. Ensure the Minimum Reportable Amount is set correctly per IRS instructions for the reporting year.

Warning: The Update Form Boxes action changes box definitions and can make previous-year reporting impossible. Always complete all reporting for the current year before running this action.

Part 2: Vendor Configuration

Setting Up Vendors for 1099 Reporting

There are two ways to configure which vendors receive 1099s:

Option A — From the IRS Reporting Period (recommended for bulk setup):

  1. On the IRS Reporting Periods page, use the Vendor Setup action.
  2. This opens the IRS 1099 Vendor Form Box Setup page.
  3. For each vendor, specify the Form No. (e.g., NEC) and Form Box No. (e.g., NEC-01).
  4. Use the Suggest action to auto-populate vendors based on filters, then assign default Form No. and Form Box No.

Option B — From the Vendor Card:

  1. Open the Vendor Card → Related → Purchases → IRS 1099 Setup.
  2. Select the Period No., Form No., and Form Box No.

Note: The IRS 1099 fields on the Vendor Card (Payments FastTab) appear grayed out because they’re calculated from the period-based setup, not edited directly.

Additional Vendor Card Settings

On the Payments FastTab:

  • Receiving 1099 E-Form Consent: Toggle on if the vendor has provided signed consent to receive 1099 forms electronically via email.
  • E-Mail For IRS: Optional separate email for IRS communications. If blank, BC uses the standard Email field.
  • FATCA Requirement: Toggle on if the vendor requires FATCA filing.

Critical Data Quality Checks

Before generating 1099 documents, validate the following for every 1099 vendor:

FieldRequirement
Federal ID No.Exactly 9 digits, numbers only. No dashes, spaces, or special characters.
NameLetters, spaces, and hyphens only. No periods, numbers, or special characters.
Primary ContactMust have a valid name (not a phone number or empty).
AddressComplete and properly formatted.
Tax Identification TypeMust be correctly set (SSN for individuals, EIN for businesses).

Real-world lesson: IRIS validates names using the pattern ([A-Za-z\-] ?)*[A-Za-z\-]. A vendor named “ESTEBAN A. RODRIGUEZ” (with a period) caused the XML to generate an empty PersonFirstNm field, which triggered a schema validation rejection. The fix was to remove the period: “ESTEBAN A RODRIGUEZ”. Review all your vendor names before the first transmission.

Part 3: Generating 1099 Form Documents

Create the Documents

  1. Search for IRS 1099 Form Documents.
  2. Use the Create Forms action.
  3. Select the Period (e.g., 2025).
  4. Optionally filter by Vendor No. or Form No.
  5. Enable Replace if you want to overwrite previously generated documents.
  6. Click OK.

Business Central calculates the amounts based on posted and applied vendor ledger entries within the reporting period. Only vendors with both IRS 1099 Form No. and IRS 1099 Form Box No. configured for the period will have documents generated.

Review and Adjust Amounts

Before releasing documents:

  1. Open each form document and review the Amount field.
  2. If Collect Details For Line is enabled, drill into the amount to see individual vendor ledger entries.
  3. If adjustments are needed (e.g., to add or subtract amounts), go to IRS Reporting Periods → Adjustments and create entries with positive or negative Adjustment Amount.

Correcting Vendor Ledger Entries

If a vendor ledger entry has the wrong Form Box No. or incorrect 1099 amount:

  1. Open the vendor’s Vendor Ledger Entries.
  2. Use Edit List.
  3. Change the IRS 1099 Form Box No. and/or IRS 1099 Reporting Amount.

If you forgot to configure the vendor entirely before posting:

  1. Go to IRS 1099 Vendor Form Box Setup.
  2. Add the vendor’s configuration.
  3. Use the Propagate action to update existing vendor ledger entries and/or open purchase documents for the period.

Release Documents

  1. On the IRS 1099 Form Documents page, select the documents you want to submit.
  2. Use the Release action (or Release All for bulk).

Only released documents are included in the transmission.

Part 4: Electronic Submission via IRIS

Create the Transmission

  1. Search for IRIS Transmissions.
  2. Use the Create IRIS Transmission action.
  3. Select the Reporting Period (2025).
  4. Click OK.

Note: If certain form boxes won’t be reported (e.g., MISC-14, MISC-15-B, MISC-16), BC shows a confirmation dialog. This is normal — click Yes to continue.

Review Before Sending

  1. Click on the Period No. to open the IRIS Transmission page.
  2. Review the list of documents, vendors, form types, and amounts.
  3. Verify the Receipt ID field and Status.

Send to the IRS

Click the Send action. Business Central transmits the XML to IRIS via Microsoft’s A2A channel. After submission:

  • The Receipt ID is returned and stored.
  • The Status changes based on the IRS response:
    • Accepted — All good.
    • Accepted with Errors — Records accepted but have minor issues.
    • Rejected — Failed validation; review errors and resubmit.
    • Partially Accepted — Some records accepted, others rejected.

Handling Rejected Transmissions

If the status is Rejected:

  1. Click Show error(s) to see the error details.
  2. Fix the root cause (vendor data, TIN format, name issues, etc.).
  3. Use Send Replacement to resubmit.
  4. Use Transmission History to track all attempts.

Correcting Accepted Transmissions

If you discover an error after the IRS has accepted:

  1. Open the IRIS Transmission.
  2. Use the Allow Correction action.
  3. Use Reopen on the affected document, make corrections, then Release again.
  4. The Needs Correction checkbox is automatically set.
  5. Use Send Correction — BC only sends the corrected lines.

Part 5: Printing and Emailing 1099s to Vendors

Print Copy Substitutes

From the IRS 1099 Form Documents page:

  1. Select a document and use the Print action.
  2. Choose the copy type:
    • Copy B — For the vendor.
    • Copy C — For your records.
    • Copy 2 — Second copy for the vendor (required in some states).

Important: The new system prints substitute forms on plain paper. Preprinted IRS forms are no longer supported.

Email 1099s

  1. Ensure the vendor has Receiving 1099 E-Form Consent enabled and an email configured.
  2. The document must be in Submitted status.
  3. Use the Send Email action from the document or the list page (for bulk).
  4. Select the copy type (Copy B or Copy 2).
  5. Enable Resend Email if you need to re-send to vendors who already received it.

Part 6: Preparing for the Next Year

When you’re ready to set up 2026:

  1. Finish all 2025 reporting first — including corrections and re-transmissions.
  2. Go to IRS Reporting Periods and create a new period: 01/01/2026 to 12/31/2026.
  3. Use Copy Setup From selecting 2025 to copy forms, form boxes, vendor setup, and adjustments.
  4. Open Vendor Setup within the 2026 period and verify each vendor has the correct Form No. and Form Box No.
  5. For vendor ledger entries already posted in 2026 that are missing 1099 codes, use Propagate from the IRS 1099 Vendor Form Box Setup page with the option to update existing entries.

Important: Do NOT run Update Form Boxes until you’ve completed all reporting for the previous year. This action can change box definitions and break previous-year reports.

Part 7: Troubleshooting — Lessons from the Field

Here are the real-world issues I’ve encountered during production deployments, along with their solutions.

XML Schema Validation Error: Empty PersonFirstNm

Symptom: IRIS rejects with “Value ” is not facet-valid with respect to pattern for type ‘PersonFirstNameType’.”

Cause: A vendor name contains characters not allowed by IRIS (periods, numbers, or special characters). BC’s XML generator fails to parse the name correctly, leaving the first name field empty.

Fix: Review all 1099 vendor names. Remove periods, numbers, and special characters. For example:

  • ESTEBAN A. RODRIGUEZ → ESTEBAN A RODRIGUEZ
  • JOHN D. SMITH JR. → JOHN D SMITH JR

Also verify that the vendor’s Primary Contact has a valid name — not a phone number or other non-name value.

SYSVR001: TCC in Test Mode

Symptom: “The TCC is in Test and not valid for Production.”

Cause: The Transmitter Control Code (TCC) is registered in IRIS as Test, but BC is sending with TestCd = P (Production).

Fix: The TCC must be moved to Production status in IRIS. This happens after the transmitter passes Communication Testing in the ATS (Assurance Testing System) environment. Contact the IRS Help Desk (1-866-937-4130) to request the status change. For SaaS environments, Microsoft acts as the transmitter, so this should already be configured — if not, open a support case.

TMFST012: Original Receipt ID Mismatch (Confirmed Bug in BC 27)

Symptom: “Original Receipt ID does not match Receipt ID from an Original transmission that was rejected previously.” This appears on every Replacement attempt, creating an infinite rejection loop.

Cause: The Original transmission was rejected during pre-receipt validation (e.g., schema error or TCC issue). IRIS never registered it as a valid “rejected Original” that can be referenced by a Replacement. BC continues sending Replacements pointing to a Receipt ID that IRIS doesn’t recognize.

Status: Microsoft has confirmed this is a known bug in Business Central 27. The fix is included in the upcoming Business Central 28 release.

Workaround for BC 27: If you’re stuck on this loop today, open a Microsoft Support case. In our case, Microsoft provided a PTE (Per-Tenant Extension) called “Reset Transmission Status” that adds a new action “Reset Status to None” on the IRIS Transmission Card page. This action changes the transmission status from Rejected back to None, which allows you to resend as a fresh Original using the standard Send action.

The workflow after installing the PTE:

  1. Open the IRIS Transmission for the affected period.
  2. Use the new Reset Status to None action.
  3. The status changes from Rejected to None.
  4. Use the Send action — BC now generates a new Original transmission (TransmissionTypeCd = O) without referencing any previous Receipt ID.
  5. IRIS processes it as a brand-new submission.

Important: This PTE is a temporary workaround. Once your environment upgrades to BC 28, the fix is native and the PTE can be uninstalled. If Microsoft Support doesn’t proactively offer this extension, explicitly ask for it — reference the known bug and request the “Reset Transmission Status” PTE.

TIN Matching Errors: “Accepted with Errors”

Symptom: The IRIS Transmission status shows “Accepted with Errors” and the error list shows: “If Person Name and TIN in Recipient Detail have a value, they must match the IRS database.” Multiple vendors are flagged with this error.

Cause: This is not a BC or formatting issue — it’s a TIN Matching problem. The IRS cross-references every vendor’s name (PersonName) and TIN (RecipientTIN) against the Social Security Administration database (for SSN) or the IRS database (for EIN). If the combination doesn’t match exactly, the record is flagged.

The good news is that “Accepted with Errors” means the IRS did receive the transmission. The flagged records need correction and resubmission, but all other records were accepted successfully.

Common causes:

  • The vendor’s legal name (as registered with the SSA/IRS) differs from the name in Business Central. For example, the vendor uses a DBA (doing business as) name but their SSN is registered under their legal name.
  • The TIN is simply wrong — a typo, a transposed digit, or the wrong type of ID (EIN vs. SSN).
  • The vendor’s last name changed (marriage, etc.) but the SSA records weren’t updated.

Fix:

  1. For each flagged vendor, request an updated W-9 form.
  2. Open the Vendor Card and verify that the Name field (General FastTab) matches exactly what appears on the W-9, which should match IRS/SSA records.
  3. Verify the Federal ID No. (Payments FastTab) matches the W-9.
  4. After correcting the data, go to the IRIS Transmission page.
  5. Use Allow Correction → open each affected document → Reopen → Release.
  6. Use Send Correction — BC only sends the lines marked as “Needs Correction.”
  7. After the IRS processes the correction, the Corrected field on those lines will show “Yes.”

Pro tip: You can proactively avoid TIN Matching errors by using the IRS TIN Matching service (available at IRS.gov/TIN-Matching) before submitting your 1099s. This service lets you validate name/TIN combinations in bulk before filing season.

Federal ID No. Format Issues

Symptom: Validation errors related to TIN format.

Fix: The Federal ID No. must be exactly 9 digits with no dashes, spaces, or formatting characters. Check both the Company Information Federal ID No. and each vendor’s Federal ID No.

IRIS Transmission Cannot Be Deleted

Symptom: “A transmission with status other than None cannot be deleted.”

Cause: BC protects transmissions that have been sent to IRIS to maintain an audit trail.

Workaround: If you need to start over, try creating a new IRIS Transmission for the period. If that doesn’t work, open a Microsoft Support case and request the “Reset Transmission Status” PTE (see the TMFST012 section above).

Quick Reference Checklist

Before you click Send for the first time each year, verify:

  • [ ] Feature is enabled in Feature Management
  • [ ] IRS Reporting Period exists for the year
  • [ ] Forms and Form Boxes are configured with correct minimum amounts
  • [ ] IRIS User ID is registered in IRS Forms Setup
  • [ ] Company Information: Federal ID No. is 9 digits, numbers only
  • [ ] Company Information: Name and address are complete
  • [ ] All 1099 vendors have Form No. and Form Box No. assigned for the period
  • [ ] Vendor names contain only letters, spaces, and hyphens (no periods or numbers)
  • [ ] Vendor Federal ID numbers are 9 digits, numbers only
  • [ ] Consider running IRS TIN Matching to validate name/TIN combinations before filing
  • [ ] Primary contacts have valid names (not phone numbers)
  • [ ] Vendor e-form consent is configured for email delivery
  • [ ] 1099 Form Documents are created and amounts reviewed
  • [ ] Adjustments are entered if needed
  • [ ] Documents are Released

Useful Pages and Actions Reference

Page / ActionPurpose
Feature ManagementEnable the new 1099 feature
IRS Forms SetupGlobal settings: TIN protection, IRIS User ID, email templates
IRS Reporting PeriodsPeriod management, copy setup, vendor setup, adjustments
IRS 1099 Vendor Form Box SetupMap vendors to forms and boxes per period
IRS 1099 Form DocumentsGenerate, review, release, print, and email 1099 documents
IRIS TransmissionsCreate transmissions, send to IRS, view history
Vendor Ledger Entries (Edit List)Correct IRS 1099 Form Box No. and reporting amounts
Propagate (on Vendor Form Box Setup)Backfill existing entries with correct 1099 codes
Copy Setup From (on Reporting Periods)Copy all configuration from a previous year
Reset Transmission Status PTE (from Microsoft Support)Workaround for TMFST012 bug in BC 27 — resets transmission to None

Conclusion

The new IRS 1099 process in Business Central is a significant improvement over the legacy system. The IRIS integration, period-based configuration, and built-in email delivery make year-end reporting more efficient. However, the transition comes with a learning curve and some rough edges — particularly around IRIS validation rules and error recovery.

From our experience deploying this in production, here’s what I’d recommend:

  1. Start early. Don’t wait until January to discover configuration issues. Set up your reporting period and validate vendor data in December.
  2. Validate vendor data aggressively. The two biggest time sinks were name formatting issues (periods, special characters) and TIN mismatches. A pre-submission data quality pass saves days of back-and-forth.
  3. Don’t panic at “Accepted with Errors.” It means the IRS received your submission. The flagged records can be corrected and resubmitted using Send Correction without affecting the accepted records.
  4. If you hit TMFST012, escalate immediately. This is a confirmed bug in BC 27. Don’t waste time trying different Receipt IDs or manual workarounds — open a Microsoft Support case and ask for the “Reset Transmission Status” PTE.
  5. Know who the transmitter is. In SaaS environments, Microsoft is the transmitter (not your company). This matters when the IRS asks questions about the transmission — some answers can only come from Microsoft’s side.

The 1099 filing process in BC will keep improving with each release. Business Central 28 addresses the TMFST012 bug natively, and Microsoft continues to expand IRIS integration capabilities. In the meantime, this guide should help you navigate the current state of the system with confidence.

Ivan Labrador is a Dynamics 365 Senior Developer at MS Cloud Experts, specializing in Business Central development and consulting.

Post Views: 628

Leave a Reply

Your email address will not be published. Required fields are marked *