> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/local-governance/access/local-governance-stack/finance/billing-payment-data/receipt-format.md).

# Receipt Format

### Introduction

Tax is levied by the government in certain brackets, i.e there are certain components of a tax which sum up and make the final trans-actionable amount. For example, a property tax could have swatch-ta tax, fire cess and certain other components which sum up and make a final amount.

### Data Table

<table><thead><tr><th width="96">Sr. No.</th><th>Code*</th><th>Service*</th><th>Category*</th><th>Name*</th><th>Is Debit*</th><th>Is Actual Demand*</th><th>Order*</th></tr></thead><tbody><tr><td>1</td><td>PT_UNIT_PENALTY</td><td>PT</td><td>Penalty</td><td>PT Penalty</td><td>FALSE</td><td>FALSE</td><td>1</td></tr><tr><td>2</td><td>PT_UNIT_EXEMPTION</td><td>PT</td><td>Exemption</td><td>PT Exemption</td><td>TRUE</td><td>TRUE</td><td>2</td></tr></tbody></table>

{% hint style="info" %}
Data given in the table is sample data for reference.
{% endhint %}

### Procedure

#### Data Definition

<table><thead><tr><th width="90">Sr. No.</th><th>Column Name</th><th>Data Type</th><th>Data Size</th><th>Is Mandatory?</th><th>Description</th></tr></thead><tbody><tr><td>1.</td><td>Code</td><td>Alphanumeric</td><td>64</td><td>Yes</td><td>The code for the tax that is being levied</td></tr><tr><td>2.</td><td>Service</td><td>Text</td><td>256</td><td>Yes</td><td>This is the module or the name of the service for which the tax head is being mentioned</td></tr><tr><td>3.</td><td>Category</td><td>Text</td><td>256</td><td>Yes</td><td>The category to which the tax head belongs such as Penalty or exemption or cess</td></tr><tr><td>4.</td><td>Name</td><td>Text</td><td>256</td><td>Yes</td><td>This is the name/description of the tax head</td></tr><tr><td>5.</td><td>Is Debit</td><td>Text</td><td>NA</td><td>Yes</td><td>In case the tax head is an amount that needs to be added up to the property tax, then this needs to be TRUE else FALSE</td></tr><tr><td>6.</td><td>Is Actual Demand</td><td>Text</td><td>NA</td><td>Yes</td><td>In case the tax head is an amount that needs to be subtracted from the property tax, then this needs to be TRUE else FALSE</td></tr><tr><td>7</td><td>Order</td><td>Integer</td><td>5</td><td>Yes</td><td>The order in which the mentioned tax head should appear on the screen</td></tr></tbody></table>

#### Steps to fill data

1. Download the data template attached to this page.
2. Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
3. In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
4. Get all the tax heads for a particular module and then proceed to the next module.
5. Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.

### Checklist

The checklist is a set of activities to be performed on the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.

#### Common Checklist

This checklist covers all the activities which are common across the entities.

| Sr. No. | Checklist Parameter                                                               | Example                                                                                                                         |
| ------- | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| 1       | Make sure that each and every point in this reference list has been taken care of | [Checklist](/local-governance/deploy/configure-digit/configuring-master-data-templates/module-setup/common-config/checklist.md) |

#### Entity Specific Checklist

Not Applicable

### Attachments

{% file src="/files/-MJ0e2gROmTwRjTSzGSY" %}
Configuration Data Template&#x20;
{% endfile %}

{% file src="/files/-MJ0e2gSK5pLNjghGuOi" %}
Sample Data
{% endfile %}


---

# 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.digit.org/local-governance/access/local-governance-stack/finance/billing-payment-data/receipt-format.md?ask=<question>&goal=<endgoal>
```

`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.