Avalara 1099 & W-9

Version avalara1099
Companies W9
Forms 1099
Forms W9
Issuers 1099
Jobs

JobResponse

Response model for job operations

This model is used in the following APIs:

Parameters
idOptional
string

Unique identifier for the job

typeOptional
string

Job type identifier. Will always be "update_job" for bulk upsert operations

statusOptional
string

Current status of the job (e.g., Success, Failed, InProgress)

Enum: InProgress, Success, Failed
errorMessageOptional
string

Error message if the job failed, null otherwise

totalProcessedOptional
integer

Total number of forms processed. Value can be 0 or another value based on what the job has available

totalRowsOptional
integer

Total number of forms in the request. Value can be 0 or another value based on what the job has available

updatedValidOptional
integer

Number of forms updated and valid for e-filing and e-delivery. Value can be 0 or another value based on what the job has available

updatedNoEmailOptional
integer

Number of forms updated and valid for e-filing but missing email or email is undeliverable. Value can be 0 or another value based on what the job has available

updatedInvalidOptional
integer

Number of forms updated but invalid for e-filing. Value can be 0 or another value based on what the job has available

skippedDuplicateOptional
integer

Number of forms skipped because they would have updated a record already updated once in the request. Value can be 0 or another value based on what the job has available

skippedInvalidOptional
integer

Number of forms skipped because they would have made a form invalid and the form is already e-filed or scheduled for e-filing, or because you do not have permission to update forms that have been scheduled. Value can be 0 or another value based on what the job has available

skippedMultipleMatchesOptional
integer

Number of forms skipped because they matched multiple forms. Value can be 0 or another value based on what the job has available

notFoundOptional
integer

Number of forms skipped because no matching form or issuer could be found. Value can be 0 or another value based on what the job has available

createdInvalidOptional
integer

Number of new forms created because no matching form could be found (and upsert was true) - with errors. Value can be 0 or another value based on what the job has available

createdNoEmailOptional
integer

Number of new forms created because no matching form could be found (and upsert was true) - valid for e-filing but missing email or email is undeliverable. Value can be 0 or another value based on what the job has available

createdValidOptional
integer

Number of new forms created because no matching form could be found (and upsert was true) - valid for e-filing and e-delivery. Value can be 0 or another value based on what the job has available

dryRunOptional
boolean

Dry run. If true, this job only simulates the changes but doesn't actually persist them.

upsertOptional
boolean

Upsert. If true, this job will first attempt to update existing records if matches can be found. Matches are done in the following order: Form ID, Form Reference ID and tax year, Form TIN and tax year.

linkOptional
string

Link to access the job details

processedFormsOptional
array

List of processed forms returned when bulk-upsert processes ≤1000 records. Same format as GET /1099/forms response. Only available in bulk-upsert endpoint responses.