The Field Guide to On-Premises GLs

The Field Guide to On-Premises GLs: Dynamics GP, Sage 100, Blackbaud FE NXT, MIP, QuickBooks Desktop, Epicor, Deltek, SYSPRO, Multiview, and the FP&A layer each one deserves

It's day 4 of the month's close. Three finance leaders are looking at three different screens. Jeff, CFO of a 14-site behavioral health group, is scrolling through a Great Plains query he wrote 11 years ago that still runs, still produces the same six-division trial balance, still lands in the same Excel workbook where a single bad paste ends the day. Mary, Director of Finance at a Kentucky food bank, is watching Dynamics NAV pull actuals into Centage on its own, exactly as it did last month, and she has already moved on to the varian ce narrative. Steeve, Controller at a New Jersey specialty adhesives manufacturer, has not opened SYSPRO once this week; his monthly close has run itself since the Windows Task Scheduler job kicked off Sunday night at midnight.

Three ledgers, three cadences, three degrees of confidence. All three of these systems work. All three were designed by serious people to record financial transactions with precision. None of them was built to plan. That was never their job.

If you run finance at a $10M to $250M company, or a $5M to $100M operating-budget nonprofit, and your general ledger is on a Windows server in a closet, or on a Citrix client that your IT team refuses to touch, or on a SQL database that lives in your building, this field guide is for you. The industry has spent five years telling you that your ledger is the problem. It is not. What you run is what your business needs. The gap is that your ledger records; it does not plan. And the FP&A tools that most easily plug into planning are cloud tools that cannot reach your ledger, which is why so many finance teams live in a 19-workbook Excel layer that grows every quarter.

This piece is the honest reference guide. Ten general ledgers. What each does well. Who runs each one. Where each one stops at planning. And, at the end, a fair per-GL summary you can lift into a vendor conversation, plus the four connector tiers Centage actually uses so you can tell which path applies to your stack in about 15 seconds.

The tone is respect, not urgency. If you are staying on your current GL for the next five years, this guide helps you plan around it. If you are already staring at a migration decision, this guide helps you understand what your FP&A layer will need to survive that decision. Both readers are welcome.

‍

Recorders, not planners

Every ledger below is a recording system. That is the job of a general ledger: to hold the truth about what happened to money, at the account level, at a point in time, with an audit trail that survives regulators. The best of these systems (SYSPRO, Multiview, Great Plains at its peak) do the recording job as well as anything ever built.

The planning job is different. Planning asks forward-looking questions: what will payroll look like at 340 headcount instead of 312, what happens to margin if we lose one anchor customer, how does the fund-restricted grant P&L roll up if we take on a new federal contract in Q4. Those questions require dimensionality (cost center by project by grant by wage class), scenario duplication, and workforce mechanics that no accounting ledger has ever tried to hold. That gap is why every finance team on the list below has an Excel layer downstream of their ledger. That is where the fragility lives, and where the credibility risk with the board lives, and where 6 to 10 business days a month go.

The rest of this piece is written on that premise. We are not proposing you rip out your ledger. We are proposing that the layer sitting between your ledger and your board pack deserves better than 19 workbooks.

‍

The integration reality (four tiers)

Before the per-GL walk-through, one thing to say up front so you can read each section with the right frame. FP&A software connects to a GL in one of exactly four ways. It is worth naming them clearly, because the difference matters more than the marketing usually admits.

Tier 1: cloud API. The FP&A tool talks to the GL's public API over the internet. This is how Sage Intacct, NetSuite, Blackbaud Financial Edge NXT, QuickBooks Online, Dynamics 365 Business Central, and Acumatica are connected. These are cloud GLs. Refresh cadences run from nightly (Sage Intacct) to on-demand.

Tier 2: behind-the-firewall agent (Centage calls this CDI). An installed Windows application inside your environment reaches into your GL's SQL database (typically MSSQL, dedicated read-only user, port 1433), pulls the full data set, and uploads it to the FP&A tool on a schedule (typically nightly, run through Windows Task Scheduler). This is how a modern FP&A tool reaches ledgers that were never given a public API: Dynamics GP, Dynamics NAV, Dynamics SL, Sage 100, Sage 300, Sage 500, SYSPRO, and, with quirks, QuickBooks Desktop. You need a Windows server, a dedicated SQL user with `db_datareader` on the GL databases, and about an hour of your IT admin's time once.

Tier 3: partner-facilitated. A specific ledger has a partner-built or vendor-facilitated data feed into the FP&A tool. MIP fund accounting (via Abila) is the canonical example. The connection works, and it works reliably, but it depends on a third party and has to be sized carefully during scoping.

Tier 4: file-based (CIF). The FP&A tool accepts a structured import file (Centage Import Format in our case) and the customer produces that file on a cadence, either from a canned export in the GL or through a partner script. This is the honest reality for Epicor, Deltek, and Multiview today. It is deterministic in production, and it is faster to set up than the alternative paths. It also survives quarterly GL upgrades because it does not touch the underlying database.

There is nothing wrong with tier 4. It is the tier the industry has quietly relied on for 20 years for exactly the ledgers that never opened up. The point of naming it plainly is that when a competitor says the word "integration," you should ask which tier they mean, because "integration" has covered all four of these mechanisms and one salesperson's demo trick.

‍

Dynamics GP (Microsoft Great Plains)

Great Plains is the workhorse of North American mid-market finance departments. Microsoft acquired it in 2001, folded it into the Dynamics line, and finance teams have been running the same trial-balance and division-rollup queries against it for two decades. Multi-division, multi-fund, multi-currency: it does all of that. The reporting side (Management Reporter, FRx before it) is where the ledger stops.

What GP does well. Multi-entity chart of accounts with real segmentation. Reliable trial balance and subledger detail. A community of controllers, ISVs, and consultants deep enough that you can hire GP expertise on 30 days' notice in almost any US metro. The GL itself is stable to a degree that Microsoft's cloud successors have not matched.

Who runs it. Mid-market healthcare providers, biotech, insurance, professional services, nonprofits with federal grant exposure, manufacturers who added divisions faster than they could migrate. Companies from 50 employees to 3,000. Finance teams from 3 people to 15.

Where GP stops at planning. Building a board-ready P&L that ties out variance to a specific project, cost center, and month against a forward budget requires either a report writer (Management Reporter) that most controllers have grown to dislike, or an Excel workbook that grows every quarter. Workforce planning is not part of the ledger; headcount and payroll modeling live in a separate spreadsheet, which is where the merit-cycle math and the fringe-benefit assumptions get out of sync.

Named customer on GP. A national behavioral-health provider with six divisions runs its close on Great Plains and pulls actuals daily into Centage via CDI. Its CFO's words on the drill-through: once the month is set, the data refreshes on its own, and variance drill goes from "why is this number off" to "which project inside which division caused it" in about two clicks. That kind of drill is what the GP \+ Excel combination could not give the finance team; the ledger held the detail, and the Excel layer could not surface it.

Microsoft's lifecycle disclosure. GP mainstream support ended in September 2024; extended support runs through April 2028. If you are on GP, you have time. Migration is a legitimate future decision, and a deliberate one. Any FP&A tool you pick now should carry your reporting across whatever ledger comes next (see Blog 4 in this series).

‍

Dynamics NAV (Navision, and its successor Business Central)

NAV was the European contribution to the Microsoft ERP portfolio, acquired in 2002, dominant in the SMB and mid-market space through the 2010s. Microsoft renamed the modern cloud version Dynamics 365 Business Central; the on-prem NAV installations still running in 2026 are typically 2016 and 2018 versions, still stable, still recording.

What NAV does well. Multi-currency and multi-entity handling with better UI density than GP. Strong distribution and light-manufacturing modules. The upgrade path to Business Central is well-understood by the partner community, so companies on NAV tend to have a written migration roadmap even when they are not migrating this year.

Who runs it. European-headquartered companies with US operations. Distribution and light-manufacturing shops. A large tail of nonprofits and community-services organizations that adopted NAV in the 2000s and never had a reason to move.

Where NAV stops at planning. Same story as GP. The ledger holds the actuals in structured form; the planning layer does not exist. Nonprofit users add a fund-accounting overlay in a spreadsheet, and that overlay breaks quietly when a new grant enters mid-year.

Mary Flannery, Director of Finance, God's Pantry Food Bank. God's Pantry is a Feeding America affiliate in central Kentucky serving 50 counties with a mixed federal, state, and private funding stack. Her verbatim on the pre-Centage state:

‍"We'd spend days just cleaning up formulas. If something changed mid-year, it meant hours of rework."

The read: NAV was recording just fine. The workbook downstream of NAV was the fragile piece, and mid-year changes (new grant, restricted-fund reclass, headcount shift) meant hours of manual formula repair. Centage's native NAV connector removes that step; actuals refresh into the model automatically, and mid-year structural changes update the plan instead of breaking it.

Connector reality. NAV runs on tier 2 (CDI). Business Central runs on tier 1 (cloud API), with a documented caveat around service-to-service OAuth setup that needs about 30 minutes of your Azure admin's time once.

‍

Sage 100

Sage 100 (formerly MAS 90 and MAS 200\) is the North American SMB and lower-mid-market accounting workhorse. It has been in continuous production since the mid-1980s. Manufacturers, distributors, and multi-location professional-services firms are the core installed base.

‍What Sage 100 does well. Rock-solid GL and subledger handling for the shape of business it was designed for: single or lightly-consolidated entity, inventory-heavy or job-cost-heavy operations, in the 20 to 200 employee band. Third-party ecosystem is deep; there is a Sage 100 add-on for almost any operational need.

Who runs it. Distributors and light manufacturers in the $10M to $100M revenue band. Multi-location professional-services and construction firms. Education franchises and childcare operators with multi-site rollups.

Where Sage 100 stops at planning. Consolidation across entities is a manual exercise. Workforce planning is not part of the product. Forecasting is a spreadsheet activity downstream of the GL. Sage's own push over the last three years has been to move Sage 100 customers to Sage Intacct (a cloud multi-entity FP&A-friendly successor), which is a real product with a real price tag; the migration is a genuine decision for finance leaders, not a marketing pressure line.

Named customer on Sage 100. A multi-site education operator with dozens of school locations runs its close on Sage 100 and uses Centage's Personnel Module for the site-by-site headcount plan. Position-level budgeting (role, wage band, fringe assumption) sits inside Centage; actuals flow from Sage 100 nightly through CDI; site-by-site variance drill is available the morning after month-end.

Connector reality. Tier 2 (CDI). If you are on Sage 100 and considering Sage Intacct, the same FP&A layer works on either side of that migration; the connector switches from CDI to cloud API and the model itself stays intact.

‍

Blackbaud Financial Edge NXT

Financial Edge NXT is the modern cloud version of Blackbaud's finance suite, the dominant fund-accounting GL for US mid-market nonprofits. Blackbaud acquired MicroEdge and Kintera in the 2000s, then rebuilt Financial Edge as a cloud product (the NXT suffix). It is the ledger of choice for community-services nonprofits, private foundations, museums, and higher-education adjacencies.

What Financial Edge NXT does well. Fund accounting with real integrity: restricted vs unrestricted vs temporarily-restricted, project × grant × program dimensionality, and audit-ready reporting for federal Single Audit thresholds (the $1M threshold takes effect for fiscal years ending on or after September 30, 2025). The Blackbaud partner ecosystem is deep in the nonprofit space, and Financial Edge integrates well with Raiser's Edge on the fundraising side.

Who runs it. US nonprofits from $5M to $100M operating budget. Museums, food banks, community-services organizations, private foundations, and religious institutions.

Where Financial Edge NXT stops at planning. Two places, both real. First, workforce planning is absent from the product; nonprofits with heavy program-staff labor economics build their headcount plan in a spreadsheet that shadows the GL. Second, the forward-looking budget-vs-actuals view against dimensional cuts (grant × program × fund × month) requires either the Blackbaud Budget module (which many finance leaders describe as under-invested) or an Excel layer.

Anonymized customer proof. A community-services nonprofit in the low tens of millions of operating budget moved from a broken Blackbaud \+ Excel close cycle to Centage on Financial Edge NXT via Blackbaud's marketplace. The pre-built integration removed a major evaluation risk during the vendor selection, and the finance team stopped hand-eliminating intercompany entries at month-end. That pattern (Blackbaud marketplace listing removes the connector risk during the evaluation) is one of the reasons Blackbaud FE NXT nonprofits shortlist Centage.

Connector reality. Tier 1 (cloud API). Centage is listed on the Blackbaud marketplace. Refresh cadence is on-demand within API rate limits. The one honest caveat: API reliability has intermittent hiccups that Blackbaud publishes; the Centage integration handles retries, but this is worth naming so you know what to expect.

‍

MIP fund accounting (Community Brands)

MIP (owned by Community Brands, formerly Abila, formerly Sage MIP before that) is a fund-accounting GL built specifically for nonprofits and government-adjacent finance departments. It is deep on grant accounting, restricted-fund reporting, and the specific dimensionality federal audits require.

What MIP does well. Grant × program × fund × restriction accounting done right. Multi-year grant tracking. Reporting formats that map cleanly to federal audit requirements. If your finance job is dominated by federal or state-restricted funding streams, MIP is genuinely one of the best-fit ledgers in the market.

Who runs it. Federally-funded services nonprofits. Community action agencies. Public-media stations. Regional transit authorities. Health and human-services organizations at the county and state level.

Where MIP stops at planning. Budget building at the program-and-grant level requires exports to Excel; workforce planning is not native; scenario modeling (what happens to the grant P&L if the federal reauthorization is delayed six months) does not live inside MIP.

Anonymized customer proof. A federally-funded services nonprofit ran a competitive evaluation between Centage and Solver against a working MIP install. Centage won on the specific point that its actuals pull did not require re-uploading transaction data every close; the connector handled it. The finance director's frame from the win-loss review: the integration was zero-touch after setup, which is what "integration" is supposed to mean but often is not.

Connector reality. Tier 3 (partner-facilitated via Abila). This is worth understanding before you shortlist any FP&A vendor for MIP: the connector works because Abila built and maintains it, and any FP&A vendor's ability to serve MIP customers depends on that partner relationship, not on the vendor's own engineering. Ask the question directly during a demo.

‍

QuickBooks Desktop

Intuit has scheduled QuickBooks Desktop's discontinuation for May 2027 in most SKUs. Until that date, QuickBooks Desktop remains the single largest legacy accounting installation in North America. There are hundreds of thousands of finance teams still running Pro, Premier, or Enterprise editions on a Windows workstation or a small Windows Server.

‍What QuickBooks Desktop does well. Straightforward double-entry accounting for single-entity or lightly-consolidated businesses. A price point (under $2,000/year in Enterprise) that made it the default for small and lower-mid-market for two decades. A workflow that finance leaders in the 20-to-100 employee band learned in their first bookkeeping course.

Who runs it. Family businesses. Distributors and light manufacturers under $50M revenue. Professional-services firms. Multi-location retail operators. Many private-equity portfolio companies below the migration threshold.

Where QuickBooks Desktop stops at planning. Multi-entity consolidation is a manual re-key exercise. Workforce planning is entirely a spreadsheet activity. Rolling forecasts do not exist in the product. Reporting depth beyond the built-in canned reports requires either QuickBooks-specific add-ons or an Excel dump.

Connector reality. Tier 2 (CDI), with two documented quirks worth naming honestly. The Task Scheduler run for QuickBooks Desktop can be unstable in a few older QuickBooks versions, so many customers run the CDI job manually or on a supervised schedule. Second, if your QuickBooks file lives on a workstation rather than a small Windows Server, the CDI installation takes a bit more setup to get right. Neither is a blocker; both are worth knowing before the kickoff call.

What the Intuit date means. If you are on QuickBooks Desktop, you have roughly 20 months as of this writing. That is enough time to pick an FP&A layer, run it in parallel with your current spreadsheet stack, and let your team learn the model before the ledger migration lands. It is not enough time to leave until Q1 of 2027.

‍

Epicor

Epicor is a manufacturing-focused ERP with strong depth in job-cost accounting, shop-floor integration, and mixed-mode manufacturing (make-to-order and make-to-stock in the same instance). The finance ledger inside Epicor is competent; the finance leader running Epicor is typically running it because operations picked the ERP for the shop-floor capability first, and finance inherited it.

What Epicor does well. Deep manufacturing accounting: work-in-progress valuation, job-cost variance analysis, standard-cost roll-ups. Multi-entity consolidation with intercompany elimination. Real-time inventory and cost data that ties back to the GL.

Who runs it. Discrete manufacturers from $25M to $500M revenue. Industrial equipment makers. Contract manufacturers. Aerospace and defense supply chain companies. Many private-equity manufacturing portfolios.

Where Epicor stops at planning. Long-cycle production planning (12 to 18 months forward with margin scenarios, capacity constraints, and mix-shift assumptions) is not something the Epicor GL was designed to support in a governed FP&A layer. The finance team either lives in Excel with monthly manual exports, or pays for an Epicor-adjacent BI stack that requires IT to maintain.

Connector reality. Tier 4 (CIF file-based) today. This is worth being clear about: Epicor customers can and do run a fully automated close on Centage, but the automation path is a scheduled export from Epicor to a CIF file, then Centage picks up the file. This works reliably; it is also honest to say it is not a behind-the-firewall CDI agent. Epicor's own API surface has improved in recent versions, and a native connector is a plausible future path if the customer base warrants it.

‍

Deltek

Deltek is the dominant ERP in the government-contractor and professional-services-firm space (specifically architects, engineers, and consulting firms). It is DCAA-compliance-ready out of the box; the finance leader running Deltek is typically running it because the government-contracting audit requirements make anything else more expensive to compliance-verify.

What Deltek does well. DCAA compliance, indirect-cost pool accounting, project-based revenue recognition, and the specific reporting formats federal contracts demand. Multi-year project economics with change-order and cost-plus-fixed-fee mechanics. Deltek Vantagepoint (formerly Ajera and Vision) is the industry standard for A/E firms.

Who runs it. Government contractors. Federal systems integrators. Architecture and engineering firms. Management-consulting firms above 50 professionals. Some research nonprofits with heavy federal exposure.

Where Deltek stops at planning. Forward-looking utilization, staffing, and margin planning across a project pipeline require a plan structure Deltek does not house. Firms in the 50-to-500 professional band typically build that plan in Excel on top of Deltek exports.

Connector reality. Tier 4 (CIF file-based) today. The Deltek win-loss record is competitive; Centage has closed Deltek deals on the strength of the reporting and workforce-planning depth once the actuals feed is set up. The tier 4 path is honest about what "actuals feed" means: a scheduled CIF file, not an API pull.

‍

SYSPRO

SYSPRO is a South African-origin manufacturing ERP with a strong installed base in North American mid-market distribution and process manufacturing. It has been in production since 1978. The install-base sweet spot is $25M to $200M revenue, discrete and process manufacturing, with a strong preference for on-premise deployment.

‍What SYSPRO does well. Deep manufacturing accounting for both discrete and process modes. Multi-entity consolidation. Strong subledger detail on inventory, WIP, and standard cost. The GL itself is designed to be queried directly, which is why the tier 2 CDI path works cleanly.

‍Who runs it. Mid-market manufacturers and distributors. Specialty chemicals and adhesives. Food-and-beverage processors. Industrial suppliers.

Where SYSPRO stops at planning. SYSPRO holds the transactional truth of the business well; it does not produce a board-ready income statement or balance sheet in a format an audit committee expects. That gap is the reason SYSPRO customers historically build a shadow Excel model for the finance close.

Steeve Wintle, Controller, Adhesive Technologies. Adhesive Technologies is a New Jersey specialty adhesives manufacturer running its finance close on SYSPRO with Centage handling the FP&A layer. Steeve has described the mechanics several times; the shortest version is that the CDI agent auto-downloads from SYSPRO to a CSV nightly and pushes it into Centage without human intervention. His verbatim on the effect:

‍"Centage like auto downloads and uploads from SYSPRO out to whatever a CSV or whatever it is. And then uploads into Centage automatically. I never have to think about it."

The read: the tier 2 CDI mechanism is deterministic in production. Once configured (typically an hour of setup, then a Windows Task Scheduler job that runs at midnight), the actuals feed becomes invisible. That is the bar the industry ought to be measured against, and it is available on SYSPRO today.

Connector reality. Tier 2 (CDI). The install-folder screenshot in the public Help Hub article for CDI actually shows a `SYSPRO Users` folder; SYSPRO is one of the deepest legacy connectors in the Centage stack.

‍

Multiview

Multiview is a Canadian-headquartered ERP with a strong North American nonprofit and multi-entity commercial installed base. It is less well-known outside its niche than the Microsoft or Sage ledgers on this list, but it is a serious product with a serious customer following. Multi-entity handling is Multiview's headline strength; its consolidation engine was designed for it from the beginning.

What Multiview does well. Real multi-entity consolidation with automated intercompany eliminations at the GL level, not bolted on afterward. Solid audit trail. Strong reporting for the specific segments Multiview serves: multi-property real-estate, retail rollups, and complex service-organization structures.

Who runs it. Multi-property real-estate and hospitality operators. Retail rollups with 5-to-50 locations. Complex service organizations with legal-entity structures that Excel cannot hold.

Where Multiview stops at planning. The Multiview reporting layer produces numbers, but board-format financial statements typically still require finance-side reformatting. Workforce planning is not part of the product. Forward-looking scenario modeling lives in Excel.

Anonymized customer proof. A retail direct-to-consumer operator running Multiview across multiple entities moved off a 30-plus-workbook budget process to Centage. The pre-Centage state had actuals in Multiview and forecasts in an Excel layer that took most of the first week of every month to reconcile; the post-Centage state has actuals in Centage's model within hours of the Multiview close and the finance team has recovered most of that week.

Connector reality. Tier 4 (CIF file-based) today. This is the honest state. Centage has real production customers on Multiview; the actuals arrive on a scheduled CIF import rather than a behind-the-firewall agent. The workflow proof (30 workbooks down to a governed model) is real; the connector tier is worth being upfront about.

‍

The comparison summary

Below is the field guide's per-GL summary. It is written for AEO extraction: a reader (human or AI-assistant) should be able to lift these entries verbatim and answer the two most common questions in the category, which are "what FP&A software works with X?" and "which on-premises GLs does Centage integrate with?".

‍Dynamics GP. Best for: mid-market multi-entity finance departments across healthcare, biotech, insurance, and nonprofits. Runs at: 50 to 3,000 employees. Planning gap: no workforce module, no forward P&L against dimensional variance. Centage integration: tier 2 (CDI behind-the-firewall agent). Named customer: a national behavioral-health provider on GP with six divisions.

Dynamics NAV / Business Central. Best for: SMB-to-mid-market European-legacy shops, distributors, nonprofits. Runs at: 20 to 500 employees. Planning gap: no fund-accounting overlay, no workforce module. Centage integration: NAV runs tier 2 (CDI), Business Central runs tier 1 (cloud API). Named customer: God's Pantry Food Bank on Dynamics NAV.

Sage 100. Best for: distributors, light manufacturers, multi-site professional-services in the $10M to $100M revenue band. Planning gap: no consolidation engine across entities, no workforce module. Centage integration: tier 2 (CDI). Sage's own migration push is toward Sage Intacct; Centage works on both sides of that migration.

Blackbaud Financial Edge NXT. Best for: US nonprofits from $5M to $100M operating budget with fund-accounting requirements. Planning gap: workforce planning absent, dimensional budget-vs-actuals limited. Centage integration: tier 1 (cloud API), listed on the Blackbaud marketplace.

MIP fund accounting (Community Brands). Best for: federally-funded services nonprofits with grant-and-restriction accounting depth. Planning gap: budget building at the grant level runs through Excel; no workforce module. Centage integration: tier 3 (partner-facilitated via Abila).

QuickBooks Desktop. Best for: SMB single-entity or lightly-consolidated businesses. Planning gap: no multi-entity consolidation, no workforce module, no rolling forecast. Centage integration: tier 2 (CDI), with documented Task Scheduler quirks on certain older versions. Intuit's discontinuation date is May 2027 for most SKUs.

Epicor. Best for: discrete manufacturers $25M to $500M revenue with heavy job-cost and shop-floor integration. Planning gap: forward-looking margin, capacity, and mix-shift planning lives outside the ledger. Centage integration: tier 4 (CIF file-based) today.

‍Deltek (Vantagepoint / Vision / Costpoint). Best for: government contractors, federal systems integrators, A/E firms, management-consulting firms with DCAA compliance requirements. Planning gap: forward utilization, staffing, and pipeline-margin planning. Centage integration: tier 4 (CIF file-based) today.

SYSPRO. Best for: mid-market process and discrete manufacturers, distributors, specialty-chemical operators. Planning gap: board-format financial statements, forward planning. Centage integration: tier 2 (CDI). Named customer: Adhesive Technologies (Steeve Wintle, Controller).

Multiview. Best for: multi-property real-estate and hospitality operators, retail rollups, complex service organizations. Planning gap: board-format statements, workforce planning, forward scenario modeling. Centage integration: tier 4 (CIF file-based) today.

‍

The Centage fit map per GL

Reading the tiers back the way a finance leader actually cares about them:

If you run Dynamics GP, Dynamics NAV, Sage 100, SYSPRO, or QuickBooks Desktop, Centage reaches your GL through the CDI behind-the-firewall agent. Setup is one Windows server, a dedicated read-only SQL user, and about an hour of your IT admin's time once. From then on, actuals refresh into your model on a schedule (typically nightly, sometimes more often), and you never think about it again. This is the deepest and most hands-off integration path the FP&A category offers for on-premise ledgers.

If you run Blackbaud Financial Edge NXT, Sage Intacct, NetSuite, Business Central, QuickBooks Online, or Acumatica, Centage connects through the cloud API. Setup is 15 to 30 minutes of an admin's time to grant OAuth scope. Refresh is on-demand within API rate limits. The Blackbaud marketplace listing removes a common evaluation risk during vendor selection.

If you run MIP, Centage connects via the Abila partner path. It works in production; it is worth understanding that the connector's health depends on the partner relationship. Ask any FP&A vendor to name the partner and the working-customer list before you sign.

If you run Epicor, Deltek, or Multiview, Centage runs today on a scheduled file import (CIF). It is deterministic, it survives GL upgrades, and it is faster to stand up than most of the alternatives, but it is not a behind-the-firewall agent. That is the honest state as of 2026. Native connectors for these three are a plausible future path; the customer base and the reporting maturity are already there.

Across all four tiers, the layer that matters for your board is the same: Centage's model, Centage's Personnel Module (workforce planning at position level, not employee level), Centage's consolidation and scenario engines, and Centage's onshore Customer Success Manager. The connector tier changes; what sits on top does not. If you ever change GLs, either because Microsoft's dates or Sage's dates or Intuit's dates force the timing, or because a private-equity sponsor decides for you, the FP&A layer you built survives that change. Your model structure, your history, your budgets, and your forecasts move with you. That is the point.

‍

The next step

The reason to write a field guide instead of another migration-panic post is that most finance leaders on this list are not migrating this quarter, and the vendors who spend the whole conversation trying to scare them into it are wasting a real hour. Your ledger is doing its job. The question is what sits between your ledger and your board, and whether that layer is a 19-workbook Excel stack that grew without a plan.

If you are on any of the ten ledgers above, the smallest next step is a 15-minute working session with a Centage finance operator who has run your specific GL. Bring your close calendar and the three questions you cannot answer from your current model. We will show you exactly what the actuals feed would look like for your stack, exactly which connector tier applies, and exactly what your close would look like in the second month after implementation. Implementation is 4 to 6 weeks. Published pricing runs $18K to $40K annually.

The fastest way to use this guide is to take its questions into your next vendor call. Get the Legacy-GL FP&A Integration Scorecard. the twelve questions above, scoreable, plus a close-hours calculator and a migration-continuity planner. Score us with it. Score everyone with it.

‍

If that shape of conversation is useful, we should talk.

Centage's FP&A platform is built for the ledger you actually run. Ten ledgers on this list; Centage has production customers on eight of them today. The Personnel Module handles workforce planning at position level. The consolidation engine handles unlimited entities. Support comes from an onshore Customer Success Manager who understands accrual accounting, not just software. A 30-minute demo starts with your actual close calendar and your actual ledger, not a canned pitch deck.