DIGITA ACCOUNTS PRODUCTION 5.0 KNOWN ISSUES AND ASSISTANCE DOCUMENT

Transcription

1 DIGITA ACCOUNTS PRODUCTION 5.0 KNOWN ISSUES AND ASSISTANCE DOCUMENT Version /04/2011

2 Contents DIGITA ACCOUNTS PRODUCTION VERSION Report Customisations... 3 Where accounts have not been started... 3 Conversion process from accounts started prior to Digita Accounts Production If importing the Trial balance... 6 If importing posting sheets... 8 Error in template when running a report Saving XBRL accounts for attaching to Corporation tax returns OTHER ISSUES Running new reports Speeding up your workflow Unable to render XML - Error when generating XBRL Report Rounding issues for users upgrading from versions prior to

3 DIGITA ACCOUNTS PRODUCTION VERSION 5.0 In order to produce accounts which are ixbrl compliant in Digita Accounts Production version 5.0, the accounts need to be produced using the ixbrl nominal code list. Report Customisations It will be necessary to make any customisations made to reports in prior version of Digita Accounts Production again as the XBRL report template is a completely new report. If accounts have only one transaction period which needs to be converted unfortunately it will be necessary to delete the current and re-enter details again. Where accounts have not been started On rolling forward the accounts to the new period, Accounts Production will, by default, produce an XBRL period for reporting. This will then prompt you to amend the Nominal code list to the XBRL Limited company Nominal code list. This can be done by the following procedure: 1. Select the Client>Change Nominal Code List menu. If changes have been made prior to this you will receive a dialogue box advising that changes have been made as seen in the screen shot below. These can be viewed in the working papers. Select OK. 2. The Mapping Selector dialogue opens. 3. Click the Add button on the bottom left hand side to create a mapping for the new codes, amend the default mapping name (this will need to be unique for each map selected), select the XBRL Limited Company nominal code list, as per the screen shot below, and press OK. 3

4 4. This will place the map in the mapping selector window; select the nominal code list and press OK. 5. In the next window, press Match code and description and select OK. 4

5 6. The Match Nominal codes dialogue box will appear. Select the third column, Dest Code, this will bring any codes unmapped to the top of the list. These codes will need to be mapped by selecting each one and typing in the source code in the map this selection to this nominal code box in the bottom left-hand corner. If the code does not exist, you will be prompted to create it as normal. 7. Once all the codes have been mapped then press OK and the nominal code list will be upgraded. 8. If changes have been made to the nominal code list, you will be asked if the nominal code list should be promoted to organisational level. If it is client specific, select No. Should you wish to use this map for other clients with the same code structure select Yes and a copy of the mapping can be made and renamed. 9. Once the nominal code list has been changed, only the XBRL accounts can be generated. Should a legacy report be selected in error, an error message will appear. 5

6 Conversion process from accounts started prior to Digita Accounts Production 5.0 If your accounts have been started in an earlier version of Digita Accounts Production and require filing in ixbrl it will be necessary to follow the conversion routine. 1. From the working papers, select the Trial balance or if you require the full transactions, select the posting sheets, then generate and export to excel. It will be necessary to ensure the excel document is now in the correct format to save as a.csv delimited file. The format is column A=code, B=description, C=debit and D=credit for a trial balance. Column C can be debit/credit mix using negative for credits if importing basic posting sheets. Please ensure there are no headings, totals or additional columns. Once complete, select save as and amend the save as type to.csv file, in a location you are able to find later. 2. Delete the period in the client. 3. Roll the year forward, ensuring you change the nominal code list as per steps 1-9 above. 4. You can now import the transactions created in step 1, using one of the following methods; If importing the Trial balance 1. On the Posting screen select Import CSV Balances and browse to where you have saved the.csv file. 6

7 2. The Transaction Filter dialog will appear which has been preset for the importing of the trail balance. Select OK. 3. Map Codes will appear with the red exclamation mark, select the Nominal codes. 4. The Match Nominal Codes screen will appear. The Destination Codes need to be mapped again (Do not press OK before finishing this operation as you may lose the work you have done). Click Save Map to use this map with another client. Select OK. 7

8 5. This will return you to the previous screen where you will be able to select OK and the import will appear. If importing posting sheets 1. On the posting screen, select Transaction import and the Import Configuration dialogue appears. 2. Select Create a new Import Configuration. 3. On the Transaction Import screen, un-tick source data has a header row (in the top left hand corner). 4. Select File to import. 8

9 5. Browse to where your file has been saved 6. Drag each column from Source data preview down to the Proposed import preview section. 9

10 7. Tick the Map imported account codes box and select edit mappings, The following screen will appear: 8. Select the first code on the left, this will enter the data in the Source code box. Add the Target code and select the Map button. 10

11 9. A green tick will appear next to the codes that have been mapped. All codes will need to be mapped before you can select OK. 10. Select OK and OK again. This will refresh the screens and a message will appear. You can now save the configuration file for use again. 11

12 Error in template when running a report This would suggest that you are running legacy reports in an ixbrl reporting period. Please select an ixbrl report. Saving XBRL accounts for attaching to Corporation tax returns 1. With the accounts on screen, they can then be saved in XBRL by clicking on the Export report to XHTML/XBRL, as seen in the screen shot below. 12

13 2. The Select Output Type dialogue box appears, Select XHTML with embedded ixbrl, as per the screen shot below, and press OK. 3. Save the accounts to a directory of your choice. 4. In Digita Corporation Tax, select the Tools drop down menu > Online filing, and in the attachments section, browse to where the file has been saved and select the XBRL accounts, as per the screen shot below. 13

14 OTHER ISSUES Running new reports Speeding up your workflow The running of the new XBRL reports will take slightly longer than before to generate in preview mode. This is due to additional steps in the tagging of the accounts. If you wish to edit or preview specific areas of the report the following steps will speed up the report generation. 1. Select the report tab, select the report to be generated, right click and immediately select edit mode. 2. Start to generate the report and then press cancel. An error message will appear to inform you that the operation failed to generate the report - Operation cancelled. Select OK. 3. A new template tree will appear on the left. You will now be able to select the section of the report you wish to view/edit, and this will generate only this section of the report. 4. You can then view, edit and regenerate just this section without needing to regenerate the whole report. Unable to render XML - Error when generating XBRL Report If, upon running the report, you receive the above message when reviewing the reports, return to the disclosure screen, and in the top right hand side, select the update button. This will now allow the report to generate without error. Rounding issues for users upgrading from versions prior to 4.1 This release provides the new rounding mechanism and the withdrawal of the previous rounding calculation. The advantages of this are that corresponding values in a report or between periods round consistently and the user is able to control those values that inherit rounding differences. Due to the change in the way that rounding differences are dealt with, previously reported values will change following the upgrade. Therefore the Ignore sub-code/category independent rounding is no longer required and has been removed from the Rounding and Scaling category. If you experience problems with rounding you now have the option to Round Independently on specific codes this is a tick box facility and can be found by editing the code and the box is located in the centre at the bottom of the code dialogue box. 14