Every January, the same scramble: a controller exports the vendor ledger, filters out corporations by hand, tries to remember which payments were reimbursements and which were fees, chases missing W-9s by email, and hand-types totals into a filing portal. Odoo core has no concept of a 1099. There is no W-9 status on res.partner, no box code on an account.move.line, no distinction between an amount billed and an amount actually paid in the calendar year, and no report that reconciles to what you are about to certify to the IRS. Off-the-shelf localization apps typically stop at a flat vendor payment list — they do not carry box mapping down to the line, do not handle a mid-year TIN correction, and do not produce a file a transmitter will accept.

What we build is a compliance layer that runs all year rather than a January report. On the vendor side we extend res.partner with W-9 fields — legal name, TIN and TIN type (EIN/SSN/ITIN), federal tax classification, backup-withholding flag, foreign-payee/W-8 marker, and a solicitation state with a document attachment — plus an @api.constrains TIN format check and a computed x_1099_status that tells you at a glance which payees are documented, which are missing paperwork, and which are exempt. Box mapping lives on a small usa.1099.box model seeded with the current NEC and MISC boxes and attached to product categories, expense accounts, and journal-item defaults, so a bill line inherits its box code without a bookkeeper thinking about it. An override field on the line and a wizard for bulk reclassification cover the exceptions.

The number that matters is cash paid in the calendar year, not invoiced, so aggregation walks account.partial.reconcile from vendor payments back to the bill lines that were settled — reimbursements, credit notes, and partially paid bills all land correctly, and payment-processor exclusions (card and third-party network payments reportable on 1099-K) are flagged out. A usa.1099.run model materializes a tax-year snapshot as usa.1099.line records with stored computed totals and @api.depends-driven recomputation while the run is in draft; confirming the run freezes it so later postings cannot silently change a figure you already filed. Thresholds are configurable per box rather than hard-coded, with a below-threshold view so you can still file voluntarily. Corrections are first-class: a confirmed run can be superseded by a correction run that records the original amount, the corrected amount, and the reason, and marks the recipient as a corrected filing. Output is an e-file-ready fixed-width IRS FIRE/IRIS-style export plus a validated CSV for your transmitter or CPA, and QWeb PDF recipient copies with a mail action that sends them to consenting payees. Security is real ir.model.access.csv plus record rules so 1099 data is visible to accounting managers, not to every internal user, and everything is reachable over XML-RPC/JSON-RPC if you drive it from an external tool.

The module targets Odoo 17.0, 18.0, and 19.0 and is built against Community, using only accounting features present in Community (account, account_payment) — no Enterprise-only dependency. If you run Enterprise we hook into the accounting dashboard and use its reporting UI where it helps, and if you already run l10n_us, we sit beside it rather than replacing your chart of accounts. Each __manifest__.py is pinned to your exact series, and we adapt to your existing customizations rather than assuming a clean database.

This is build-to-order, not a download. We start with a scoping call where we look at your vendor master, how bills and payments are actually entered, whether you file yourself or through a CPA or transmitter, and which boxes you genuinely use. From confirmed scope, typical delivery is one working week: we build on our own instance, install and configure on a staging copy of your database, run a UAT pass against a prior tax year you already know the answers to, then go live with a rollback plan. You receive the full source, a git repository, technical and user documentation, a training session, and a post-go-live support window. Nothing about filing is guesswork we ask you to trust — the reconciliation report shows every payment behind every box total.