CaseWare Africa Regional BETA - IFRS 16
Gain an understanding of IFRS 16 Leases compliance and disclosure changes
It would be beneficial if you have IFRS client files with leases which could be used in the BETA process as this session is specifically focused on the changes to leases. To obtain full coverage we would greatly appreciate as much input as possible from actual lease data and exposure.It would be to your advantage to utilise CaseWare Cloud with Working Papers security integration to test the new Probe Security feature.
We are looking for users with the following:
Required software
- You have to own the CaseWare Working Papers, IFRS and Probe Template.
- For per engagement licensed template a testing license will be provided
- All software tested should be installed on your PC (installation assistance, where required, will be provided before the session starts).
Technical Knowledge, Skills and Abilities
- Solid experience working with CaseWare Working Papers, with a technical inclination to understand how the software works “under the hood”.
- Above average technical ability (International Standards of Auditing, IFRS, IFRS for SME's, Companies Act)
- Maintain the highest technical and professional standard.
- Strong interpersonal skills, problem solving and attention to detail.
Required experience
- 2+ years’ experience with CaseWare Working Papers
- 2+ years' experience working with the templates/apps being tested
Beta testing can be considered "pre-release testing." The beta phase can last anywhere from days to weeks. Beta software is generally considered "complete" by the development team but still not ready for general use due to a lack of testing "in the wild". Beta software is either released to everyone (called an open beta) or like we do at CaseWare Africa a controlled group (called a closed beta).
What is the Purpose of Beta?
Beta software serves one main purpose: to test performance and identify issues, sometimes called bugs. Allowing beta testers to try out our software and templates and provide feedback to the development team is a great way for the software to get some real-world experience and to identify how it will work when it's out of beta. Just like regular software, beta software runs alongside all the other tools that a computer or device is using, which is often the entire point — to test compatibility.
Beta testers are usually asked to give as much feedback as they can about the beta software — what sort of crashes are occurring, if the beta software or other parts of their computer, or device are behaving strangely, etc. Beta testing feedback might just include bugs and other issues that testers experience, but often it's also a chance for the development team to take suggestions for features and other ideas for improving the software.
Another common reason someone may intentionally download something that's only in the beta stage is to preview the newer, updated software. Instead of waiting for the final release, a user (like you) could download the beta version of a program, for example, to check out all the new features and improvements that will likely make it into the final release.
Is Beta Software Safe?
It's generally safe to download and test beta software, but be sure that you understand the risks that come with it. Remember that the software or template is in the beta stage for a reason: the bugs need to be identified so that they can be fixed.
This means you're more likely to find inconsistencies and hiccups in the software than you would if it were out of beta. If you're worried that your computer may crash or that the beta software may cause some other unsavory problem with your computer, we recommend using the software in an isolated, virtual environment.
What is the Purpose of Beta?
Beta software serves one main purpose: to test performance and identify issues, sometimes called bugs. Allowing beta testers to try out our software and templates and provide feedback to the development team is a great way for the software to get some real-world experience and to identify how it will work when it's out of beta. Just like regular software, beta software runs alongside all the other tools that a computer or device is using, which is often the entire point — to test compatibility.
Beta testers are usually asked to give as much feedback as they can about the beta software — what sort of crashes are occurring, if the beta software or other parts of their computer, or device are behaving strangely, etc. Beta testing feedback might just include bugs and other issues that testers experience, but often it's also a chance for the development team to take suggestions for features and other ideas for improving the software.
Another common reason someone may intentionally download something that's only in the beta stage is to preview the newer, updated software. Instead of waiting for the final release, a user (like you) could download the beta version of a program, for example, to check out all the new features and improvements that will likely make it into the final release.
Is Beta Software Safe?
It's generally safe to download and test beta software, but be sure that you understand the risks that come with it. Remember that the software or template is in the beta stage for a reason: the bugs need to be identified so that they can be fixed.
This means you're more likely to find inconsistencies and hiccups in the software than you would if it were out of beta. If you're worried that your computer may crash or that the beta software may cause some other unsavory problem with your computer, we recommend using the software in an isolated, virtual environment.
