Skip to main content
Version: 1.7.0

Post

This method can be used to transmit payouts from the payer to each recipient. This API can be used as many times as needed within a tax year. TaxBandits will keep track of all transactions involving payouts from payers to beneficiaries. You can utilize our 1099 endpoints to generate and file Form 1099 for the recipients who are eligible to receive it at the conclusion of the tax year.

Here’s how Form 1099Transactions endpoint may be used:

  1. Call the Auth method to get the access token. This access token must be supplied in the request header as the ‘Bearer‘ token. Refer OAuth authentication API for more information on JWT authentication and how to integrate with the subsequent requests.
  2. The second step is to call the Form1099Transactions Post method [POST Form1099Transactions] with the following values.
  • Business - Specify the payer from whom the Transactions were made. 

Any one of the following unique identifiers of the business (Payer) is mandatory.

  • Payer Reference - This identifier is specified by the client while using the endpoint Business/RequestByUrl.

  • BusinessId - This ID is generated by Taxbandits and returned in the response of Business/Create and Business/RequestByUrl endpoints. Refer to the Business endpoint to learn more about creating a Business in TaxBandits and retrieving the Business Id.

  • TIN - Use Business TIN as an alternate identifier if you have not saved the Payer Reference or BusinessId.

  • Recipients - Specify the recipients to whom the Transactions were made. Any one of the following unique identifiers of the recipient is mandatory.

    • PayeeRef - This identifier is specified by the client while using the endpoint FormW9/RequestByUrl. Refer Form W-9 endpoint to know more about Form W-9 in TaxBandits API.
    • RecipientId - This ID is generated by Taxbandits and returned in the webhook responses of Form W-9 and TIN Matching endpoints. The RecipientId is also returned in the 1099 (MISC, NEC) create response.
    • TIN - Use Business TIN as an alternate identifier if you have not saved the PayeeRef or RecipientId.

  • Transactions (Txns) - Transactions made by the payer to recipient.

    • SequenceID - It is the unique identifier for each transactions.
    • TxnDate - Date in which the transaction is made. This should be given in EST.
    • TxnAmt - Transaction amount in dollars. Enter the full compensation(Including the withholding amount) that has to be paid to the recipient/affiliate.
    • WHAmt - Amount withheld from the compensation paid to the recipient/affiliate.

Key Factors:

  • A single submission can include transactions from numerous payers to multiple recipients.
  • Transactions that have already been posted cannot be changed. Instead, use the Delete endpoint to remove an old submission and replace it with a new one.
POST Form1099Transactions
Run in Postman

Request Body

FieldTypeDescription
TxnDataobject[]This Object contains the Payer, Recipient and Transaction details.
    BusinessobjectPayer Information. Either PayerRef, BusinessId or TIN is mandatory.
        PayerRefStringUnique identifier of the payer. Set by the client in the endpoint Business/RequestByUrl.
        BusinessIdGuidTaxBandits Unique Business Identifier. This ID is generated by TaxBandits after you create a business in your account using the Business endpoint.
        TINTypeStringTIN Type of the business.
Allowed values: "SSN", "EIN"
        TINStringTaxpayer Identification Number. Use this as an alternative for BusinessId or PayerRef.
Size Range: 9-11
    Recipientsobject[]Recipient Information. Either PayeeRef, RecipientId or TIN is mandatory.
        PayeeRefStringUnique identifier of the recipient. Set by the client.
        RecipientIdGuidUnique identifier of the recipient.
        TINTypeStringTIN Type of the recipient.
Allowed values: "SSN", "EIN"
        TINStringTaxpayer Identification Number. Use this as an alternative for RecipientId or PayeeRef.
Size Range: 9-11
        Txnsobject[]Collection of Transactions.
    SequenceIDStringOptional The SequenceId will act as a unique identifier for the transaction. TaxBandits will throw an error when there is an API request with a SequenceId that was previously sent. The SequenceId is an optional node.
It can be used to eliminate any chance of duplicate transaction submission.
Size Range: ..50
        TxnDateStringDate of transaction. In the format mm/dd/yyyy or mm-dd-yyyy.
        TxnAmtStringTransaction Amount.
        WHAmtStringOptional Amount withheld.

Request JSON

Post Transaction with BusinessId and RecipientId, with no errors.

{
  "TxnData": [
    {
      "Business": {
        "PayerRef": "Be8523",
        "BusinessId": "50e6e084-6c22-47a4-8a4e-018fd34eab42",
        "TINType": null,
        "TIN": null
      },
      "Recipients": [
        {
          "PayeeRef": "Pe123",
          "RecipientId": "43931da4-ccec-4054-81b5-7ca7249f3891",
          "TINType": null,
          "TIN": null,
          "Txns": [
            {
              "SequenceId": "1",
              "TxnDate": "09/04/2020",
              "TxnAmt": "178.25",
              "WHAmt": "49.92"
            },
            {
              "SequenceId": "2",
              "TxnDate": "08/03/2020",
              "TxnAmt": "108.26",
              "WHAmt": "28.91"
            },
            {
              "SequenceId": "3",
              "TxnDate": "02/03/2020",
              "TxnAmt": "138.26",
              "WHAmt": "35.44"
            }
          ]
        }
      ]
    }
  ]
}

Response Body

FieldTypeDescription
SubmissionIdGuidUnique identifier of a submission.
StatusMsgStringStatus Message.
StatusTsStringTime Stamp of the status.
ErrorsobjectShows error information. This object will list the errors in the request parameters.

Response JSON

The transaction is successfully saved against the specified BusinessId and RecipientId, as there are no errors in the submitted data.

{
  "SubmissionId": "7f54c788-5673-4cc2-afc2-d5933b54bc37",
  "StatusMsg": "Transactions saved successfully",
  "StatusTs": "2021-09-16 07:13:51 -04:00",
  "Errors": null
}