Bulk Transaction Processing

When you need to process more than a handful of transactions, individual posting is slow and inefficient. The bulk transaction import system processes hundreds of records in a single operation, with intelligent caching, duplicate detection, and per-record error isolation that makes large-scale data entry reliable and fast.

When to Use Bulk Import

Bulk import is the right choice whenever you have four or more transactions to process. Common scenarios include uploading a CSV file of monthly vendor invoices, importing historical transactions during system migration, processing a batch of journal entries for period-end adjustments, or entering a set of recurring transactions from a template.

The system accepts mixed transaction types in a single batch. You can include AP invoices, AR invoices, journal entries, and payments in the same import, and each record is routed to its correct executor automatically.

Performance and Efficiency

The bulk import system is significantly faster than processing records individually. It pre-caches all reference data (vendors, customers, accounts, tax codes, dimensions) at the start of the import, then resolves each record against the cache. This means your 200-record import does one vendor lookup instead of 200. The performance difference becomes dramatic as batch sizes grow.

For large imports (over 50 records), the system processes asynchronously. You submit the batch and receive an import ID, then check progress at any time. The system reports how many records have been processed, how many succeeded, how many were skipped as duplicates, and how many encountered errors.

Flexible Entity Resolution

You do not need to look up internal IDs before importing. The system resolves vendors, customers, and accounts by name, tax ID, external ID, or internal ID -- whichever you provide. If your CSV has vendor names, the system matches them to existing vendor records. If you are migrating from QuickBooks or Xero and have external IDs, those work too.

Error Handling

Per-record error isolation means one bad record does not block the rest of your import. If record 47 has an invalid account number, records 1 through 46 and 48 through 200 still process successfully. The system collects all errors and presents them at the end, so you can fix the issues and re-import only the failed records.

Duplicate detection uses transaction type plus reference number to prevent double-posting. If you accidentally import the same file twice, duplicates are skipped automatically rather than creating double entries in your ledger.

Validation Mode

Before committing a large import, you can run it in validate-only mode. This performs all the same checks -- field validation, reference resolution, balance verification -- without actually creating any transactions. You can review the validation results, fix any issues in your source data, and then run the import for real with confidence.