Business Central vs NetSuite vs Dynamics GP for ERP & Core Accounting

For a $180M professional services company managing 8 legal entities across the US and Canada, NetSuite OneWorld delivers automated dual-sided intercompany posting through three complementary mechanisms. The primary mechanism is the Advanced Intercompany Journal Entry: a user selects an originating subsidiary (Entity A) and one or more receiving subsidiaries (Entity B), enters the debit and credit lines, and upon saving, the system simultaneously posts to the ledger of each involved subsidiary. As documented in the OneWorld help center, 'when you save the journal entry, the ledger of each subsidiary is appropriately debited and credited.' For recurring shared-cost allocations (e.g., shared rent, overhead), Intercompany Allocation Schedules automate this further: at each scheduled run, NetSuite automatically creates an advanced intercompany journal entry for each destination subsidiary and posts the appropriate amount to the specified account, requiring no manual initiation per period. For service-billing scenarios where Entity A charges Entity B for services rendered, the Intercompany Framework's Cross Charge Generation feature produces paired transactions automatically: 'NetSuite generates one transaction for the selling subsidiary, and one for the buying subsidiary,' creating open intercompany payable and receivable balances that are audit-native. Period-close elimination of intercompany balances is handled by the Automated Intercompany Management feature, which automatically generates elimination journal entries during the period close process, directly addressing the buyer's controller's 12-day close driven by manual eliminations.

For a $180M professional services company with 8 legal entities, Business Central's native Intercompany (IC) Partner framework is the relevant mechanism. Each entity pair is linked via an IC Partner Code assigned to the corresponding customer or vendor record; once configured, all orders and invoices for transactions between these companies produce corresponding documents in the partner company, resulting in correctly balanced accounts. The dual-entity flow works through an IC Inbox/Outbox pipeline: depending on your intercompany setup, some transactions are automatically handled; you can set up the source company and partner companies to automatically create documents and journals that correspond to transactions that partners post through the intercompany general journal. When all entities share the same Business Central database (standard for a single-tenant multi-company deployment), the partners can automatically accept transactions, going directly to the Handled Intercompany Inbox Transactions and Handled Intercompany Outbox Transactions pages. Setup requires enabling two toggles: for the synchronization partner, on the Intercompany Setup page, turn on the Auto. Send Transactions toggle; for partner companies, on the Intercompany Partner page, turn on the Auto. Accept Transactions toggle. The critical limitation is that Auto Accept stops short of a fully touchless post: on the Intercompany Partner page, turn on the Auto Accept Transactions toggle — the journal lines are created for you, but not posted. The sending entity's side posts normally when Entity A books its transaction; the receiving entity's journal is auto-created and pre-populated, but a human must still execute the post action in Entity B's books. This is materially better than the buyer's current QuickBooks spreadsheet workflow (no re-keying, no manual construction of both sides), but it does not satisfy the buyer's stated requirement that 'both sides should post automatically' without any manual intervention.

For a $180M, 8-entity company needing both sides of an intercompany transaction to post automatically, Dynamics GP offers a native Intercompany Processing module that partially delivers. A user enters a transaction in the Originating Company (via Payables Transaction Entry or General Ledger Transaction Entry), marks the Intercompany flag, and assigns distributions to one or more Destination Companies using pre-configured Due To/Due From accounts. Once you post an intercompany transaction from the GL in the Originating Company, a matching journal entry will be created in the Destination Company. This allows you to create the whole entry in Entity A without having to go into Entity B to manually create that portion, with Intercompany Processing automatically using the Due To and Due From accounts in both the Originating and Destination Companies. However, the destination-side entry is created as an unposted GL batch, not as a posted transaction. During the intercompany posting process, the destination company entries are sent to the destination companies, but not posted; you have to log in to each destination company to post them. Intercompany transactions posted to the destination company appear in the destination company's journal entry area for review before posting through to General Ledger. This two-step process is also confirmed for void scenarios: the only entries that are backed out automatically are those in the originating company, and you must make adjustments manually in destination companies.

For a $180M multi-entity professional services and distribution company needing to slice financials across entity, department, service line, project, and location simultaneously, Business Central uses a Dimensions framework where each GL entry carries independent dimension codes as tags rather than separate accounts. Dimensions are values that categorize entries so you can track and analyze them on documents such as sales orders; they can indicate the project or department an entry came from, and instead of setting up separate GL accounts for each department and project, you can use dimensions as a basis for analysis and avoid a complicated chart of accounts structure. The system supports up to 2 Global Dimensions and up to 8 Shortcut Dimensions per transaction: you can set up two global dimensions and eight shortcut dimensions, and you choose the dimensions you use most frequently. The two global dimensions receive first-class treatment: the two global dimensions differ from other dimensions because you can use them as filters anywhere in Business Central. Beyond global dimensions, you can use global and shortcut dimensions as filters on reports, batch jobs, ledger entry pages, and analysis views. For multi-dimensional analysis, the Financial Reports feature (formerly Account Schedules) provides a row/column matrix builder: on the Dimensions FastTab, you can define dimension filters for the report. The Analysis Views module goes further: by using more than two dimensions when you create an entry, you can carry out a more complex analysis, for example exploring sales per sales campaign per customer group per area. Consolidated cross-entity reporting flows through Business Central's consolidation company feature: after the batch job runs, all entries in general ledger accounts are processed, and for every combination of selected dimensions and date, the contents of the entries' Amount fields are totaled and exported.

For a $180M professional services company operating across 8 legal entities in the US and Canada, NetSuite maps the buyer's five required dimensions almost one-to-one to native segment fields: Subsidiary (entity), Department, Class (service line), Location, and Customer/Project. Each transaction carries all active segment codes at the line-item level with full GL impact, so every AP invoice, journal entry, and revenue transaction is simultaneously tagged across all five axes. Within the Financial Report Builder, income statements and balance sheets can be filtered and grouped by any combination of class, department, location, and subsidiary, with the 'View Columns By' list enabling persistent matrix columns for a chosen dimension and 'Group By / Then By' supporting two levels of nested row grouping within a section; the Customer/Project axis is available as a Group By option in financial statement sections as well. If the buyer uses Class for service line and needs project as a separate axis, a Custom Segment can be created with GL impact and added as a horizontal dimension in financial reports via the same 'View Columns By' mechanism, with no SuiteApp required. Consolidated views across all 8 entities are delivered through NetSuite OneWorld's Subsidiary Context (Consolidated) footer control, which rolls all child subsidiaries into a single report while preserving the ability to slice by department, class, or location within that consolidated view.

For this $180M, 8-entity professional services company that needs simultaneous reporting across entity, department, service line, project, and location, Dynamics GP offers two intra-entity dimension mechanisms: (1) account segment structure, where the GL account number itself encodes dimensions such as department or location as embedded segments (up to 10 segments, max 66 characters per account number, set at installation and very difficult to change later), and (2) the Analytical Accounting (AA) module, which allows users to tag GL distributions with unlimited transaction dimension codes — such as Cost Centre, Profit Centre, or Project — independently of the account string. Analytical Accounting is described in official documentation as a tool to 'analyze, interpret, and create reports based on your company's chart of accounts' that lets users 'enter detailed analysis information without resorting to segmental accounting' and supports 'unlimited analysis dimensions.' Within a single entity, users can 'generate multilevel queries based on your specific requirements and transaction dimensions' and 'create queries based on columns that you choose to display.' SmartLists and Excel Reports for AA display each dimension as a separate column, enabling pivot-table analysis across dimensions like Cost Centre and Project simultaneously. However, the buyer's requirement spans 8 legal entities, and with Dynamics GP, each entity runs in a separate database — meaning AA dimension codes are scoped per company and do not natively cross entity boundaries in a single report. Third-party analysis confirms that 'Dynamics GP on its own is not built to handle the complexity of multi-companies' for consolidated reporting, and achieving cross-entity dimensional slice reporting requires either Management Reporter report trees (which aggregate entity totals but do not expose sub-entity AA dimension slicing within a consolidated view) or export to Excel/Power BI. The account segment approach introduces the additional anti-pattern risk: the account framework 'represents the maximum length of your accounts, number of segments, and segment lengths' and 'is very difficult to change later after it's set up,' making it brittle for expanding dimensional needs across 5 axes.

For a company processing 2,500 vendor invoices monthly across 8 entities, Business Central's native mechanism centers on the Incoming Documents framework, which serves as the AP ingestion queue. PDFs or image files received from vendors can be sent to an external OCR service from the Incoming Documents page; alternatively, some OCR providers process files forwarded to a dedicated email address, automatically creating an incoming document record in BC. Incoming document records can also be created directly from vendor emails using the Outlook add-in. For scanned documents, users can upload received files or use a mobile device camera to create entries representing external documents. Once the OCR service returns structured data, the conversion to a purchase invoice can be triggered manually or via an included workflow template, 'From Incoming Electronic through OCR to Open Purchase Invoice Workflow.' A critical ceiling applies, however: the OCR feature is provided by external providers, and organizations must choose a compatible service package from the Microsoft Marketplace. This means native BC does not embed its own AI extraction engine for unstructured PDFs. Additionally, when converting OCR documents to journal lines or purchase invoices, multiple lines on the source document are summed to a single line, with Description and account number fields left empty. The vendor portal channel (suppliers submitting invoices directly into an AP queue) is not a native BC feature; it requires a third-party ISV add-on from the AppSource ecosystem.

For a $180M professional services and distribution company migrating from QuickBooks Enterprise and processing 2,500 vendor invoices per month, NetSuite addresses two of the three required ingestion channels natively via a separately licensed add-on. The core mechanism is Bill Capture, which uses Oracle Cloud Infrastructure's Document Understanding large multimodal model (LMM) to extract header and line-level data from vendor invoice PDFs, JPEGs, and PNGs. Using Bill Capture, invoices can be emailed or uploaded to create NetSuite vendor bills, minimizing data entry effort, and the system learns from user corrections over time to improve extraction accuracy. Bill Capture leverages Oracle Cloud Infrastructure (OCI) Document Understanding Custom Generative Model to intelligently extract key values from vendor bills. The email channel is handled separately: the Bill Capture email capability is implemented through the Transaction Email Capture SuiteApp, which must be installed alongside the AP Automation license. On the third channel, NetSuite does include a Vendor Center: the Vendor Center role gives vendors access to view, search, and print purchase orders and reference order and payment history. Third-party NetSuite partner documentation describes the Vendor Center as supporting invoice submission that creates a vendor bill in Pending Approval status linked to the corresponding PO, but for invoice automation beyond basic vendor visibility, most organizations use customized workflows or third-party solutions rather than relying on the standard Vendor Center alone. The glass ceiling is this: Bill Capture (email and upload channels) requires the AP Automation add-on license, and the basic NetSuite vendor portal is an add-on offered through the NetSuite Procurement module. Organizations that need high-volume, touchless processing with robust supplier portal invoice submission (true structured inbound entry without OCR dependency) typically layer a certified third-party solution such as Stampli, Tipalti, or Medius on top of NetSuite.

For a $180M multi-entity company processing 2,500 vendor invoices per month with a 12-month audit-readiness deadline, Dynamics GP's native Payables Management module provides no OCR, AI extraction, email ingestion, or vendor self-service portal. The module is a manual transaction-entry system: a user opens the Payables Transaction Entry window, keys in vendor, invoice number, amount, and GL distributions, and posts to the ledger. Payables Management allows users to maintain vendor information, enter and post purchase transactions, and track payments to vendors — there is no capture stage at all. The closest feature in the native product is the Document Attachment capability introduced in GP 2015, which allows a user to enter a payables invoice, scan it and attach the record from the vendor, and then submit the invoice for approval — but this is image-attachment to a manually-keyed record, not OCR field extraction, and it does not satisfy multi-channel ingestion. Every ISV in the GP ecosystem (Rillion, Fidesic, MetaViewer, MineralTree, EchoVera, DocStar) explicitly exists to fill this gap: Microsoft Dynamics GP provides core payables processing and workflow approvals; Rillion extends GP with AI invoice capture and auto coding, flexible approvals, automated 3-way PO matching, and payment automation. Even with an ISV layered on, GP itself is on a sunset trajectory: new perpetual license sales ended April 1, 2025; new subscription license sales end April 1, 2026; and all product enhancements, regulatory updates, and technical support end December 31, 2029. Microsoft is making no new AP automation investments in GP.

For this $180M professional services and distribution company replacing QuickBooks Enterprise, NetSuite delivers customer portal functionality through two native mechanisms. First, the Customer Center role gives each customer a dedicated login where, once the administrator enables 'Customer Access' under Web Presence and 'Customers Can Pay Online' under Payment Processing, customers can view all their transactions and pay open invoices directly inside the NetSuite-hosted portal. Second, the Payment Link and Direct Invoice Payment features allow invoices to be emailed with an embedded link that takes the customer to a branded payment page without requiring a full portal login. The richer self-service experience is delivered through SuiteCommerce MyAccount (SCMA), a dedicated self-service web portal where customers can manage account information, view recent transactions, and pay invoices; SCMA requires a separate license. Payment is recorded in NetSuite automatically, updating the invoice status and AR ledger in real time. For this buyer's 8-entity OneWorld environment, customers can be shared across subsidiaries, and the Customer Payment page correctly routes AR postings to the appropriate subsidiary.

For a $180M professional services company expecting customers to self-serve invoices and pay online, Business Central's native mechanism is an emailed payment link rather than a persistent portal. When a posted sales invoice is emailed, Business Central embeds a PayPal link in the email body and attached PDF; the customer clicks it, is redirected to PayPal's hosted payment page, and Business Central automatically posts the entry and closes the AR document via PayPal Instant Payment Notification when payment is confirmed. However, Business Central does not ship a native customer-facing login portal: there is no persistent customer account where buyers can browse invoice history, download prior invoices, or select multiple open invoices to pay simultaneously. The PayPal Payments Standard extension handles the payment gateway writebacks natively, but the WorldPay Payments Standard extension is being deprecated. Reaching a true self-service portal requires either AppSource ISV add-ons (such as iPayments/iSolutions, EBizCharge, or Kapittx, all of which write payments back to the BC AR subledger) or a custom build via Microsoft Power Pages connected to Business Central data via APIs.

For a $180M professional services company pursuing audited financials within 12 months, Dynamics GP offers no native customer-facing portal for invoice access or online payment. The GP Receivables Management module is entirely internal-facing: it handles payment application, aging, and customer inquiry windows used by AR staff, but exposes no self-service web interface to customers. The historical 'Business Portal' was a legacy SharePoint-based add-on that has not received active development for years and does not constitute a modern payment portal. Any customer portal capability requires separately licensed third-party ISVs: EBizCharge Connect, for example, syncs GP invoices to a bill-pay portal where customers can view and pay invoices, with payments writing back to GP AR automatically; Paygration offers a similar branded portal where 'paid invoices are automatically updated in Microsoft Dynamics GP, eliminating manual reconciliation.' DynamicPoint provides a SharePoint-based B2B portal tied to GP data. None of these are included in the GP base product, and all require separate procurement, implementation, and ongoing maintenance.