# Purchase Types

<p class="doc-lead">Purchase Types (form types) define how purchase documents are numbered, titled, taxed, and printed. Each purchase quotation, order, invoice, and related document selects a form type that controls transaction ID format, footer notes, and tax behaviour.</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-types?id=overview">Overview</a>
<a href="#/purchase/purchase-types?id=fields">Fields</a>
<a href="#/purchase/purchase-types?id=how-it-works">How It Works</a>
<a href="#/purchase/purchase-types?id=actions">Actions</a>
<a href="#/purchase/purchase-types?id=faq">FAQ</a>
<a href="#/purchase/purchase-types?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 Types</b> from the left menu.

Purchase Types are master data. Edit them directly from the list or view screen — there is no Master Update workflow on this screen.

Use purchase types to separate regular and import supply chains, enforce tax on every line, set auto-numbering per document, and pre-fill footer notes and default notes on print.

<b>List columns</b>

| **Column** | **Description** |
|------------|-----------------|
| Id | Form type record ID. |
| Name | Form type name shown as <b>Form Type</b> on purchase documents. |
| Supply Type | Regular, Import, or GCC Import (Bahrain). |
| Bill Heading | Additional heading on printed bills. |
| Bill Sub Heading | Additional subheading on printed bills. |
| Branch | Branch limit when multi-branch is enabled. |
| Brand | Default brand when brand tracking is enabled. |
| Status | Active or Suspended. |

<b>Quick filter tabs</b>

| **Tab** | **Shows** |
|---------|-----------|
| Active | Active purchase types (default). |
| Suspended | Suspended types. |

<b>Advanced filters</b>

| **Filter** | **Description** |
|------------|-----------------|
| Name | Filter by form type name. |
| Branch | Filter by branch. |
| Status | Active or Suspended. |
| Created Date | Date the type was created. |

<b>List row actions</b>

| **Action** | **Description** |
|------------|-----------------|
| View | Opens read-only type details. |
| Edit | Opens the edit form. |
| Delete | Removes the type when not referenced. |
| Suspend / Activate | Disables or re-enables the type. |

<b>New Purchase Types</b>

<img src="purchase/images/purchase-types.webp" alt="Purchase Types form" loading="lazy">

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

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

<h3>Basic Information</h3>

| **Field** | **Description** |
|-----------|-----------------|
| Name * | Unique name for the form type. Shown as <b>Form Type</b> on purchase documents. |
| Supply Type | <b>Regular</b> or <b>Import</b>. Companies in Bahrain also see <b>GCC Import</b>. Controls import-related tax and compliance behaviour on linked documents. |
| Description | Optional notes about when to use this type. |

<h3>Document Headers</h3>

| **Field** | **Description** |
|-----------|-----------------|
| Document header for purchase invoice | Title printed at the top of purchase invoices using this type. |
| Document header for purchase order | Title printed on purchase orders. |
| Document header for debit note | Title printed on debit notes. |
| Additional Heading for bills | Extra heading line on printed bills. |
| Additional SubHeading for bills | Extra subheading line on printed bills. |

<h3>Tax &amp; Field Settings</h3>

| **Field** | **Description** |
|-----------|-----------------|
| RCM Applicable | When enabled, reverse charge mechanism rules apply on documents using this type. |
| Require tax for every item | When enabled, every item line must have tax before the document can be saved or approved. |
| Branch | Limits this type to a specific branch when multi-branch is enabled. |
| Brand | Default brand for documents using this type when brand-wise tracking is enabled. |

<h3>Transaction ID Format</h3>

Table with one row per document type. Configure auto-numbering independently for each transaction.

| **Column** | **Description** |
|------------|-----------------|
| Transaction | Document type: Purchase Invoice, Purchase Order, Purchase Quotation, Purchase Return Order, Debit Note, Work Order |
| Auto generate id | <b>Yes</b> — system assigns the next number. <b>No</b> — user enters the number manually. |
| Prefix | Text placed before the number (e.g. PO-). Must be unique when used. |
| Suffix | Text placed after the number. |
| Reset counter | <b>Yes</b> — counter restarts from Starting No on schedule. <b>No</b> — continuous numbering. |
| Starting No | First number when reset counter is enabled. |

<h3>Footer Notes</h3>

Rich-text footer printed at the bottom of each document type:

| **Field** | **Description** |
|-----------|-----------------|
| Purchase Invoice Footer Note | Default footer on purchase invoices. |
| Purchase Order Footer Note | Default footer on purchase orders. |
| Purchase Quotation Footer Note | Default footer on quotations. |
| Debit Note Footer Note | Default footer on debit notes. |
| Purchase Return Order Footer Note | Default footer on return orders. |

<h3>Notes</h3>

Default body notes pre-filled on new documents (editable before save):

| **Field** | **Description** |
|-----------|-----------------|
| Purchase Invoice Note | |
| Purchase Order Note | |
| Purchase Quotation Note | |
| Debit Note Note | |
| Purchase Return Order Note | |

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

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

<ul>
<li><b>Form Type selection</b> — When a user picks a purchase type on a quotation, order, invoice, or related document, numbering rules, headers, footers, and field requirements from that type apply immediately.</li>
<li><b>Numbering</b> — Auto-generated bill numbers use the prefix, suffix, and sequence configured per transaction on this purchase type.</li>
<li><b>Tax resolution</b> — Purchase type is the first key in <a href="#/purchase/purchase-tax-config">Purchase Tax Config</a>. Item group and item rows override defaults for the same purchase type. <b>Require tax for every item</b> blocks save when any line has no tax. <b>RCM Applicable</b> flags reverse charge treatment on linked documents.</li>
<li><b>Print layout</b> — Document headers, additional headings, footer notes, and default body notes from this type print on the corresponding purchase document.</li>
<li><b>Approval workflow</b> — When multi-level approval is configured on the purchase type, documents use the approval workflow instead of the direct <b>Approve</b> button on <a href="#/purchase/purchase-quotations">Purchase Quotation</a>, <a href="#/purchase/purchase-order">Purchase Order</a>, <a href="#/purchase/purchase-invoice">Purchase Invoice</a>, <a href="#/purchase/debit-note">Debit Note</a>, and <a href="#/purchase/work-order">Work Order</a>.</li>
</ul>

<p><b>Connected reports:</b> Filter by form type on <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/order-wise-purchase">Order Wise Purchase</a>, and other purchase reports when the form type filter is available.</p>

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

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

<b>List header:</b> <b>New</b>

| **Action** | **Description** | **Available when** |
|------------|-----------------|-------------------|
| Edit | Opens the edit form | Active types |
| Delete | Removes the type | When no linked transactions (if permitted) |
| Suspend | Deactivates the type | Active |
| Activate | Re-enables a suspended type | Suspended |
| Print | Prints the type configuration view | All |

<b>Form buttons:</b> <b>Update</b>, <b>Reset</b>, <b>Cancel</b>

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

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

<b>Why is Form Type required on my purchase documents?</b><br>
When at least one active purchase type exists, purchase entry screens require a form type to apply the correct numbering and tax rules.

<b>Can two types share the same prefix?</b><br>
Prefix must be unique across auto-generate configurations to avoid duplicate bill numbers.

<b>What does RCM Applicable do?</b><br>
It flags documents for reverse charge tax treatment where your company accounts for tax instead of the supplier.

<b>Do footer notes lock after save?</b><br>
Footer notes on the type are defaults. Users can still edit <b>Notes</b> on individual documents.

<b>What does Tax Required on a purchase type do?</b><br>
When enabled, purchase documents of this type require tax on applicable lines — useful for regulated or taxable supply types.

<b>How does multi-level approval relate to purchase types?</b><br>
When configured on a type, documents use workflow approval instead of the direct <b>Approve</b> button on the form.

<b>Do purchase types filter by branch or brand?</b><br>
Types can be scoped to branches or brands when multi-branch or brand tracking is enabled — only matching types appear on new documents.

<b>Which documents use purchase type numbering?</b><br>
Each type defines prefixes and auto-numbering for quotations, orders, invoices, return orders, debit notes, and work orders linked to that type.

<b>Do changes to a purchase type affect old documents?</b><br>
No. Numbering, headers, and tax flags apply to new documents and drafts going forward. Approved documents keep their original type settings.

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

<ul>
<li><a href="#/purchase/purchase-settings-config">Purchase Settings</a></li>
<li><a href="#/purchase/purchase-tax-config">Purchase Tax Config</a></li>
<li><a href="#/purchase/purchase-quotations">Purchase Quotation</a></li>
<li><a href="#/purchase/purchase-order">Purchase Order</a></li>
<li><a href="#/purchase/purchase-invoice">Purchase Invoice</a></li>
</ul>
