CasewareDocs
New in Caseware Cloud EngagementsSee what's new

Author content and deliverables in multiple languages

Authoring content and deliverables in multiple languages helps support product offerings in regions and markets where multilingual capabilities are required.

For firm or enterprise authors, multilingual support enables the flexibility to switch the language of content and deliverables directly within the engagement file. This allows for efficient content creation and updates.

Recommendations for multilingual implementation

To set up translated versions of note disclosures, letters, query questions or checklist procedures you can create multiple versions in different languages.

Notes:

  • Manual translation required: Multilingual capabilities do not automatically translate content. You must provide translations for all supported languages.

  • Language deletion: Removing a language from the template settings does not delete any translated content already added.

  • Carry forward behavior: The selected content language is carried forward to the next period’s file.

  • Language management:

    • Firm authors cannot add or delete languages.

    • Firm-level content language changes are preserved during updates from the product template.

    • Caseware language settings will override the firm or enterprise template once you update the template. For more information, see Authoring index.

Select available languages for an engagement

Caseware can set which languages and how many languages are available for documentation within an engagement. As an enterprise or firm author, you can select which languages to include based on the available languages set by the Caseware.

To select languages for an engagement:

  1. From the product template, click the [] Information button at the top of the screen.

  2. Select the Settings option to open Product Settings.

  3. Select Content language under the Format section

    • In the table, you can select or deselect languages for availability in your engagements.

    • You can also set one language as your default language.

User interface for selecting languages from the Product Settings of a Caseware template.

Add multiple languages to labels

As an author, you can use Product Settings to translate existing labels into multiple languages. The labels appear to users in the content language set for the engagement.

The settings available to you depend on your authoring role.

Product Settings access Enterprise authors Firm authors
Features | Assertions Can modify existing. Can add. Cannot access.
Features | Phases Can modify existing. Can add. Cannot access.
Features | Cycles Can modify items created by them. Can add. Cannot access.
Features | Areas Can modify items created by them. Can add. Can modify items created by them. Can add.
Features | Dimensions Can modify items created by them. Can add. Can modify existing. Can add.
Features | Components Can modify items created by them. Can add. Can modify items created by them. Can add.
Risks | Fields Can modify items created by them. Can add. Cannot access.
Risks | Scales Can modify items created by them. Can add. Cannot access.
Controls | Fields Can modify items created by them. Can add. Cannot access.
Signoffs | Roles Can modify items created by them. Can add. Can modify items created by them. Can add.

To add languages to labels:

Before you begin, ensure at least two content languages are configured in your template. See Select available languages for an engagement for information about selecting available languages.

  1. Open your template.

  2. Open the Entity's Detail dialog.

  3. Under Content language, select the language you want to add labels for.

  4. Select Information [at the top left of the window.

  5. Select Settings. The Product Settings dialog opens.

To add translated labels under Features:

  1. Under Features, select the item you want to add a translated label to:

    1. Assertions — enter the translated label for each assertion.

      1. Abbreviation — enter the translated abbreviation for each assertion in the second Assertion column.

      2. Note: Do not modify the first column — it drives calculations and formula references and serves as the default.

    2. Phases, Cycles and Areas — enter the translated label for each phase, cycle and area.

      1. Note: The Areas tab is only available if it has been enabled by Caseware.

    3. Dimensions — enter the translated label for each dimension category and dimension.

    4. Components — enter the translated label for each component category, component name and component ID.

An example of assertion abbreviations:

Product Settings showing assertion abbreviations and translated assertion labels.

To add translated labels under Risks, Controls and Signoffs:

  1. Under Risks, select Fields or Scales and enter the translated label for each field that allows customization.

  2. Under Controls, select Fields and enter the translated label for each field that allows customization.

  3. Under Signoffs, select Roles and enter the translated label for each role name.

An example of the Risks | Fields dialog:

Product Settings Risks Fields dialog showing translated field labels.

Repeat steps 3–9 for each supported content language, then publish the template.

Add multiple languages to engagement content

Unlike labels, which are configured in Product Settings, you add multiple languages to engagement artifacts directly on the template. Engagement artifacts includes the text, instructions and methodology that users interact with in an engagement such as checklists, letters, financial statements and the risk library.

The following instructions use French as an example of how to add content in another language using a firm template or an engagement file. If multiple languages are supported in your product, you can author the content and deliverables (and make changes to existing ones) in more than one language.

Notes:

  • Authoring in multiple languages can be done by firm authors in the firm template or staff members in an engagement file.

  • You must repeat the steps listed in this use-case for each language that you need to author content and deliverables for.

Assumption: English content and deliverables have already been added and authored in the template.

Before you start

  • Ensure the language (or languages) that you need to author in are active. For detailed instructions, see Content language.

  • Ensure you have the translated content for all the languages that you need to author in. The application does not automatically translate text.

  • Switch the Content language of the template to the language you want to author in (in this use-case, switch to French).

Note: On carry forward, the selected language in the current period file is carried over to the next period's file.

How to switch content language in your template.

Select content in another language

To input or edit translated content in any of the above areas, follow these steps:

  1. Select the top-left corner of the engagement to open the Entity dialog.

  2. Under Content Language, select a preferred language from the drop-down menu. This setting applies to the current editing session.

  3. Go to the Documents page to access the relevant form or checklist.

  4. Open the form (Materiality or Summary of Misstatement) or a checklist, depending on what you want to update.

  5. Select into an editable field to add or edit content in the selected language.

  6. Select the checkmark beside the field to save the content.

  7. Repeat if you require the same content in other languages. For checklists, you can click editable fields from both the Procedure and Guidance tab.

  8. For the Checklist Procedure settings: Select the Edit icon [].

  9. Select the Checklist Settings icon [].

  10. Add or edit content in the selected language in an editable fields.

  11. Select Save.

Repeat if you require the same content in other languages.

Letters/memos

To add and select a French version for the letter or memo content:

  1. Select +New section to add a section for each piece of content that needs to have a French equivalent.

  2. Enter the French content in the corresponding section.

  3. Add the following visibility logic for each French section.

    1. Select More actions [...] | Edit [].

    2. Select Edit Visibility, then select Language from the Add Condition drop-down.

    3. Set the Content language is parameter to French.

    4. Change the condition logic to Show.

Here is what the condition setup should look like.

Checklists and queries

As a firm or enterprise author, you have multilingual capabilities in the editable fields of checklists that are authored by you. This includes editable fields in the following areas within your checklist:

  • Guidance fields:

    • accessed from within the Procedures tab

    • accessed from the Guidance tab of your checklist

  • Titles for the following within the Checklist and Procedure Settings:

    • Guidance title

    • Risk title

    • Conclusion title

    • Note placeholder title

    • Response placeholder text

    • Other field in response options

Within the Procedures tab:

The user interface for selecting guidance within a checklist from its Procedure tab.

From the Guidance tab:

The user interface for selecting guidance from the Guidance tab.

Within the Checklist Settings:

The user interface for selecting options for multilingual support from the Checklist settings.

In addition, this feature extends to settings for procedures within the checklist.

the user interface for managing procedure settings within a checklist.

To add a language version of each procedure and query question (the French language is used as an example of this feature):

  1. Open the checklist and select Edit []. For each procedure:

  2. Select the procedure description. The formatting toolbar displays.

  1. Select Add Data Link [] from the toolbar. The Data Link dialog opens.

  1. At the Dynamic Text tab, add the French description of the procedure in the Output field.

  2. Select Save.

  3. If required, select the Summary field above the description to enter the French summary for the procedure.

To add the French query questions:

  1. Open the query document. For each query question:

  2. Select the description of the query question. The formatting toolbar displays.

  3. Select Add Data Link [] from the toolbar. The Data Link dialog opens.

  4. At the Dynamic Text tab, add the French description of the question in the Output field.

  5. Select Save.

  6. If required, select the Summary field above the text to enter the French summary for the query question.

You can add French response options for picklist or multi-picklist response types in the checklist default settings.

To add French picklist response options to the checklist default settings:

  1. Select the Settings icon [] to open the Checklist Settings dialog.

  2. Select the Edit icon [].

  3. Enter the French version of each picklist option.

  4. Select Save.

You can also add French response types to individual checklist procedures and query questions that have a picklist or multi-picklist response type.

To add French picklist response options for a checklist procedure or a query question:

  1. Go to the procedure in the checklist or the question in the query.

  2. Select More actions [...] | Settings [].

  3. Select the Edit icon [].

  4. Enter the French version of each picklist option.

  5. Select Save.

Financial statements

To provide content in another language, set the template's content language to your desired option. Then, update the text sections, headers, and footers by replacing the existing content with the new language version. The French language is used as an example of this feature.

Note: Trial balance groups automatically display in French once you switch the content language.

To add the French version of text sections in financial statements:

  1. Navigate to the existing text section in the financial statements.

  2. Remove the English language content and add the French version of the content.

To add French headers and footers in financial statements:

  1. To add the document level header and footer, select the Settings icon [] and choose Document Print Settings.

  2. Enter the header and footer content in the Header and Footer text fields.

You can also add custom French headers and footers for individual areas in the financial statements, the financial statement notes, and page breaks.

To add a custom French header or footer in an area or page break:

  1. Go to the desired area.

  2. Select the More actions (...) icon at the top right corner of the page.

  3. Choose Edit Print Settings from the list of actions.

  4. Select Custom header and Custom footer to display the text fields for the header or footer.

  5. Enter the header and footer content in the text fields.

To add a custom French header or footer for the financial statement notes:

  1. Select the Settings icon [] and choose Notes Print Settings.

  2. Enter the header and footer content in the Header and Footer text fields.

For any other French version items, such as the titles of areas, in the financial statements, you need to either use dynamic text or add the French version of the content and then set them to only show if the selected content language of the template is French.

To author financial statements in French using dynamic text:

  1. Go to the section you want to add French content to and select Add Data Link [] from the toolbar. The Data Link dialog opens.

  2. At the Dynamic Text tab, add the French content in the Output field.

  3. Select Save.

To author financial statements in French using visibility logic:

  1. Add French content in the desired areas.

For each area:

  1. Select Add [] | Text section.

  2. Enter the French content.

  3. Set up the visibility logic to have the content only display when the content language is French.

  1. Add the French note disclosures:

For each note:

  1. Go to the Document Map and select Add []| Create Note.

  2. Enter the French note.

  3. Set up the visibility logic to have the note only display when the content language is French.

To set up the visibility logic for each French area and note:

  1. Select More actions (...) | Edit Visibility.

  2. Select Language from the Add Condition drop-down.

  3. Set the Content language is parameter to French.

  4. Change the condition logic from to Show.

Here is what the condition setup should look like.

Materiality form

As a firm or enterprise author, you have multilingual capabilities in editable fields in the Materiality form. You can select a default language for your engagements and have the additional flexibility to change the language within editable fields.

Editable fields that include multilingual capabilities include:

  • Document and Sections Guidance

  • Sections Titles

  • Tables Headings

  • Overall Materiality - Benchmarks Input fields in Tables (Custom formulas / Other)

  • Performance Materiality & Trivial - % description

  • Conclusion procedures (including conclusion for Group component allocation)

To switch languages in an engagement

  1. Select the top-left corner of an engagement, to open the Entity dialog box.

  2. Select the drop-down menu under Content Language.

  3. Select the language you wish to use.

  4. Open the Materiality form under the Documents page.

  5. Edit or add content in the language that you selected in the editable fields.

  6. Select the checkmark beside the field to save the content.

  7. Repeat if you require the same content in other languages.

A mock example of French and German instructions

User interface of simulate French content language within an engagement form beside a user interface of simulated German content language.

Summary of Misstatements

Similar to the Materiality form, authors can use multilingual capabilities in the Summary of misstatements document, specifically the Guidance and Key Data (input) fields.

A mock French example of the Summary of misstatements

User interface of simulated French language used in the Summary of misstatements form

Folders, subfolders, documents and placeholders

To rename folders, subfolders, documents and placeholders:

  1. Go to the Documents page.

  2. Rename each folder, subfolder, document and placeholder.

For each item:

  1. Select More actions [...] | Edit [].

  2. Enter the French name and identifier of the folder or subfolder, document and placeholder.

Custom analytic tests

You can author custom analytic tests in multiple languages. When you copy a default analytic test, the system automatically creates versions for each language configured in Product settings | Content language.

To author custom analytics in multiple languages:

  1. In the product template, select the Engagement name in the top left to make the Engagement properties dialog appear.

  2. In Content language, select the language for which you are translating labels in the customized analytic test.

  3. Go to Analytics Hub and select a default test.

  4. Select the Copy icon () to create a custom version of the analytic test. Refer to Customize analytic tests for more information.

Localizing labels for a custom analytic test.

Element Description
1 Name of the analytic test
2 Description of the analytic test
3 Parameter names
4 Purpose
  1. Save changes per language. You can only edit one language at a time.

Note:

  • Default analytic tests provided by Caseware are pretranslated.

  • Translations for custom analytics are not automatic. You must provide the localized content.

  • If a translation is missing, the system displays the default language (typically English).

Risk Library

As an enterprise author, you can create and import Risk Library content in more than one language. You manage the additional languages through the Risk Library import Excel file, so a single library can serve firms that operate in more than one official language and networks that deploy content to member firms in different countries. Your users then work with Risk Library content in the language selected in their engagement.

You can provide additional-language content for the Risk Library fields that are defined in the import file. To learn more, see Manage the risk library.