> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useglimps.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Working without approvals

> For companies that do not approve invoices in advance, with an optional amount limit.

Plenty of companies do not approve invoices one by one. The order was the decision, or the supplier is on a contract, or the amounts are small and the checks are enough.

Under **Settings > Approvals** there is one switch for that: **Automatically process invoices without a purchase order or approval**. Only an administrator can change it.

## What it does

An invoice that carries no purchase order and no approval route is processed automatically instead of waiting for someone to pick it up.

## What it does not do

Everything else stays on. The reading, the supplier check, the coding rules, the math check, the duplicate check, and the bank account check all still apply. This switch removes the waiting, not the safety.

## The amount limit

Set a limit and only invoices up to that amount are processed automatically. Anything above it follows the normal route.

Leave the field empty for no limit.

<Tip>
  You can set the limit while the switch is still off. It starts applying the moment you switch on, so you can decide the number today and flip it when you are ready.
</Tip>

## Is this for us?

<AccordionGroup>
  <Accordion title="Yes, if the decision happens before the invoice">
    You order with purchase orders, or you sign contracts, and by the time the invoice arrives the decision has been made. The check that matters is whether the invoice matches, not whether somebody approves it again.
  </Accordion>

  <Accordion title="Maybe, with a limit">
    Small invoices flow, large invoices get a person. A limit gives you both without a rule per supplier.
  </Accordion>

  <Accordion title="No, if approval is your control">
    If your process depends on a manager seeing each invoice, leave this off and build proper [flows and rules](/approvals/flows-and-rules) instead.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.