Audit trail transactions data fields you can import

Summary

Which Audit trail transactions data fields you can import in Sage 50 Accounts.

Description

You can use the Import option to import data into your accounts, to create audit trail transactions.

Here you can check which data fields you can import and find out more about the format required for each field.

 TIP: There are reports in Sage 50 Accounts that you can use to export your existing data in the correct format for CSV files.

Audit Trail Transactions

This includes journal entry transactions.  

Field Type Size Left blank? Format Excel column Report to use
Transaction Type Text 2 No This must be BP, BR, CP, CR, VP, VR, JC, JD, SI, SC, SA, SP, PI, PC, PA and PR. A Transaction CSV
You can't import Sales Recipt (SR) or Purchase Payment (PP) transactions. Instead import (Sales Payment on Account (SA) and (Purchase Payment on Account (PA) transactions and manually allocate them once imported.
Account

(Customer, Supplier or Bank Account Reference)

 Text 8 Yes, but only for JC and JD transactions. The account reference must already exist in your accounts data. B Transaction CSV
Nominal Code Text 8 No The nominal code must already exist in your accounts data. C Transaction CSV
Department Integer 3 Yes Enter a number between 0 - 999 with no decimal places. D Transaction CSV
Date Date 10 Yes - Uses the current program date. This must be in the format DD/MM/YYYY. E Transaction CSV
Reference Text 30 Yes   F Transaction CSV
Details Text 60 Yes   G Transaction CSV
Net Decimal 11 No 8 digits + 2 decimal places. H Transaction CSV
T/C (Tax Code) Integer 3 Yes - Uses tax code T0. Enter a code between T0 and T99. I Transaction CSV
Tax Decimal 11 Yes, however, if left blank the transaction imports with a VAT value of 0.00. 8 digits + 2 decimal places. J Transaction CSV
Exchange Rate Decimal 11 No. Exchange rate 1 is used when importing Base currency transactions. 8 digits + 2 decimal places. K Transaction CSV (Extended)
Ex.Ref Text 30 Yes   L Transaction CSV (Extended)
User Name Text 32 Yes   M Transaction CSV (Extended)
Project Reference Text 12 Yes

Up to 12 characters with no spaces. The project must already exist within the accounts data.

 NOTE: For certain transactions (for example purchase invoice (PI) and bank payments (BP)), when you enter a Project Ref you must also enter a Cost Code.

 N Transaction CSV (Extended)
Cost Code Reference Text 8 Yes

Up to 8 characters. The cost code must already exist within the accounts data.

 NOTE: For certain transactions (for example purchase invoice (PI) and bank payments (BP)), when you enter a Code Code you must also enter a Project Ref.

 O Transaction CSV (Extended)
Country of VAT Text 2 Yes 2 letter code as defined in Settings > Countries P Transaction CSV (Extended)
Report Type Number 1 Yes

0= No report type

1= Union OSS

2= Non Union OSS

3= IOSS

 Q Transaction CSV (Extended)
Fund Text 60 Yes

The fund reference must already exist in your accounts data.

 R Transaction CSV (Extended)

As with non-foreign currency transactions, you can't import customer receipts (SR) and supplier payments (PP).

If you import foreign currency transactions, SI, SC, PI and PC. Use the foreign currency values and enter the base to foreign exchange rate for the transaction. 

Next steps

For further with importing journals, follow our import journals article.

Solution Properties

Solution ID
250321114601443
Last Modified Date
Fri Mar 21 13:03:51 UTC 2025
Attributes
Product Details
Modules: Bank feeds
Modules: Contact Management
Modules: Customers
Modules: Financials
Modules: Inventory Optimization
Modules: Project accounting
Modules: Suppliers
Views
0