# Purchase Tax Config

<p class="doc-lead">Purchase Tax Config maps default purchase taxes to combinations of purchase type, item group, and item. When a user adds an item on a purchase bill, the system applies matching tax rules automatically.</p>

<div class="doc-toc">
<p class="doc-toc-title">On this page</p>
<div class="doc-toc-section">
<div class="doc-toc-links">
<a href="#/purchase/purchase-tax-config?id=overview">Overview</a>
<a href="#/purchase/purchase-tax-config?id=fields">Fields</a>
<a href="#/purchase/purchase-tax-config?id=how-it-works">How It Works</a>
<a href="#/purchase/purchase-tax-config?id=actions">Actions</a>
<a href="#/purchase/purchase-tax-config?id=faq">FAQ</a>
<a href="#/purchase/purchase-tax-config?id=related">Related</a>
</div>
</div>
</div>

<hr class="doc-section-divider">

<h2 id="overview">Overview &amp; List View</h2>

Go to <b>Purchase → Settings → Purchase Tax Config</b> from the left menu.

Tax rates themselves are maintained under <b>Accounts → Settings → Taxes</b>. Purchase Tax Config only links which taxes apply on purchase for each scope.

This screen is an inline table — not a standard list. Add rows at the bottom and delete existing rows with the trash icon. There is no separate edit form.

Configurations are matched in priority order: exact match on purchase type + item group or item, then broader rules with blank purchase type, item group, or item. The first matching row wins.

<b>List columns</b>

| **Column** | **Description** |
|------------|-----------------|
| Purchase Type | Optional scope by <a href="#/purchase/purchase-types">Purchase Type</a>. |
| Item Group | Optional scope by item group. |
| Item | Optional scope by single item. |
| Taxes | One or more purchase taxes applied when the row matches. |

<b>Purchase Tax Config</b>

<img src="purchase/images/purchase-tax-conf.webp" alt="Purchase Tax Config" loading="lazy">

<hr class="doc-section-divider">

<h2 id="fields">Fields</h2>

Each row defines one tax mapping:

| **Field** | **Description** |
|-----------|-----------------|
| Purchase Type | Optional. Limits the rule to one <a href="#/purchase/purchase-types">Purchase Type</a>. Leave blank for all types. |
| Item Group | Optional. Applies to all items in the group. Cannot be combined with Item on the same row — choose one or the other. |
| Item | Optional. Applies to a single item. Cannot be combined with Item Group on the same row. |
| Taxes * | One or more purchase taxes (tax type = purchase) from Accounts. Required on every row. |

<b>Validation rules when adding a row:</b>
<ul>
<li>At least one of Purchase Type, Item Group, or Item must be selected.</li>
<li>Item Group and Item cannot both be filled on the same row.</li>
<li>Taxes is required.</li>
</ul>

<hr class="doc-section-divider">

<h2 id="how-it-works">How It Works</h2>

<p>When an item line is added on a purchase bill, the system resolves taxes in this order:</p>

<ol>
<li><b>Purchase type + item</b> — exact match on form type and item</li>
<li><b>Purchase type + item group</b> — form type and item group match (when no item row)</li>
<li><b>Broader fallbacks</b> — rows with blank purchase type, item group, or item</li>
</ol>

<p>If the purchase type has <b>Require tax for every item</b> enabled, save is blocked when the resolved tax list is empty. <b>RCM Applicable</b> on the purchase type flags reverse charge treatment where your company accounts for tax instead of the supplier.</p>

<p>Config provides defaults at item selection. Users who can edit purchase documents can still adjust taxes on the line when editing drafts.</p>

<p><b>Connected reports:</b> Tax amounts flow into <a href="#/purchase/reports/purchase-bill-report">Bill Wise Purchase</a>, <a href="#/purchase/reports/purchase-bill-report-adv">Bill Wise Purchase Advanced</a>, <a href="#/purchase/reports/bill-item-wise-purchase">Bill Item Wise Purchase</a>, and accounts tax reports.</p>

<hr class="doc-section-divider">

<h2 id="actions">Actions</h2>

| **Action** | **Description** |
|------------|-----------------|
| Add (+) | Saves a new row from the blank entry line at the bottom of the table. |
| Delete (trash) | Removes a configuration row. |

There is no separate edit form — delete and re-add to change a mapping.

<hr class="doc-section-divider">

<h2 id="faq">FAQ</h2>

<b>Why are taxes not appearing on my purchase invoice line?</b><br>
Check that a matching Purchase Tax Config row exists, taxes are active in Accounts, and the purchase type on the bill matches the rule.

<b>Which rule takes priority — item or item group?</b><br>
The system prefers the most specific match (purchase type + item, then purchase type + item group, then fallbacks with blank fields).

<b>Can I set different taxes for the same item on different purchase types?</b><br>
Yes. Create separate rows with the same item but different purchase types.

<b>Does this override taxes entered manually on a line?</b><br>
Config provides defaults at item selection. Users who can edit purchase documents can still adjust taxes on the line when editing drafts.

<b>What if no purchase tax config row matches?</b><br>
Tax must be selected manually on the line, or come from item or supplier defaults configured elsewhere in Accounts.

<b>Can I deactivate a tax config row?</b><br>
Yes. Inactive rows are ignored on new documents. Existing approved bills keep the taxes they were posted with.

<b>Does purchase tax config apply to debit notes and expenses?</b><br>
Rules apply wherever purchase type and item drive default tax on purchase documents — primarily invoices, orders, and quotations. Confirm tax on debit notes and purchase expenses when entering drafts.

<b>Should I create a catch-all row with blank item and group?</b><br>
Optional. Blank item group fields act as broader fallbacks after specific item and item-group rows are checked.

<h2 id="related">Related Topics</h2>

<ul>
<li><a href="#/accounts/taxes">Taxes</a></li>
<li><a href="#/purchase/purchase-types">Purchase Types</a></li>
<li><a href="#/purchase/purchase-invoice">Purchase Invoice</a></li>
<li><a href="#/purchase/purchase-settings">Purchase Settings hub</a></li>
</ul>
