How Acumatica works

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

For a controller managing 8 legal entities and preparing for audited financials, Acumatica's financial period controls operate through a four-status system managed on the Manage Financial Periods screen (and optionally via a Centralized Period Management feature that governs all entities from a single master calendar). Every financial period carries one of four statuses: Inactive, Open, Closed, or Locked. The 'Closed' status acts as a role-gated barrier: if the 'Restrict Access to Closed Periods' checkbox is selected on the General Ledger Preferences form (GL102000), only users assigned to the Financial Supervisor role can post transactions to closed periods. …

Limitations: Authorized posting to a closed period is controlled by role assignment (Financial Supervisor), not by a per-transaction approval workflow or documented reason code; there is no built-in mechanism requiring a supervisor to formally justify each closed-period entry before it posts, which may require process discipline ra …

Requirement evaluated: Real-time GL posting; we cannot accept batch-only posting

For a professional services and distribution company moving off QuickBooks Enterprise, Acumatica's GL posting architecture centers on a per-document 'Release' action rather than a nightly batch run. When an AP bill, AR invoice, or GL journal entry is released, Acumatica can post it to the general ledger immediately if the 'Automatically Post on Release' setting is enabled. This checkbox lives in the General Ledger Preferences (GL102000) form and has a parallel setting in both AP Preferences and AR Preferences, so the behavior applies consistently across all transaction types. …

Limitations: The default out-of-box configuration may not have 'Automatically Post on Release' pre-enabled across all modules; the implementation team must explicitly activate it in GL, AP, and AR Preferences to ensure consistent real-time behavior. …

Requirement evaluated: Real-time GL posting; we cannot accept batch-only posting

For a company moving off QuickBooks and needing a GL that reflects current balances at all times, Acumatica's posting architecture works as follows: every AP bill, payment, or journal entry passes through a 'Release' action, which creates a GL batch. Whether that batch posts to the GL immediately or sits in a queue depends on a single configuration switch. In AP Preferences (and equivalent Preferences screens for AR and other sub-ledgers), the 'Automatically Post on Release' checkbox, when enabled, commits the GL batch to the ledger at the moment the Release action fires, with no separate manual step or scheduled job required. …

Limitations: The 'Automatically Post on Release' setting is a configurable toggle that can be inadvertently disabled; Acumatica's own community forums document cases where it was turned off and transactions silently accumulated as 'Unposted' until a manual or scheduled Post Transactions run cleared them, so access to the AP Prefere …

Requirement evaluated: Support for multiple fiscal calendars (our Canadian entities have a different fiscal year-end)

For a company with US and Canadian entities on different fiscal year-ends, Acumatica addresses this through its named 'Multiple Calendar Support' feature, enabled on the Enable/Disable Features (CS100000) form. When 'Multiple Calendar Support' is disabled, all companies share a single master calendar; when it is enabled, financial years are generated separately for each company, and the system generates corresponding years in the master calendar automatically. Each legal entity (configured as a separate 'Company' in Acumatica) maintains its own Company Financial Calendar (GL201100), with an independent fiscal year start and year-end date. …

Limitations: Users configuring multi-calendar tenants have reported period-mapping friction at consolidation: when one company runs April-to-March and another January-to-December, period mismatches arise and must be resolved by mapping posting periods between entities. …

Requirement evaluated: Dedicated support contact (not ticket-only) during the first year

For a $180M professional services and distribution company moving off QuickBooks Enterprise, Acumatica's support model operates on two distinct layers. First, your local VAR partner supports you through ERP implementation to go-live and beyond, with personalized support guaranteed through the partner relationship. Second, Acumatica's Direct Customer Support program complements partner support by giving you access to technical resources, troubleshooting, and product experts, with two plan tiers: Basic and Premier. …

Limitations: Training, consulting, and implementation services are explicitly excluded from Acumatica's direct support plans, with Acumatica directing customers to their partner for these services. …

Requirement evaluated: Dedicated support contact (not ticket-only) during the first year

For a $180M professional services and distribution company moving off QuickBooks Enterprise, the closest analog to a dedicated support contact in Acumatica's model lives at the VAR layer, not the Acumatica platform layer. Acumatica sells and implements exclusively through a 100% channel model: all licensing, implementation, and ongoing support flow through a certified Value Added Reseller (VAR) partner, not Acumatica directly. During implementation and the first year, the VAR assigns its own project consultants and, in many cases, a named account manager or success manager who owns the relationship. …

Limitations: Whether a dedicated named contact is included depends entirely on which VAR the buyer selects and what terms they negotiate in the implementation contract: Acumatica itself makes no platform-level commitment to a dedicated contact for end customers, so a buyer who chooses a smaller or less structured VAR may receive on …

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

For a company migrating 8 QuickBooks entities with divergent charts into Acumatica, CoA rationalization is not optional: Acumatica's architecture enforces a single, shared chart of accounts across all companies within one tenant, so the buyer's 8 charts must be consolidated into one unified structure before or during implementation. The platform provides concrete tooling for this work: the Chart of Accounts form (GL202500) supports bulk import and export via Excel, allowing the implementation team to build the unified account list and map legacy codes to new ones; the trial balance import tool (GL303010) …

Limitations: The quality and depth of CoA rationalization assistance varies by VAR partner, as Acumatica does not deliver this consulting directly; the buyer should explicitly evaluate prospective VARs for multi-entity CoA design experience, particularly for the US/Canada intercompany and audit readiness use case. …

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

For a company migrating from 8 separate QuickBooks Enterprise COAs, Acumatica's architecture enforces a single shared COA across all branches and companies within a tenant. All branches within a tenant share the same chart of accounts, calendar, and base currency, and a multibranch company can have a unified chart of accounts where all accounts are multibranch accounts. …

Limitations: The segmented key structure is a foundational configuration decision: segment identifiers cannot be deleted, and if any transaction has been posted to a subaccount, removing a segment key is not possible without SQL-level intervention. …

Requirement evaluated: Export to Excel and integration with Power BI for advanced visualization

For a controller at an 8-entity US/Canada business who needs to pull financial data into Excel and push it into Power BI for board-level dashboards, Acumatica's primary mechanism is its Generic Inquiries (GI) framework combined with a native OData v4.0 endpoint. The Generic Inquiry writer can access any data in Acumatica, including data stored in customized fields, and publish it, export to Excel, or format it for OData; the OData formatting option exposes the data in the Open Data Format supported by business intelligence tools like Microsoft Power BI. …

Limitations: When generating financial reports using ARM, Acumatica publishes financial report data to a single Excel tab, requiring significant manual copy-and-paste work to create per-entity views — so your controller's 8-entity consolidated reports will not land in separate entity tabs natively without a custom macro or a third- …

Requirement evaluated: Audit-ready reports: trial balance, reconciliation schedules, and journal entry listing with full detail

For a $180M professional services and distribution company moving toward audited financials, Acumatica's General Ledger module delivers all three document types an external auditor typically requests. The Trial Balance Summary (GL632000) and Trial Balance Detailed (GL632500) are standard delivered reports: these period-end reports display account balances for a selected period range, including beginning and ending balances as well as the period's total debits and credits, grouped by account type. The Journal Transactions screen (GL301000) serves as the journal entry listing: from any source document, the user clicks the Batch Number link and the Journal Transactions (GL301000) …

Limitations: The field-level audit trail is not enabled universally by default: administrators must navigate to the Audit configuration screen (SM205510) and enable auditing for specific screens and fields. …

Requirement evaluated: Export to Excel and integration with Power BI for advanced visualization

For a company running 8 legal entities that needs both ad-hoc Excel exports and live Power BI dashboards, Acumatica delivers through two well-documented native paths. First, any Generic Inquiry (GI) can be flagged as an OData endpoint by checking 'Expose via OData' on the GI form; Power BI then connects to that endpoint using the standard OData feed connector, with no middleware required, and supports scheduled refresh. GIs can be designed to include entity and branch dimensions, letting the controller build a single consolidated data set across all 8 entities before Power BI consumes it. Second, GI result grids and Analytical Report Manager (ARM) …

Limitations: On Acumatica's cloud-hosted deployment, Power BI can only reach data that has been surfaced through a published Generic Inquiry OData endpoint; direct SQL Server access is not available to cloud tenants, so consolidated multi-entity views in Power BI depend on the team correctly scoping GIs to join or filter across all …

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

For a controller at your $180M, 8-entity company who currently emails flash reports manually from spreadsheets, Acumatica replaces that process with its native Business Events framework. An administrator builds a Generic Inquiry that defines the financial data to be delivered (e.g., flash KPIs from the GL, cross-entity balances), creates an email notification template with the report attached, and sets the Business Event type to 'Trigger By Schedule.' The system then runs the inquiry on the configured cadence, such as every Monday morning for the weekly leadership flash report or on a defined day each month for the board package, and delivers the report as an email attachment to the specifie …

Limitations: Setting up scheduled delivery via Business Events requires building a dedicated Generic Inquiry for each report cadence, which involves initial configuration work and is not a simple point-and-click scheduler; reports with many dynamic date parameters (e.g., auto-rolling prior-period comparisons) …

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

For a multi-entity professional services company running checks across Bank of America commercial accounts, Acumatica does not ship a dedicated positive pay export module with pre-built, bank-specific file templates. The documented native path relies on Acumatica's Generic Inquiry (GI) and Export Scenario tooling: a consultant or administrator obtains BofA's positive pay file specification (field order, record length, delimiters), then builds a GI querying the APPayment, APAddress, and APContact tables to surface check number, amount, payee name, and date, then configures an export scenario to produce the output file. …

Limitations: Acumatica has no native, turnkey positive pay export with a pre-built BofA format template; the GI/Export Scenario path requires meaningful configuration effort (custom SQL views, field mapping to BofA's fixed-width spec, and often a custom data provider) …

Requirement evaluated: Vendor self-service portal for W-9 submission, banking updates, and payment status

For a $180M professional services and distribution company needing vendors to self-submit W-9s, update ACH banking details, and check payment status, Acumatica has no native mechanism. Acumatica's documented portal product is its Customer Self-Service Portal, which is explicitly AR-side and customer-facing: it lets your customers view contracts, financial statements, and support cases, and submit payments to you. …

Limitations: This capability is fully absent from Acumatica's native product at any tier or price point; the buyer must independently source a separate third-party AP automation vendor (e.g., Tipalti, PayEX AP, AvidXchange) …

Requirement evaluated: Three-way matching for PO-based invoices with configurable tolerance (we need 2% on price, 5% on quantity)

For a $180M professional services and distribution company processing 2,500 vendor invoices per month with PO-based purchasing, Acumatica delivers three-way matching natively through its Purchase Orders module. The workflow links three documents: a Purchase Order (PO), a Purchase Receipt (the goods receipt confirmation), and an AP Bill (vendor invoice). When a vendor invoice arrives, Acumatica compares the purchase order, receipt, and vendor bill to confirm that the ordered, received, and billed quantities and costs align. …

Limitations: Acumatica community discussions indicate that configuring automatic approval routing specifically triggered by a PO-to-invoice price or quantity variance requires implementation effort, as there is no single out-of-the-box approval map preconfigured for variance-driven routing; the buyer's team or implementation partne …

Requirement evaluated: Three-way matching for PO-based invoices with configurable tolerance (we need 2% on price, 5% on quantity)

For a professional services and distribution company running 2,500 vendor invoices per month across 8 entities, Acumatica natively supports three-way matching between the purchase order, the PO receipt, and the AP bill. When an AP bill is created directly from a PO (after a PO receipt is also created from the same PO), all three documents automatically link and are compared against each other within the Purchase Management module. The 'Three-Way Match Validation' setting in the Purchase Orders Preferences form (PO101000) is the documented control point for this capability: it can be enabled to hold or flag bills pending receipt confirmation. …

Limitations: The specific requirement for dual configurable tolerance thresholds, 2% on price and 5% on quantity as independent parameters, is not confirmed by Acumatica's help documentation; community evidence indicates that price-variance exceptions route through manual approval workarounds rather than a native tolerance rule eng …

Requirement evaluated: REST API with documented endpoints for custom integrations

For a multi-entity professional services company migrating from QuickBooks and needing to connect Salesforce and ADP, Acumatica provides a fully documented, natively built contract-based REST API as its primary integration surface. Acumatica exposes its data through a contract-based REST API alongside a legacy screen-based SOAP interface, with the REST API being the recommended path for all new integrations. The contract-based approach means API endpoints expose business logic objects rather than screen fields, so changes to forms, localizations, or customization projects do not break existing integrations. …

Limitations: API request throughput is rate-limited, with published rates of approximately 100 to 150 requests per minute depending on license tier, which could constrain high-frequency sync jobs between Acumatica and both Salesforce and ADP simultaneously. …

Requirement evaluated: REST API with documented endpoints for custom integrations

For a $180M professional services and distribution company needing to connect Acumatica to Salesforce, ADP, and custom workflows across 8 entities, Acumatica delivers a mature, fully documented contract-based REST API. The mechanism works as follows: each endpoint is a versioned contract that maps to a specific Acumatica screen, exposing its fields, validations, and business rules to external callers via standard HTTP verbs (GET, POST, PUT, DELETE). Developers can interact with over 200 default endpoints covering financial management, order management, inventory, purchasing, project accounting, and CRM modules. …

Limitations: Documentation depth for specialized module endpoints (such as Manufacturing) has been noted by community users as less thorough than the default financial/distribution endpoint, which could require additional discovery effort if the buyer's integration scope expands beyond core financials. …

Requirement evaluated: Bidirectional integration with Salesforce CRM: customer master sync, closed-won opportunities create billing events

For a company running Salesforce alongside Acumatica, the integration is delivered through Acumatica's own native Salesforce Integration feature, enabled directly on the platform's Enable/Disable Features form. Once active, the Salesforce Sync screen (SF205030) manages bidirectional, real-time synchronization of record types between the two systems: Acumatica Customer records map to Salesforce Account objects (including billing and shipping addresses, credit limits, and contact data), and changes in either system propagate to the other automatically. …

Limitations: The fully automated Closed-Won-to-Sales-Order trigger requires deliberate configuration during implementation; some partner-led deployments document it as a button-initiated step by default that must be configured for full automation, meaning the buyer should confirm automatic trigger behavior with their implementation …

Requirement evaluated: Bank feed integration with Bank of America and TD Canada Trust for automated reconciliation

For a company like yours spanning US and Canadian entities with Bank of America and TD Canada Trust accounts, Acumatica's native Bank Feeds module connects to over 14,000 financial institutions via two aggregators, Plaid and MX. Once enabled, users link their bank accounts to corresponding GL cash accounts inside Acumatica; the system then pulls transactions on a user-defined schedule and uses AI and machine learning to auto-match imported transactions against existing payments, invoices, receipts, credit memos, and debt adjustments. Unmatched items surface in a dashboard for manual review, and all updates are logged at the record and field level for audit traceability. …

Limitations: TD Canada Trust connectivity is not guaranteed through Plaid or MX: community posts document persistent connection failures with Canadian institutions and a workaround via SFTP file import that requires bank coordination and manual mapping setup. …

Requirement evaluated: Multi-currency support: CAD to USD translation with automatic gain/loss calculation per ASC 830

For a company running CAD-functional-currency entities alongside USD entities, Acumatica's Currency Management module handles the full ASC 830 workflow at two levels. First, at the transaction level: when the Canadian entity enters AR invoices, AP bills, or GL entries in CAD, the system captures the exchange rate at entry and automatically calculates and posts realized gains or losses to designated GL accounts when payments are settled against those documents. …

Limitations: The financial statement translation feature (CM203000 / CM301000) requires both the Multi-Currency and Financial Statement Translation features to be enabled in Acumatica; these are the vendor's own configuration flags within the Currency Management module, not third-party products, so a willing buyer can access the fu …

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

For a $180M professional services and distribution firm running 8 legal entities, Acumatica's centralized AP model works as follows: the AP team operates from a single login session and can be granted role-based access to multiple branches or companies within the same tenant, with the ability to switch views across companies without logging in again, and an audit trail of user activity. When entering a vendor invoice, the AP clerk opens the Bills and Adjustments (AP301000) form and specifies the branch that incurs the expenses for each line of the bill in addition to specifying the originating branch -- meaning a single invoice can be split across all 8 entities in one data-entry session. …

Limitations: The buyer's Canadian entities introduce a potential currency complication: one developer source notes that Acumatica does not support multiple base currencies within a single tenant, which could require the Canadian entities to be housed in a separate tenant rather than as branches or companies alongside the US entitie …

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

For a $180M company with 8 legal entities spread across the US and Canada, Acumatica's multi-entity consolidation story splits into two distinct architectures depending on how those entities are deployed. When all entities live within a single Acumatica tenant (using branches or separate companies inside one database), intercompany journal entries and eliminations are created automatically as transactions are posted, and consolidated financial statements can be run on demand with current data: as one partner describes it, 'intercompany journal entries and eliminations are created automatically as transactions happen, keeping your books accurate in real time' (Milestone IS, Intercompany Accou …

Limitations: For this buyer, the critical variable is whether all 8 US/Canada entities can be unified in a single Acumatica tenant: within one tenant, consolidation updates in real time as transactions post, but cross-tenant consolidation (separate tenants per entity) …

Requirement evaluated: Automated elimination entries during consolidation without manual journal entries

Your controller's current pain point, spending 12+ days on manual intercompany eliminations across 8 entities, maps directly to what Acumatica's Inter-Company Accounting module is designed to eliminate. Once your 8 US and Canada entities are configured within a single Acumatica tenant, the system requires you to define intercompany relationships and account mappings upfront (via the Inter-Company Accounting screen, GL104500, and interbranch account mapping). …

Limitations: For complex consolidation adjustments beyond standard intercompany receivables/payables and revenue/cost eliminations, such as unrealized intercompany inventory profit eliminations or equity pickup for partially-owned entities, community practitioners have noted that some manual steps may remain; a third-party Acumatic …

Requirement evaluated: Credit limit management by customer

For a professional services and distribution company moving off QuickBooks Enterprise, Acumatica delivers credit limit management natively within its Accounts Receivable module. An administrator sets a dollar credit limit and maximum days-past-due threshold directly on each customer master record under the General Info tab's Credit Verification Rules section (Customers form AR303000); default rules can be configured at the Customer Class level (AR201000) and overridden per individual customer. …

Limitations: The out-of-box 'AR-CreditLimitCustomers' generic inquiry shows the credit limit set on the customer master, but the available or remaining credit limit is not captured in that standard report; a custom generic inquiry or the built-in GI attachment is needed to surface real-time available credit, which may require minor …

Requirement evaluated: Aging reports and dunning automation with escalation rules

For a professional services and distribution company moving off QuickBooks Enterprise and targeting audited financials, Acumatica's native AR module covers this requirement end to end. The AR Aging report (AR631000) shows all outstanding AR documents and their overdue balances as of any specified date, with up to five configurable aging buckets defined per statement cycle (by days past due or financial period), feeding directly into auditor-ready collections visibility. For dunning, administrators enable the Dunning Letter Management feature and then configure any number of dunning levels in AR Preferences (AR101000) …

Limitations: The escalation mechanism is level-based dunning progression (letter severity and fees increase by configured day thresholds) rather than a dedicated collector-routing or manager-reassignment workflow engine; teams that need automatic reassignment of overdue accounts to a senior collector or external collections agency …

Requirement evaluated: Automated payment application from bank lockbox and ACH receipts

For a company like yours processing ACH receipts and bank lockbox deposits across 8 entities, Acumatica provides two complementary but distinct mechanisms. First, the Cash Management module supports BAI2 file format ingestion via Bank Feeds (CA205500): an administrator creates a bank feed selecting BAI2 as the file format and entering SFTP credentials, and the system checks for .bai, .bai2, or .btrs files, parsing them into bank transactions for a specified cash account. …

Limitations: Per Acumatica community experts, native rule-based matching for AR cash application is not a single setup screen like in some other ERPs, and most companies with true straight-through requirements turn to Acumatica Marketplace solutions. …

Requirement evaluated: Aging reports and dunning automation with escalation rules

For a company like yours managing AR across 8 legal entities and preparing for an audit, Acumatica's native AR module covers the core of this requirement but stops short of full escalation-to-human workflow. On the aging side, the AR Aging report (AR631000) shows all outstanding documents grouped by customer, broken down by configurable aging periods, and aged against due dates, giving the credit control team a starting point for collections action. On the dunning side, Acumatica's Dunning Letter Management feature (enabled as a system feature via Enable/Disable Features) …

Limitations: Escalation routing to specific collectors or managers requires custom Business Events configuration rather than a native collector workbench or queue, which adds implementation complexity and creates a maintenance burden as your entity count grows. …