# Edge cases

Source: https://developer.avalara.com/transaction-reconciliation/ljc5722798799060/

# Edge cases

This section describes operational considerations and edge cases that may occur during reconciliation workflows and how they’re handled.

## Real-time data requirements

The `ExportDocumentLine` Report API is the default for bulk reconciliation, but has an approximate 30-minute data delay. Use the Transactions API directly when:

-   Reconciling transactions created in the last 30 minutes

-   Investigating a specific discrepancy flagged by a user right now

-   Verifying a just-completed fix before closing a case

For real-time queries exceeding 10,000 transactions, paginate with `$top` and `$skip` parameters.

## Multicompany scenarios

When reconciling across companies in a reporting entity:

-   Query each company separately

-   Aggregate results at reporting entity level

-   Track discrepancies by company for resolution

-   Detect intercompany transactions (same amount, same date, related entities)

-   Flag potential duplicate reporting across entities

## Locked transactions

Transactions locked for filing can’t be modified (Error 1100).

-   Alert the user that the transaction is locked

-   Explain the transaction is already included in a filed or approved return

-   Suggest alternatives: amended return, adjusting entry in next period

Note

If hitting API rate limits (Error 1715, 1716):

-   Implement exponential backoff

-   Queue requests over time

-   Notify user of delay for large reconciliations

## Partial failures in batch operations

When processing multiple transactions:

-   Track success and failure individually

-   Continue processing remaining items on individual failure

-   Report summary: "15 of 18 transactions processed successfully"

-   Provide details on failed items with specific error messages