Multi-Entity AP Automation for Biotech on Sage Intacct

The Controller Managing Five Entities in One Sage Intacct Instance

A Controller at a growing biotech company runs five legal entities inside one Sage Intacct instance: R&D, manufacturing, a clinical trials subsidiary, and two regional entities. Invoices land in a shared inbox. Some vendors write the entity name on the invoice. Most don’t. The AP team spends the first week of every month figuring out which entity actually owes which vendor, and whether the purchase was ever approved in the first place.

This piece is for mid-market biotech finance teams (roughly 100 to 1,000 employees) running several legal entities in one Sage Intacct instance. If you’re a single-entity biotech still on QuickBooks, this is more than you need yet. If you’re enterprise pharma on SAP or Coupa, it’s too lightweight.

It is a common growing pain. PYMNTS Intelligence’s 2026 research found that only 43% of fast-scaling mid-market firms feel their tools match their current scale, against 75% of their more established peers, and companies without integrated systems run into weekly or daily cash shortages at more than four times the rate of established firms.

Sage Intacct handles the accounting side of this well. It was built for multi-entity structures, and its dimensional reporting is a real reason biotech finance teams choose it over QuickBooks or Xero. But Sage Intacct records a transaction after it exists. It doesn’t stop an unapproved purchase from happening, entity by entity, before the invoice reaches AP.

That’s the gap ProcureDesk closes. ProcureDesk sits upstream of Sage Intacct as a purchase control layer. A request gets approved, a budget gets checked, and a purchase order exists before money moves, for every entity in your instance. When the invoice finally shows up, it has something to match against instead of becoming the first record of the purchase.

This isn’t a small operational annoyance. A biotech company juggling five entities is usually also juggling grant reporting, investor updates, and sometimes an FDA submission timeline. Every one of those depends on finance being able to say, with confidence, what each entity has actually committed to spend, not just what’s been paid so far.

How Do You Centralize AP Across Biotech Entities That Each Report Into Sage Intacct?

Centralize AP by routing every entity’s purchasing through one system that checks budgets and approvals before a PO exists, instead of exporting each entity’s ledger separately.

Sage Intacct already centralizes the accounting side of a multi-entity structure. Every entity’s chart of accounts, vendor list, and dimension values can live in one instance, and finance can report across entities without exporting five separate ledgers.

What Sage Intacct doesn’t centralize is the request-and-approval step that happens before an invoice exists. A lab manager in the R&D entity and a facilities coordinator in the manufacturing entity are both buying from vendors right now, and neither purchase touches Sage Intacct until AP keys it in weeks later.

ProcureDesk runs as a single instance across all your entities instead of one procurement tool per entity. A Controller sees committed spend across R&D, manufacturing, and the clinical subsidiary in one dashboard, before any of it becomes an invoice. For the technical detail on how the sync itself works, see ProcureDesk’s Sage Intacct integration guide.

What Does Multi-Entity Accounts Payable Actually Require for Life Sciences Companies?

Multi-entity AP needs four things: entity-restricted vendors, dimension-level budget checks, correct GL coding per entity, and an audit trail that holds up entity by entity.

A biotech’s dimension structure often looks like this: Department (R&D, Clinical Trials, Manufacturing, QA), Cost Center (Lab Operations, Cell Culture, Animal Studies), and Project (Drug Candidate A, Clinical Trial Protocol 123). Sage Intacct’s dimensional accounting is built to report on all of it.

Reporting on it is not the same as controlling it. Dimensions describe a transaction after it happens. They don’t decide, in the moment a lab tech adds reagents to a cart, whether that purchase fits the Lab Operations budget for Q3. That decision has to happen before the PO exists, which means it has to happen outside Sage Intacct, in a layer built for approvals and budget checks.

• Vendor restrictions: a regional contractor approved for one entity only, a national supplier available to all five
• Dimension-level budgets: a Lab Operations budget of $85,000 that alerts before an approver clicks Approve, not after
• Entity-correct GL coding: an invoice for the clinical subsidiary posts to the clinical subsidiary, not to corporate by default
• An audit trail that survives entity by entity: who requested, who approved, what was received, what was invoiced, for each legal entity separately

Why This Matters More for Biotech Than Most Industries

A construction company with three entities cares about job costing. A biotech company with three entities usually has a grant, an investor, or an FDA submission attached to at least one of them. Money that isn’t tracked cleanly by project doesn’t just make month-end slower. It can make a grant audit or an investor due diligence request a lot more painful than it needs to be.

Lab spend adds its own wrinkle. A single R&D entity might buy from 20 or 30 different vendors in a given month, reagents, single-use plasticware, specialty gases, instrument service contracts, and most of those purchases happen at the bench, not through a formal procurement process.

Someone has to decide, before that reagent order goes out, whether it’s coming from R&D’s budget or a specific grant’s budget. Sage Intacct can report on that split after the fact. It can’t make the call before the order ships.

How Do You Consolidate Invoices Across Five or More Legal Entities Without Manual Exports?

Consolidate invoices by centralizing intake and auto-tagging each one to its entity before it reaches a spreadsheet, not by exporting from each entity in Sage Intacct after the fact.

Most biotech finance teams consolidate invoices today by exporting from each entity in Sage Intacct, pasting into a spreadsheet, and reconciling by hand. It works, but it takes days, and it only shows what’s already been posted. Anything still sitting in someone’s inbox is invisible.

ProcureDesk centralizes invoice intake before consolidation becomes a spreadsheet problem. Invoices arrive by email forwarding, vendor portal, or upload, and get tagged to the correct entity automatically based on the requester, the PO, or the vendor’s entity assignment. Lab supply purchases route through punchout catalogs with 200-plus vendor integrations, including major lab suppliers, so the item, the GL code, and the entity are already attached before the order ships.

Once every entity’s purchasing runs through one system, a Controller pulls a consolidated view across all five entities without touching an export button. For the mechanics of how POs, receipts, and invoices match automatically, see ProcureDesk’s 3-way match process.

Consolidation also has to survive partial deliveries, which are routine in a lab environment. An order for 200 lab kits might arrive in two shipments. If the first shipment of 120 kits gets invoiced separately, that invoice should match against 120 units received, not the full 200, and the second invoice should clear when the rest arrives. Handled correctly, per entity, that stops becoming a manual reconciliation problem and turns into a system rule applied consistently.

What Does Intercompany AP Automation Look Like When R&D, Manufacturing, and Corporate Sit in Separate Entities?

Intercompany AP automation routes each request to its own entity’s approvers and budget check first, so R&D, manufacturing, and corporate never draw against each other’s spend by mistake.

This is the PO-Before-Invoice Rule in practice: no invoice reaches AP without a PO that was approved, entity by entity, before the purchase happened. Once that rule holds for every entity, intercompany reporting stops being a reconciliation exercise and becomes a real-time view.

Employees at one entity can’t accidentally spend against another entity’s budget. A request from the San Francisco office only sees San Francisco’s remaining budget when creating a purchase, not the combined total across every location. That boundary gets enforced automatically, not by someone in finance checking after the fact.

Intercompany billing gets simpler too. If manufacturing orders a service on behalf of corporate, or R&D shares a piece of lab equipment with clinical trials, the request can be tagged to the entity that actually benefits from the purchase at the moment it’s created. That avoids the quarterly scramble to figure out which entity should have been billed and manually reclassifying entries after the fact.

How Do You Build a Multi-Entity Procurement Workflow on Top of Sage Intacct Rather Than Replacing It?

Build it by connecting a purchase control layer directly to Sage Intacct’s API, syncing master data down and approved bills back up, without replacing the ERP itself.

Nobody wants to rip out an ERP they chose specifically for its multi-entity accounting. ProcureDesk doesn’t ask you to. It connects directly to Sage Intacct through the Web Services API, pulls master data (vendors, GL accounts, dimensions, entities) down into ProcureDesk, and pushes approved bills back up once they clear a PO, receipt, and invoice match.

A single-entity implementation typically takes 2-3 weeks. A full multi-entity rollout across five or more entities, with dimension mapping and entity-specific approval routing, usually runs 6-8 weeks depending on how many entities and how complex the dimension structure is.

There’s also a licensing argument for keeping purchasing outside Sage Intacct entirely. Sage Intacct seats run $400 to $600 per user annually, which adds up fast across five entities if every lab tech and department admin needs a login just to request supplies. Routing requests through ProcureDesk instead means only the AP and finance team need Sage Intacct access, while everyone else works in a system built for requesting and approving, not one built for closing the books.

• Week 1-2: connect to Sage Intacct, map GL accounts, configure entity boundaries and dimension requirements
• Week 3-4: build approval workflows by entity, department, and amount, and set dimension-level budgets
• Week 5-6: pilot with two or three entities, process real purchase orders and invoices, confirm entity-correct GL coding
• Week 7-8: roll out to remaining entities and monitor sync performance across the full instance

Common Mistakes When Adding Purchase Control to a Multi-Entity Setup

Across the multi-entity Sage Intacct rollouts we’ve run, the single biggest predictor of a clean go-live is sorting out which dimensions actually need a budget check before anyone touches approval rules.

Three mistakes show up again and again in multi-entity rollouts, and all three are avoidable with a bit of planning up front.

The first is mapping dimensions too late. Teams sometimes start approval workflow design before they’ve agreed on which dimensions actually need a budget check versus which ones are just reporting labels. Sort that out before you touch approval rules, not after.

The second is treating all five entities the same. A two-person regional entity doesn’t need the same five-step approval chain as a 40-person R&D entity. Building one workflow and forcing every entity into it usually means someone starts working around the system within a month.

The third is skipping the pilot. Rolling out to all five entities on day one, instead of piloting with two or three first, means any GL mapping error or dimension mismatch shows up everywhere at once instead of in a contained test group you can fix quietly.

A Sage Intacct Biotech Customer’s Results

Metabolon, a biotech company running Sage Intacct as its ERP, had an open purchasing process before ProcureDesk. Employees in the lab, HR, and administration could buy goods and services with no approval step, and finance only found out once the invoice arrived.

Industry-wide, the gap between manual and automated AP is well documented. Ardent Partners’ latest State of ePayables benchmarks put the average cost to process an invoice at $9.84, the average processing time at 8.2 days, and the average exception rate at 18.4%. Best-in-class AP teams run 79% lower cost, 79% faster cycle times, and 47% lower exception rates. Separately, The Hackett Group found in 2025 that organizations on advanced AP platforms achieve 60% touchless processing, 59% faster cycle times, and 3.5 times higher productivity.

Sage Intacct Alone vs. Sage Intacct Plus a Purchase Control Layer

Keep Sage Intacct. Add the Control Layer It Was Never Built to Provide.

Sage Intacct is the right ERP for a multi-entity biotech company. It was never meant to be a purchase control system, and expecting it to catch unapproved spend across five entities is asking it to do a job it wasn’t designed for.

ProcureDesk gives every entity in your Sage Intacct instance a PO before the invoice, a budget check before the approval, and a consolidated view your Controller can actually trust at month-end.

ProcureDesk is a procurement and AP automation platform built for mid-market finance teams (100 to 1,000 employees) on Sage Intacct, NetSuite, or QuickBooks. It puts a PO, a budget check, and entity-correct coding in front of every purchase, entity by entity. A single-entity setup goes live in 2 to 3 weeks and a five-entity rollout in 6 to 8. Metabolon cut month-end close from 5-6 days to 3-4 after adding it.

Frequently Asked Questions

Does Sage Intacct have multi-entity procurement built in?

No, Sage Intacct handles multi-entity accounting, not multi-entity purchase approval. It reports on entities and dimensions well once a transaction posts, but nothing stops an unapproved purchase before it happens, so that check has to come from a layer in front of it.

How do you centralize AP across biotech entities on Sage Intacct?

Run purchasing through one system that connects to all entities in your Sage Intacct instance at both the top level and the entity level, so every entity’s spend is visible in one place before invoices post.

What’s the difference between multi-entity accounting and multi-entity purchase control?

Multi-entity accounting reports what already happened, broken out by entity. Multi-entity purchase control decides, before the purchase happens, whether it’s approved and within budget for that specific entity.

Do Procurify or Precoro support multi-entity Sage Intacct the same way?

Confirm this directly with each vendor before you buy. Integration with QuickBooks or a general Sage connection doesn’t guarantee entity-level vendor restrictions or dimension-level budget enforcement, and that gap only shows up after implementation starts.

How long does it take to implement multi-entity AP automation on Sage Intacct?

A single-entity setup usually takes 2-3 weeks. A full multi-entity rollout across five or more entities, with dimension mapping and entity-specific approvals, typically takes 6-8 weeks.

Can an employee at one entity accidentally spend against another entity’s budget?

Not when entity boundaries are enforced at the system level. Employees only see and spend against their own entity’s budget, and cross-entity purchases require explicit routing, not accidental access.

How does grant or project-level spend tracking work across entities?

Tag each purchase request to the relevant project or grant dimension at the time it’s created, before approval. That keeps grant spend and general operating spend separate from the start, instead of trying to split them apart during month-end close.

Does adding a purchase control layer slow down lab purchasing?

No, not if approval rules match how each entity actually operates. A routine reagent order under a preset threshold can auto-approve in seconds, and only purchases that fall outside budget or policy need a human to look at them.

About the author

Sachin Sharma

Sachin Sharma is the CEO of ProcureDesk and has spent over 23 years in procurement and supply chain technology. He previously led procurement operations at a Fortune 500 company before founding ProcureDesk. Connect with him on LinkedIn.

View all posts by Sachin Sharma → Connect on LinkedIn →