About Bank transaction assistant file import

Use Bank transaction assistant file import to import bank and credit card transactions into Sage Intacct for reconciliation. Transactions automatically match against Intacct transactions using the rules in the account's rule set.

You can use either Bank transaction assistant file import experience or the classic import experience, but not both simultaneously. The classic method is going away in a future release, some time after May 2026.

Differences between classic import and Bank transaction assistant file import

Unlike the classic import experience, you do not need to import during reconciliation. Instead, import transactions from a centralized location on the Bank transaction import files list. Transactions remain in Intacct even after reconciliation and you can increase control of who imports transactions with permissions.

  Bank transaction assistant file import Classic import experience

Where to import bank transactions

From the Bank transaction import files list.

From the Reconciliation page.

Bank transactions remain in Intacct after reconciliation

Yes

No. Unless you drill down from the matched Sage Intacct transaction.

Limited to importing data for the current reconciliation

No, Because bank transactions are stored in Sage Intacct, you can import data from outside of the reconciliation period.

Yes

Can import credit card transactions

Yes

No

Support for CSV, XLS, XLSX, QIF, OFX, ASO, CAMT.053, BAI2 files

Yes

No. Only CSV and QIF.

Can combine with bank feed data

Yes

No

Import data for any date range

Yes

No

Supports most special characters

Yes

No

Support for multiple date formats

Yes

No, only MM/DD/YYYY

Format a file

How you format your file depends on the file type.

During the upload process, select Open file import guide for details and example templates. Or download an example import template.

File type Formatting Maximum file size Notes

CSV, XLS, XLSX

  • Make sure that the file contains the correct headers.

  • Include 1 of the header options from the example in each column. For example, column 1 can be Date or Posting date.

  • Keep transaction descriptions on 1 line.

  • Include a description and amount for each transaction.

  • Format dates:

    • using a dash (01-01-23)

    • using a slash (01/01/23)

    • using a period (01.01.23)

CSV: 9 MB

XLS: 9 MB

XLSX: 9 MB

Use the 3-column format if your transaction amounts are in a single column. For example, money out of your account is shown as -50 and money into your account as 50. If money coming in and going out of your account is in separate columns, use the 4-column format.

You can upload more detailed transaction information by including additional column headers.

XLS and XLSX files: Only the first tab in the file can be processed. To import data from other tabs, you can do the following:

  • Copy all the data into the first tab.

  • Upload each tab as a separate file.

  • Upload each tab individually by moving each tab to the first tab position before you start a new import.

QIF

None. File is ready for importing.

 

3 MB

 

OFX or ASO

None. File is ready for importing.

31 MB

You can only import transactions from 1 account at a time.

During the import process, select how dates are formatted. Open the file in a text editor and find a date linked to a transaction.

BAI2

None. File is ready for importing.

9 MB

BAI2 files can contain transactions for more than 1 account. If the file has transactions from more than 1 account, you can select the account you need before completing the import.

CAMT.053

None. File is ready for importing.

230 MB

CAMT.053 files can contain transactions for more than 1 account. If the file has transactions from more than 1 account, you can select the account you need before completing the import.

Field mapping

There are many fields that you can include when you import your file. However, some fields are not yet mapped to Intacct fields.

File column name Field in Intacct Notes Example Can be used in a Matching rule?

Date, Posting Date

Posting date

Required

 

Yes

Amount, Credit/debit

Amount

Required if you're using the 3 column template.

 

Yes

Money in, Credit, Credit amount, Deposit

Amount

Required if you're using the 4 column template.

 

Yes

Money out, Debit, Debit amount, Withdrawal

Amount

Required if you're using the 4 column template.

 

Yes

Description, Bank reference, Reference, Merchant/description, Transaction narrative, Details

Description

Required

 

Yes

Check number, Check, Check ref., Document Number

Document number

Recommended

12 character limit

For example, 650240

Yes

Reference, Reference number, Transaction reference, Transaction ref

Bank reference number

Recommended

For example, Buying a pair of shoes

No

Payee name, Payee, Payee description, Appears on your statement as, Customer reference, Customer, Cust ref

Payee

Optional

For example, Jane Doe

No

Address Line1, Address, Street, House/street

Payee address

Not used

 

No

City, Town/city, Town

Payee city

Not used

 

No

State, Region, Province

Payee state

Not used

 

No

Postcode, Post code, Post-code, ZIP, ZIP code, ZIP-code

Payee postal code

Not used

For example, NE13 9AA

No

Country

Payee country

Not used

 

No

Phone number, Phone, Phone #

Payee phone number

Not used

For example, 07700 900 982

No

Payee bank ID, Payee BankID, Bank ID

Payee bank ID

Not used

For example, HSBC

No

Payee Account ID, Payee Account ID, AccountID, Payee account, Payee account number, Payee account ref

Payee account ID

Not used

For example, 12345678

No

Additional reference 1, Document type, Card member, Extended payee name, Type

Payee Address1

Not used

For example, Jane M Doe

No

Additional reference 2, Transaction type, Card #, Account #

Payee Address2

Not used

For example, HSBC

No