> For the complete documentation index, see [llms.txt](https://help.allwage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.allwage.com/modules/payroll.md). # Payroll Get all your payroll information here At AllWage, we understand that managing payroll is a critical aspect of your business operations. It involves not only the accurate calculation and distribution of employees' wages but also the meticulous handling of financial data, statutory requirements, and reporting. Our payroll documentation is designed to guide you through the intricacies of payroll processing, from setting up your first pay run to generating bi-annual filing reports for SARS. We've tailored this resource to ensure clarity, efficiency, and compliance with industry standards. ## What You'll Find in This Documentation This documentation is structured to provide you with step-by-step instructions, insights, and best practices related to AllWage's payroll system. Whether you're a seasoned payroll professional or just getting started, you'll find valuable information to help you streamline your payroll processes, minimise errors, and maintain accurate financial records. Click on next below to start your payroll journey with AllWage --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://help.allwage.com/modules/payroll.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. 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.