Import Transactions

Transactions are typically data related to time-stamped orders, invoices, sales process activities, or payments. Transactions can come from a variety of external systems. You can import transactions if your instance has transactions enabled.

Prerequisites

Permissions required: Import Capabilities

Understand and complete your

Reference: Transactions

Navigation

Navigate to Integration > Import Data
.

Import Transactions

Before you can import transactions, you need to create your

Reference: Transactions

. Your transaction field definitions determine what columns appear in your transactions template.

Transactions only import to child accounts, using the same mapping available for Actuals or Plan imports. You can't import linked accounts with

Show actuals if linked account has them

enabled because the General Ledger Account won't hold its own Actuals.

See

Reference: Transactions

for details.

Select Transactions
as the Import Type.

You can select

Import without Code and Name columns for display names

to import templates without columns for Code and Name fields. This option also allows importing from older templates created before the introduction of display names. When you turn on

Enable Single Column Data Import/Export for Display Name

General Setup

, we apply

Import without Code and Name columns for display names

across the application and hide the option in the Import page.

Click Download template
and follow its instructions to fill in the data you need to import.

Click Choose File
and browse to the template you edited and click Import
.

Click Continue
.

Transaction Example Import Template: The columns for a transaction import vary depending on your transaction field definitions.

The Transactions import template has columns for:
Posting Date (Required): A date field for the transaction posting date.
Transaction Type (Required): The transaction type.
Account (Required): The account code for the transaction. This column header can also use the label Account Code.
Level Code (Required): The level the transaction applies to.
Transaction Amount (Required): The amount for the transaction.
Description: A text field.
<Dimension> Code: A dimension code field. Enter the code of the dimension. Required when you enter a dimension on a row. Example: Product Code.
<Dimension> Name: A dimension name field. Enter the name of the dimension. Optional when you enter a dimension on a row so that you can use a name that's different from the code while the data import automatically creates the dimension values. Example: Product Name.

Deleting Transactions

You can delete transactions by navigating to the

Integration

Operations

Manage Transactions

page.

When you import, you can also choose to delete existing transactions as part of the import process:

If you select No, your import adds to the existing transactions.

If you select Yes, you can provide a date range and select which transactions to remove before the import begins.