Tax1099
Your posted vendor payments become 1099-NEC, MISC, INT, and DIV amounts, box by box. You review the run in DualEntry; Tax1099 transmits it to the IRS.
Overview
January starts with the same exercise every year. Someone pulls a year of vendor payments out of the ledger, drops them into a spreadsheet, decides which account belongs in which form box, hunts down the TINs that never made it onto the vendor record, and then retypes all of it into a filing portal. The numbers already exist in your books. The work is moving them.
This integration computes the 1099 data where the payments live. DualEntry sums posted vendor payments on a cash basis, so a payment counts toward the tax year in which it was paid rather than when the bill was dated. Each GL account carries a category_1099 tag, and that tag is what sorts the payment into a form box. Net-negative boxes are capped at zero, and DualEntry flags lines that fall below IRS thresholds so you can see them before you finalize. Five adjustment types let you exclude a vendor, force one in below threshold, replace a box amount, add or subtract a delta, or add a manual recipient that never came from the ledger.
Data submission runs one way and status comes back the other. DualEntry sends payer company details, eligible vendor data, and computed amounts to Tax1099; Tax1099 returns filing status updates, form PDFs, and validation errors. DualEntry is the source of truth for how amounts were computed, which adjustments were applied, and what the finalized figures are. Tax1099 is the source of truth for filing state, and DualEntry mirrors what Tax1099 reports rather than tracking its own.
Tax1099, from Zenwork, is an IRS-authorized e-file provider. DualEntry computes the 1099 data and Tax1099 transmits it to the IRS; DualEntry does not file directly with the IRS itself.
Payer company details, including TIN, legal name, and address
1099-eligible vendor records, including TIN and legal name
Computed 1099 amounts by form box
Adjustments and finalized amounts
TIN match results
Form submissions and resubmissions
Filing status updates, per form and per run
Form PDFs, summary PDFs, and validation errors
Data synced
The integration syncs the following data types:
- The filing company's TIN, legal name, and address are sent to Tax1099 through the register_payer operation before forms are submitted.
- Payer details must be populated in DualEntry as a setup step; the run cannot be submitted without them.
- Each run covers a single payer company, so multi-company payers are not supported in one run.
- You select the tax year and company at the start of the run, and both scope every amount computed within it.
- Vendor TIN and legal name are sent to Tax1099 as recipients through the register_recipients operation.
- A vendor is picked up only if it is active in DualEntry and marked 1099-eligible on the vendor record.
- Vendors without a TIN are excluded from computation entirely rather than submitted with a missing value.
- The recipient TIN and legal name on each form must match IRS records, or the IRS rejects the form during e-filing.
- Legal names should be confirmed against the vendor's W-9 documentation before the run is finalized.
- Computation sums posted vendor payments for the selected tax year and company on a cash basis, so a payment counts toward the year it was paid rather than the year the bill was dated.
- Each payment is sorted into a form box using the category_1099 tag on the GL account it posted through, for example NEC or NEC-Box 1.
- Net-negative boxes are capped at zero so no box carries a negative amount into the filing.
- DualEntry flags computed lines that fall below IRS thresholds, with a $600 default for 1099-NEC, for review before finalization.
- Accrual-basis computation is not supported.
- Five adjustment types are available at review: exclude vendor, include vendor, fixed amount, delta amount, and manual recipient.
- Exclude vendor drops a vendor from the filing while keeping the computed line for audit, and include vendor forces a vendor to file even though the amount is below the IRS threshold.
- Fixed amount replaces the computed amount for a box with a value you enter, and delta amount adds to or subtracts from the computed amount for a box.
- Manual recipient adds a recipient and amount that did not come from your ledger.
- DualEntry stores the computed lines, the adjustments applied, and the finalized amounts, and it is the finalized amounts that are sent to Tax1099.
- Submission runs as a sequence of operations against Tax1099: register the payer, register recipients, validate forms, import forms, and submit forms.
- Supported form types are 1099-NEC, 1099-MISC, 1099-INT, and 1099-DIV; W-2s and other information returns are excluded, as are non-US 1099 forms.
- Rejected forms can be resubmitted through the resubmit_rejected_forms operation after the underlying data is corrected.
- DualEntry computes the 1099 data and Tax1099 transmits it to the IRS; DualEntry does not file directly with the IRS itself.
- Recipient TIN and legal name are sent to Tax1099 for matching against IRS records through the verify_tins operation.
- You can run the TIN match before filing to catch recipient TIN and name mismatches ahead of a rejection.
- Match results come back into DualEntry so mismatched vendors can be corrected on the vendor record before the run is submitted.
- Correcting a TIN or legal name after an IRS rejection and resubmitting the form is the documented resolution path.
- Tax1099 reports form status asynchronously and DualEntry retrieves it through get_form_statuses, mirroring the reported state rather than tracking its own.
- Run status progresses through DRAFT, COMPUTING, COMPUTED, REVIEW, and then ACCEPTED, REJECTED, or PARTIAL.
- Form status covers PENDING_IMPORT, IMPORTED, PENDING_SUBMIT, PENDING, PROCESSING, ACCEPTED, REJECTED, BLOCKED, RESUBMIT, and RESUBMITTED.
- Official form PDFs and summary PDFs are retrieved from Tax1099 as filing copies for your records and for furnishing to recipients.
- Validation errors and rejection reasons come back per form, and blocked forms are resolved by clearing the flag in Tax1099 and resubmitting.
Key Features
- Amounts computed from your ledger
DualEntry sums posted vendor payments for the tax year and company you select. Computation is cash basis: a payment counts toward the year it was paid, not the year the bill was dated. - Box assignment from your chart of accounts
Each GL account carries acategory_1099value, such asNECorNEC-Box 1. Tag the account once and every payment through it lands in the right box on every run. - Adjustments that leave the ledger alone
Exclude a vendor, include one below threshold, set a fixed box amount, apply a delta, or add a manual recipient. Excluded vendors keep their computed line for audit. - TIN matching before you submit
Run a TIN match through Tax1099 to catch recipient TIN and name mismatches ahead of filing. Vendors without a TIN are excluded from computation rather than filed with a gap. - Threshold visibility at review
DualEntry flags lines below IRS thresholds, with a $600 default for 1099-NEC, and caps net-negative boxes at zero. You decide whether a flagged line gets an include adjustment. - Status mirrored per form and per run
Run status moves through DRAFT, COMPUTING, COMPUTED, REVIEW, and ACCEPTED, REJECTED, or PARTIAL. Form status arrives asynchronously from Tax1099 across states from PENDING_IMPORT through ACCEPTED, REJECTED, BLOCKED, and RESUBMITTED. - PDFs pulled back for your records
Official form PDFs and summary PDFs come back from Tax1099 as filing copies for your records and for furnishing to recipients. Validation errors and rejection reasons return per form. - Connected with your own Tax1099 credentials
Authentication uses an OAuth password grant against Tax1099's API. You generate a login, password, and app key in the Tax1099 portal under Settings then API, paste them into DualEntry once, and access tokens refresh automatically. DualEntry builds and maintains the connection directly against Tax1099's API, with no third-party connector platform in between.
FAQ
The connection itself is not. DualEntry builds and maintains it directly against Tax1099's API, and no third-party connector platform sits in between. You authenticate with your own Tax1099 credentials using an OAuth password grant.
The filing itself does involve Tax1099, which is an IRS-authorized e-file provider from Zenwork. DualEntry computes the 1099 data and Tax1099 transmits it to the IRS; DualEntry does not file directly with the IRS itself.
The 1099 amounts are computed from the posted vendor payments already sitting in your ledger, rather than exported and rebuilt in a spreadsheet. Each GL account carries a category_1099 tag, and that tag is what sorts payments into form boxes, so the mapping is set once in your chart of accounts and reused on every run.
From there you review the computed lines, apply adjustments where the ledger does not tell the whole story, and submit through Tax1099 without retyping figures into a separate portal.
Yes. Data submission runs one way out and status comes one way back. DualEntry sends payer details, eligible vendor data, and computed amounts to Tax1099, and Tax1099 returns filing status updates, form PDFs, and validation errors.
Status arrives asynchronously and is tracked per form and per run. Run status moves through DRAFT, COMPUTING, COMPUTED, REVIEW, and then ACCEPTED, REJECTED, or PARTIAL. DualEntry mirrors the state Tax1099 reports rather than maintaining its own.
Four federal form types are supported: 1099-NEC, 1099-MISC, 1099-INT, and 1099-DIV.
W-2s and other information returns are explicitly excluded, as are non-US 1099 forms. Each run also covers a single payer company, so multi-company payers are not supported within one run.
Computation is something you trigger. You select a tax year and company, generate the eligible vendor amounts, then review and finalize. There is no automatic recompute, so if payment data changes after the initial computation you need to trigger the recalculation yourself.
Status is the part that moves on its own: Tax1099 reports form and run status updates asynchronously, and DualEntry reflects them as they arrive.
Errors surface per form with a documented resolution path. Invalid credentials are fixed by re-copying the login, password, and app key from the Tax1099 portal. A missing vendor means correcting the vendor record and recomputing, and a wrong box assignment means tagging the GL account with the correct category_1099 value and recomputing. An amount below the IRS threshold can be brought in with an include adjustment.
If the IRS rejects a form, the recipient TIN and legal name are corrected and the form is resubmitted; running a TIN match through Tax1099 first catches those mismatches before they cause a rejection. Blocked forms are resolved by clearing the flag in Tax1099 and resubmitting.
.avif)