> For the complete documentation index, see [llms.txt](https://docs.mindee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mindee.com/use-cases/extraction-models/payslip.md). # Payslip Automatically parse payslips and extract structured salary data using the Payslip model template available in the Catalog. Documentation for the data schema of the Payslip model template. ## Create Your Payslip Model * Click on "Create your document AI model" in your dashboard, then select **"Payslip"**. * The Payslip model template comes pre-configured with [standard fields](#payslip-fields). * Once your model is created, you can immediately [test](/models/live-test.md) with your own documents. * Optionally, you can adjust the model's [Data Schema](/extraction-models/data-schema.md) if you need to modify fields. ## Payslip Fields Documentation for all fields present in the data schema. Field *accessors* are used as the keys for accessing the values in the returned data. On the data schema interface, this is the "Field Name". Field *value types* indicate how the value is returned by the API. On the data schema interface, this is the "Field Type".

First Name

Employee's first name Accessor: `first_name`\ Value Type: `string` Has a single value.

Last Name

Employee's last name Accessor: `last_name`\ Value Type: `string` Has a single value.

Employee Address

Employee's address Accessor: `employee_address`\ Value Type: `string` Has a single value.

Pay Period Start Date

Start date of the pay period Accessor: `pay_period_start_date`\ Value Type: `date` Has a single value.

Pay Period End Date

End date of the pay period Accessor: `pay_period_end_date`\ Value Type: `date` Has a single value.

Gross Pay

Gross pay amount Accessor: `gross_pay`\ Value Type: `number` Has a single value.

Net Pay

Net pay amount Accessor: `net_pay`\ Value Type: `number` Has a single value.

Deductions

List of deductions Accessor: `deductions` **Subfields** * **Name**\ Name of the deduction\ Accessor: `name`\ Value Type: `string` * **Amount**\ Amount of the deduction\ Accessor: `amount`\ Value Type: `number` Can have multiple values (is a list/array).

Taxes

List of taxes Accessor: `taxes` **Subfields** * **Name**\ Name of the tax\ Accessor: `name`\ Value Type: `string` * **Amount**\ Amount of the tax\ Accessor: `amount`\ Value Type: `number` Can have multiple values (is a list/array).

Employer Name

Name of the employer Accessor: `employer_name`\ Value Type: `string` Has a single value.

Employer Address

Address of the employer Accessor: `employer_address`\ Value Type: `string` Has a single value.

Social Security Number

Employee's Social Security Number Accessor: `social_security_number`\ Value Type: `string` Has a single value.

Employee ID

Employee's ID Accessor: `employee_id`\ Value Type: `string` Has a single value.

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.mindee.com/use-cases/extraction-models/payslip.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 `automate deployments from our CI pipeline` 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.