Imports

Overview

The Imports feature allows institutions to create accounts and post transactions in bulk using CSV files.

This guide explains how import files are processed, validated, and committed.

Import processing model

All imports follow the same processing model:

1. A CSV file is uploaded to the import endpoint.
2. The file is parsed and validated.
3. If validation fails, no records are created or posted.
4. If validation succeeds, all records are processed in a single operation.

This all-or-nothing behavior prevents partial imports and keeps data consistent.

Account imports

Account imports create multiple GL accounts in a single request.

CSV structure

• A header row is required.
• Column order does not matter.
• Unknown columns are ignored.
• Each row represents one account.

Required fields

• Account Number
• Account Title
• Account Type

Optional fields

• Account Status
• Currency Type

Account import validation

Account imports are validated before any accounts are created.

Common validation checks include:

• Required fields are present
• Account numbers are unique within the institution
• Account types and statuses are valid
• Currency types are supported

If any row fails validation, the entire import fails and no accounts are created.

Transaction imports

Transaction imports allow bulk posting of transactions using a CSV file.

Each row represents a single transaction. Transactions may be grouped into transaction sets during processing.

Required fields

• Account Number
• Debit Credit
• Amount

Optional fields

• Effective Date
• Description
• Branch Id
• Entry Type
• Transaction Set Id
• Transaction Id
• Cost Center

Transaction grouping

• Transactions with the same Transaction Set Id are grouped together
• Transactions without a Transaction Set Id are grouped into a single set
• Each transaction must have a unique Transaction Id within its set

Each transaction set is validated and posted independently.

Transaction validation

Transactions are validated in multiple stages:

1. Account existence and postability
2. Transaction-level validation (amounts, debit/credit)
3. Transaction set validation (balancing, size limits)
4. Effective date and posting window validation

If validation fails at any stage, the affected transaction set is rejected.

Error handling

When an import fails:

• No partial data is committed for the affected operation
• The response includes details describing the validation errors
• Clients can correct the file and safely retry the request

Import operations are safe to retry once errors are resolved.