Choose an IRS-authorized e-file provider or aggregator service that supports 1099-NEC filing via API; review their documentation for authentication and submission format requirements.
Authenticate with the filing provider using their specified method (commonly an API key or OAuth token) and identify the correct endpoint for 1099-NEC submissions.
Construct the 1099-NEC payload for each recipient: include payer TIN and name/address, recipient TIN (SSN or EIN), recipient name and address, box 1 nonemployee compensation amount, and tax year.
Submit the payload; most providers return a submission ID or tracking number for each filing; store these for status polling and correction workflows.
Poll the provider's status endpoint or receive webhooks to confirm acceptance or rejection; IRS rejections typically include an error code and description requiring correction and resubmission.
After acceptance, retrieve recipient copy PDFs (if offered by the provider) for distribution to contractors; maintain records of accepted submission IDs for audit purposes.
Known gotchas
1099-NEC filings for the prior tax year are due to the IRS and recipients by January 31; verify the provider's processing cutoffs well before this deadline.
Payer and recipient TINs must match IRS records exactly; TIN validation errors are the most common rejection reason and require corrected submissions.
Corrections to already-accepted 1099-NEC filings require a separate corrected filing workflow (typically setting a 'corrected' flag and resubmitting); most providers have a distinct correction endpoint or parameter.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp