Every January the same scramble starts. Accounts payable exports a year of vendor payments to Excel, someone hand-filters the contractors from the incorporated suppliers, TINs get chased by email in the last week, and the totals never quite tie back to the vendor ledger. Business Central does ship the basics — IRS 1099 Form-Box codes on the vendor card and on purchase invoice lines, a vendor 1099 report, and printable forms — but the native flow assumes the box code was set correctly on every document at posting time, offers no structured W-9 or TIN-type record, treats amounts as invoice-based rather than payment-application-based, and gives you nothing usable when a recipient calls in March to say their figure is wrong. Corrections happen outside the system, which means next year's audit trail has a hole in it.\n\nThe USA 1099 & E-File Pack is an AL extension we build for your Business Central tenant that closes those gaps end to end. On the vendor side, a table extension and page extension add W-9 received date, TIN, TIN type (EIN or SSN), backup-withholding status and solicitation history to the vendor card, with a validation codeunit that flags incomplete or duplicate TINs before season instead of during it. On the transaction side, event subscribers on posting capture 1099-eligible amounts into a dedicated ledger keyed to vendor, box code, payment date and applied entry — so the figure you report follows the money, not the invoice. Box assignment is driven by configurable rules (by vendor, purchase account, dimension value or item category) with a per-line override that is still visible after posting, which is what makes reruns and audits sane.\n\nThe year-end run itself is a codeunit that builds a validated staging table: per-box thresholds applied, below-threshold vendors suppressed with the reason recorded, missing TINs and address problems listed as exceptions you can clear before anything leaves the system. From that staging table the extension produces both an IRS fixed-width e-file layout and a CSV shaped for your filing service, plus recipient copies. A corrected-return run reads the prior filed snapshot and emits only the deltas, keeping a permanent record of what was transmitted and when. Optional API pages (REST API v2.0 / OData v4) expose the staging data if you want it in Power BI or a Power Automate flow, and long-running builds can be scheduled through a job queue entry rather than tying up a user session.\n\nBecause this is an extension and not a modification, it stays upgrade-safe: table extensions, page extensions, codeunits and event subscribers only, no base-application changes, with dedicated permission sets so AP clerks, the controller and the auditor each see the right slice. We build it against your current Business Central release wave and target either SaaS (per-tenant extension) or on-premises deployment, whichever you run.\n\nThis is a build-to-order product, not an AppSource download. After you request a quotation we run a scoping call — your Business Central version and deployment model, your chart of accounts and how contractor spend actually posts, which boxes you file (1099-NEC and 1099-MISC are the usual pair), your filing service or transmitter, and how vendor onboarding captures W-9s today. From confirmed scope, typical delivery is one working week: development, then UAT on a sandbox copy of your production database against an agreed acceptance script, then a production install with a documented rollback. You receive the full AL source in your own Git repository, so the extension is yours to keep, extend or hand to another partner.