> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to handle purchase requests across multiple branches
- URL: https://blog.jestor.com/purchase-requests-across-branches/
- Published: 2026-09-16T18:52:39.000Z
- Updated: 2026-09-16T18:52:39.000Z
- Author: Bruno Bannach

Managing **purchase requests across branches** means giving each unit enough autonomy to operate while keeping head office able to see and control the whole. In **Jestor**, branches are records, requests carry their unit, and routing can differ by location while consolidation happens automatically.

## Why centralizing everything slows units down

Routing every branch purchase through head office guarantees control and guarantees delay. The branch waits on someone with no context about local conditions.

Decentralizing entirely produces the opposite problem: speed with no visibility, and a consolidated picture that only exists at month end.

What the right structure balances:

- Local autonomy below a defined amount
- Head office approval above it
- One consolidated view across every unit
- Consistent categories so consolidation is meaningful
- Different **ERP** accounts per legal entity where they exist

## Local and central responsibilities

| Decision                          | Local    | Head office |
| --------------------------------- | -------- | ----------- |
| Routine purchases below the limit | Yes      | No          |
| Purchases above the limit         | Requests | Approves    |
| New supplier approval             | Requests | Approves    |
| Category structure                | Uses     | Defines     |
| Consolidated reporting            | Own unit | All units   |

## Step by step to structure it

1. **Create the branches registry**, with the legal entity and **ERP** account of each.
2. **Make the branch a required field** on every request.
3. **Set a local limit**, above which requests route to head office.
4. **Standardize categories centrally**, so consolidation is comparable.
5. **Route the approved entry** to the ERP account of the correct entity.
6. **Build the consolidated dashboard**, filterable per branch.
7. **Set permissions** so each branch sees its own data and head office sees everything.

## Why standardized categories matter more than limits

Limits control spend. Categories determine whether the consolidated view means anything. If each branch invents its own classification, head office ends up with a report that cannot be compared across units, which is the same as no report.

## Why choose Jestor

**Jestor** handles several **Omie** accounts in one environment at no additional cost per legal entity, routes each approved entry to the correct account, keeps categories in a central registry referenced by every branch, and applies permissions per role and record so a unit sees its own data while head office sees the consolidated picture.

## Frequently Asked Questions

### Can each branch have its own ERP account?

Yes, and several accounts can be connected in the same environment. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Can approval limits differ per branch?

Yes. Routing can read the branch alongside the amount.

### Can a branch see only its own requests?

Yes, through permissions applied per role and record.

## Video Tutorial: Step by Step

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by **AI**. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.