Most US companies discover their 1099 problem in the last week of January. Contractor payments sat in ERPNext all year as ordinary Purchase Invoices and Payment Entries with nothing distinguishing a reportable non-employee compensation payment from a reimbursement, a materials purchase, or a payment to a corporation that is exempt from reporting. Somebody then exports a supplier ledger to a spreadsheet, guesses at boxes, chases missing W-9s by email, and hand-keys totals into a third-party filing portal. ERPNext core has no Form W-9 record, no TIN or entity-classification fields with validation, no concept of a 1099 box on a bill line, no $600 threshold logic, no correction flag, and no IRS-formatted export. Supplier and Supplier Group carry tax_id as a free-text field, and that is essentially where native support ends.

The USA 1099 & E-File Pack is a proper Frappe app — its own module, DocTypes, fixtures and hooks — installed on your bench alongside ERPNext rather than a pile of customizations on standard doctypes. A 1099 Vendor Profile DocType hangs off Supplier and holds the W-9 data that actually matters: legal name, DBA, TIN and TIN type (EIN vs SSN), federal tax classification, backup-withholding flag, the signed W-9 attachment, and a default 1099 box. A custom field on Purchase Invoice Item and on Payment Entry references a 1099 Box DocType (NEC box 1, MISC boxes 1, 2, 3, 6, 10, 14 and the rest), defaulted from the vendor profile by a client script on supplier selection and overridable per line. Validation runs in hooks.py doc events — Purchase Invoice: validate blocks submission when a supplier is marked reportable but no box is set, and warns when the TIN is missing or fails checksum/format rules.

Reporting is built on cash basis, because that is what the IRS wants: a query report and a background job walk Payment Entry and Journal Entry allocations back to the bills they settled, so a December invoice paid in January lands in the correct tax year. A 1099 Filing Run DocType is the year-end control record. You pick the tax year and company, it aggregates per vendor per box, applies the reporting threshold per box, excludes vendors whose classification makes them exempt, and produces a child table you can review line by line with drill-through to the source vouchers. Anything unresolved — missing TIN, missing address, a vendor over threshold with no W-9 on file — surfaces as an exception list before you can mark the run ready. Corrections are first-class: a filing run can be created as a correction of a prior run, carrying the original amounts alongside the corrected ones and flagging each affected recipient.

Output comes in three shapes. A fixed-width IRS FIRE / IRIS-compatible transmittal file generated to your specification, a CSV in the exact column layout your filing service or CPA expects (Track1099, Tax1099, Avalara and similar all differ, so this is mapped during scoping), and recipient copies rendered from Frappe Print Formats as PDF, optionally emailed in bulk to each vendor's contact through the standard Frappe email queue with delivery status tracked on the filing run. Everything is exposed through whitelisted methods on the Frappe REST API, so your CPA portal or an external automation can pull totals without touching the database. Role profiles keep it tight — an AP clerk can maintain vendor profiles and box mappings, only a 1099 Filing Manager can generate a run or produce a transmittal file, and TIN fields are permlevel-restricted so the full number is not visible to everyone in the AP queue. Scheduler events run a monthly reportable-spend check so a vendor crossing threshold in June is flagged in June, not in January.

This is build-to-order, and we are explicit about what that means. It is not a listing you download from the Frappe Cloud Marketplace today. We start with a scoping call, confirm your filing route (self-file to FIRE/IRIS, or hand off to a filing service and which one), your box usage, your entity and multi-company structure, and your Frappe/ERPNext version — v15 and v16 are both supported. You get a fixed written scope and quotation. Typical delivery is one working week from confirmed scope, built against your version, tested on a staging bench with your own anonymized supplier and payment data, and only then migrated to production with a documented rollback. You keep the source: the app is handed over as a git repository you own, so nothing about your year-end filing is locked behind us.