Understanding E-Document Transaction Response
The Electronic Transaction Response feature enables you to create and send transaction responses with Acknowledged and Accepted response types when receiving the inbound e-document. To use this feature, you must do the following:
-
Check the Support Transaction Response box in the subsidiary preferences.
-
Assign the E-Document Transaction Response template to a specific subsidiary and transaction type. For more information, read Creating E-Document Transaction Response Template.
-
Assign the E-Document Transaction Response sending method to the required subsidiaries. For more information, see Creating E-Document Sending Methods.
Currently, the SuiteApp supports creation of transaction responses with Acknowledged and Accepted response types. The acknowledged transaction response will be created when the inbound record or e-document is in For Conversion status.
The accepted transaction response will be created when:
-
The invoice inbound record or e-document is converted successfully to a bill, and the bill is set to Approved status.
-
The credit memo inbound record or e-document is converted successfully to a bill credit.
-
The purchase order inbound record or e-document is converted successfully to a sales order, and the sales order is set to Pending Fulfilment status.
The acknowledged transaction response is shown on an inbound record whereas acknowledged and accepted transaction responses are shown on the successfully converted transaction. You can view the responses in the E-Document Transaction Response subtab under the E-Document subtab present in a converted transaction or inbound record.
Generation and Sending of transaction response content is currently supported for transaction response records with response type For Cancellation, For Rejection and Rejected. Users can use the Generate and Send button present on the transaction response records to use these features. For more information see, Generating Transaction Response Content, Sending Transaction Response Content for Avalara Users, Sending Transaction Response Content for Non-Avalara Users.
The transaction response record contains the following fields:
|
Field Name |
Description |
Subtab |
|---|---|---|
|
Reason for Cancellation or Reason for Rejection |
This field displays the reason for which the transaction linked to this transaction response is requested for cancellation/rejection or cancelled. Field names for response type: For Cancellation – Reason for Cancellation For Rejection, Rejected – Reason for Rejection |
- |
|
Error Code |
This field displays the error code when an error is encountered while generating or sending the transaction response content. |
Error Details |
|
Error Message |
This field displays the error message when an error is encountered while generating or sending the transaction response content. |
Error Details |
|
OBN Document ID |
This field stores the OBN Document ID for transaction response sent. (Applicable for Avalara Transactions) |
Network References |
|
Avalara Mandate |
This field displays the primary value that identifies a particular e-invoicing mandate. This is same as the code used by Avalara to represent a particular country-mandate. (Applicable for Avalara Transactions) |
Network References |
|
Avalara Document ID |
This field contains the value of the Avalara Doc ID returned through the Document Status record. (Applicable for Avalara Transactions) |
Network References |
|
Transaction Response Content |
This field allows you to preview and download the generated transaction response content. |
- |
|
Response Type |
This field displays the type of the transaction response. For list of response types, see Response Type Field Values |
- |
|
Status |
This field displays the status of the transaction response. For list of statuses, see Status Field Values |
- |
|
Response Issue Date |
This field displays the date and time at which the transaction response is issued from the customer or vendor. |
- |
|
Transaction ID |
This field displays the transaction ID to which the response belongs to. |
- |
|
Direction |
This field indicates whether the response is received (inbound) or sent (outbound). It contains either of the two values: Inbound or Outbound. |
- |
|
Inbound E-Document |
This field contains a link to the inbound e-document to which the response belongs to. |
- |
|
Response Sent Date |
This field displays the date and time at which the transaction response is sent. |
- |
Response Type Field Values
The Response Type field may contain one of the following values:
-
Accepted
-
Acknowledged
-
Conditionally accepted
-
For Cancellation
-
For Rejection
-
In process
-
Paid
-
Rejected
-
Under query
Status Field Values
The Status field may contain one of the following values:
-
Ready for Generation
-
Generation Failed
-
Ready for Sending
-
Sending Failed
-
In Error
-
Processing
-
Cancelled
-
Request Completed
-
Sent
-
Not Sent