Skip to content
AI & Automation

6 Best Financial Close Software for Family Offices 2027

Nov 17, 2026

The category decision comes first

If you are comparing the best financial close software for family offices, decide first whether you need a general ledger that closes every entity's books or a reporting layer that reads books someone else has already closed. That choice narrows the shortlist more than any feature list does, because most products that show up in family office searches were built for one job or the other, and buying a reporting tool to do a ledger's work is the expensive mistake this category invites.

TL;DR: For a monthly close across several trusts, LLCs and partnerships, shortlist multi-entity ledgers first. Add a reporting layer such as Addepar only when investment reporting is the bottleneck, not the close itself.

This guide covers six vendors. Five are candidates for the ledger role, and Addepar is included as the reporting comparison. Ledgex came up in research but is not scored, because its public pages describe reconciling statements, capital calls and K-1s rather than running a general ledger or a close.

Key Takeaways

  • A family office close has to consolidate entities and partnership capital accounts, so a ledger that keeps entity-level books is the core requirement.

  • FundCount's pricing page is the only one of the six I opened that publishes starting prices. The others point to a quote, a demo, or a page I could not reach.

  • FundCount says its quote depends on entities, users and funds, and that implementation and hosting are scoped separately from the license.

  • Implementation runs in months rather than weeks, and Family Office Exchange advises planning for a long project, not a quick go-live.

  • Close-speed claims on Asseta's and SumIt's sites are vendor claims I could not confirm on deep pages, so test them with one historical month in a demo.

  • Sage Intacct's API reference lists General Ledger and Consolidation areas, but its product and pricing pages were blocked in this check, so its fit rests on the reference and your own demo.

What a family office close has to cover

A financial close is the set of steps that finalizes each entity's books for a period, covering reconciliations, intercompany eliminations, allocations and sign-off, so that consolidated statements rest on entity-level numbers someone has checked.

BPM's September 2026 article explains why this gets hard: family offices add trusts, holding companies, real estate and private investments over time, and the first tool was often chosen for a simpler structure. It says QuickBooks-type software "may handle an individual entity reasonably well" but struggles with consolidated reporting across many related entities, and it uses "twenty or thirty related entities" as its example of scale, according to BPM (2026). BPM also implements Sage Intacct and recommends it, so read its framing as a practitioner's view with a commercial stake.

In this guide, a ledger is the system that posts journals and produces each entity's statements, and a reporting layer is the system that consolidates positions, returns and ownership for family members. Addepar's family office page describes "a unified, single source of truth" for multi-custodial data and complex legal entities, which is a reporting-layer description rather than a claim to run the books, per Addepar's family office page.

How we evaluated these tools

This guide weights seven criteria by how much each one affects a monthly close. It does not assign numeric scores, because the public pages do not support a consistent score for every vendor. The weights are a buyer's judgment, not vendor-supplied or market data, and each vendor was checked only against the pages cited in this guide.

CriterionWeightWhy it carries that weight
Multi-entity ledger with entity-level books25%A close fails at entity level before consolidation starts
Consolidation with intercompany eliminations20%Eliminations are where manual reconciliation tends to pile up
Partnership, trust and look-through structures15%Family structures bring capital accounts and layered ownership
Implementation burden and data migration15%Long rollouts consume staff time before any benefit arrives
Published pricing or quote scope10%Lets a budget be built before a demo
API and integration documentation5%Matters only if you plan exports or a review layer
Access controls and security evidence10%Family members and advisers need different views of the same data

Close-speed claims are scored as claims. A vendor that says it closes faster earns no credit until a demo shows the same result on a historical month you choose.

Feature matrix: what the public pages confirm

Each cell reflects a page opened for this guide. "Not described" means the page did not say, not that the product lacks the feature.

VendorMulti-entity ledgerConsolidation and eliminationsClose supportPublic API documentationPublic pricing
Sage IntacctGeneral Ledger API area listedConsolidation API area listedNot verifiedYes, public referenceNot verified
SumItMulti-entity general ledger under one loginAutomated multi-layer consolidation with automatic eliminationsClose-time claims, no deep pageNot documented on page openedPricing link did not resolve
AssetaMulti-entity partnership accountingAutomated intercompany reconciliation"Close in hours, not days" claimNo public API docs mentionedDemo only
FundCountDouble-entry ledger under the investment recordIntercompany eliminations on consolidation"Faster closes" claim, no checklist describedNot mentionedStarting prices published
ElysysBuilt on Business CentralCross-entity aggregated viewNot describedBusiness Central API reference (Microsoft)Demo only
AddeparNot described as a general ledgerLook-through and consolidated viewsNot described as a close toolNot described on page openedDemo only

Sage Intacct's product and pricing pages returned access errors in this check, so its row rests on its public API reference. That reference lists 17 API areas, including General Ledger and Consolidation, according to Sage Intacct (current reference). An API area listing shows what can be integrated, not how well the close works, so Sage's close capability needs to be tested in a demo.

Pricing and budget signals

Pricing checked November 13, 2026.

FundCount is the only vendor in this set whose pricing page I opened that publishes starting prices. FundCount single family office starting price: $35,899 per year according to FundCount (current pricing page). FundCount multi-family office starting price: $26,950 per year according to FundCount (current pricing page). The page says digital transformation and hosting fees sit on top and are scoped in the quotation, and it describes each solution as an annual platform license rather than a per-seat fee.

The same page says the quote depends on the number of entities, users and funds, along with assets and deployment model, so a starting figure is a floor, not a budget. Using the single family office figure as that floor, three years of subscription comes to $107,697 ($35,899 × 3) and five years to $179,495 ($35,899 × 5), before the add-on fees. The multi-family office floor works out to $80,850 over three years and $134,750 over five, using the same arithmetic.

VendorPublic pricing statusAsk for in the written quote
Sage IntacctNot verified: pricing page returned an access errorBase users, employee licenses, entity count, modules
SumItNot published on the pages checked; pricing link did not resolveEntity and family count, data migration scope
AssetaQuote-based: the site lists a demo as its only call to actionEntity count, dimensions, bill pay and banking modules
FundCountStarting prices published (figures above)Entities, users, funds, digital transformation, hosting
ElysysQuote-based: the site lists a personalized demo as its only call to actionBusiness Central scope and partner services
AddeparQuote-based: the pricing page has no price list and offers a demo requestData volume, asset classes, implementation scope

This guide prints no Sage price. Third-party sites publish price ranges for Sage Intacct, but those are not Sage's own figures, and I did not verify them against Sage's pricing page.

Vendor profiles: where each one fits

Each profile separates what the vendor says from what the pages confirm. Where a figure appears, its source is cited.

Sage Intacct

Best fit: finance teams with in-house accounting staff who want an API-first general ledger and can run a partner-led implementation. The API reference shows the General Ledger and Consolidation areas cited above.

Limitations: the product and pricing pages were not reachable in this check, so the close workflow, period controls and family-office structures are unverified here. BPM's recommendation comes from a firm that implements the product, so ask for references from family offices with a similar entity count.

Implementation: plan a partner-led project and get the scope, data migration and training listed in writing before signing.

SumIt

Best fit: offices that want a family-office-specific general ledger with one login across many entities, including multi-family offices managing several client families. The site calls it "a simple, multi-entity, and family-office-specific general ledger" and describes automated multi-layer consolidation with automatic eliminations, supporting equity pickup, full consolidation and ownership-percentage consolidation.

Limitations: the pricing link on the site did not resolve, integrations are described without named connectors, and the security and MCP pages it links were not reviewed. Third-party directories describe the company's ownership and headquarters differently, so confirm both in diligence.

Implementation: the site refers to go-live timing, but I did not find a deep page to cite for it, so ask for the timeline in the proposal.

Asseta

Best fit: family offices that want accounting, bill pay, banking, reporting and intercompany reconciliation in one platform, especially offices moving off QuickBooks-style tools. The site lists multi-entity partnership accounting, automated intercompany reconciliation and multi-dimensional tagging by fund, entity, family member and asset class.

Funding context: Asseta seed round: $4.2 million in November 2025 according to CPA Practice Advisor (2025). Funding is not proof of product depth. The same article says the company plans to add forecasting, planning and performance applications, so confirm which modules are live today.

Limitations: there is no price list, the only call to action is a demo, and the site I opened mentions no public API documentation. The site cites SOC 2 Type II and ISO 27001 compliance, so ask for the reports rather than relying on the claim. The "close in hours, not days" language is marketing until a demo shows it on your data.

FundCount

Best fit: offices that want the books and the investment record in one system. The page says "A double-entry general ledger sits under the investment record" and lists capital accounts, profit-and-loss allocations, management and incentive fees, and partner statements. It also models nested ownership across trusts, LLCs and partnerships, and it reports time-weighted returns and IRR.

Limitations: the page does not say FundCount replaces an existing general ledger. It frames the product against a stack of QuickBooks, Excel and a separate reporting tool, so replacement is implied. It promises "Faster closes" but describes no close checklist, task workflow or period-locking process. It mentions automated daily feeds and AI extraction from PDFs but no APIs, and its security badge gives no report scope.

Implementation: the page says implementation and training are "scoped transparently in your quotation," so the cost and timeline come from the quote, not the starting price.

Elysys

Best fit: buyers who run Microsoft Dynamics 365 Business Central or are willing to adopt it, and who want investment accounting and portfolio management in one environment. The site says the product is "built natively on Microsoft Dynamics 365 Business Central," and a testimonial on the site says it is "natively integrated with Business Central, not bolted on with middleware."

Evidence: Microsoft's Business Central API reference is public, so an integration team can read the general ledger entry resource before a demo.

Limitations: the site lists no pricing and offers a personalized demo, so cost depends on a quote. The platform choice brings Business Central skills and Microsoft licensing into the decision, and the site does not publish a service scope.

Addepar

Best fit: multi-generation families with alternatives, trusts and look-through ownership who need consolidated investment reporting while the ledger lives elsewhere. The family office page says the platform can "map the most complex entity structures" and describes look-through ownership across family branches.

Limitations: the site calls the product a "global data and AI platform" and does not describe itself as a general ledger, so it will not close entity books on its own. Addepar's pricing page shows no price list and offers a demo request. The implementation page says "Timelines vary based on legacy data complexity, custodial feeds and historical data migration requirements," so ask for a scoped plan.

Ledgex is excluded from scoring. Its homepage calls it "The verifiable source of truth for your family's wealth" and describes reconciliation of custodian statements, capital calls, distributions and K-1s. It belongs in a reconciliation shortlist, not a close shortlist.

Implementation time and the benchmarks behind it

Family Office Exchange describes a common pattern in which a firm spends six months selecting accounting software and then about a year training on a system that is still not live. It says all-in-one solutions take half a year at the very least, according to Family Office Exchange (2025). FOX advises earmarking one year for implementation according to Family Office Exchange (2025). The same article says clean data is a prerequisite, and that messy data makes the project much longer.

BenchmarkFigureSource yearHow to use it
Software selection in a common scenariosix months2025Set a decision date
All-in-one implementation, at minimumhalf a year2025Floor for any rollout plan
Recommended planning windowone year2025Budget staff time
Entity scale in BPM's exampletwenty or thirty related entities2026Test a demo on your own entity count

Staff time is the constraint most offices underestimate, because the people who run the close are usually the people who must also learn the new system.

Where a review layer fits the close

A US Tech Automations design could sit beside any ledger above and handle the reconciliation step inside the close, not the whole close. This is a proposed, configurable workflow to scope, not a description of a deployed system or a measured result.

The trigger is the close calendar opening a period, or a custodian or bank statement file landing in a shared folder. The action pulls each entity's posted journal lines and trial balance through the ledger's API or an export file, matches them to the bank and custodian feeds, and flags any difference above a tolerance the controller sets. The output is one exception list per entity, showing the source file, the ledger balance, the statement balance and the difference, plus a draft reconciliation for a person to review.

Before it runs, the design needs API or export access enabled on the ledger, read-only credentials to start, a named controller, and a copy of the books for one historical month. The controller stays in the loop at two points: approving every intercompany elimination and every manual journal. The workflow should not post to the ledger on its own.

A second proposed workflow covers shared expenses. The trigger is a shared bill landing on a holding entity. The action applies an allocation key the controller owns, by ownership percentage or an agreed split, and drafts the allocation journal. The output is a proposed entry in draft status with its split shown by entity. Prerequisites are an allocation table per family or entity and approval rights in the ledger, and a person approves before anything posts.

To see how this would be scoped for a specific ledger, start with US Tech Automations and bring the ledger name, the entity count and the API access you already have.

Zapier, Make, n8n, or an in-house build

Zapier, Make and n8n can connect a ledger API, a bank feed and a spreadsheet, and they can keep run histories, retries, error branches and audit evidence when you configure them. The buyer still designs and owns the rest: observability, idempotency so a retried run does not post twice, escalation paths, access controls, and maintenance when an API changes. An in-house build gives the most control and carries the same ownership burden, plus the risk that the one person who wrote it leaves.

A proposed US Tech Automations design would differ mainly in where the design work sits. The approval gates, exception queue and escalation rules are part of the scope from the start, the prerequisites (API access, reviewer roles, a test copy of the books) are listed before anything is built, and the human review points stay with the controller. A glue-code build can match that design. The real question is who maintains it, so price the maintenance hours before you choose.

A worked close example with illustrative numbers

Consider an illustrative office, not a benchmark, with 12 entities that each need 3 hours of manual tie-out at month end. That is 36 hours a month and 432 hours a year. Suppose a review queue built on the ledger's entry data flags 9 of 48 journal lines for a controller, so the remaining 39 lines, about 81%, skip manual review because the check found no difference. In Business Central, each posted entry is a generalLedgerEntry with a documentType field typed NAV.genJournalDocumentType, so a check can read that field before it flags a line, according to Microsoft Learn (2026). The math is only as good as the match rate, and the 432-hour figure is an assumption to replace with the office's own timesheets.

Who this is for

This guide is for the controller or operations lead who runs a monthly close across several entities and signs off on eliminations, and for the family office CFO who must produce entity statements and a consolidated view for family members. It is not for a single entity with one bank account, where a simpler accounting tool fits better.

Red flags: a vendor that will not demo on a sample of your entity structure, a quote that leaves data migration or hosting out of scope, and a close-speed claim with no historical month you can test.

Common mistakes when buying

  • Buying a reporting platform to close entity books. A reporting layer reads the books; it does not replace them.

  • Treating a starting price as a total. The FundCount page says the quote depends on entities, users and funds.

  • Scheduling data migration last. Family Office Exchange treats clean data as a prerequisite, and messy data makes the project much longer.

  • Accepting close-speed claims without a test. Ask for one historical month run during the demo.

  • Skipping the review design. Decide who approves eliminations and manual journals before choosing the tool.

Choose by scenario

VendorChoose it ifSkip it if
Sage IntacctYour team can run a partner-led ERP project and wants an API-first general ledgerYou need family-office structures working out of the box and cannot confirm them in a demo
SumItYou want a family-office general ledger with one login across many entitiesYour references cannot confirm close times or the company's ownership
AssetaYou want accounting, bill pay and reconciliation in one platformYou need forecasting or planning live now and the demo does not show them
FundCountYou want the ledger and the investment record together and accept a quote-based scopeYou need only a single-entity bookkeeping tool
ElysysYou run or will run Microsoft Dynamics 365 Business CentralYou have no Business Central skills or partner to support it
AddeparYour main problem is investment reporting across custodians and alternatives, with a ledger elsewhereYour main problem is the entity-level close itself

When not to use US Tech Automations: skip a proposed review layer if your ledger already produces clean reconciliations and the only gap is reporting, since the ledger's own reports or a dedicated reporting vendor will serve better. Skip it if you have one controller who prefers manual tie-outs and no bank or custodian feeds to automate yet, because a checklist inside the ledger is enough. Skip it if your books are not yet in a single ledger, because a workflow layer on inconsistent books spreads errors faster.

Frequently asked questions

Which is the best financial close software for family offices?

No single product fits every office, so shortlist the multi-entity ledgers in this guide and test each one on a historical month before deciding.

Is Sage Intacct the cheapest option?

This guide cannot say, because Sage's pricing page was not reachable in this check and the guide prints no Sage price.

Does a reporting platform like Addepar replace a general ledger?

No, Addepar's site describes a single source of truth for data and entity structures, not a ledger that closes entity books.

Do I need an API?

Only if you plan an export, a review layer or a second system; without one, any integration will depend on manual file exports.

Can Zapier, Make or n8n run the close?

They can move data and run checks once configured, but the buyer still owns the design, retries, access controls and escalation.

How long does implementation take?

Plan for a multi-month project, because selection, training and data cleanup each take time, and clean data is the factor most likely to lengthen it.

Conclusion

Start with the category decision: a ledger for entity books and a reporting layer for investment views. Use FundCount's published starting figures as a floor, request written quotes from the other vendors, and test every close claim on one historical month before you sign. If a review layer belongs in your close, see how US Tech Automations configures this for a specific ledger, with API access, reviewer roles and approval gates confirmed before any build starts.

About the Author

Garrett Mullins
Garrett Mullins
Workflow Specialist

Helping businesses leverage automation for operational efficiency.