USA 1099 & E-File Pack

Key Features

Dedicated Frappe app with its own module, DocTypes, fixtures and `hooks.py` — installed via `bench get-app` / `bench install-app`, not a pile of customizations on core doctypes

`1099 Vendor Profile` DocType linked to Supplier: legal name, DBA, TIN + TIN type (EIN/SSN), federal tax classification, backup-withholding flag, W-9 attachment and effective date

TIN format and checksum validation on save, with permlevel-restricted TIN fields so full numbers are visible only to a `1099 Filing Manager` role

`1099 Box` DocType covering 1099-NEC and 1099-MISC boxes, with per-box reporting thresholds and per-box exemption rules maintained as data, not hardcoded

Custom fields on Purchase Invoice Item and Payment Entry to tag the applicable 1099 box, defaulted from the vendor profile by a client script and overridable per line

`Purchase Invoice: validate` and `Payment Entry: on_submit` doc events in `hooks.py` that block or warn when a reportable supplier has no box, no TIN, or no W-9 on file

Cash-basis aggregation that walks Payment Entry and Journal Entry allocations back to the settled bills, so a December invoice paid in January lands in the correct tax year

`1099 Filing Run` DocType as the year-end control record: per-vendor per-box totals, threshold application, drill-through to source vouchers, and a hard exception list before it can be marked ready

Correction runs that reference a prior filing, carry original vs corrected amounts, and flag each affected recipient for a corrected form

Fixed-width IRS FIRE / IRIS-compatible transmittal file generation, built to your confirmed filing route and validated against the layout in scope

Filing-service CSV export mapped to your provider's exact column layout (Track1099, Tax1099, Avalara or your CPA's template) — chosen during scoping, not assumed

Recipient copies as Frappe Print Formats rendered to PDF, with optional bulk email through the standard Frappe email queue and per-recipient delivery status on the filing run

Whitelisted REST API methods (`frappe.whitelist()`) for vendor 1099 status, year-to-date reportable totals and filing-run results, so a CPA portal or external automation can pull data without DB access

Scheduler event that runs a monthly reportable-spend check and flags vendors crossing threshold mid-year, plus a missing-W-9 chase list

Role profiles separating AP data entry from filing authority, with a full audit trail on every filing run submission and amendment

Multi-company and multi-EIN aware — filing runs are scoped per Company so a group files separately per legal entity

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your ERPNext.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

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 2 to 4 weeks 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.

What you get

Installable Frappe app source built for your exact Frappe/ERPNext version (v15 or v16), delivered as a versioned release

Installation on your bench and full configuration: box catalogue, thresholds, role profiles, permlevel permissions and vendor-profile defaults

Technical documentation — DocType reference, `hooks.py` doc events, scheduler jobs, whitelisted API methods and export file layouts

End-user guide covering the year-end run, exception clearing, corrections and recipient-copy distribution, plus a live training session for your AP and finance team

UAT on a staging bench using your own anonymized supplier and payment data, with a written test script and a documented production rollback plan

Data migration assistance: back-populating vendor profiles and tagging historical bills for the current tax year where records permit

Post-go-live support window for defect fixes and configuration adjustments, agreed in the quotation

Git repository handover — you own the source, with commit history, branch strategy and upgrade notes

Who this is for

Controller at a US services company paying 40-300 contractors

Owns the January deadline and the penalty exposure. Needs per-vendor NEC totals that reconcile to the general ledger without a spreadsheet rebuild, and wants missing W-9s surfaced in June rather than on the 28th of January.

Accounts payable manager

Enters the bills and chases the vendors. Needs the 1099 box to default itself on supplier selection, needs the system to stop a submission when a reportable vendor has no TIN, and needs a working missing-W-9 chase list instead of an inbox search.

Outsourced CPA or bookkeeping firm serving ERPNext clients

Files on behalf of several entities. Needs a clean per-company export in the exact layout their filing platform accepts, a REST endpoint to pull totals without a bench login, and correction runs that do not require rebuilding the original year.

ERPNext systems owner or IT lead

Has to live with the app after go-live. Wants a proper Frappe app on a git repo they own, version-pinned to their bench, upgradeable to v16, with documented hooks and no undocumented core patches.

How USA 1099 & E-File Pack Compares

Criterion	ECOSIRE	Custom Build	Competitor	ERPNext Native
W-9 and TIN capture	Dedicated `1099 Vendor Profile` DocType with TIN type, classification, format validation and the signed W-9 attached	Whatever your developer specifies; validation rules usually get cut when the deadline nears	Often a handful of custom fields on Supplier with no validation or attachment workflow	A single free-text `tax_id` field on Supplier; no W-9 record, no classification, no validation
Box mapping on transactions	Box selectable per Purchase Invoice line and Payment Entry, defaulted from the vendor profile, enforced at validate	Feasible, but the doc-event enforcement is the part that typically gets skipped	Usually one box per supplier, so mixed NEC/MISC vendors need manual splitting	No 1099 box concept exists anywhere in the transaction flow
Cash-basis year attribution	Payment and Journal allocations walked back to settled bills, so December-billed/January-paid lands in the right year	Commonly built on invoice date, which quietly misstates both years	Varies; often invoice-date based with no allocation walk	Supplier ledger reports are accrual-oriented and require manual reconstruction
Threshold and exemption handling	Per-box thresholds and entity-classification exemptions maintained as data on the `1099 Box` DocType	Usually hardcoded at $600, which breaks the year a threshold or box changes	Fixed thresholds in code; changes need a new app release	Not applicable — no reporting logic in core
E-file output	IRS FIRE/IRIS-compatible fixed-width file plus a CSV mapped to your specific filing provider's layout	One layout, built for whichever provider you used at build time	Typically a generic CSV that still needs reformatting for your provider	Export the report to spreadsheet and rebuild the file by hand
Corrections	Correction runs referencing the original filing, with original vs corrected amounts and per-recipient flags	Rarely scoped in round one; usually a phase-two request in February	Frequently absent — corrections handled outside the system	Manual, entirely outside ERPNext
Access control over TIN data	Permlevel-restricted TIN fields, a separate filing-manager role, audit trail on every run	Depends on the developer; permlevels are easy to overlook	Usually standard read permissions — full TINs visible to anyone in AP	`tax_id` visible to any user with Supplier read access
Ownership and ongoing cost	Git repository handed to you; no runtime licence key; optional support agreement	You own it, but you also own the whole cost of discovery and rebuild	Annual subscription per site, and you cannot change the code	Free, but the annual cost is your controller's January

Frequently Asked Questions about USA 1099 & E-File Pack

How long does delivery take, and is this something I can download today?

No — this is build-to-order, not an existing Frappe Cloud Marketplace listing. We start with a scoping call, confirm your filing route, box usage and ERPNext version, and issue a fixed written scope and quotation. Typical delivery is 2 to 4 weeks from confirmed scope, including staging UAT before production migration. If you are approaching a January filing deadline, tell us at the scoping call so we can plan the window honestly rather than promise it.

Does this file the forms with the IRS for me?

The app produces e-file-ready output — an IRS FIRE/IRIS-compatible transmittal file and/or a CSV in your filing service's exact column layout — plus recipient copies as PDFs. The actual transmission is done by you or your filing provider using your own IRS TCC or provider account. We build to the file layout you confirm during scoping; we do not act as your transmitter or tax advisor.

Which Frappe and ERPNext versions are supported?

We build against Frappe/ERPNext v15 or v16, targeting the exact version running on your bench. The app is a standard Frappe app with its own module, DocTypes and `hooks.py` doc events — no patched core files — so it upgrades cleanly. If you are on v15 and plan to move to v16, say so at scoping and we will structure the code and fixtures for that path.

What happens to support and updates after go-live?

Every engagement includes a post-go-live support window, agreed in the quotation, covering defect fixes and configuration adjustments. After that, ongoing support and annual maintenance — IRS layout or threshold changes, a new box, an ERPNext version upgrade — is available as a separate agreement. Because you receive the git repository, your own team or another developer can also maintain it; there is no runtime licence key holding your filing hostage.

We already have thousands of historical bills with no 1099 tagging. Can they be backfilled?

Yes, within limits. We include data migration assistance to back-populate vendor profiles and tag historical bills for the current tax year, driven by supplier, expense account and item rules we agree during scoping. Where the source records genuinely do not distinguish reportable from non-reportable spend, the app surfaces those vendors on the exception list for a human decision rather than guessing.

How is sensitive TIN data protected?

TIN and TIN-type fields sit on the `1099 Vendor Profile` DocType at a restricted permlevel, so only holders of the filing-manager role see the full number — AP clerks maintaining bills do not. Filing runs carry a full audit trail on submission and amendment, and the export files are generated as Frappe File records under the same permission model rather than dropped on a shared disk path.

Can we handle corrections and multiple legal entities?

Both are first-class. A filing run is scoped per Company, so a group with several EINs files separately per entity. A correction run references the prior filing, carries original and corrected amounts side by side, and flags exactly which recipients need a corrected form and a re-issued copy.