# Multi Approval

<p class="doc-lead">Multi Stage Approval is a staged sign-off on a business document before it posts. Instead of one person clicking <b>Approve</b>, a Sale Invoice, Purchase Order, or similar voucher moves through named stages (for example Sales Manager → Finance → Director). You can require the chain always, or only when a condition matches — such as customer outstanding over a limit, or Payment Mode = Bank.</p>

<div class="doc-toc">
<p class="doc-toc-title">On this page</p>
<div class="doc-toc-section">
<span class="doc-toc-group-title">Getting started</span>
<div class="doc-toc-links">
<a href="#/features/multiapproval?id=how-it-works">How it works</a>
<a href="#/features/multiapproval?id=quick-start">Quick Start</a>
</div>
</div>
<div class="doc-toc-section">
<span class="doc-toc-group-title">Setup</span>
<div class="doc-toc-links">
<a href="#/features/multiapproval?id=stages">Approval Stages</a>
<a href="#/features/multiapproval?id=templates">Approval Templates</a>
<a href="#/features/multiapproval?id=launch-terms">When a template applies</a>
</div>
</div>
<div class="doc-toc-section">
<span class="doc-toc-group-title">On the document</span>
<div class="doc-toc-links">
<a href="#/features/multiapproval?id=approval-view">Approval view &amp; actions</a>
<a href="#/features/multiapproval?id=modals">Approval dialogs</a>
<a href="#/features/multiapproval?id=statuses">Statuses</a>
</div>
</div>
<div class="doc-toc-section">
<span class="doc-toc-group-title">Examples</span>
<div class="doc-toc-links">
<a href="#/features/multiapproval?id=example-sale-invoice">Sale Invoice — 3 stages</a>
<a href="#/features/multiapproval?id=example-customer-balance">Credit over customer balance</a>
<a href="#/features/multiapproval?id=example-bank-paymode">Bank invoices need manager approval</a>
</div>
</div>
<div class="doc-toc-section">
<span class="doc-toc-group-title">More</span>
<div class="doc-toc-links">
<a href="#/features/multiapproval?id=best-practices">Best Practices</a>
<a href="#/features/multiapproval?id=vs-workflow">Compared with WorkFlow Request</a>
<a href="#/features/multiapproval?id=faq">FAQ</a>
<a href="#/features/multiapproval?id=related">Related</a>
</div>
</div>
</div>

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

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

Setup is under <b>Settings → Multi Stage Approval</b>:

| **Page** | **Path** |
|----------|----------|
| Approval Stage | **Settings → Multi Stage Approval → Approval Stage** — [documentation](settings/approval-stage.md) |
| Approval Template | **Settings → Multi Stage Approval → Approval Template** — [documentation](settings/approval-template.md) |

Your company plan must include <b>Multi Level Approval</b>. Contact support if templates never attach.

When a template applies, the one-click <b>Approve</b> button is replaced by a staged review.

<ol>
<li>Create <b>Approval Stages</b> — who can approve, and whether any one, all, or a minimum number of them must act.</li>
<li>Create an <b>Approval Template</b> — which employees can start the chain (<b>Originators</b>), which document types it covers, the stage order, and optional launch terms.</li>
<li>An originator creates a document (for example a Sale Invoice) and fills <b>Employee</b> with their own record.</li>
<li>On save, Freespace checks for a matching active template. If one matches, it is stored on the document. Direct <b>Approve</b> (and <b>Save &amp; Approve</b>) is blocked — the message is <b>Multi level approval is required</b>.</li>
<li>On the document view, the originator clicks <b>Send Request</b> on Stage 1, picks one or more approvers from that stage, and optionally adds notes or attachments.</li>
<li>The document status becomes <b>Multi Level Approval</b>. Assigned approvers see <b>Approve</b>, <b>Reject</b>, and <b>Send For Revise</b>.</li>
<li>When a stage is approved, the next stage can be requested immediately (<b>Request Next Stage</b>) or later with <b>Send Request</b> on that stage. Stages run in order — the previous stage must be <b>Approved</b> first.</li>
<li>When the last stage is fully approved, the document is approved automatically (ledger, inventory, and close rules run as usual).</li>
</ol>

<div class="doc-workflow">
  <div class="doc-workflow-step">
    <strong>Save document</strong>
    <span class="doc-workflow-detail">Template attaches if terms match</span>
  </div>
  <div class="doc-workflow-arrow" aria-hidden="true">→</div>
  <div class="doc-workflow-step">
    <strong>Send Request</strong>
    <span class="doc-workflow-detail">Status = Multi Level Approval</span>
  </div>
  <div class="doc-workflow-arrow" aria-hidden="true">→</div>
  <div class="doc-workflow-step">
    <strong>Stage approvals</strong>
    <span class="doc-workflow-detail">Approve, reject, or send back</span>
  </div>
  <div class="doc-workflow-arrow" aria-hidden="true">→</div>
  <div class="doc-workflow-step">
    <strong>Final approve</strong>
    <span class="doc-workflow-detail">Last stage complete → Approved</span>
  </div>
</div>

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

<h2 id="quick-start">Quick Start</h2>

<h3>1. Create stages</h3>
Go to <b>Settings → Multi Stage Approval → Approval Stage</b>. Add one stage per review step (for example Sales Manager, Finance, Director). See <a href="#/settings/approval-stage">Approval Stage</a>.

<h3>2. Create a template</h3>
Go to <b>Settings → Multi Stage Approval → Approval Template</b>. Name it, add originators, select document types, add stages in order, then choose <b>Always launch</b> or <b>Based on terms</b>. See <a href="#/settings/approval-template">Approval Template</a>.

<h3>3. Create a matching document</h3>
Log in as an originator. Open the document type you selected (for example <a href="#/sales/sale-invoice">Sale Invoice</a>), set <b>Employee</b> to that originator, and save.

<h3>4. Send the first request</h3>
Open the document. Use <b>Send Request</b> on Stage 1. Choose approvers from the stage list and confirm.

<h3>5. Approve through the chain</h3>
Each approver opens the same document, reviews the panel, and clicks <b>Approve</b>. On the last stage, the document becomes <b>Approved</b>.

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

<h2 id="stages">Approval Stages</h2>

A stage is one review step. Reuse the same stage on more than one template.

| **Field** | **Description** |
|-----------|-----------------|
| Stage Name * | Label shown on the document panel (for example Sales Manager Approval). |
| Approval Rule * | <b>ANY</b>, <b>ALL</b>, or <b>MINIMUM</b>. |
| Minimum no. of approvals required | Shown only when the rule is <b>MINIMUM</b>. |
| Approvers * | Employees who can be selected when a request is sent for this stage. |
| Allow Document Editing on Revision | When checked, the original requestor can open <b>Edit</b> on the panel after <b>Send For Revise</b>. |
| Notes | Instructions for approvers. |
| Status | Active or Suspended. Suspended stages should not be used on new templates. |

<h3>Approval rules</h3>

| **Rule** | **When the stage is complete** |
|----------|--------------------------------|
| ANY | The first assigned approver who approves completes the stage. Other pending requests on that stage expire. |
| ALL | Every approver who was requested must approve. The panel shows <b>Pending Approval By</b> until the last one acts. |
| MINIMUM | The number in <b>Minimum no. of approvals required</b> must approve. The panel shows that count while the request is open. |

A Super User can <b>Approve</b>, <b>Reject</b>, or <b>Send For Revise</b> even when they are not in the stage's approver list.

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

<h2 id="templates">Approval Templates</h2>

A template is the chain: who may start it, which documents it covers, the stage order, and when it launches.

| **Field** | **Description** |
|-----------|-----------------|
| Name * | Template name. |
| Description | Purpose and when to use it. |
| Originators * | Employees whose documents can pick up this template. Matching uses the document <b>Employee</b> field. |
| Select documents you will like to add * | One or more document types. |
| Stages | Ordered list of Approval Stages. Serial number is the sequence. |
| Launch Approval * | <b>Always launch</b> or <b>Based on terms</b>. |
| Terms | Shown only for <b>Based on terms</b>. Every term on the template must match. |
| Status | Active or Suspended. Only Active templates attach. |

<h3>Documents you can add</h3>

| **Group** | **Documents** |
|-----------|---------------|
| Sales | Sale Quotation, Sale Order, Sale Invoice, Pro Forma Invoice, Credit Note, Sale Debit Note |
| Purchase | Purchase Quotation, Purchase Order, Purchase Invoice, Debit Note |
| Accounts | Expense, Receipt Voucher, Payment Voucher |
| Other | Inventory Adjustment, Expense Claim, Production Voucher |

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

<h2 id="launch-terms">When a template applies</h2>

On save (and on update while the document is still a draft), Freespace looks for an Active template that:

<ol>
<li>Includes this document type under <b>Select documents you will like to add</b>.</li>
<li>Lists the document <b>Employee</b> as an <b>Originator</b>. If Employee is blank, no template attaches.</li>
<li>Matches launch rules (below).</li>
</ol>

If more than one template matches, an <b>Always launch</b> template is chosen first. Only if none of those exist does a <b>Based on terms</b> template apply. Do not keep both kinds for the same originators and document type — Always launch will hide the terms-based one.

<h3>Launch Approval</h3>

| **Option** | **When it attaches** |
|------------|----------------------|
| Always launch | Every time that originator saves that document type. |
| Based on terms | Only when <b>every</b> term on the template matches the document. |

To treat two conditions as “either / or” (Bank <b>or</b> high customer balance), create two templates. Terms on a single template are always “and”.

<h3>Term fields</h3>

| **Field** | **Operations used** | **Value** | **Applies to** |
|-----------|---------------------|-----------|----------------|
| Total | Equal to, Greater than, Less than | Amount | Most documents use <b>Total</b>. Expense, Expense Claim, Receipt Voucher, and Payment Voucher use the voucher amount. |
| Payment mode | Matched to the selected mode | Cash, Bank, Cheque, PDC, Digital Wallet | Sale Invoice, Purchase Invoice, Receipt Voucher, Payment Voucher, Expense, Credit Note, Sale Debit Note, Debit Note |
| Customer Balance | Equal to, Greater than, Less than | Amount | Sale Invoice, Sale Order, Sale Quotation, Pro Forma Invoice — and only when Payment Mode is <b>Credit</b> |
| Customer Group | Equal to | A customer group | Sale Invoice, Sale Order, Sale Quotation, Credit Note, Sale Debit Note, Pro Forma Invoice |
| Customer | Equal to | A customer | Same sales documents as Customer Group |
| Variance Exceeded | Equal to | True or False | Used for <a href="#/production/production-voucher">Production Voucher</a> when production variance requires approval |

<b>Customer Balance</b> is compared as:

<b>invoice Total + customer's current closing balance</b>

against the term value. Cash, Bank, and other non-credit invoices never match a Customer Balance term.

<b>Payment mode</b> in terms does not include Credit. Use Customer Balance, Total, Customer, or Customer Group for credit invoices.

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

<h2 id="approval-view">Approval view &amp; actions</h2>

When a template is assigned, the document view shows a stage panel under the bill. Each stage shows its name, current status, history, attachments, and the buttons the logged-in user is allowed to use.

Click the <b>stage name</b> to open the stage master in a dialog.

<h3>What each stage shows</h3>

| **Item** | **Description** |
|----------|-----------------|
| Stage name | From the Approval Stage. |
| Status | Not Requested, Approval Requested, Approved, Rejected, Cancelled Request, or Requested for Revision. |
| Request / Approval / Rejected / Cancelled / Send For Revision | One history block per action, with <b>By</b>, <b>Time</b>, and <b>Note</b>. |
| Next Action By | Approvers the request was sent to (joined with OR, AND, or commas depending on the approval rule). |
| Pending Approval By | Remaining approvers when the rule is ALL or MINIMUM and some have already approved. |
| Min no. of approvals required | Shown while a MINIMUM stage is waiting. |
| Paperclip | Add attachments to that log. Existing files can be downloaded or deleted. |

<h3>Buttons on the panel</h3>

These are the actions on the multi-stage approval view. They are separate from the document toolbar <b>Approve</b> button, which is hidden whenever a template is assigned.

| **Button** | **Who sees it** | **When it appears** | **What it does** |
|------------|-----------------|---------------------|------------------|
| Send Request | Employees listed as allowed requestors for that stage | Stage is <b>Not Requested</b>, <b>Cancelled Request</b>, or <b>Requested for Revision</b>, and the previous stage is already Approved (or this is Stage 1) | Opens <b>Request Approval</b>. After confirm, document status becomes <b>Multi Level Approval</b> and approvers are notified. |
| Approve | Assigned approvers, or a Super User | Stage is <b>Approval Requested</b> | Opens <b>Approve Request</b>. Completes the stage when the approval rule is met. On the last stage, the document is approved. |
| Reject | Assigned approvers, or a Super User | Stage is <b>Approval Requested</b> | Opens <b>Reject Request</b>. Document status becomes <b>Multi Level Approval Rejected</b>. |
| Cancel | The employee who sent that request | Stage is <b>Approval Requested</b> | Opens <b>Cancel Request</b>. Approvers are notified. On Stage 1, the document returns to <b>Draft</b>. On a later stage it stays <b>Multi Level Approval</b> so the requestor can send again. |
| Send For Revise | Assigned approvers, or a Super User | Stage is <b>Approval Requested</b> | Opens <b>Send For Revisal</b>. Stage becomes <b>Requested for Revision</b>. The original requestor can send the stage again. |
| Edit | The original requestor | Stage is <b>Requested for Revision</b> and the stage has <b>Allow Document Editing on Revision</b> | Opens the document edit form. |

<h3>Who can send each stage</h3>

| **Stage** | **Who can click Send Request** |
|-----------|--------------------------------|
| First stage | Template <b>Originators</b> (until a request exists). After a cancel or revise on Stage 1, only the person who sent that request. |
| Later stages | The employees who approved the previous stage. |

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

<h2 id="modals">Approval dialogs</h2>

| **Dialog** | **Fields** | **Opened by** |
|------------|------------|---------------|
| Request Approval | Notes, Approver * (multi-select from the stage's approvers) | Send Request |
| Approve Request | Notes, Request Next Stage, Next Stage Approver | Approve |
| Reject Request | Notes | Reject |
| Send For Revisal | Notes | Send For Revise |
| Cancel Request | Notes | Cancel |

<b>Request Next Stage</b> appears on Approve only when another stage remains and the current stage can finish with this approval (ANY, or ALL/MINIMUM when this is the last required approval). Tick it and choose <b>Next Stage Approver</b> to send the next stage in the same step. If you leave it unchecked, someone who approved this stage later uses <b>Send Request</b> on the next stage.

Approvers must be mapped to a user login. If a selected employee has no user map, the request fails with <b>Employee not mapped to user</b>.

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

<h2 id="statuses">Statuses</h2>

<h3>Document status</h3>

| **Status** | **Meaning** |
|------------|-------------|
| Draft | Saved with a template attached, but Stage 1 has not been sent (or Stage 1 was cancelled). |
| Multi Level Approval | At least one stage has been requested. Also used after <b>Send For Revise</b>. |
| Multi Level Approval Rejected | An approver rejected the current stage. |
| Approved | The last stage is complete. Normal posting has run. |

Lists such as Sale Invoice include a <b>Multi Level Approval</b> quick filter for documents waiting in the chain.

<h3>Stage status on the panel</h3>

| **Status** | **Meaning** |
|------------|-------------|
| Not Requested | This stage has not been sent yet. |
| Approval Requested | Waiting for an assigned approver. |
| Approved | Stage is complete. |
| Rejected | An approver rejected. |
| Cancelled Request | The requestor cancelled while it was waiting. |
| Requested for Revision | An approver sent it back. |

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

<h2 id="example-sale-invoice">Example — Sale Invoice with three stages</h2>

A typical credit-control chain: Sales Manager → Finance → Director. Every invoice from the sales team must go through all three stages before it posts.

<h3>1. Create stages</h3>

| **Stage Name** | **Approval Rule** | **Approvers** | **Allow Document Editing on Revision** |
|----------------|-------------------|---------------|----------------------------------------|
| Sales Manager Approval | ANY | Sales managers | Yes |
| Finance Approval | ALL | Finance executives | No |
| Director Approval | ANY | Directors | No |

<h3>2. Create the template</h3>

| **Field** | **Value** |
|-----------|-----------|
| Name | Sale Invoice — Standard |
| Originators | Sales executives (the people who create invoices) |
| Documents | Sale Invoice |
| Stages | 1 Sales Manager Approval → 2 Finance Approval → 3 Director Approval |
| Launch Approval | Always launch |

<h3>3. Run the flow</h3>

<ol>
<li>A sales executive creates Sale Invoice SI-1042 (Credit, customer Acme, total 18,000) with <b>Employee</b> set to themselves, then saves. The template attaches. The toolbar <b>Approve</b> button is hidden.</li>
<li>On the invoice view they click <b>Send Request</b> on Sales Manager Approval, select a manager, and add a note. Status becomes <b>Multi Level Approval</b>. The manager is notified.</li>
<li>The manager opens SI-1042, reviews lines and customer balance, and clicks <b>Approve</b>. They tick <b>Request Next Stage</b> and select both finance executives (rule is ALL).</li>
<li>Each finance executive clicks <b>Approve</b>. The panel shows <b>Pending Approval By</b> until the second one approves.</li>
<li>The last finance approver ticks <b>Request Next Stage</b> and selects a director.</li>
<li>The director clicks <b>Approve</b>. There is no further stage, so SI-1042 becomes <b>Approved</b> and posts.</li>
</ol>

If Finance finds a wrong rate, they click <b>Send For Revise</b> instead. The executive sees <b>Requested for Revision</b>, clicks <b>Edit</b> (allowed on the first stage), corrects the invoice, then <b>Send Request</b> again to the manager.

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

<h2 id="example-customer-balance">Example — Extra approval when customer balance is over a limit</h2>

You want executives to approve small credit invoices themselves. When the customer's outstanding plus this invoice exceeds 50,000, a credit-control stage is required.

<h3>1. Stages</h3>

| **Stage Name** | **Approval Rule** | **Approvers** |
|----------------|-------------------|---------------|
| Credit Control | ANY | Credit controller, Finance manager |

<h3>2. Template</h3>

| **Field** | **Value** |
|-----------|-----------|
| Name | Sale Invoice — High outstanding |
| Originators | Sales executives |
| Documents | Sale Invoice |
| Stages | 1 Credit Control |
| Launch Approval | Based on terms |

| **Sl Num** | **Field** | **Operation** | **Value** |
|------------|-----------|---------------|-----------|
| 1 | Customer Balance | Greater than | 50000 |

Do <b>not</b> also create an Always launch Sale Invoice template for the same originators, or this terms template will never attach.

<h3>3. What happens</h3>

Customer Acme already owes 42,000.

| **Invoice** | **Total** | **Balance used for the term** | **Template attaches?** |
|-------------|-----------|-------------------------------|------------------------|
| Credit SI-2001 | 5,000 | 42,000 + 5,000 = 47,000 | No — executive can use <b>Approve</b> |
| Credit SI-2002 | 12,000 | 42,000 + 12,000 = 54,000 | Yes — executive must <b>Send Request</b> to Credit Control |
| Bank SI-2003 | 80,000 | Not evaluated (not Credit) | No — Customer Balance terms apply only to Credit |

After Credit Control approves SI-2002, the invoice is approved and posted.

You can add a second term on the same template if both must be true — for example Customer Balance Greater than 50000 <b>and</b> Customer Group Equal to Wholesale.

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

<h2 id="example-bank-paymode">Example — Executives cannot approve Bank invoices</h2>

Bank collections need a supervisor to confirm the account and reference. Cash invoices can still be approved by the executive.

<h3>1. Stages</h3>

| **Stage Name** | **Approval Rule** | **Approvers** |
|----------------|-------------------|---------------|
| Manager Bank Review | ANY | Branch managers |

<h3>2. Template</h3>

| **Field** | **Value** |
|-----------|-----------|
| Name | Sale Invoice — Bank |
| Originators | Sales executives |
| Documents | Sale Invoice |
| Stages | 1 Manager Bank Review |
| Launch Approval | Based on terms |

| **Sl Num** | **Field** | **Operation** | **Value** |
|------------|-----------|---------------|-----------|
| 1 | Payment mode | Equal to | Bank |

<h3>3. What happens</h3>

| **Invoice** | **Payment Mode** | **Template attaches?** | **How it is approved** |
|-------------|------------------|------------------------|------------------------|
| SI-3101 | Cash | No | Executive uses toolbar <b>Approve</b> |
| SI-3102 | Bank | Yes | Executive uses <b>Send Request</b> → manager <b>Approve</b> → invoice Approved |
| SI-3103 | Credit | No | Payment mode terms do not include Credit. Use a Customer Balance or Always launch template if credit also needs review. |

The same pattern works on Payment Voucher, Receipt Voucher, Expense, Purchase Invoice, Credit Note, Sale Debit Note, and Debit Note.

To require both a Bank payment <b>and</b> a high total, add a Total term on the same template. To require Bank <b>or</b> high customer balance, use two templates.

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

<h2 id="best-practices">Best Practices</h2>

<ul>
<li>Put originators and approvers on different lists. An originator who is also the only approver can send and approve their own document.</li>
<li>Keep one Always launch template <b>or</b> several terms-based templates per document type and originator group — not both.</li>
<li>Use short stage names that match job titles so the panel is easy to read.</li>
<li>Turn on <b>Allow Document Editing on Revision</b> on the first stage if approvers often send invoices back for rate or quantity changes.</li>
<li>Ensure every approver has a user login mapped to their employee. Otherwise notifications and requests fail.</li>
<li>Set <b>Employee</b> on every sale document that should enter a chain. A blank Employee skips template matching.</li>
<li>Use <a href="#/hr/reports/approval-request-report">Approval Requests Report</a> to watch pending, rejected, and cancelled requests across modules.</li>
</ul>

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

<h2 id="vs-workflow">Compared with WorkFlow Request</h2>

After you understand document sign-off, note that <a href="#/hr/workflow-request">WorkFlow Request</a> is a different feature. Use it to run a company process around a document (purchase, site visit, stock in, delivery, invoice). Completing that process does not approve or post the origin document.

| | <b>Multi Stage Approval</b> (this page) | <b>WorkFlow Request</b> |
|--|----------------------------------------|-------------------------|
| <b>Purpose</b> | Sign off the document before it posts | Coordinate later work steps around a document |
| <b>Setup</b> | Settings → Multi Stage Approval | HRMS → Settings → WorkFlow Approval Stage / Template |
| <b>How it starts</b> | Template attaches when the document is saved | Created from the document more menu, or from HRMS → Workflow Request |
| <b>Effect on the document</b> | Last stage complete → document becomes Approved | Origin document status does not change |
| <b>Stage buttons</b> | Send Request, Approve, Reject, Cancel, Send For Revise, Edit | Same, plus optional Create Delivery Note / Create Sale Invoice (and similar) |

Do not configure a WorkFlow Request when you need the invoice itself held until managers sign it. Do not configure Multi Stage Approval when you only need a delivery or purchase process after the order already exists.

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

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

<b>Why is Approve hidden on my Sale Invoice?</b><br>
A matching approval template is assigned. Use Send Request on the first stage. Direct approve is blocked until the last stage is complete.

<b>Why did no template attach?</b><br>
Confirm the template is Active, the document type is selected, Employee on the document is an Originator, and the company plan includes Multi Level Approval. For terms-based templates every term must match. Customer Balance only matches Credit invoices.

<b>Can I skip a stage?</b><br>
No. Stages run in serial order. A Super User can act as an approver on the current stage, but they cannot jump over a stage that has not been requested.

<b>What if two templates match?</b><br>
Always launch is chosen over Based on terms. If two Always launch templates both match, one of them is used. Keep a single Always launch template per originator group and document type.

<b>Does Reject let the executive edit and send again?</b><br>
Reject sets the document status to Multi Level Approval Rejected. Use Send For Revise to return the stage to the requestor for another Send Request (and Edit when the stage allows it).

<b>Who is notified?</b><br>
Approvers are notified when a request is sent or cancelled. The requestor is notified when someone approves, rejects, or sends for revision.

<b>Is this the same as WorkFlow Request?</b><br>
No. This feature signs off the document itself. A WorkFlow Request is a separate process you start from a transaction (or from HRMS) to coordinate later steps such as purchase, delivery, or invoicing. Completing that process does not approve the origin document. See <a href="#/hr/workflow-request">WorkFlow Request</a>.

<b>Where do I see all pending document approvals?</b><br>
Use the Multi Level Approval quick filter on the document list (Sale Invoice, Purchase Order, and others). <a href="#/hr/reports/approval-request-report">HRMS → Reports → Approval Requests</a> also lists pending requests across modules.

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

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

<ul>
<li><a href="#/settings/approval-stage">Approval Stage</a></li>
<li><a href="#/settings/approval-template">Approval Template</a></li>
<li><a href="#/sales/sale-invoice">Sale Invoice</a></li>
<li><a href="#/hr/workflow-request">WorkFlow Request</a> — company process tracker, not document sign-off</li>
<li><a href="#/hr/reports/approval-request-report">Approval Requests Report</a></li>
<li><a href="#/settings/settings?id=multi-stage-approval">Settings hub — Multi Stage Approval</a></li>
</ul>
