startJournal Export File Definition
How To

Journal Export File Definition

CCH Audit Automation
Last update: Reading time 5 minutes
Data ExportTrial BalanceJournals

    As previously indicated, it is possible to define the format of the journal posting file for the system as a whole. The definition of the posting file is made up of three sections:

    Export header                 the information output at the beginning of the file
    Export transactions        the information exported for each journal entry which needs to be generated
    Export footer                  the information which is output at the end of the file.

    Audit Automation allows you to define each area via the [Control] option of the File menu on the Pack window. On selecting this option, a sub menu will appear which includes options to export the header, footer and transaction. The method of defining each of the three areas is the same, utilising the same dialog box, however, certain codes are available when defining transactions which are not available in the header or footer sections.

    Editing the definition

    Select the section to be edited from the sub menu and the Export definition dialog box will be displayed, showing any current definition.

    clipboard_e4ff32559d8fb731dd4a15547a202216e.png

    Export definition dialog box

    The fields available for export are listed in the list box headed Fields available and are as follows:

    All areas
    * Up to 5 user defined text strings
    * A date - 4 formats available
    * Day
    * Month
    * Year - in 2 forms
    * File name

    Additional fields for transactions
    * Reference
    * Narrative
    * Nominal ledger code
    * Amount

    The user defined text strings can contain whatever information you wish, up to a maximum of 20 characters. To enter the text to be used, select the entry box beside the text number, either using the <Tab> key or with the mouse, and enter the text required.

    When the export file is created, the system will generate the section by writing the fields in the order in which they appear in the Current definition list box. To add a field to the definition, either double click on the name of the field in the Fields available list box, or highlight it with a single click and click on [Add]. The name of the field will appear in the Current definition list box. Continue to add the fields required until the Current definition shows all the fields to be output, in the order in which they are required. If you have added a field in error, or in the wrong order, you may remove the field, either by double clicking on it in the Current definition list box or by highlighting it with a single click and clicking on [Remove].

    The final option on the Export definition dialog box is the Export mode. If the CSV format check box is checked, then the system will output the items on a single line, separating each field with a comma. If the check box is not checked, then the fields will be written to the file in line separated format with one field being written on each line.

    Example

    As an example of the definition of an export file we will look at creating a posting file in the format required for import by PROcap for DOS, the DOS version of our nominal ledger and accounts production system. The definition of the posting file for Accounts Production is as follows:

    Header - included once at the beginning of the file

    Posted flag         Contains 0 before posting and is set to 1 by Accounts Production after posting
    File name           The name of the file being posted
    Date                    In format dd,mm,yyyy and is the date of the period end to which the data should be posted
    VAT type            A single character of “N” to indicate that the entries have no effect on the VAT records
    Control code    The nominal ledger code to which the run total is taken. Not used for journal entries

    The definition of this header would be as follows:

    clipboard_e0fcddf41f89b0cac93e49c3ddb0535da.png

    Accounts Production header export definition

    As Accounts Production expects each field to be on a separate line, the CSV format check box is not checked. In addition, it should be noted that within headers, the date output is the period end date of the register.

    Transaction record - one for each journal entry

    Date                     In the format dd,mm,yy
    Reference           The entry reference
    Narrative            The entry narrative
    Account code    The account to which the item is to be posted
    Amount              The amount of the entry, credits are included as negative items

    VAT code            The VAT table to be affected by the entry - ignored for journals
    VAT amount      The amount of VAT associated with the transaction - ignored for journals

    The following is the definition of the transaction section, which will achieve the above:

    clipboard_e8e23d989283cc0bf48f85d2913b0ef78.png

    Export definition for transactions

    As with the header, each field is expected on a separate line and the CSV format box is unchecked. For transactions the date output is the date of the transaction itself.

    Footer - output once at the end of the file.

    Accounts Production continues processing transactions until it comes to a line where the date is recorded as “99,99,99”. The only information which needs to be included in the footer is an instruction to output this line. The definition is therefore as follows:

    clipboard_ea8c291ed378a64b28e11acda3f529cb5.png

    Export definition - footer

    As indicated above, the export definition is stored within the system and it is only necessary to enter the definition once.

    Related documents

    Inherent Risk Questions
    This document outlines the process for assessing inherent risk in clients through a systematic approach of questions. The system can store up to 99 risk areas, each containing 99 questions, which are assigned point scores for "Yes" and "No" answers. It details steps for editing, adding, and deleting risk areas and questions, including interface navigation and confirmation prompts. Additionally, it emphasizes that once numbers are assigned to risk areas or questions, they cannot be changed. The document serves as a guide for managing inherent risk assessments effectively.
    Audit Risks
    This document details the functionality of CCH Audit Automation for recording Identified Audit Risks, also referred to as Significant Business Risks. It provides instructions for users to add, edit, and manage risks, including features for maintaining risks for future audits, assessing their significance, and linking them to assertions. The system includes tools for risk assessment, audit response, and documenting conclusions. Other functionalities encompass risk summarization, printing options, and risk linkage across multiple sources, enhancing the audit process's efficiency and accountability.
    Default Specific Risk Questions
    CCH Audit Automation allows users to define specific risk questions for audit areas, although it's not mandatory. If no specific questions are set, default questions will be used. Users can edit the default questions through the "Specific risk questions" option in the Risk Model section. Up to 99 default questions can be defined, similar to inherent risk questions. The system utilizes a lookup table that combines specific and inherent risks for audits, with editing instructions provided in the manual.
    Risk/Sample Selection
    This document outlines the concept of audit risk, defined as the likelihood of undetected material errors during an audit. It introduces a risk model used in Audit Automation that requires total audit risk to remain below acceptable levels across various audit areas. The risks are broken down into inherent risk, control risk, and detection risk, with further subdivisions for detection risk. It emphasizes the importance of understanding these concepts to design effective audit procedures and assess risk at different levels. Additionally, it discusses general and control environments, and the calculation of residual risk, alongside a risk scoring system.
    Inherent Risks
    The document outlines the procedure for addressing inherent risk questions in an audit context. Users can access a dedicated window to view up to 99 risk areas, answer questions, and modify responses as necessary. The system prompts users to validate changes to ensure proper risk assessments. It includes functionalities for viewing prior comments, copying text, and overriding calculated risk levels, emphasizing that auditor judgment is crucial. Comments on overrides must be provided to rationalize any adjustments made. The document serves as a guide for navigating and utilizing the auditing software effectively.