Imports and exports

The central Imports / Exports page is a job monitor. Import capture is started from a supported entity page or its import action; exports are created from the relevant list, report, schedule, statement, or document screen.

This area is separate from Financial Data Operations. Ordinary Imports create or update supported business and reference records. Financial Data Operations validates and posts Payment Batches or Transaction Journals. It is also separate from the planned migration overhaul.

Start an Import

1. Open the supported entity list and select its Import action.
2. Download the current template rather than reusing an older file.
3. Keep the worksheet names, column names, and expected value formats.
4. Upload the completed file and review its field mapping or preview when the entity provides one.
5. Correct validation errors before submission.
6. Submit the staged job and complete maker-checker when the entity requires it.

Each import applies the same required fields, reference checks, duplicate rules, permissions, and authorization model as the corresponding screen. Warnings identify rows that can proceed but need review. Errors identify rows that cannot be applied.

The System Data import flow currently supports Nations and Languages. Do not assume that its generic mapping interface makes every System Data entity importable.

Monitor Imports

Open Processing & Monitoring → Imports / Exports → Imports. With the applicable entity permission, filter by Company, entity, status, or search. Open a job to review total rows, successful and failed rows, validation errors, requester, and timestamps.

Submitted Import Jobs use maker-checker. The central detail exposes Approve, Reject, or Deny only when the user's authorization authority and separation rules allow that decision. The job then completes as Completed or Completed with Errors; row results remain available for reconciliation.

Use the row results to reconcile Source Row, normalized values, warning or error messages, and the created record reference. Correct the source data and start a new Import when the job is terminal.

Monitor Exports

Use Exports to find queued, running, completed, failed, revoked, or expired Export Jobs. A completed artifact can be downloaded while it remains available and the user still has access. Revoked or expired artifacts are not valid downloads.

The initiating screen's Export permission controls creation. The central job list is not a way to export an entity the user could not export at source.

An Export freezes the filters and selected fields sent by the source screen. The completed artifact is available only until its expiry time. Revocation invalidates the artifact before that time without deleting the Export Job's audit history.