> For the complete documentation index, see [llms.txt](https://docs.irs.systems/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.irs.systems/report-analyzer/documentation/manual.md). # Modules ## Program functions in detail ![Overview](/files/F38JLVcZ6MlXTurVUHdJ) The software is available in several languages. The screenshots of this user manual have been made in the English version. The names of the windows, buttons, etc. are therefore also in English in this manual and may differ from the actual representation of the respective language. ### System requirements * Windows 7, 8, 10 (32/634 bit) * 4GB RAM minimum, 8GB recommended * .NET 4.6.2 or higher ### Installation To install the program, run the installer and follow the instructions. ### Activation The software must be activated with a valid license to use it. For a period of up to 60 days the software can be tested in trial mode. The trial mode is identical to the licensed version in terms of functionality. Only the created exports (PDF, Word, etc) are watermarked. For activation a valid license key is required to unlock the software. The license key must be activated once on the IRS server. The documentation for software activation can be found [here](https://www.irs.systems/software-activation/). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.irs.systems/report-analyzer/documentation/manual.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.