RFP Requirements: ERP & Core Accounting (Manufacturing) ##: Comparison

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: an administrator defines journal entry approvals for each GL journal, and each journal can have either one approver or a chain of approvers, with 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. Delegation and out-of-office rerouting are also supported natively. However, Sage Intacct's own help center documentation is unambiguous about the ceiling: journal entry approvals differ slightly from most application approvals; the process is more straightforward; they are not based on values and value thresholds, but on approvers that you configure. This means the amount-threshold routing the buyer requires (e.g., entries over $50K route to CFO) and account-type-based routing are not available in the native GL approval engine. Entity-level differentiation is achievable only indirectly: because approvers are configured per journal, different journals assigned to different entities can carry different approver chains, but this is not dynamic conditional logic tied to an entity dimension. A Sage Intacct Marketplace add-on, Advanced Approvals by Baker Tilly, does offer the ability to create separate approval workflows by entity and create approval rules on any field, with flexible approval logic to skip approvers based on a specific dollar threshold, but this is a third-party paid add-on, not included in the base product.

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. 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. On the Schedule tab, users configure the recurrence frequency (daily, weekly, monthly, quarterly, yearly) and define an end condition: either an explicit end date or a set number of occurrences. For automatic reversals, if a recurring entry is always reversed in the following period (a common pattern for accruals), both schedules can be configured at setup time; two reversal options are available: linking the reversing entry to the original at a fixed interval after posting, or creating an independent reversal schedule not tied to the original posting date. One material constraint: recurring GL journal entries can be created only if the company uses standard reporting periods; custom reporting periods are not supported. Additionally, journal entries with custom allocations cannot be used to create recurring entries.

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. The module supports statistical accounts or relative financial account balances as the basis out-of-the-box, and allows any standard or user-defined dimensions to limit the inputs and outputs of each allocation. Non-financial drivers such as machine hours, labor hours, units produced, and square footage are captured via Sage Intacct's native statistical accounts: costs can be allocated based on statistical accounts such as square footage, labor hours, unitized shares, or other non-financial metrics to allocate based on the most accurate drivers of cost or revenue. The statistical entries for each period serve as the live basis values when the allocation runs. Recurring allocations can be auto-scheduled, and the true-up feature automatically reverses any previous allocation in the same source period before generating the new one. The resulting distribution is posted as GL journal entries with full drill-down and audit trail. Dynamic Allocations is a native module that automates the allocation of indirect costs, revenue, assets, and liabilities across multiple dimensions such as departments, projects, and locations, as well as across entities.

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. There are two types of accounts in Intacct: financial accounts that track monetary value, and statistical accounts that track operational data (such as headcount) and can be used in combination with financial accounts to track metrics. Users post non-monetary quantities against these accounts via statistical journal entries: the developer API documents a dedicated statistical journal entry object (GLBATCH posted to a statistical journal), where each line references a statistical account number, a dimensional tag (department, location), and a non-monetary amount representing the operational measure. Once recorded, these statistical account balances serve as allocation drivers in the Dynamic Allocations engine: Sage Intacct supports statistical accounts or relative financial account balances as a basis out-of-the-box. The CLA partner documentation confirms the end-to-end flow: a statistical account and statistical journal entry are used to record the operational measure (e.g., FTEs per department), and the allocation basis then references the account group containing that statistical account. Finally, statistical accounts in Sage Intacct allow organizations to measure what matters most, and the financial report writer surfaces non-financial data tracking alongside monetary figures for smarter decision-making.

For a manufacturing buyer running intercompany journal entries across plants, subsidiaries, and holding entities, Sage Intacct's Inter-Entity Transaction (IET) engine handles both halves of this requirement. On the offsetting-entry side: when a user enters a manual journal entry that involves two or more entities, Intacct automatically adds offsetting transactions into the journals of each affected entity. The inter-entity accounts mapped in the inter-entity account mapping plan are used to record the inter-entity payables and receivables for inter-entity transactions, with administrators choosing between a Basic plan (one set of IET accounts per entity) or an Advanced plan that defines distinct due-to/due-from account pairs for each entity relationship. General Ledger journal entries show the source and inter-entity transaction entries, which makes it easy to drill down and reconcile a given transaction. On the elimination side, Sage Intacct's Consolidation module (Domestic, Global, or Advanced Ownership) provides a dedicated elimination mechanism: during consolidation, you can configure your ownership structure or consolidation book to automatically generate offsetting entries against inter-entity activity in the elimination entity, Intacct automatically eliminates inter-entity receivable and payable balances in the single reporting currency of the consolidation book, and these elimination entries are netted out in the elimination entity in the consolidation book, thus avoiding overstatement of the consolidated financial statements. You can also designate other accounts to eliminate, such as investment in subsidiary or inter-entity sales, covering intercompany revenue, expense, and loan balances beyond the standard IET accounts. The elimination entity is a dedicated shell entity: elimination entities are shell entities used only for posting consolidation entries for a consolidation book; the elimination entity is where Consolidation posts consolidation entries, including elimination transactions for inter-entity activity, currency translation adjustments, and non-controlling interest entries.

For a manufacturing finance team that needs invoices, variance schedules, and calculation workpapers tied to manual and adjusting journal entries, Sage Intacct provides a native Attachment field directly on the journal entry form in the General Ledger module. When creating or editing a journal entry, the accountant uses the Attachment dropdown to add a new attachment bundle: they can drag and drop or upload spreadsheets, scanned images (e.g., PDF invoices), or word processor documents, and that bundle is stored with a unique ID linked to the JE record. The Attachment field stores "a digital version of a supporting document as an attachment," where "an attachment is a bundle of one or more supporting documents" and "these can be spreadsheets, scanned images, or word processor documents." Users can drag and drop files to add an attachment. For period-end workflows where the same support document must be linked to multiple accrual entries at once, a bulk attachment feature is available from the Journal Entries list view. This section describes how to add an attachment to multiple journal entries: "when you add an attachment to multiple journal entries simultaneously, the attachment shares the same ID across those entries," and "any changes to the attachment affect all journal entries using the same attachment ID." Attachments are also accessible via the XML API using the SUPDOCID field on the GLBATCH object, confirming full programmatic support. The developer documentation defines an attachment as "any document, such as a bill, spreadsheet, or tax form, that provides tangible, historical, and auditable information in support of a transaction or financial record."

For a manufacturing operation requiring that journal entry creators and approvers be distinct users, Sage Intacct enforces this directly in General Ledger configuration. An administrator navigates to General Ledger > Setup > Configuration and deselects the 'Submitter can approve own entries' checkbox; once disabled, a substitute approver can only be added when the 'Submitter can approve own entries' checkbox is not selected, at which point the Substitute approver column appears in the Approvers list. The system then routes the entry to a different designated approver: a substitute approver can approve only journal entries submitted by the primary approver, and substitute approvers can be assigned only if the 'Submitter can approve own entries' checkbox is not selected; for example, if Karla makes an entry in the general journal, Penny must approve it. Permission separation is enforced at the role level: only users who already have the Journal Entry Approver permission are selectable as approvers or substitute approvers, with the documented best practice being to create a dedicated role with the Approve Journal Entries permission and assign appropriate users to it. This means a preparer role and an approver role can be kept mutually exclusive at the user level, satisfying the SoD requirement end-to-end.

For a manufacturing buyer that regularly imports large volumes of journal entries (month-end accruals, variance entries, payroll allocations) from external files, Sage Intacct provides two native import paths within the General Ledger module. The legacy path accepts CSV files via General Ledger > All > Journal Entries, using downloadable company-specific templates that define required fields, character limits, and valid values for each column. Users import GL journal entry information directly into Intacct with a CSV file, and the area now also supports the newer import service. The newer Import Service, accessed via Company > Setup > Import Data, accepts .XLS, .XLSX, and .CSV files: column names in the upload file do not have to match Intacct headers; during import the user maps fields to Intacct fields; the service then validates data against business logic and required fields (including journal entry imports); the review sheet displays errors or discrepancies; the user corrects errors before committing; and accepted file types are .XLS, .XLSX, and .CSV. The validation layer operates as a true pre-posting staging layer: after a file is loaded and fields are mapped, data is displayed on a preview sheet showing how it will look in Intacct; the user can review and validate or add information; and the sheet must be error-free before import into Intacct is permitted. Errors flagged as 'Not valid' can be corrected inline or in the source file and revalidated. All entries are imported in Draft format, so the final step is to navigate to General Ledger > Journal Entries and post them from the list, ensuring no unreviewed entries reach the GL.

For a manufacturing company needing backdated journal entries to prior open periods, Sage Intacct delivers control through a layered architecture of period status management, role-gated access, approval workflows, and an immutable audit trail. Closing the books in Intacct prevents transactions from being posted to prior periods; the system retains all transaction detail at all times, and after an audit is completed, closing the books prevents anyone from posting additional transactions to the already-audited fiscal year. For periods that remain open (or need to be reopened), access to the Open Books page is highly restricted to the accounting manager, controller, or CFO, enforcing role-based access control at the period level. Organizations can also lock periods after closing them, preventing reopening; this feature is managed via user permissions, with an Accounting Manager permitted to reopen books while a Controller with lock/unlock rights can prevent the Manager from reopening periods before financial statements are distributed. For entries targeting already-closed periods, the Adjustment Journal Entries page is the designated mechanism; if a closed period is locked, adjustments are blocked until it is unlocked. All journal entries in configured journals pass through an approval chain: two or more approvals can be required per journal entry, with each entry routed to the first approver and then to the next after approval. To enforce prior-period-specific oversight, administrators configure a dedicated journal (for example, an adjusting or prior-period journal) with a stricter approver chain: in the Approvers section of GL configuration, specific journals are mapped to specific approvers or user groups. The audit trail is system-wide and object-level: Sage Intacct keeps a continuous audit trail of transactions, showing what a field value was before, what it was changed to, when it was changed, and who changed it, effectively eliminating speculation and maintaining GAAP compliance. The developer-accessible AUDITHISTORY object is a combination of standard object record audit trail logs, user access logs, and smart event log records, and can return the aggregated history for a given user, all records of a specific object type, or all records across a defined period of time. Sage Intacct's own Record to Report compliance documentation explicitly lists "the ability to post to prior or future periods is restricted" and "controls to ensure that journals are recorded in the correct period" as native internal control options.

For a manufacturing finance team needing to reverse a batch of period-end accrual entries (including variance accruals), Sage Intacct provides two complementary mechanisms in its General Ledger module. First, a 'Process multiple journal entries' bulk action allows users to navigate to General Ledger > All > Journal Entries, select a journal, check individual or all transaction checkboxes, and click 'Reverse' to apply a user-specified reversal date across all selected entries simultaneously; the mass update feature reverses multiple entries at once, allowing the original date or a new date, but only posted journal entries can be reversed. Second, recurring journal entry templates support built-in auto-reversal scheduling: the Schedule tab controls automatic reversals, and if a recurring entry is always reversed in the following period (a common accrual pattern), both schedules can be configured at setup time; two options are available, including linking the reversing entry to the original at a fixed interval. However, there is a critical constraint for manufacturing variance accruals specifically: transactions created in other applications (such as WIP or inventory costing sub-modules) cannot be reversed in the General Ledger; to undo such a transaction, the user must go to the originating application. Additionally, bulk reversal updates work only for transactions in the same journal, meaning accruals spread across multiple journals require multiple separate reversal runs.

For a manufacturer operating plants, distribution subsidiaries, sales offices, holding companies, and joint ventures across multiple countries, Sage Intacct uses its Multi-Entity Management module and a 'Multi-Entity Shared' container architecture. Each legal entity is set up as a separate record representing "a separate tax identification or a separately secured, fully balancing set of books," with shared data lists (chart of accounts, vendors, customers) defined at the top level and entity-level access controls restricting users to specific entities. The platform supports consolidations across "hundreds" of entities within a single instance without requiring separate tenants. For multi-country deployments with different base currencies, the Global Consolidation subscription handles currency translation and intercompany eliminations; for joint ventures and partially owned entities, the Advanced Ownership Consolidation subscription explicitly supports "tiered structure or partial ownership" scenarios. New entities can be added by administrators without IT involvement, inheriting existing lists and process definitions.

For a manufacturing buyer needing always-current consolidated financials across plants, distribution subsidiaries, sales offices, holding companies, and joint ventures, Sage Intacct provides its Global Consolidations module (and Domestic Consolidation for single-currency structures), which uses 'consolidation books' configured with designated elimination entities and inter-entity account mappings. During consolidation, users configure their ownership structure or consolidation book to automatically generate offsetting entries against inter-entity activity in the elimination entity. By default, Sage Intacct automatically applies elimination to the inter-entity payable and receivable accounts specified in the inter-entity account mapping, covering due-to/due-from balances, intercompany loans, and intercompany revenue/expense pairs. The critical limitation for the buyer's 'real-time' requirement is the trigger model: consolidation requires the user to select books and a period range and click the consolidate button, though a recurring schedule can be set up so the process runs in the background. For a quick look at financials, a user can consolidate any time on the fly, but the consolidated book does not update automatically and continuously as individual entity transactions post. This means the consolidated ledger reflects the state of each entity as of the last consolidation run, not the current moment, which is a material gap against the buyer's requirement for real-time roll-up. The vendor's positioning claims the ability to 'consolidate 100s of entities across currencies and geographies in minutes, not days,' which reflects run speed rather than continuous ledger aggregation.

For a manufacturing buyer with joint ventures and partially owned subsidiaries, Sage Intacct addresses this requirement through its Advanced Ownership Consolidation subscription, a tier above Global Consolidation built specifically for partial-stake structures. The user configures an ownership structure object that defines parent-subsidiary relationships and the exact ownership percentage per entity; this object includes complex information such as parent and subsidiary relationships, the percentage of each entity owned by the company, and the consolidation method to be used. During a consolidation run, Intacct determines the net income or loss for the subsidiary, multiplies it by the non-controlling interest percentage (expressed as 100% minus the percent owned), posts the calculated amount to the net income attributable to NCI account, and posts the offset to the NCI equity account. For JV structures where the buyer holds a minority stake rather than a controlling stake, the equity consolidation method automatically records a subsidiary's net income to the parent entity based on ownership percentage, automating the recording of subsidiary income to a user-defined book for the parent entity. Advanced Ownership Consolidation supports consolidated reporting for companies with complex organizational structures by using the Full consolidation, Consolidation, Equity, and Proportional methods to produce accurate consolidated reports. Ownership percentages can be updated by period as JV stakes change over time.

For a manufacturing group needing legal, management, geographic, and product-line consolidation views simultaneously, Sage Intacct's primary mechanism is the Consolidation Book: consolidation books define how to combine the financial and operational information of selected entities within multi-entity companies. An administrator creates separate books by freely selecting any subset of entities to include, assigning a dedicated elimination entity per book, and configuring auto-elimination and dimensions independently for each. The platform supports flexible addition and removal of entities to model organizational structure based on how you report results, with full control of auto-eliminations, currency translation rules, and dimensions to consolidate and create detailed reports. This means a geographic book (e.g., APAC entities) and a product-line book (e.g., all entities in a specific division) can coexist as separate books, each running intercompany elimination independently. For multi-level ownership trees, Advanced Ownership Consolidation provides on-demand consolidation and the ability to define multi-level ownership structures by period with dedicated reporting books generated for each reporting level and parent entity. However, this tiered book-per-level feature is anchored to legal ownership structures: the hierarchy is built by defining parent-child ownership percentages, not by freely assigning entities to non-ownership-based groupings. A management or product-line hierarchy that cuts across legal ownership would be modeled as a flat book (all relevant entities lumped into one book without sub-levels), not as a true multi-level tree with intermediate roll-up nodes and eliminations at each node. The buyer will get multiple independent consolidation books with per-book elimination for geographic or product-line groupings, but will not get the same multi-level intermediate-node elimination capability for non-ownership hierarchies that Advanced Ownership Consolidation delivers for the legal hierarchy.

For a manufacturing buyer with subsidiaries or plants operating on different fiscal year calendars (e.g., a UK entity with an April year-end rolling up into a US parent with a December year-end), Sage Intacct handles the mismatch at the consolidation layer rather than forcing a shared calendar. Each entity configures its own accounting calendar independently: standard calendars allow any month as the fiscal first month, and custom calendars allow fully bespoke period boundaries including 4-4-5 structures. When consolidation runs, the Consolidation application performs automatic mapping of reporting periods based on dates, and the documentation explicitly notes that the user can override this default mapping when the system does not resolve the alignment correctly. This means period-bridging occurs within the consolidation module without requiring entities to restructure their local books. The three consolidation tiers (Domestic, Global, and Advanced Ownership) all operate within this architecture, so the mechanism scales to multi-currency, multi-jurisdiction structures.

For a manufacturing group needing to bill shared services (IT, HR, engineering, quality, logistics) across legal entities, Sage Intacct provides two interlocking mechanisms. First, the inter-entity bill back feature handles the billing leg: inter-entity bill back enables you to automatically generate an AP purchase invoice in the Accounts Payable of the receiving entity each time an AR sales invoice is created from the service-provider entity. Templates are configured per service relationship, so when the shared-service entity raises an AR invoice, the system automatically generates an Accounts Payable bill for the other entity. Second, the Dynamic Allocations module handles driver-based cost distribution upstream of billing: Sage Intacct supports statistical accounts or relative financial account balances as basis out-of-the-box, and allows use of any standard or user-defined dimensions when setting up allocations. Recurring allocations can be set up to run automatically, without needing to be manually triggered. These allocations can span entities, distributing assets, costs, and revenue contributions across products, projects, departments, and other dimensions, including auto-scheduled recurring allocations across entities. Settlement uses the centralized due-to/due-from framework: centralized inter-entity transaction setup of due-to, due-from, and direct settlement accounts keeps intercompany AR and AP balanced, and the receiving entity settles via its standard AP payment workflow.

For a manufacturing buyer running intercompany transactions across plants and subsidiaries, Sage Intacct mitigates many imbalances at the point of entry rather than through a dedicated pre-close workbench. Sage Intacct records inter-entity transactions separately from other transaction types, and for each entity users can specify the payable and receivable accounts used for IETs, all configurable on one central page. An Advanced mapping plan defines separate due-to/due-from account sets for each entity relationship (entity pair), enabling granular tracking by counterpart. Intacct auto-balances IET general ledger journal entries across entities with multiple base currencies, and GL journal entries show the source and inter-entity entries, making it possible to drill down and trace a given transaction. At period-end, it is best practice to select inter-entity auto-elimination on the consolidation book; during consolidation, Intacct automatically eliminates inter-entity receivable and payable balances, netting them out in the elimination entity and avoiding overstatement. However, no dedicated intercompany reconciliation workbench surfaced in Sage Intacct's documentation: there is no purpose-built UI that surfaces out-of-balance positions by entity pair before the period close, no automated cross-entity matching engine that flags unmatched items, and no workflow for assigning discrepancies to owners and marking them resolved. Users who want visibility into intercompany balances by entity pair must build a custom financial report, navigating to Reports > Financial Reports and expanding actual columns by location, to see IET balances by GL account and location. The BlackLine Intercompany Hub, listed as a separate marketplace add-on, is positioned as a clearinghouse that reconciles, nets, and settles intercompany transactions in real time; its existence on the Sage Intacct Marketplace confirms that this workbench-level capability is not native.

For a manufacturing group needing to enforce arm's-length pricing on intercompany product transfers across tax jurisdictions, Sage Intacct's Multi-Entity and Global Consolidations module handles the accounting mechanics: users configure inter-entity transaction (IET) accounts for each entity pair, and administrators establish relationships and define intercompany accounts through a centralized mapping page. The module offers configurable rules for inter-entity transactions and allows setup of eliminations and currency translation rules. However, these "configurable rules" govern account routing and balancing, not pricing method selection or markup enforcement. For mid-market groups where transfer pricing documentation is prepared by the finance team or an external advisor rather than a dedicated TP platform, Sage Intacct provides the cleanest intercompany data architecture available at this price point - but no native mechanism enforces arm's-length pricing methods (cost-plus, CUP, resale price), defines pricing schedules by entity pair or jurisdiction, or generates BEPS-aligned documentation (Master File, Local File, CbCR). Avalara's transfer pricing module adds dedicated TP documentation and benchmarking for groups that need a compliance layer beyond what the ERP provides.