How Sage Intacct works

Requirement evaluated: Automated recurring journal entries and templates for standard monthly entries

For a controller spending 12+ days on manual close entries across 8 entities, Sage Intacct's General Ledger module addresses this directly through three native mechanisms. First, <cite index="4-18,4-19,4-20">recurring journal entries let users automate any regularly posted entry; they can be created for any type of book (GAAP, tax, or user-defined) and work exactly like standard journal entries except they post according to a schedule the user sets.</cite> The user defines the entry once via a Transaction tab (accounts, dimensions, amounts) …

Limitations: <cite index="4-22,4-23">Recurring GL journal entries can only be created when the company uses standard reporting periods; custom reporting periods are not supported.</cite> Additionally, <cite index="4-11">editing a line amount in a recurring journal entry can retroactively update previously posted journal entries,</c …

Requirement evaluated: Statistical accounts for non-financial KPIs (headcount, square footage for allocations)

For a multi-entity professional services company like yours that needs headcount and square footage to drive cost allocations across 8 entities, Sage Intacct provides a dedicated Statistical Accounts account type within the Chart of Accounts, living natively alongside financial accounts under General Ledger > Accounts. Your controller creates a statistical account (e.g., 'Headcount' or 'Square Footage'), assigns it its own account number range to keep it separate from monetary GL accounts, and posts quantities via statistical journal entries — which, unlike financial entries, do not need to debit/credit balance; they simply increase or decrease a unit count. …

Limitations: The Dynamic Allocations module that connects statistical account balances to automated cost distribution rules requires a separate subscription ('Subscribe to Dynamic Allocations' per Intacct's own documentation), so the allocation-driver functionality is a priced add-on rather than part of the base GL. …

Requirement evaluated: Statistical accounts for non-financial KPIs (headcount, square footage for allocations)

For a multi-entity professional services and distribution company moving off QuickBooks Enterprise, Sage Intacct's native statistical accounts feature directly addresses the need to track headcount and square footage as allocation drivers within the GL. A controller creates dedicated statistical accounts (e.g., 'Headcount,' 'Square Footage') in the chart of accounts under a separate account range, keeping them fully distinct from financial accounts so the trial balance is never polluted. …

Limitations: Statistical journal entries are entered manually or via import/API per period; there is no automatic real-time sync from an HRIS or facilities system, so the buyer will need to establish a data ownership process (e.g., a monthly import from ADP payroll data) to keep headcount figures current. …

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

Your scenario involves US entities on one fiscal year-end and Canadian entities on a different one, all within a single Sage Intacct multi-entity shared instance. Sage Intacct does expose a per-entity 'firstfiscalmonth' field (visible in the developer API for the LOCATIONENTITY object), which allows each entity to independently declare a different fiscal year start month within the Standard calendar type. For example, your US entities could run a December year-end while a Canadian entity runs a March year-end, provided both use the Standard calendar structure and the year-end falls on a calendar month boundary. …

Limitations: If your Canadian entities require a custom (non-month-boundary) year-end or a different period structure than your US entities, Sage Intacct's documented constraint that all entities in a shared company must share the same calendar type (Standard or Custom) will prevent true per-entity calendar isolation. …

Requirement evaluated: Support for 8 legal entities today, scalable to 15+ as we acquire companies

For a $180M professional services and distribution company moving off QuickBooks Enterprise's separate-company-file model, Sage Intacct's native Multi-Entity Shared architecture is a direct architectural replacement. Rather than separate database instances per entity (which creates the spreadsheet consolidation problem the buyer is escaping), all 8 legal entities live under a single tenant with a shared chart of accounts, shared vendor/customer/employee master data lists defined once at the top level, and each entity maintaining its own fully balancing set of books with separate tax IDs and balance sheets. …

Limitations: Sage Intacct charges per entity, so adding entities acquired through M&A requires confirming subscription tier capacity before provisioning. The Global Consolidations module (required for CAD/USD translation across the US and Canada entities) …

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

For a company like yours with US entities reporting in USD and Canadian entities in CAD, Sage Intacct's Global Consolidations module handles the full ASC 830 translation chain natively. Each entity is assigned its own functional currency (CAD for Canadian entities, USD for US entities), and when the consolidation runs, the system applies layered exchange rate types exactly as ASC 830 requires: ending spot rate for balance sheet accounts, weighted average rate for income statement accounts, and historical rate for non-monetary and equity accounts. …

Limitations: The full ASC 830 CTA engine (entity-level functional currency translation, layered rate types, and CTA posting to OCI equity) requires the Global Consolidations subscription tier, which is priced separately from base Sage Intacct; buyers should confirm this module is included in their quote for all 8 entities. …

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

For a company like yours with 8 legal entities and a centralized AP team currently fragmented across QuickBooks and spreadsheets, Sage Intacct's Multi-Entity Shared environment is purpose-built for this model. The system has a 'top level' that acts as the parent container: <cite index="25-1,25-2">the top level is where users create, edit, and manage objects that are shared across entities, and users can enter transactions at the top level and select the entities or locations where they want to post the transactions.</cite> This means your entire centralized AP team operates under a single login without toggling between separate entity databases: <cite index="26-6">Sage Intacct lets you manag …

Limitations: <cite index="11-8">You cannot approve entity-level bills at the top level,</cite> so the shared services model works cleanest when the centralized AP team enters all invoices at the top level (the documented best practice); bills entered directly inside individual entity contexts fall outside the top-level approval que …

Requirement evaluated: Ability to report at entity level, entity group level (US vs. Canada), and full consolidated level

For a company with 8 legal entities split across the US and Canada, Sage Intacct's Multi-Entity Shared architecture keeps each entity as a fully isolated ledger, so entity-level P&L and balance sheet reports are available at any time without aggregation. <cite index="2-6">In multi-entity shared companies, transaction lists at the entity level include transactions created at the top level that are tagged to your entity</cite>, giving each entity a closed, auditable book. For the intermediate US vs. …

Limitations: <cite index="26-25,26-26">A wholly-owned multi-base currency company is a good candidate for the Global Consolidation subscription, while a tiered structure or partial ownership scenario is a good candidate for Advanced Ownership Consolidation</cite>; since the buyer's 8 entities are described as wholly owned and the U …

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

For a $180M professional services company running 8 entities and needing to connect ADP and Salesforce without native connectors, Sage Intacct functions as a well-documented integration endpoint for both Workato and Celigo. Workato publishes a Sage Intacct community connector (installed from the Workato community library) with triggers covering new and updated AP bills, vendors, invoices, purchasing transactions, and customers, plus actions spanning journal entries, GL accounts, AP bill creation, purchasing transactions, and more. …

Limitations: The Workato connector is a community (not first-party certified) connector and must be manually installed from the Workato library; object coverage for multi-entity consolidation objects should be verified before go-live. …

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

For this buyer's US and Canadian multi-entity footprint, Sage Intacct's Cash Management module delivers bank feed integration through its Banking Cloud, enabled via a Sage Cloud Services subscription. Bank of America is supported through a dedicated, named direct API connection: the buyer's controller navigates to the Banking cloud tab in Cash Management, searches for 'Bank of America CashPro (US),' and authenticates via the Bank of America CashPro Information Reporting API; provisioning credentials with Bank of America typically takes a couple of weeks, after which the feed connects in minutes and refreshes automatically every four hours. …

Limitations: The Bank of America connection uses a certified, direct CashPro API (the most stable tier), but the TD Canada Trust connection relies on a standard aggregator path, which is subject to periodic reauthorization requirements and connection instability as flagged in Sage Intacct's own troubleshooting documentation; the bu …

Requirement evaluated: REST API with documented endpoints for custom integrations

For a company moving off QuickBooks Enterprise with 8 legal entities, active Salesforce and ADP connections, and an audit readiness deadline, Sage Intacct provides two documented, bidirectional API layers. The modern REST API, publicly documented at developer.sage.com/intacct, uses OAuth 2.0 Bearer token authentication, standard HTTP verbs, and JSON payloads; it covers the full financial data model including customers, vendors, invoices, bills, GL accounts, and consolidation objects. The developer portal includes a Quick Start guide, full API reference, tutorials, a Postman collection, and a developer community forum. …

Limitations: As of early 2026, some advanced modules including project accounting and fixed asset management are not yet fully migrated to the REST API and still require the legacy XML API, meaning integrations touching those objects must maintain two API clients and two authentication flows. …

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

For a company running 8 legal entities across the US and Canada, Sage Intacct's Cash Management module delivers automated bank feed connections for both of the buyer's named banks. Bank of America is connected via a dedicated Bank of America CashPro Information Reporting API pathway, documented step-by-step in Sage Intacct's own help center: the buyer requests CashPro API credentials from Bank of America, then enters the Client ID and secret directly into the Banking cloud tab inside Cash Management — no file exports required. TD Canada Trust is connected through FISPAN, which Sage has designated its recommended bank feeds provider (Tech Partner Plus since 2023) …

Limitations: Feed latency is not intraday: Sage Intacct's own FAQ states that transactions typically appear the business day after they post at the bank, with auto-matching running on a 4-hour cycle, which means same-day cash visibility is not guaranteed. …

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

For a company migrating from QuickBooks Enterprise with 3 years of transactional history across 8 entities, Sage Intacct provides a structured import framework that covers three layers of data: master data (chart of accounts, vendors, customers), open items (unpaid AP bills and AR invoices), and historical balances or transactions. Sage Intacct's native import tooling, accessed at Company > Setup > Import Data, provides pre-configured CSV templates for journal entries, AP bills, AR invoices, and other transaction types; detailed GL history from QuickBooks can be loaded as dimensionalized journal entries so that entity-level and vendor/customer reporting works natively in Intacct post-migrati …

Limitations: There is no automated one-click extraction tool from QuickBooks Enterprise to Sage Intacct; the migration requires data extraction, field mapping (notably QuickBooks Classes to Intacct Dimensions), cleanup, and phased CSV imports, which implementation partners consistently estimate at 5 to 9 months of preparation time …

Requirement evaluated: Role-based training plan (not generic): controller, AP clerk, entity bookkeeper, executive

For a company moving from QuickBooks Enterprise across 8 entities, Sage Intacct delivers role-differentiated training primarily through Sage University, its branded learning platform accessible via single sign-on from inside the product. The official Sage University help center documents named learning paths organized by Intacct role, with sequenced lanes covering 'Get started' (basic functions) and 'Core learning' (everyday duties). …

Limitations: The executive persona has no documented dedicated Sage University learning path, meaning that persona's training must be assembled by the implementing VAR or the buyer's own controller, with no vendor-provided pre-built curriculum covering approval workflows, board reporting, or exception escalation in context. …

Requirement evaluated: Phased implementation: core GL and consolidation first, then AP/AR, then advanced reporting

For a company migrating from QuickBooks Enterprise across 8 legal entities with an audit deadline, Sage Intacct's subscription-based modular architecture maps directly to the buyer's requested phase sequence. Phase 1 (core GL and consolidation): the Core Financials base includes the General Ledger from day one, and the Multi-Entity and Global Consolidations module is a separately licensed add-on activated via an admin 'Subscriptions' page without reinstallation -- it automates intercompany eliminations, supports multi-level ownership structures, and provides audit-ready consolidation journals across all 8 entities. …

Limitations: AP and AR are bundled inside Core Financials in Sage Intacct's standard packaging, so the 'GL-first, then AP/AR later' split requires deliberate scope gating in the implementation statement of work rather than a hard licensing boundary; a partner who does not manage this rigorously may default to enabling all core modu …

Requirement evaluated: Guaranteed 99.5%+ uptime SLA with defined severity levels and response times

For a $180M professional services company moving toward audited financials and board-level scrutiny, Sage Intacct publishes a formal, publicly available SLA called the 'Buy with Confidence Program' that applies directly to the Core Financials application service. The contractual uptime commitment is 99.8% monthly availability (exceeding your 99.5% minimum), with subscription credits triggered at 10% of monthly fees per percentage point below the threshold, up to 50% of monthly fees. Severity tiers are documented: the most critical level (system fully down) …

Limitations: The resolution time commitments for severity tiers are described as 'good faith efforts' and 'target' goals in the Buy with Confidence documentation, not contractually guaranteed remedies with automatic financial penalties: only the uptime credit mechanism is financially enforceable. …

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 multi-entity professional services company replacing a QuickBooks-plus-spreadsheets environment, Sage Intacct provides three layered self-service report-building tools, all designed for finance users without IT involvement. First, the Financial Report Writer (included in the core subscription) lets the controller build formatted financial statements: income statements, balance sheets, and custom P&Ls, using GL account groups and any of Intacct's dimensions (department, location, project, class, and others) as rows and columns, with options for actuals, budget, and variance calculations. Second, the Custom Report Writer (also included in core) …

Limitations: The most advanced visual reporting capability (ICRW with drag-and-drop, real-time pivoting, and prebuilt report templates) requires purchasing the Interactive Custom Report Writer add-on subscription; the core Financial Report Writer and CRW, while fully self-service, have more limited layout flexibility and do not upd …

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 $180M multi-entity professional services and distribution company currently stitching together QuickBooks Enterprise and spreadsheets, Sage Intacct offers two native self-service report-building tools that require no IT or vendor assistance. The first, the Custom Report Writer (CRW), is a wizard-guided tool included in the core subscription; it lets the controller build financial or non-financial tabular reports from scratch or by duplicating an existing report, selecting fields from across modules (GL, AP, AR, Projects, and more), adding calculated columns, and applying filters, all without writing code (Sage Intacct help center: 'Welcome to Custom Report Writer'). …

Limitations: The ICRW, which delivers the most flexible and interactive report-building experience, requires a separate paid subscription beyond the base Sage Intacct license; the buyer should budget for this add-on. …

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

For a controller at your 8-entity, $180M company, Sage Intacct covers Excel and Power BI connectivity through two distinct paths. First, native Excel export is built into every report surface: the Financial Report Writer, Custom Report Writer, and Interactive Custom Report Writer (ICRW) all offer an Export As option with HTML, CSV, PDF, and Excel as output formats, as documented in Sage Intacct's own help center. This covers on-demand, formatted static exports your team already runs today. …

Limitations: Sage Intacct does not ship a first-party Power BI connector from Sage itself, so live Power BI integration requires a separately licensed marketplace solution such as CData (priced on an annual subscription basis per report builder and server size); the native ICRW Excel export produces a static snapshot, not a live-co …

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

For a controller at an 8-entity company moving off QuickBooks and spreadsheets, Sage Intacct provides three complementary no-code report builders, all operable by finance users without IT or vendor involvement. The core subscription includes the Financial Report Writer (FRW), which lets the controller build row/column matrix reports using GL account groups and dimension structures (entity, department, project, class), including consolidated and entity-specific views that directly address your intercompany reporting needs; the controller navigates Reports > Financial Report Writer, selects accounts or dimensions as rows, configures column sets (actual, budget, variance), and saves the report …

Limitations: The ICRW is a separately licensed add-on (not included in the base subscription), so the most advanced ad hoc features require an incremental budget commitment. The ICRW is also documented as optimized for exploratory/operational analysis rather than formal presentation-ready financial statements; for audited financial …

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

For this multi-entity professional services and distribution company running check payments through Bank of America commercial accounts, Sage Intacct supports positive pay file generation through two paths. The first is native: within Cash Management and Accounts Payable, <cite index="35-3,35-4,35-5,35-6">you can create positive pay reports when a company uses a positive pay system with the bank, and positive pay ensures that only checks that are on the report are accepted by the bank; because there can be a gap between payment submission and posting, you can build a custom report to view pending check payment requests and submit the positive pay report to the bank.</cite> <cite index="5-3,5 …

Limitations: <cite index="5-6,5-7,5-8">The native custom report path may not accommodate all positive pay bank requirements (validation with your bank is required) and cannot auto-upload to the bank; RKL and other Sage Intacct partners offer advanced Positive Pay modules available for purchase if the native report does not meet you …

Requirement evaluated: Configurable approval workflows by entity, department, GL account, and dollar threshold

For your 8-entity US/Canada operation, Sage Intacct's native AP Bill Approval module supports three of your four required routing dimensions directly. Entity-level routing is handled through the Location dimension: when a bill is entered at a specific entity, the system routes it through approvers scoped to that Location, and user roles can be restricted so approvers only see bills for their own entities. Department-level routing uses the 'Value Approval - Transaction Department' rule type, which lets you configure distinct approvers and dollar thresholds per department, with department-specific rules overriding a default when a department needs unique criteria. …

Limitations: GL account is not a native routing condition in Sage Intacct's AP bill approval engine; routing a bill to a specific approver based solely on which GL account it hits (for example, routing all capital expenditure account bills to the CFO regardless of department) …

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

For a company processing 2,500 invoices monthly across 8 entities, Sage Intacct's native AP Automation (powered by Sage AI) covers two of the three ingestion channels your team needs. First, Sage provisions a unique email address for each legal entity; forwarding vendor invoices to that address triggers automated processing without any staff intervention. Second, AP staff can upload batches of PDFs or image files directly within Intacct. In both cases, Sage AI/ML extracts vendor identity, invoice number, date, amounts, and line items, populates a draft bill, and improves prediction accuracy as staff post and correct drafts over time. …

Limitations: For this buyer's 8-entity structure, each entity gets its own Sage-provisioned email address natively, which aligns well with multi-entity routing; however, the absence of a native vendor portal means roughly any invoices that suppliers would submit through a self-service channel must either be routed through the email …

Requirement evaluated: 1099 preparation and electronic filing

For a company with 8 legal entities that needs to replace spreadsheet-driven 1099 processes and support audited financials, Sage Intacct delivers end-to-end 1099 preparation and electronic filing natively within its Accounts Payable module. In the AP vendor master, each vendor is flagged as 1099-eligible with a designated form type (1099-NEC, 1099-MISC, 1099-INT, 1099-DIV, 1099-R, 1099-S, 1099-PATR, 1099-G, and W2-G are all supported) …

Limitations: <cite index="2-27,2-28,2-29">State-level 1099 filing rules vary: some states participate in the IRS Combined Federal/State Filing program and others require direct filing, both of which are manageable through the TaxBandits integration, but the buyer's Canadian entities are outside the scope of US 1099 obligations enti …

Requirement evaluated: Customer portal for invoice access and online payment

For a professional services and distribution company like yours moving off QuickBooks and needing auditable AR processes, Sage Intacct addresses this requirement through Sage AR Automation, a Sage-owned product (formerly Lockstep, acquired by Sage) available via the Sage Intacct Marketplace as a separately priced subscription. <cite index="22-6,22-7">The module empowers customers with a self-service portal to view, pay, and manage invoices with ease, eliminating questions about what is owed or how to pay.</cite> <cite index="9-11,9-12">The portal supports invoice delivery through a customer account portal, magic links, and email; invoice status tracking for acceptance, disputes, and rejectio …

Limitations: <cite index="2-17,2-18,2-19">Sage Intacct's core AR module does not include native credit card or ACH payment processing or a built-in customer portal out of the box; the Sage AR Automation add-on (or a third-party marketplace partner) …

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

For a $180M multi-entity company processing 2,500 invoices per month and targeting audited financials, Sage Intacct's native Cash Management module provides bank feeds that pull transaction data from connected financial institutions and apply configurable rule sets to auto-match incoming payments against open entries. <cite index="18-3,18-5,18-6">The bank feed connects bank and credit card accounts to Sage Intacct, transmits data regularly, and can automatically match payments and transactions to invoices.</cite> <cite index="17-5,17-14,17-15">Rules and rule sets define how to match and create transactions for reconciliation based on bank feed or imported file data, and matching rules can be …

Limitations: The native Cash Management bank feed provides best-effort invoice matching but lacks systematic lockbox BAI2 file processing and full AR auto-apply: <cite index="19-6,19-8">Sage Intacct's native bank feed experience is narrower than many accountants expect, with a more rigid auto-categorization rules engine compared to …

Requirement evaluated: Customer portal for invoice access and online payment

Sage Intacct's core AR module handles invoice creation, delivery, and payment recording for your staff, but it does not include a native customer-facing self-service portal out of the box. The buyer-facing portal layer is delivered through Sage's own curated Marketplace, where multiple certified, deeply integrated partners cover this requirement fully. …

Limitations: A third-party marketplace partner (Versapay, Paystand, REPAY, Invoiced by Flywire, or others) must be licensed separately, as Sage Intacct's native AR does not include a customer-facing portal or embedded payment gateway on its own. …

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

For a $180M professional services and distribution company replacing QuickBooks spreadsheet-based revenue schedules, Sage Intacct's native Contracts module is purpose-built for exactly this scenario. Each contract record holds separate, independent billing and revenue schedules per contract line: <cite index="21-29,21-30,21-31,21-32">a billing schedule shows when a contract line's flat/fixed amount is expected to be invoiced, a revenue schedule shows when deferred revenue is expected to be recognized, and the two schedules can be independent — for example, invoicing a fixed fee upfront while recognizing revenue monthly over the contract term.</cite> For milestone-based service contracts, <ci …

Limitations: The buyer's mixed professional services and distribution contracts may require the Contract Advanced Revenue Management tier (separately licensed above the base Contracts Standard subscription) to access multi-element arrangement (MEA) …

Requirement evaluated: Support manual journal entries with configurable approval workflows based on amount thresholds, account type, or entity.

For a manufacturing buyer needing approval routing conditioned on amount, account type, and entity, Sage Intacct's native General Ledger module provides journal entry approvals configured at General Ledger > Setup > Configuration: <cite index="22-40,22-41">an administrator defines journal entry approvals for each GL journal, and each journal can have either one approver or a chain of approvers</cite>, with <cite index="25-13,25-14">multiple approvers creating a multi-step approval chain where, as each approver in the chain approves a journal entry, it then appears in the list of transactions requiring approval from the next approver</cite>. …

Limitations: The native GL journal entry approval module explicitly excludes amount-threshold routing and account-type-based conditional routing; achieving the buyer's full requirement (amount, account type, and entity as simultaneous routing conditions) …

Requirement evaluated: Provide recurring journal entry templates with flexible scheduling (monthly, quarterly, annual) and automatic reversal options.

For a manufacturing buyer needing recurring journal entry templates with flexible scheduling and automatic reversals (e.g., monthly depreciation accruals, quarterly overhead accruals, annual prepaid amortization), Sage Intacct's General Ledger module provides a dedicated Recurring Journal Entries feature. <cite index="1-4,1-6">Users can automate any journal entry that is entered regularly; the recurring entry works the same as a standard journal entry but is repeated according to a schedule.</cite> <cite index="2-1,2-9">On the Schedule tab, users configure the recurrence frequency (daily, weekly, monthly, quarterly, yearly) …

Limitations: Recurring journal entries require standard (not custom) reporting periods, which may constrain manufacturing entities that use non-standard fiscal calendars. Entries with custom allocation splits cannot be set up as recurring templates, meaning complex cost-distribution accruals common in manufacturing must be handled …

Requirement evaluated: Support allocation journal entries that distribute costs across plants, departments, cost centers, or product lines using configurable allocation drivers (machine hours, labor hours, units produced, square footage, direct costs).

For a manufacturing buyer needing to distribute overhead costs across plants, departments, cost centers, and product lines using operational drivers, Sage Intacct provides a dedicated Dynamic Allocations module (an add-on subscription to the core GL). A finance user builds an allocation definition by specifying: a source pool (the account group and percentage of balance to distribute), a basis (the 'how' of the split), and target dimension combinations. …

Limitations: Dynamic Allocations is a separately priced subscription add-on, not included in the base GL license; buyers should confirm it is scoped into the contract. <cite index="17-12,17-13">The allocation percentage can be defined by dollars or statistical accounts, but the module requires an additional Sage Intacct subscriptio …

Requirement evaluated: Support statistical journal entries for non-financial data (units produced, machine hours, labor hours, scrap quantities) that can be used as allocation bases and in reporting.

For a manufacturing buyer needing to capture units produced, machine hours, labor hours, and scrap quantities as first-class GL data, Sage Intacct provides a dedicated statistical account type within the chart of accounts, distinct from financial accounts. <cite index="21-2,21-3,21-4">There are two types of accounts in Intacct: financial accounts that track monetary value, and statistical accounts that track operational data (such as headcount) …

Limitations: Dynamic Allocations, the module that uses statistical accounts as allocation drivers, requires a separate paid subscription beyond the base GL; <cite index="19-2">your company must have a subscription for Dynamic Allocations and the appropriate permissions for account allocations.</cite> The documented examples for sta …