Importing Account Transactions (Journal Entries)

Account Transactions is a Tier 2 (First Week) data type. This import allows you to bring general journal entries into AccuArk from a CSV file. Each row represents one side of a double-entry transaction, specifying the debit account, credit account, and amount. Use this feature to migrate historical journal entries from a previous accounting system or to batch-load adjusting entries.

Before You Begin

• Import your Chart of Accounts first. Every account code referenced as a debit or credit account must already exist in AccuArk.
• Prepare a CSV file with your journal entry data. Each row should include the transaction date, description, the debit account code, the credit account code, and the amount.
• If you have multi-line journal entries (entries that affect more than two accounts), assign the same Reference value to all rows that belong to the same entry.

Step-by-Step Import

1. Open the Data Exchange Center from the Business menu
2. Click Import on the Account Transactions card
3. Select the Location from the dropdown if your business operates multiple locations
4. Select the Default Debit Account and Default Credit Account from the dropdown selectors. These are used as fallback accounts if a row does not specify its own debit or credit account.
5. Click Browse and select your CSV file
6. Click Next to map columns
7. Ensure the following required fields are mapped:
   • Transaction Date (required)
   • Description (required)
   • Debit Account Code (required)
   • Credit Account Code (required)
   • Amount (required)
8. Map optional fields: Reference, Payee Name, and Notes
9. Click Next to validate
10. Review validation results and click Import

Available Fields

How Double-Entry Records Are Created

For each row in your CSV, AccuArk creates a double-entry accounting record by debiting the Debit Account Code and crediting the Credit Account Code for the specified Amount.

For simple two-account entries, each row in the CSV becomes one complete journal entry.

Reference-Based Grouping

If you have complex journal entries that involve more than two accounts, use the Reference field to group rows together. All rows that share the same reference value are treated as parts of a single journal entry.

Within each group, the total debits must equal the total credits. If the totals within a reference group do not balance, the validation step will report an error for that group.

For example, to record a payroll entry that debits Salary Expense and Payroll Tax Expense while crediting Cash:

Both rows share the reference "PAY-001" and are grouped into a single journal entry.

Important Warning: Duplicates

Account transaction imports always create new records. There is no duplicate detection or upsert behavior. If you import the same file twice, every journal entry will be recorded a second time.

To avoid duplicates:

• Keep a log of which files you have already imported
• Use distinct reference numbers so you can identify and remove duplicates if needed
• Consider importing in date-range batches to maintain clarity

Tips

• Use references for multi-line entries — The reference field is the key to importing complex journal entries. Assign the same reference to all rows that belong together.
• Verify balancing — For grouped entries, confirm that the sum of amounts for debit rows equals the sum for credit rows within each reference group before importing
• Start with a small batch — If you are importing a large number of journal entries, test with a small sample file first to verify your column mapping and account codes are correct
• Review after importing — After the import completes, spot-check a few entries in AccuArk to confirm they were recorded correctly