What Slows a Multi-Entity Sage Intacct Close

A close that slips a little with every entity you add rarely looks like a system failure. The reports run and the journals post. But deep into the second week your controller is still asking who has the last bills, why a management fee hit one entity and not the other, and whether a late invoice belongs to this month or next. Sage Intacct tends to take the blame in those conversations, and someone starts pricing a new module.

Usually the software has done its part. The days go to the work around it: approvals waiting on a person, coding that varies by entity, intercompany charges nobody scheduled, reviewers still preparing, and no one able to say which entity is holding up the rest.

Here are six places the days go, what Sage’s own documentation says the system does at each point, and what closes the gap.

Approvals: a bill waiting on one person is not in the close

With bill approvals turned on, Sage’s documentation says a bill reaches Posted only after the last level approver approves it. Until then it sits as Submitted or Partially approved. A bill waiting on an administrator who is out this week has not reached the General Ledger.

Intacct can route approvals by vendor, by value, by transaction department or to a single named user. That covers who gets asked. Getting an answer by your cutoff is people work, and each entity adds more approvers whose week can become your close date.

What fixes it: process. Publish a cutoff. Write approvers by role with a named backup. Give one person the job of working the pending list on a fixed day, and decide in advance what happens to anything that misses. If you use value approval, bills under your lowest level post without approval, so check that level sits where you want it. Our Sage Intacct finance teams handle invoice intake, approvals, payment scheduling and vendor management inside your system.

Vendors and coding: the same invoice, three ways

In a multi-entity shared company, Sage’s default is to create vendors at the top level and share them with every entity. A vendor created at the entity level is accessible only in that entity. So when entities add their own, one linen company can become several records carrying several coding habits.

Dimensions add another layer. Sage describes a dimension as a tag, and a transaction can carry several. A tag is only as consistent as the person applying it. If one entity tags Department and the next one skips it, the totals still foot and the comparison between them means little.

What fixes it: process first, then software. Give new vendors and new dimension values one owner, and write a short coding guide. Once the rules are written, review exceptions instead of every line. At a 100+ facility outsourced accounting operation, Ledger Classifier runs 16 configurable rules after AP close, and GL review went from several hours to under 1 hour per facility.

Intercompany: the entry balances, the agreement does not

With inter-entity transactions enabled, Sage says Intacct adds the offsetting entries to each affected entity’s journal, using the accounts you mapped. That mechanical part is handled. Two limits are worth knowing: the mapping has to be set up first, and entries balance by entity, so balancing by dimension is manual.

The system also has no view on what the management fee should be this month, who agreed the split on shared payroll, or whether the charge is posted by the day the other entity’s accountant needs it. In close week those questions tend to get settled by email.

What fixes it: process. Keep one intercompany schedule listing each recurring charge, its basis, who posts it and by what day. Post on a fixed day before entity close starts. Add a mapping check to your new-entity checklist. Our teams help tag transactions properly, manage intercompany entries and generate consolidated reports.

Review: your reviewers are still preparing

A controller cannot read what is not finished. When preparation runs long it eats review, and the people you pay for judgment spend the month on reconciliations and data entry.

Paradigm Healthcare runs 19 nursing homes and provides back-office accounting for another 12 facilities. Its case study puts the constraint plainly: “The biggest constraint was not systems. It was people.” A dedicated Touch Support team now prepares the prelims and hands them to Paradigm’s onshore team for review and publishing. The back office supports 30+ facilities, with prelims delivered on time and no added local headcount.

What fixes it: people, arranged differently. Split preparation from review and staff them separately. An outside preparer does not have to mean open access. Sage recommends role-based permissions in most cases, and access to entities can be restricted user by user. Our teams work within role-based access that you control, only in the modules the work needs.

Status and late items: nobody can say who is holding it up

A multi-entity close finishes when the last entity does. If status lives in one person’s spreadsheet, the controller finds the holdout by asking around.

Sage offers a Close Automation subscription whose Close Assistant shows an overview of all entities and flags incomplete tasks. If you have it, use it. If you do not, a shared calendar with one row per entity and one date per step answers the same question: who is next? Either way it reports status, and someone still has to act on it.

Late items need a rule as well. Once books are closed, transactions cannot be posted to earlier dates in any application, and Sage points to the adjustment journal for changes after close. It also notes that access to reopen books usually sits with the accounting manager, controller or CFO. That is a sound control, and it means every late item lands on your most senior people.

What fixes it: process. Name one close owner per entity. Set a dollar line for late items: below it they go to the next period, above it they go to the controller with a written reason.

Corrections: the reason disappears

Every reclassification tells you something upstream is off, and most of that information gets lost. A healthcare accounting operation running tens of thousands of invoices a month asked accountants to log each GL reclassification in a separate ticketing system after correcting it in Sage Intacct. By its own estimate, roughly 15% got logged. The case study does not put that down to carelessness: a second job, in a second system, after the first job is finished, gets skipped.

What fixes it: software, because the rule is known. The Sage Extension build uses a Sage Smart Event to send the transaction data when an accountant reclassifies a GL entry or deletes a bill. Smart Events come with a Customization Services or Platform Services subscription. Finance leadership now has a searchable record of what changed, who changed it and why. Where one GL code keeps getting corrected, the guidance behind it can be rewritten.

Five dates and one count to log on your next close

Before you buy anything, log these for every entity. The widest gap between two dates is where your days are going.

If one entity is late on every line, that is an ownership problem at that entity. If every entity is late on the same line, that line is your close. Only after that is it worth asking whether a new module would help.

Frequently asked questions

How Sage Intacct works, from Sage’s help documentation, read November 2026: bill states, bill approval setup, managing multiple entities, shared vendors, dimensions, inter-entity transactions, permissions, entity restrictions, Close Assistant, close books, open books and Smart events. Case study figures are as published on each linked page.