# Edge cases

Source: https://developer.avalara.com/ai-onboarding/uoq2129440683444/

# Edge cases

This section describes edge cases and operational considerations that may occur during onboarding and post onboarding workflows and how the system handles them safely.

## Existing AvaTax configuration

This subsection describes how onboarding behaves when preexisting AvaTax companies or nexus declarations are detected.

When an existing configuration is found:

-   Existing AvaTax companies and nexus are shown as **existing** in the preflight summary.

-   Existing AvaTax companies can be mapped to ERP entities. Mapping is ERP-side configuration only.

-   A nexus health check is performed by comparing proposed nexus against existing declarations.

-   The system offers to add missing nexus declarations but never deletes or modifies existing nexus without an explicit user request.

## Idempotency and resume behavior

This subsection describes how onboarding supports safe re runs and recovery from interruptions.

-   Each onboarding step checks for existing data before creating new records and doesn’t duplicate configuration.

-   If a user exits mid process, completed steps persist and the user can resume onboarding from the last completed step.

-   Onboarding never performs destructive actions or deletes data without explicit user confirmation.

## Large dataset handling

This subsection describes how onboarding scales when working with large ERP datasets.

Dataset

Threshold

Approach

**Items**

10,000 or more

Pagination, progress indicators, and batch classification workflows

**Customers**

50,000 or more

Paginated synchronization with prioritization based on certificate status

**Locations**

100 or more

Batch address validation and aggregated nexus recommendations

## Multi company scenarios

This subsection describes how onboarding handles environments with multiple companies or entities.

-   Onboarding supports both single-company and multi company strategies.

-   Each ERP entity is mapped to a single AvaTax company.

-   Intercompany transactions are detected and flagged for user review.

-   Shared customers across companies are handled through ECMS customer linking.

## UI and performance considerations

This subsection describes UI behavior and performance safeguards during onboarding and monitoring.

-   **AI panel**: The AI assistant is delivered by the connector application and appears as a persistent panel or drawer where supported by the ERP.

-   **Progress indicators**: Bulk operations, such as item classification and customer synchronization, display real-time progress indicators.

-   **Background processing**: Long-running operations are queued and processed in the background with status updates provided to the user.

**Rate limiting**

For large catalogs, batch API calls are used to avoid rate limiting errors (1715 and 1716). The system applies exponential backoff and queues requests over time to ensure reliable execution.