> For the complete documentation index, see [llms.txt](https://apis.rightrev.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apis.rightrev.com/rightrev-rest-api/platform/error-transactions/retrieve-error-transactions.md).

# Retrieve Error Transactions

Method - POST

API End Point

```
/apis/errortransactions/v1/
```

**Payload** 

```
  { "transaction_type": "order", 
    "error_warning_type": "remediable",
    "error_warning_code": "ERR-00015", 
    "error_request_id": "95847f5d-44d9-4da4-bc29-cb6f886704e2", 
    "financial_id": "SO_OFID_SNOW_1310_AE_87", 
    "error_from_date": "2025-07-31", 
    "error_to_date": "2025-12-06"
    "legal_entity" : "LE_18"
    }
```

* NOTE: The API for fetching Remediable and Discarded Error Transactions supports multiple request parameters. All fields provided in the request payload function as filters to narrow down the error records returned in the response.\
  This design allows customers to retrieve only the relevant error transactions based on their operational or audit needs, without requiring all fields to be mandatorily populated.

**Screenshot for reference**

<div data-with-frame="true"><figure><img src="/files/a6lmJbAWHhk9syBcdmX8" alt=""><figcaption></figcaption></figure></div>

Response

```
[
    {
        "compliance_id": "8147084f-9246-49ac-ba3b-771e190e0d7e",
        "compliance_name": "error_transactions",
        "compliance_spec": [
            {
                "bg_run_id": "pi-snow-kri##123366a5-832e-49b3-b8a5-8b89aeec1455",
                "document_details": {
                    "BUNDLE_CONFIG_KEY": "",
                    "Cost_Amount": "",
                    "Deferred_Cost_Account": "",
                    "Recognized_Cost_Account": "",
                    "amendment_reason": "New",
                    "billing_revenue_accrual": false,
                    "carves_eligible": true,
                    "carves_liability_segment": "1111",
                    "carves_revenue_segment": "2222",
                    "contract_liability_segment": "1111",
                    "contract_revenue_segment": "2222",
                    "customer_id": "No Revenue Rule",
                    "customer_name": "KJ_SNOW_1310",
                    "discount_amount": "",
                    "discount_percent": "",
                    "functional_currency": "USD",
                    "functional_exchange_rate": "1",
                    "global_currency": "USD",
                    "global_exchange_rate": "1",
                    "legal_entity": "LE_14",
                    "order_date": "01/01/2021",
                    "order_financial_id": "SO_OFID_SNOW_1310_AE_87",
                    "order_number": "SO_ON_SNOW_1310_AE_1",
                    "order_quantity": "1",
                    "parent_order_reference": "",
                    "po_number": "",
                    "product_id": "",
                    "product_name": "Product_Event_AA",
                    "revenue_end_date": "06/30/2021",
                    "revenue_start_date": "01/01/2021",
                    "source_system": "SFDC",
                    "ssp_date": "",
                    "total_list_price": "14500",
                    "total_sell_price": "11000",
                    "transaction_currency": "USD",
                    "transaction_type": "Order",
                    "unit_list_price": "",
                    "unit_sell_price": "",
                    "usage_bookings": false
                },
                "document_identifier": "SO_OFID_SNOW_1310_AE_87",
                "error_date": "2025-07-31",
                "error_id": "97446309-a14a-4769-bddd-88bb69954996",
                "error_warning_code": "ERR-00015",
                "error_warning_field": "REVENUE_RULE_GUID",
                "error_warning_message": "No valid Revenue Rule Policy available in the system",
                "error_warning_type": "remediable",
                "request_id": "95847f5d-44d9-4da4-bc29-cb6f886704e2",
                "suggestions": "Check and create appropriate revenue rule policy and try re-processing",
                "transaction_type": "ORDER"
            }
        ],
        "total_records": "1"
    }
]
```

**Payload fields description**

<table><thead><tr><th width="176">Field Name</th><th width="490">Description</th><th width="227">Example</th></tr></thead><tbody><tr><td>transaction_type</td><td>Indicates the type of transaction for which error records are requested.<br>Supported values are order, invoice, event, and mje.<br>This is a mandatory field.</td><td>order</td></tr><tr><td>error_warning_type</td><td>Specifies the category of the error. remediable – errors that can be corrected and reprocessed. discarded – errors that resulted in transaction rejection.<br>Supported values are remediable or discarded</td><td>remediable</td></tr><tr><td>error_warning_code</td><td>Unique code representing the specific error condition encountered during processing.</td><td>ERR_00015</td></tr><tr><td>error_request_id</td><td>Unique identifier assigned to the error occurrence for tracking and audit purposes.<br>This is the request ID of transaction file processed for collection</td><td>95847f5d-44d9-4da4-bc29-cb6f886704e2</td></tr><tr><td>financial_id</td><td>Unique identifier of the impacted transaction.<br>This can be an order financial ID or bill financial ID depending on the transaction type.</td><td>GL_Int_RR600.01.01</td></tr><tr><td>error_from_date</td><td>Start date of the date range for which error transactions should be fetched. Format: YYYY-MM-DD.</td><td>2025-01-05</td></tr><tr><td>error_to_date</td><td>End date of the date range for which error transactions should be fetched. Format: YYYY-MM-DD.</td><td>2025-02-05</td></tr><tr><td>legal_entity</td><td>Users can retrieve error transactions by applying a legal entity filter, which returns errors specific to the selected legal entity.</td><td>LE_01</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://apis.rightrev.com/rightrev-rest-api/platform/error-transactions/retrieve-error-transactions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.