Imports and Exports

Imports and exports in remoteEaze are controlled workflows, not one-click file actions. The platform tracks who requested work, what was processed, and the final result.

Exports

Exports are started from list screens through a shared export flow.

Users can choose:

• file format (CSV or XLSX)
• row scope (current page, filtered data set, or selected rows)
• column set and custom header labels

Export jobs and downloads

When an export is large or needs deferred processing, the system creates an export job.

Export jobs track:

• request details (format, scope, columns, filters)
• progress and status
• failure reason when applicable
• generated file reference

Downloads are provided through generated links with access control and expiry handling.

Imports

Imports run through a structured sequence:

1. Download the template for the target entity.
2. Prepare and upload the file (CSV or XLSX).
3. Preview parsed rows and suggested mapping.
4. Validate row-level results.
5. Commit directly or submit for approval, depending on entity rules.

Validation is row-aware, so teams can see which rows are valid, invalid, skipped, or committed.

Direct import vs review import

Some entities can be imported directly after validation. Others require a review workflow before commit.

Review workflow currently applies to:

• account conditions
• fee definitions
• commission types
• transaction codes

This split is intentional: higher-risk configuration data goes through approval.

Import jobs

Submitted imports are tracked as import jobs with clear processing counts and workflow status.

Teams can review:

• total and processed row counts
• valid and invalid counts
• commit outcomes
• approval progress and decision history

External ID imports

Third-party external ID imports are supported for:

• nations
• languages

These imports add context selection (for example destination system and company scope where relevant) before validation and commit.