Please note, these steps are for the v.25 version and above of Sage 50. If you have any intra-account transfers on the statements to import, please see here for handling these transactions before importing.
Download your extracted bank statement data from AutoEntry in the Sage 50 format. Sage 50 requires the account number from Sage, the nominal account and tax code entered before uploading to Sage. These details cannot be added by AutoEntry and so must be added before importing.
Open the .csv file that you downloaded from AutoEntry.
Enter the correct bank account code for the account you're looking to import to in the Account Reference field (column B). This is the Sage 50 nominal code, not the actual bank account number. AutoEntry defaults to 1200 in the .csv
Enter the appropriate Nominal Account Codes (the code number) in column C for Nominal Account. Note that for any transaction that is a transfer to a second bank account in the same Sage 50 company, then instead of adding this second bank account's code here (e.g. 1210), enter a suspense account code (e.g. 9998) - this balance will then be "contra'd off" when the equal-and-opposite entry is posted into the second bank account.
Enter the appropriate Tax Codes (T1/T2 etc) in column for Tax Code (column I).
Save the file as a regular .csv
Close the file.
In Sage 50
Click 'File' and select 'Import'. The data import pop-up opens, there are 5 steps to
complete the import. If a backup is required it can be done here also.
Select the first option - 'Audit Trail Transactions' and click Next.
Leave the selection on 'CSV' and browse your PC for the saved file of transactions.
Ensure to check the box that the first row contains headings and click Next.
All the fields are pre-mapped for Sage 50 so simply click Next.
On the final screen, simply click Import.
Sage can take a minute or two to import the file depending on file size, your computer's processing speed etc. An 'Import Results' window will then show the successful import once the process is complete.
If there are any errors, these would need to be corrected in the .csv file by you, and then imported again.
AutoEntry's Sage 50 export file from bank statements uses the template of Sage 50 UK's "Audit Trail Transactions" import file - this Sage 50 import file explicitly does not support importing SR or PP transactions. Sage 50's guidance is to import these as SA or PA transactions instead, and then allocate them manually. Further instructions can be found here.
Apr 28, 2022, 12:00 PM