How Microsoft Dynamics GP works

Requirement evaluated: 1099 preparation and electronic filing

For a company like yours processing vendor payments across 8 legal entities, Dynamics GP's Payables Management module handles the preparation side of 1099 reporting natively: each vendor card is flagged with a 1099 tax type and box number, the system tracks 1099 amounts on individual transactions throughout the calendar year based on paid date, and the 1099 Setup window lets you configure thresholds by form type and box. At year-end, you run the 1099 Edit List for review, make corrections via the Edit 1099 Transaction Information window, and print IRS-compliant forms (1099-NEC, 1099-MISC, 1099-INT, 1099-DIV) on blank paper with lines and boxes as of GP 18.6. …

Limitations: The Taxpayer First Act now mandates electronic filing for any organization submitting 10 or more information returns, a threshold your company will far exceed; GP's native module stops at form printing and produces no IRS FIRE-compatible electronic file, so e-filing requires engaging a separate ISV (Greenshades, Aatrix …

Requirement evaluated: Multi-channel invoice ingestion (email, scan, vendor portal) with OCR/AI data extraction

For a $180M company running 8 legal entities and 2,500 invoices per month, Dynamics GP has no native multi-channel invoice capture or OCR capability. The Payables Management module requires AP staff to key invoice data manually through the Payables Transaction Entry window (Microsoft Learn, Payables Management in Dynamics GP). Multi-channel capture is available only through Mekorma Invoice Capture, a third-party ISV add-on built on Microsoft Power Platform: vendors email invoices to a dedicated inbox, Microsoft AI Builder extracts the data, and a Power Automate flow pushes it into GP where AP staff validate and batch-post (Mekorma Invoice Capture product page). …

Limitations: The mechanism stops materially short of the buyer's requirement on two dimensions: the email-only AI extraction captures only 4 header fields with no documented line-level data, which limits straight-through processing at 2,500 invoices per month; and there is no vendor portal channel for supplier-initiated invoice sub …

Requirement evaluated: Positive pay file generation for our Bank of America commercial accounts

For a multi-entity professional services company running Bank of America commercial accounts, Dynamics GP's built-in Safe Pay module (found at Financial > Routines > Safe Pay > Configurator) directly addresses positive pay file generation. After obtaining Bank of America's format specification, an AP administrator uses the Safe Pay Configurator to define the output file structure: selecting the file type (fixed-width, comma-delimited, or tab-delimited), mapping GP payment fields (account number, check number, date, amount, payee) to BofA's required field positions, and specifying character lengths, justification, and filler characters per field. …

Limitations: Dynamics GP Safe Pay does not ship with a pre-built Bank of America commercial format template; the buyer must obtain BofA's format specification document and manually configure every field mapping in the Configurator, which Microsoft documentation notes can be a lengthy setup process requiring bank validation and iter …

Requirement evaluated: 1099 preparation and electronic filing

For a professional services and distribution company processing ~2,500 vendor invoices per month across 8 entities, Dynamics GP's Payables Management module handles the preparation side of 1099 compliance natively: each vendor record is flagged with a 1099 tax type (Nonemployee Compensation/NEC, Miscellaneous, Dividend, Interest), the system accumulates year-to-date payment amounts in the Vendor Yearly Summary window on a paid-date basis, and users can print forms 1099-NEC, 1099-MISC, 1099-INT, and 1099-DIV directly from Purchasing > Routines > Print 1099, including blank-paper versions with pre-printed boxes as of the 18.6 update. …

Limitations: Electronic filing, which is now mandatory for organizations submitting 10 or more information returns, is absent from GP natively and requires a separate third-party vendor's product, reintroducing the integration and audit-trail gaps the buyer is explicitly trying to eliminate. …

Requirement evaluated: SSO via Azure Active Directory

For the buyer's scenario, a $180M multi-entity company preparing for audited financials and running Azure Active Directory (now Microsoft Entra ID) as its identity provider, Dynamics GP offers a narrow path to Entra ID sign-on, but only through its web client. To set up the Dynamics GP web components for user access using Organizational Accounts, you must register the application in your Microsoft Entra ID; for an application to use Microsoft Entra ID for sign-in and authorization, it must first be registered with Microsoft Entra ID. Once registered, a deployment where users will use an Organizational Account for access will be redirected to the Azure sign-in page. …

Limitations: Dynamics GP product support and updates will now end on December 31, 2029, and new customer sales of Dynamics GP ceased by April 1, 2025, with no new subscription licensing available. …

Requirement evaluated: SSO via Azure Active Directory

For your organization's Azure AD SSO requirement, Dynamics GP supports organizational account authentication against Microsoft Entra ID (formerly Azure AD), but only through its web client interface. The setup requires an administrator to register the GP web client as an application in Azure AD, then configure GP Utilities to use 'Organizational Account' as the authentication type and supply the Entra domain name. Once configured, users logging into the GP web client are redirected to authenticate with their Azure AD corporate credentials, providing a single sign-on experience consistent with Office 365 and other Microsoft cloud applications. …

Limitations: The Azure AD SSO mechanism is confined to the GP web client; the desktop client has no native Azure AD federation, meaning organizations with a mixed or desktop-first deployment will have inconsistent login experiences and must manage separate credentials for desktop users. …

Requirement evaluated: ADP payroll integration: automated journal entry posting after each pay run with departmental cost allocation

For a multi-entity professional services company running ADP Workforce Now, Dynamics GP addresses this requirement through its built-in 'Payroll Connect' module. After a pay run, ADP generates a comma-delimited .GLI file via its GL Interface; a user then navigates to Tools > Integrate > Import From ADP, selects the file, specifies a batch, and clicks Process. GP creates a unique journal entry and adds the ADP transactions to the specified GL batch, with account, debit, and credit fields imported directly from the ADP file. …

Limitations: Two material gaps exist for this buyer: first, the mechanism is file-import-based and user-initiated (not event-driven automation), so a staff member must manually retrieve the ADP .GLI file and trigger the GP import after every pay run, which only partially eliminates the manual effort the buyer is trying to remove. …

Requirement evaluated: Support for iPaaS platforms (Workato or Celigo) for non-native integrations

For your scenario — connecting Dynamics GP to ADP and Salesforce across 8 legal entities using your existing Workato or Celigo investment — the coverage is split and materially incomplete. On Workato: a Dynamics GP connector exists, but it is sourced from Workato's community library rather than being a vendor-certified connector. It requires deploying a Workato on-premises agent on the same server that hosts eConnect and the GP SQL Server database, authenticating via a Windows domain user with DYNGRP database role access, and calling GP's eConnect API (a COM/.NET-based interface, not a modern REST API). …

Limitations: The buyer specified Workato or Celigo as required iPaaS platforms: Celigo has no Dynamics GP connector, and Workato's GP connector is community-maintained (not vendor-certified), requires on-premises agent infrastructure co-located with the GP server, and cannot cover all GP objects via eConnect alone. …

Requirement evaluated: Self-service report builder; our controller must be able to create custom reports without IT or vendor assistance

For a controller at a company like yours running 8 legal entities, Dynamics GP offers several layered reporting tools. SmartList is included with GP and lets everyday users create real-time data queries for all master and transactional records, with the ability to add columns or shift column order without IT involvement. SmartList Designer, a free tool from Microsoft, extends this by letting users join tables to create SmartLists that cannot be built by simply adding fields to out-of-the-box SmartLists. …

Limitations: The controller can build self-service reports within a single entity using SmartList and Management Reporter, but cross-entity consolidated custom reporting requires either SQL/SSRS skills (IT-dependent) …

Requirement evaluated: Dimensional reporting across entity, department, service line, project, and location simultaneously

For a company operating 8 legal entities like yours, Dynamics GP addresses multi-dimensional reporting through two layered tools: the Analytical Accounting (AA) module and Management Reporter (MR). AA sits on top of the standard GL and lets users tag each transaction distribution line with codes from an unlimited set of user-defined dimensions (department, service line, project, location, etc.) without expanding the account string itself. …

Limitations: For your 8-entity structure, the AA-Intercompany incompatibility means dimension tags on cross-entity transactions must be manually re-entered in each destination company, undermining consistent simultaneous reporting across entity, department, service line, project, and location. …

Requirement evaluated: Scheduled report delivery (weekly flash report to leadership, monthly board package)

For a company needing weekly flash reports to leadership and a monthly board package, Dynamics GP delivers scheduled report delivery through two complementary mechanisms. First, Management Reporter (MR), GP's native financial reporting tool, supports scheduling so that report groups — including consolidated multi-entity financials drawn from all 8 GP company databases via reporting trees — are generated automatically on a daily, weekly, or monthly cadence and published to a secured Reports Library, where role-based recipients access them via links without needing to log in to GP. …

Limitations: Both mechanisms require on-premises SQL Server infrastructure to be correctly configured: SSRS email subscriptions depend on a working SQL Agent service and an authenticated SMTP relay, and Management Reporter scheduling requires the MR service to be running continuously on the server — setup complexity that a cloud-na …

Requirement evaluated: Dimensional reporting across entity, department, service line, project, and location simultaneously

For a $180M professional services and distribution company needing to slice financials simultaneously across entity, department, service line, project, and location, Dynamics GP's Analytical Accounting (AA) module is the primary mechanism. AA attaches free-floating transaction dimension codes directly to GL distribution lines at posting time, completely separate from the fixed account-string segments. …

Limitations: Because Dynamics GP maintains a separate database per legal entity, AA dimension setup must be configured consistently across all 8 company databases for cross-entity slices to produce reliable results; any inconsistency in dimension codes between entities creates reconciliation gaps in consolidated dimensional reports …

Requirement evaluated: Data migration of 3 years of transactional history from QuickBooks plus open balances

For your migration from QuickBooks Enterprise into Dynamics GP, the primary tool is Integration Manager, GP's built-in ETL utility explicitly designed for 'one-time data conversion from your existing system to Dynamics GP products.' It ingests CSV or ODBC-connected data sources and maps them to GP destination modules including journal entries, payables invoices, and receivables transactions. For high-volume or programmatic loads, eConnect provides a lower-level API that bypasses the UI and inserts records directly into GP's back-office tables. …

Limitations: GP's native GL can post back only one historical year at a time, so importing 3 full years of QuickBooks transactional detail at line level requires a staged or non-standard approach that most implementations resolve with summarized monthly journal entries rather than individual transactions, which would undermine dril …

Requirement evaluated: Chart of accounts redesign assistance; we need help rationalizing 8 divergent charts into one unified structure

For a company migrating 8 divergent QuickBooks charts into Dynamics GP, the rationalization challenge starts at the architectural level: Dynamics GP uses a single Account Framework (segment lengths and structure) defined once at installation that applies across all companies, but each legal entity runs in its own separate database with its own chart of accounts — there is no native mechanism to enforce or share a single unified COA across entities. The Microsoft documentation states explicitly that the Account Framework 'is very difficult to change later after it's set up,' making upfront design the primary point of control. …

Limitations: Dynamics GP has no native shared-COA architecture across its separate company databases, so rationalization produces parallel-but-consistent charts rather than a single authoritative structure — any account added to one entity must be manually maintained in others, recreating a lighter version of the current divergence …

Requirement evaluated: Target go-live within 6 months of contract signing

For a $180M, 8-entity professional services and distribution company migrating from QuickBooks Enterprise, a 6-month Dynamics GP go-live faces two compounding obstacles that individually disqualify it. First, Microsoft ended new subscription license sales for Dynamics GP on April 1, 2026, meaning this buyer can no longer acquire a new GP instance. Second, even if licenses were obtainable, GP is an on-premise (or partner-hosted) product requiring SQL Server provisioning, Windows Server configuration, domain accounts, and client installation before any functional setup begins. …

Limitations: New GP license acquisition for new customers closed in April 2026, making this a moot question for a net-new buyer. Even setting that aside, the GP partner ecosystem is actively contracting as consultants retrain on Business Central, reducing the available pool of qualified implementers for a rapid engagement at this o …

Requirement evaluated: Chart of accounts redesign assistance; we need help rationalizing 8 divergent charts into one unified structure

For a company rationalizing 8 divergent QuickBooks charts into a unified structure, Dynamics GP approaches this through a system-wide 'account framework' that must be designed before installation. GP Utilities is used to enter a framework for account formats that will apply to all companies in the system; the documentation specifically advises planners to consider the account format used in previous accounting systems and future expansions for additional companies. Within that shared framework, each of the buyer's 8 legal entities retains its own per-company COA (each with its own account list), but all entities must fit inside the same segment maximums. …

Limitations: The account framework is explicitly documented as near-impossible to change after setup, making COA design a one-shot, pre-installation decision; any subsequent rationalization requires expensive third-party ISV tools such as the CRG Account Reformatter. …

Requirement evaluated: Unified, segment-based chart of accounts that works across all 8 entities while allowing entity-specific sub-segments

For a company like yours with 8 legal entities, Dynamics GP uses a two-layer account structure. At installation, an administrator defines a system-wide 'account framework' that sets the maximum number of segments (up to 10) and maximum account length (up to 66 characters); this framework applies to all companies in your Dynamics GP system and represents the maximum length of your accounts, number of segments, and segment lengths. …

Limitations: The account framework is very difficult to change after you set it up using Dynamics GP Utilities, and once transactions including beginning balances have been entered, you cannot shorten the account length or reduce the number of segments: this means the segment design must be fully locked down before go-live across a …

Requirement evaluated: Unified, segment-based chart of accounts that works across all 8 entities while allowing entity-specific sub-segments

For a buyer running 8 legal entities that needs a shared account structure with entity-specific flexibility, Dynamics GP uses a system-wide 'account framework' defined at installation. The framework you enter in GP Utilities is used for the account format in all companies you plan to set up, and it establishes maximums for account length, number of account segments, and the length of each segment across every company in the instance. This framework applies to all companies in the GP system and represents the maximum length of accounts, number of segments, and segment lengths; GP imposes an absolute limit of 66 characters and 10 segments. …

Limitations: The account framework is very difficult to change after it is set up, so the buyer must design their full segment structure (covering all 8 current and any future entities) correctly before implementation. …

Requirement evaluated: Period-close controls that prevent posting to closed periods while allowing adjustments with proper authorization

For a company like yours pursuing audited financials across 8 entities, Dynamics GP uses a Fiscal Periods Setup window (Tools > Setup > Company > Fiscal Periods) where each period can be marked closed per module series: GL, AP, AR, Payroll, and others independently. Once a period is marked closed for a series, the system hard-blocks posting to that period for that series; as Microsoft's GL year-end documentation confirms, 'after a period is marked as closed, transactions can't be posted to the period unless you reopen the period.' For authorized prior-period adjustments, GP provides two mechanisms: (1) …

Limitations: For a company preparing for its first audit, the absence of a formal approval workflow for period reopening is a material gap: an auditor will want documented evidence of who authorized each prior-period entry and why, and Dynamics GP's mechanism relies on restricting access to an administrative setup window rather tha …

Requirement evaluated: Unified, segment-based chart of accounts that works across all 8 entities while allowing entity-specific sub-segments

For a company with 8 legal entities like yours, Dynamics GP handles multi-entity chart of accounts through its Account Framework architecture. At installation time, an administrator uses Dynamics GP Utilities to define a system-wide framework: the account framework applies to all companies in your Dynamics GP system, and represents the maximum length of your accounts, number of segments, and segment lengths. This framework allows a maximum account length of up to 66 characters and up to 10 account segments, which can be designated to represent natural account, entity, department, location, or any other dimension. …

Limitations: The critical shortfall for your 8-entity scenario is that GP has no single shared master chart of accounts: each entity's COA lives in a separate company database and must be manually replicated and synchronized across all 8 entities, recreating the manual maintenance burden your team is trying to escape. …

Requirement evaluated: Real-time consolidated financial statements (not batch/overnight)

For a $180M company running 8 legal entities across the US and Canada, Dynamics GP offers two native paths toward consolidated financial statements, neither of which delivers the real-time, on-demand experience the buyer requires. The first path is the Intercompany Processing module: when using Intercompany Processing, users post transactions across companies and can print consolidated financial statements. However, this is a transaction-posting mechanism, not a live roll-up. …

Limitations: The native period-consolidation routine in GP is a destructive batch process: once consolidation is complete, detailed transactions are no longer available for reporting or inquiry, and a single total replaces per-transaction detail. …

Requirement evaluated: Shared services model: centralized AP team processes invoices for all entities with proper entity coding

For a $180M company running 8 legal entities, Dynamics GP's Intercompany Processing module allows a centralized AP team to enter vendor invoices in a single 'originating company' database, then distribute expense amounts to one or more 'destination companies' by entering a Co. ID field in the Payables Transaction Entry Distribution window. The system automatically generates balanced due-to/due-from GL entries between entities, so each company's books remain segregated. …

Limitations: The buyer's centralized AP team will face two material gaps: first, destination entities receive only a GL journal entry, not an AP payable, so vendor sub-ledger aging and payment runs must originate from the single originating company rather than being managed at the entity level; second, after originating-company pos …

Requirement evaluated: Shared services model: centralized AP team processes invoices for all entities with proper entity coding

For a company running 8 legal entities like this buyer, Dynamics GP separates each entity into its own company database. Users are granted access to multiple company IDs via the User Access Setup window, and when logging in they select which company context to operate in. The Intercompany Processing module then allows an AP clerk, while logged into the originating company (e.g., the central AP entity), to open the Payables Transaction Entry window, mark the Intercompany checkbox, and assign individual distribution lines to a destination company ID — selecting accounts directly from that destination company's chart of accounts. …

Limitations: For this buyer's 8-entity structure, the AP team must still log into each destination company's database to post the pending intercompany GL batches after the originating entry is made, and dimensional coding (Analytical Accounting) …

Requirement evaluated: Real-time consolidated financial statements (not batch/overnight)

For a $180M company with 8 legal entities needing real-time consolidated financials, Dynamics GP faces a structural ceiling. GP maintains separate SQL databases per legal entity, meaning there is no shared ledger that can produce a consolidated view by querying live OLTP data. Consolidated financial statements are generated through Management Reporter (MR), which uses a dedicated data mart database (ManagementReporterDM) …

Limitations: The 2-minute data mart polling lag falls short of true zero-latency real-time consolidation, and the separate-company-database architecture means intercompany eliminations require manual setup rather than automatic on-post generation, which directly extends the buyer's current 12-day close problem. …

Requirement evaluated: Automated invoicing with configurable templates per entity/service line

For a company running 8 legal entities, Dynamics GP delivers entity-level invoice template isolation through its native multi-company architecture: each legal entity lives in its own company database, and Word Templates (built on Report Writer definitions) are assigned per company via the Report Template Maintenance window's 'Assign >> Company' function. An administrator selects the SOP Blank Invoice Form, clicks Assign, highlights the target company, and sets that template as the default for that entity. …

Limitations: Each of the buyer's 8 company databases must be configured and maintained independently: there is no centralized template management hub, so a branding or terms change must be replicated manually across all 8 entities. …

Requirement evaluated: Revenue recognition support for our service contracts (milestone and time-based billing)

For a professional services company running milestone and time-based service contracts, Dynamics GP's Project Accounting module provides multiple documented revenue recognition methods: for Time and Materials projects, revenue can be recognized either 'When Performed' (as cost transactions are posted) or 'When Billed' (when the billing invoice posts, with costs held in WIP until then); for Fixed Price and Cost Plus projects, a Revenue Recognition Entry routine supports percentage-complete calculations based on costs incurred, quantities consumed, or direct labor hours, using the formula (Actual to Date / Forecast Total) * Forecast Billing Amount. …

Limitations: For this buyer's specific goal of audited financials within 12 months under ASC 606, Dynamics GP's native revenue recognition does not automate the five-step performance obligation model: industry practitioners have documented that GP users must take complex recognition calculations outside the ERP and re-enter them as …

Requirement evaluated: Credit limit management by customer

For a professional services and distribution company needing per-customer credit control, Dynamics GP delivers this natively across two integrated modules: Receivables Management and Sales Order Processing. A credit limit is assigned individually on each Customer Maintenance Options card with three settings: None, Unlimited, or a specific dollar Amount. You can set a credit amount for a customer and mark whether that customer has no credit, an unlimited amount of credit, or a specified credit limit; if you select Amount, you must enter the dollar figure being extended to that customer. …

Limitations: Dynamics GP is a legacy on-premises product that Microsoft has committed to maintaining through at least 2031 but is no longer actively developing; the buyer's push toward audited financials and multi-entity consolidation is better served by a cloud ERP, and GP's credit limit hold reporting and centralized hold-list vi …

Requirement evaluated: Customer portal for invoice access and online payment

For a $180M professional services company preparing for audited financials and needing customers to self-serve invoices and pay online, Dynamics GP offers no native mechanism to deliver this. The Receivables Management module documented at learn.microsoft.com covers only internal staff-facing workflows: applying cash receipts, aging customer balances, printing statements, and running AR inquiries. There is no customer login, no external-facing portal, and no payment gateway integration built into the base product. …

Limitations: There is no native Dynamics GP customer portal for invoice access or online payment at any tier; the buyer must procure, implement, and maintain a separate ISV solution, adding integration complexity, additional licensing cost, and a dependency on a third-party vendor roadmap layered on top of a platform Microsoft has …