Moving to Intuit Enterprise Suite (IES) was the right call. Your old setup on QuickBooks Online couldn’t handle multiple entities, couldn’t consolidate reporting across subsidiaries, and couldn’t track performance across the dimensions your business actually runs on. IES solved all of that.

But here is the problem no one mentioned during your IES evaluation: IES is a financial management platform, not a procurement control system. It tells you what was spent. It does not stop spending that should have been reviewed first.

For companies with one entity and ten buyers, that gap is manageable. For companies that chose IES specifically because they have multiple entities, custom dimensions, and growing purchasing volume across departments, that gap compounds every month.

ProcureDesk closes it. This guide explains exactly how, including how ProcureDesk maps to your IES dimension structure, handles multi-entity purchasing from a single instance, and syncs approved data back to IES in real time.

What IES Does Well, and the Gap It Was Never Built to Fill

IES delivers genuine enterprise-grade financial management for mid-market companies. The capabilities that make it worth the upgrade are real:

• Multi-entity management with consolidated reporting across up to 100 entities from a single login
• Up to 20 custom accounting dimensions for tracking performance by department, location, project, class, or any combination your business requires
• Intercompany transactions with automatic eliminations, eliminating manual Excel consolidations at month-end
• AI-assisted reconciliation, cash flow forecasting, and reporting that surfaces insights without manual intervention
• Approval workflows for invoices and bills, with role-based access controls

That last point is where most IES buyers assume the procurement problem is solved. It is not. IES approval workflows operate at the invoice level. IES invoice approval workflows operate after a vendor sends a bill. They do not operate at the purchase request level. ProcureDesk approval workflows operate before anyone places an order.

The distinction matters more than it sounds. By the time an invoice reaches IES for approval, the purchase has already happened. The budget has already been committed. The vendor relationship is already in motion. Approving or rejecting that invoice is not spend control. It is spend documentation.

Real spend control happens earlier: at the moment someone in your organization decides to buy something.

Why the Procurement Gap Gets Worse When You Have More Entities and Dimensions

The complexity that made IES the right accounting choice is exactly what makes uncontrolled purchasing more expensive.

On QuickBooks Online with one entity, a rogue purchase is a nuisance. One buyer orders something without approval, the invoice arrives, you manually code it, and you move on. Painful, but contained.

On IES with three entities, eight departments, and active project tracking across all of them, that same rogue purchase creates a different problem:

• Which entity does the invoice belong to?
• Which department initiated it?
• Which project code should absorb it?
• Does the vendor relationship exist in that entity’s vendor list, or did someone buy from an unapproved supplier?
• Was there a budget available at the entity-department-project intersection, or did this push someone over?

Your AP team answers all of those questions manually at month-end. The more dimensions your IES setup tracks, the more combinations they have to untangle. A company with three entities, five departments, and ten active projects has 150 possible entity-department-project intersections where a purchase could land. Without procurement controls, every one of those is a potential misallocation.

The problem scales with your IES configuration. The more sophisticated your financial reporting structure, the more damage uncontrolled purchasing does to it.

What Uncontrolled Purchasing Looks Like on an IES Setup

Before walking through what ProcureDesk adds, it helps to be specific about what IES users experience without a procurement layer. This is the pattern we see consistently across multi-entity companies:

The Purchase Request

A department head needs lab supplies, a field equipment rental, or a software subscription. They email the request to their manager, or drop a message in Slack. Sometimes they just buy it on a company card and submit an expense report afterward.

No purchase request form. No budget check. No PO number created before the order goes out.

The Invoice Arrives

Three weeks later, the vendor sends an invoice. It lands in a shared AP inbox, or directly in IES via a vendor portal. Your AP team sees an invoice with no PO attached and no receipt to match it against.

They spend the next 20 minutes tracking down who ordered it, what entity it belongs to, which project it should be coded to, and whether the amount is what was actually agreed. This is manual reconciliation work. This is the exact thing IES was supposed to eliminate.

Month-End Close

Your Controller pulls the IES consolidated report and finds purchases coded to the wrong entity, invoices without dimension assignments, and budget variances they are seeing for the first time, after the money is already gone.

The month-end close stretches because the accounting system is accurate but the inputs were not controlled. IES can only report what it received.

How ProcureDesk Maps to Your IES Dimension Structure

This is the section most integration articles skip. They explain that a tool “integrates with IES” without explaining what that means for the way your finance team actually uses dimensions. Here is what it means in practice.

Step 1: One-Time Dimension Setup

When you connect ProcureDesk to IES via OAuth 2.0, ProcureDesk reads your IES chart of accounts structure, including your active dimensions and their values. During the one-time onboarding setup, your ProcureDesk implementation team maps those dimensions to the requisition form that buyers see when they submit a purchase request.

After setup, the dimension values stay in sync automatically. Add a new project in IES, and it appears in ProcureDesk’s dropdown menus within minutes, with no manual updates required.

Step 2: Budget Enforcement at the Point of Request

Once dimensions are mapped, ProcureDesk enforces budget limits against them before a purchase is approved. Not when the invoice arrives. Not at month-end. When the buyer clicks submit.

A few examples of what this looks like for different IES configurations:

IES Configuration	ProcureDesk Budget Enforcement
3 entities, 6 departments per entity	Separate budget limits per entity-department combination. A marketing purchase for Entity A cannot consume the Entity B marketing budget.
Project-based billing with 20 active projects	Budget tracked by project code. Buyers select the project on the requisition form. ProcureDesk shows remaining project budget before submission.
Entity + cost center + grant dimensions (biotech/nonprofit)	Budget enforced at the grant level. A lab supply request against Grant X cannot exceed the approved grant budget, regardless of department.
Job site + cost type (construction)	Field buyers see available budget for their specific job site and cost category before placing an order. Overages route to a project manager for approval.

The key point: ProcureDesk does not create a parallel budget structure that your Controller has to maintain separately. It reads the structure that already exists in IES and enforces it upstream. The accounting structure in IES becomes the control structure in ProcureDesk.

What Buyers See

When an employee submits a purchase request, they see a form that reflects your IES dimension structure. They select the entity, department, project, or cost center that applies to their purchase. ProcureDesk shows them the remaining budget for that combination in real time, before they submit.

They do not need access to IES to do this. They do not touch your financial data. They fill in a purchase request form and ProcureDesk handles the rest.

Multi-Entity Purchasing From One ProcureDesk Instance

One of the reasons companies choose IES is consolidated visibility across entities. You get one login, one reporting dashboard, and one place to see how all your entities are performing, without logging into separate accounts.

ProcureDesk works the same way on the purchasing side. One instance handles all your IES entities. You do not run separate ProcureDesk setups for each subsidiary.

Within that single instance, each entity operates independently where it needs to:

• Separate approval chains per entity: a purchase request from Entity A routes to Entity A’s approval hierarchy, not a shared queue
• Separate vendor catalogs per entity: each entity sees only the approved suppliers relevant to their operations
• Separate budget structures per entity: budget consumption for Entity A does not affect Entity B reporting
• Separate PO numbering if required: entities that operate under different legal names or contracts can have their own PO format

At the Controller level, the consolidated view across all entities is available in ProcureDesk’s reporting dashboard. Your Controller sees total committed spend across all entities, open PO status across all entities, and invoice matching status across all entities, in one place. This mirrors what IES gives them on the accounting side: the same consolidation principle, applied to the purchasing layer.

What the IES Integration Actually Does: Data Flow

The integration between ProcureDesk and IES runs on OAuth 2.0, the same authentication standard IES uses for its own connected apps. No CSV exports. No scheduled connectors to monitor. No middleware.

What Flows From IES to ProcureDesk

• Chart of accounts: GL codes available for purchase coding
• Dimension values: departments, locations, projects, custom dimensions (synced in near real-time after one-time setup)
• Vendor/supplier list: approved vendors from IES available in ProcureDesk catalogs
• Payment status updates: when a bill is paid in IES, status reflects in ProcureDesk

What Flows From ProcureDesk to IES

• Approved purchase orders: sync to IES within seconds of manager approval
• Matched bills: after 3-way matching (PO + receipt + invoice), approved bills flow to IES ready for payment with no manual re-entry
• GL coding: dimension assignments made at the requisition stage carry through to the bill in IES automatically
• Vendor records: new vendors added in ProcureDesk can sync back to IES

The practical result: your AP team stops re-keying data that already exists. A purchase that starts as a requisition in ProcureDesk arrives in IES as a matched, coded, approved bill. Your Controller does not receive an invoice with questions. They receive a payment-ready document with a complete audit trail.

The 3-Way Match: Why It Matters More in Multi-Entity Environments

Three-way matching means validating that a purchase order, a goods receipt, and a vendor invoice all agree before payment. It is a standard AP control. Most finance teams know they should do it. Most do not, because doing it manually across multiple entities is too time-consuming to maintain consistently.

ProcureDesk automates 3-way matching for every invoice that enters the system, regardless of entity. When an invoice arrives:

1. ProcureDesk’s OCR captures the invoice data Capturing: vendor name, line items, amounts, PO reference.
2. The system matches the invoice to the original PO Verifying amounts and line items align with what was approved.
3. It checks the goods receipt Confirming what was ordered was actually received before any payment is authorized.
4. Matched invoices sync to IES automatically Ready for payment with no AP team involvement.
5. Exceptions route for human review Discrepancies flag for AP team resolution before anything reaches IES.

In a multi-entity environment, this matters because exceptions are more expensive. A mismatched invoice on the wrong entity requires correction in IES, reclassification in the dimension structure, and potentially a vendor communication, all for something that a proper PO at the beginning would have prevented. ProcureDesk’s 3-way match is the last defense. The requisition and approval process at the front is the first.

For reference: according to Ardent Partners’ 2024 State of ePayables report, best-in-class AP teams process invoices at $2.78 per invoice versus the industry average of $9.40. The gap is almost entirely explained by automation and upstream PO coverage. Companies with high PO coverage have fewer exceptions, fewer manual touchpoints, and shorter cycle times. That benchmark applies directly to IES users who add a procurement layer upstream.

Who Gets the Most Value From ProcureDesk + IES

ProcureDesk and IES together are the right fit when the following conditions are true:

You Have Multiple Entities With Active Purchasing

If your IES setup includes more than one entity and buyers across those entities are placing orders, the procurement gap exists at scale. The more entities, the more the gap matters. A holding company with three operating subsidiaries, each with its own department structure and vendor relationships, needs entity-aware purchasing controls, not just IES consolidation after the fact.

You Track Spending Across Custom Dimensions

IES’s dimension flexibility is a competitive advantage for mid-market companies. If you are tracking performance by project, grant, job site, or cost center in IES, you want that same granularity enforced at the point of purchase, not reconstructed at month-end from invoices that may or may not be coded correctly.

Your Buying Team Is Larger Than Your Finance Team

This is the core ICP signal. If you have 15-30 buyers across departments and a finance team of 1-3 people, manual purchasing oversight is not possible. ProcureDesk gives each buyer a self-service purchasing experience with guardrails: they shop from approved vendors, submit requests against their budget, and get approvals without involving the Controller in every transaction. See how this plays out in industries like logistics, biotech, and charter schools where this ratio is common.

You Recently Moved From QBO or QBE to IES

Companies mid-migration from QuickBooks Online or QuickBooks Enterprise to IES are at the highest-intent moment for adding a procurement layer. They are already restructuring their financial systems. Adding ProcureDesk during the IES implementation, rather than six months later after the first painful close, means dimension mapping happens once and the procurement layer launches with clean inputs from day one. If you are still evaluating whether to move from QBO, the QuickBooks procurement limitations guide covers what typically pushes companies toward IES.

What Setup Looks Like: 2-3 Weeks, No IT Project

One concern Controllers raise when evaluating procurement software alongside a new accounting platform: implementation complexity. You just went through an IES migration. Adding another system feels like another project.

ProcureDesk’s implementation for IES customers is handled entirely by the ProcureDesk onboarding team. Here is what the 2-3 week timeline covers:

6. IES connection setup OAuth 2.0 authentication configured in one session. Takes under 30 minutes.
7. Dimension mapping Your IES entities, departments, locations, and projects are mapped to ProcureDesk requisition fields. The ProcureDesk team handles this with you, not for you to do alone.
8. Approval chain configuration Multi-level approval rules set per entity, per department, per spend threshold. Rules can be as simple or as granular as your organization needs.
9. Vendor catalog setup Approved vendors from IES imported to ProcureDesk, plus punchout catalogs configured for suppliers like Amazon Business, Grainger, and 200+ others.
10. User onboarding Buyers trained on purchase request submission. Because the interface resembles a standard e-commerce checkout, most users are proficient within one session.

No IT resources required. No code to write. No integration middleware to configure. ProcureDesk uses the same OAuth 2.0 connection IES uses for its other connected apps. If your IES environment is already configured, the ProcureDesk connection follows the same pattern. Compare this to implementations for NetSuite or Sage Intacct. The principle is the same: procurement control live in weeks, not months.