Infor CloudSuite vs Odoo vs QB Desktop for ERP & Core Accounting

For a company like yours -- running 8 legal entities through a patchwork of manual controls and seeking audit-ready financials -- Infor CloudSuite's General Ledger module (documented in both the Infor LN Financials and Lawson/CloudSuite Financials lineages) delivers a three-tier period status system enforced at the GL level. Periods carry one of three statuses managed in the Period Status session (tfgld0107m000): 'Open' (transactions permitted), 'Closed' (no new transactions, but an authorized user can reopen the period for final adjustments by changing its status back to Open), and 'Finally Closed' (permanent hard lock -- no transactions can ever be entered and the status cannot be reversed). Separately, the Lawson/CloudSuite Financials variant (GL199) exposes the same duality as 'Limited Close' (reopenable for additional posting) versus 'Final Close' (irreversible). Period statuses are set independently per module type -- General Ledger (GLD), Accounts Payable (ACP), Accounts Receivable (ACR), and Integration (INT) -- so your controller can close AP while the GLD correction period remains open for adjustment journal entries. For entities that need authorized posting to already-closed periods without a full reopen, Infor LN provides the Requested Exceptions for Integration Transactions session (tfgld4585m000): a user submits a request, an authorized approver reviews and approves it, and only then can the transaction be logged and posted to the closed period. Access to the AccountingPeriods object itself is secured through role-based authorization in the AccountAuthorizations table, meaning only users or groups explicitly granted that privilege can change period status -- standard accounts payable clerks cannot reopen a period on their own. Period status can also be managed per financial company, meaning each of your 8 entities can be closed independently.

For a company like yours closing 8 entities and preparing for an audit, Odoo's Accounting module provides a tiered Lock Date system configured under Accounting > Accounting > Lock Dates. The first tier is a 'Lock Date for Non-Advisers' (soft lock): standard users not in the Accounting/Invoice Setup group are blocked from posting to the locked period, while users in the all-users lock tier face the same restriction across the board. The second tier is a 'Lock Everything' date that ensures journal entries with an accounting date on or before the lock date cannot be created or modified during the audit. A third, irreversible 'Hard Lock' date exists for permanent inalterability. When a legitimate adjustment is needed after the Lock Everything date is set, users with Administrator access rights can create an exception, specifying whether it applies to just themselves or everyone and how long it should last, with a Reason field available to document the purpose. All of this information is logged in the chatter of the company record, providing the documented audit trail your auditors will expect.

For a $180M, 8-entity company pursuing audited financials, QuickBooks Desktop's period-close control centers on a single 'Closing Date' with an optional shared password, configured via Edit > Preferences > Accounting or Company > Set Closing Date. Once set, any user who attempts to post to a period on or before that date is prompted for the password before the transaction saves; without the password, they receive a warning but the system does not hard-block the entry. There is no tiered soft/hard close, no per-user or per-role authorization workflow, and Intuit's own support documentation confirms: 'setting up the user's permission to edit closed transactions in QuickBooks isn't available yet' and 'there is only one password' shared across all users. Changes made to closed periods after the fact are captured in the Closing Date Exception Report (Reports > Accountant & Taxes), which logs who changed what and when, providing a reactive audit trail. QuickBooks Enterprise adds a separate user-level 'Edit Closed Transactions' permission that can restrict which users are even allowed to enter the shared password, adding one layer of role-based gating, but the underlying override mechanism remains a single shared credential with no approval chain or documented authorization reason.

For a $180M professional services and distribution company migrating off QuickBooks Enterprise and targeting audited financials within 12 months, Infor offers a named human contact through two complementary mechanisms. First, Infor's current CareFor Success flagship support program assigns a Customer Success Executive (CSE) to each enrolled customer: Infor describes CSEs as 'dedicated advisors within CareFor Success, Infor's flagship customer support program' who provide 'strategic guidance and personalized support for your Infor CloudSuite solution' and who 'resolve roadblocks that may slow your progress' throughout the engagement. Second, Infor's legacy Xtreme Support program (still referenced across Infor's support infrastructure) defined an Xtreme Elite tier that includes 'an assigned Xtreme Elite Account Manager' described as 'dedicated to help resolve issues and deliver customer satisfaction,' with each manager covering 8-10 accounts. Infor's AWS Marketplace listing also commits to 'dedicated Customer Success Partners' ensuring 'continuous adoption and measurable value beyond go-live.' The CareFor Success program sits above the base support subscription and is purchased as a flagship plan add-on.

For a $180M, 8-entity company migrating from QuickBooks and targeting audited financials, Odoo's answer to dedicated support is the 'Success Pack': a pre-purchased block of consulting hours through which Odoo assigns a named project manager and functional consultant to the buyer's implementation. Per Odoo's own pricing configurator, 'you are assigned an expert to provide unique personalized assistance to help you customize your solution and optimize your workflows as part of your initial implementation.' Odoo's pricing-packs page confirms this consultant conducts planned sessions (phone or online) covering requirements analysis, configuration, training, and coaching. However, the same page notes these hours expire after one year, and Odoo S.A. directly focuses the pack on 'standard configuration and coaching via remote sessions'; the named-contact relationship is bounded by the pack's finite hours, not a standing annual commitment. Once hours are consumed the named contact lapses unless additional packs are purchased, and Odoo's baseline Enterprise subscription support reverts to ticket-based access with no named contact.

For a company of your profile spanning 8 legal entities across the US and Canada, QuickBooks Desktop Enterprise's premium support offering is called Priority Circle, which is bundled at no extra charge with all Enterprise subscription tiers. Intuit describes Priority Circle as 'a direct line to top-tier QuickBooks support agents' accessible by phone or chat, with callback and screen sharing options. This is a priority-access agent pool, not an assigned named contact: Intuit's own documentation consistently describes the mechanism as connecting callers to 'top-tier agents' rather than committing to a specific, named individual. A thread on the official QuickBooks Community forum, confirmed by a user quoting their former Priority Circle manager directly, states that 'Intuit has disbanded Priority Circle and there is no longer a dedicated agent to your account.' Intuit's moderator response in that thread redirected to standard phone and in-product help channels without contradicting this. Intuit did announce a separate Account Management Program in May 2024 for selected customers with complexity and growth trajectory, but that program is invitation-only and directed at accounting partners' clients, not a structured mechanism a buyer can request or purchase.

For a $180M multi-entity operation preparing for audited financials, Infor CloudSuite's AP module handles 1099 preparation and electronic filing natively within the ERP, with no need for a separate third-party filing vendor. In the vendor master, each supplier is flagged as '1099 Reportable' at the payment distribution level, and a Federal ID (TIN/EIN) is required on the Vendors form before any 1099 form can be generated. The system automatically accumulates qualifying paid-invoice amounts throughout the year and applies IRS minimum thresholds (defaulting to $600, configurable) per vendor. At year-end, the controller runs the 1099 Form Printing Report to generate forms covering 1099-MISC, 1099-NEC (non-employee compensation), interest income, dividends, government payments, merchant card, and foreign-person income types, selecting either paper or electronic output. For electronic filing, the AP146 (1099 Tape Creation) program produces a flat file formatted to IRS Publication 1220 specs, which is uploaded directly to the IRS filing system. The 'Reportable Income Group' construct (AP02.1) lets your team group companies and process levels across your 8 legal entities under a single tax identification number for consolidated 1099 reporting, which directly addresses your multi-entity consolidation challenge. Infor conducts an annual review of IRS bulletins to update the 1099-MISC and 1099-NEC magnetic media output, as documented in release notes.

For a company already running QB Desktop across 8 legal entities, 1099 preparation uses the built-in 1099 Wizard (Vendors > 1099 Forms > Print/E-file 1099 Forms). The wizard walks through vendor selection, maps expense accounts to the correct 1099 boxes (NEC Box 1, MISC boxes, etc.), automatically excludes ineligible payment types such as credit card, debit card, and PayPal, and checks IRS thresholds. Once forms are reviewed, the controller selects the E-file button, which imports the prepared data directly into a Tax1099 account — Intuit's integrated e-filing partner — where federal and eligible state filings are submitted electronically and filing status is tracked. Recipient copies can be emailed or mailed through Tax1099 as well. E-filing carries a per-form fee through Tax1099, but the mechanism is fully accessible to any buyer willing to pay it, and the data flows from QB Desktop into Tax1099 automatically rather than requiring manual re-entry.

For a company like yours moving off QuickBooks and toward audited financials, Odoo does cover the preparation side of the 1099 workflow natively. Vendor records include a '1099 Box information' field (documented in Odoo's Contacts module across v15 through v19) for classifying each supplier, and the `1099 Reporting (l10n_us_1099)` module -- part of the US localization -- adds a report wizard under Accounting > Reporting > Management: 1099 Report. A user selects a date range, reviews and edits the qualifying journal items, and clicks Generate to download a CSV grouped by partner. However, Odoo's own documentation is explicit that this CSV is intended 'to file electronically via a third-party service': there is no direct IRS FIRE or IRIS portal submission built into Odoo. The electronic filing step requires the buyer to take the exported CSV into a separate, externally sourced e-filing service, which introduces a manual handoff and a reconciliation gap that your audit-readiness goal is specifically trying to eliminate.