Campfire vs Rillet vs NetSuite for ERP & Core Accounting

For a professional services and distribution company running 8 legal entities across the US and Canada, Campfire's AR module supports configurable invoicing at the entity level through a natively documented feature called Configurable Invoice Fields Per Entity. As of Campfire's January 2026 product update, finance teams can tailor invoice fields on a per-entity basis: hiding fields irrelevant to a jurisdiction, renaming standard labels to match local legal terminology, and ensuring each entity generates invoices that read correctly for its local market without manual template management. Per-entity branding is further supported at the entity settings level, where each entity carries its own logo URL. At the service-line level, Campfire's invoice line items support department, product, tag, and tag-group fields, allowing each line to carry service-line identity that flows through to GL coding and reporting. Invoices are always entity-scoped (the entity field is required on every invoice creation call), so the data model enforces entity segregation through the full AR workflow from invoice creation to reconciliation.

For your 8 entities, NetSuite OneWorld treats each entity as a subsidiary and lets you set invoice templates per subsidiary, which goes well beyond the single company-wide invoice layout you have in QuickBooks Enterprise. The IPT Preference page lets you pick a default invoice template for each subsidiary. The choices include standard PDF/HTML, advanced PDF/HTML and Advanced Localization Feature templates. The default for a subsidiary carries to the customers associated with it. Advanced PDF/HTML templates are editable in a WYSIWYG or source-code editor. They can show the correct branding, bank details, tax IDs and currency formatting for each subsidiary. For service-line variants, partners report using separate custom transaction forms or workflows that switch the print template. Practitioners describe using a workflow to set distinct templates, so one UI form can print with different templates. Invoice creation itself is automated: when a billing schedule is assigned on a sale or line, NetSuite adds a bill to the billing queue at the schedule's intervals. Advanced Billing is a separately enabled feature. This operates at the invoice-generation and presentation step of AR, and invoices post to the same unified ledger, so your later consolidation and close steps are unaffected.

No public documentation covering this requirement was found on the documentation sources this vendor publishes. That is a limit of the public evidence, not a finding about the product.

For a $180M company with 8 legal entities spanning professional services and distribution, Rillet's native AR module handles automated invoice generation in two modes: contract-driven schedules (where Rillet generates an invoice sequence from contract terms, with per-line descriptions configurable per contract item) and standalone invoices created manually, via template file upload, or through its public API. Rillet automatically generates an invoice schedule based on the details of the contract, which can be further customized to fit customer needs. Standalone invoices can be created manually, loaded through a template file, or pushed via Rillet's public API. As of July 2026, Rillet added account-wide branding controls to AR documents: invoices, credit memos, customer statements, and emails now support a custom color that carries through every document, and 'Powered by Rillet' branding has been removed. Invoices carry a subsidiary identifier in the data model, so each invoice is associated with the correct entity, but there is no documented mechanism for assigning distinct invoice templates (separate logos, layouts, or field configurations) per entity or per service line within the platform's UI.

For a 320-person, 8-entity company moving off QuickBooks Enterprise, Rillet offers inbound enterprise SSO for logging in to the ERP itself. Its Security and Permissions page lists SSO through Google, Microsoft Entra, or Rippling, plus magic-link login as an alternative (Rillet Security and Permissions page). Rillet's own control summary also lists SSO alongside SOC 1 Type II and SOC 2 Type II audits as a platform security feature (info.rillet.com, Control Integrity in Rillet). Users sign in through the Entra identity provider, then receive one of Rillet's roles: Owner, Admin, Accountant, or view-only. Permission changes take effect immediately and are recorded in an audit history. This covers the sign-in step for the controller, AP staff, and auditors before the 12-month audit.

For your 8-entity US/Canada group moving off QuickBooks Enterprise (which has no native Azure AD SSO), NetSuite's SAML Single Sign-on feature lets Microsoft Entra ID (formerly Azure AD) act as the identity provider. The feature is based on SAML v2.0, and any SAML 2.0-compliant application can serve as the IdP. An administrator enables the feature under Setup > Company > Enable Features > SuiteCloud, in the Manage Authentication section. They then complete the SAML Setup page and add the SAML permission to the roles that need SSO. Microsoft publishes a gallery app for this setup: a tutorial for integrating Microsoft Entra SSO with NetSuite. Access control then sits in Entra, where you control who has access to NetSuite.

For a buyer running 320 employees across 8 entities and preparing for audited financials, centralized identity management is a security baseline. SSO is confirmed as a named Campfire security feature: a competitor comparison page notes that Campfire 'publicly emphasizes SOC 1/SOC 2, encryption, RBAC, AI audit trails, and SSO,' and an independent ERP evaluation site flags 'Strong access controls (SSO/MFA)' as part of Campfire's posture. However, no official Campfire help-center documentation was found that specifies the identity protocol (SAML 2.0 or OIDC), names Azure Active Directory/Entra ID as a supported identity provider, or documents SCIM-based automated user provisioning and deprovisioning. The fact sheet's claim of 1,200+ granular permissions confirms a rich access-control model, but that covers authorization within the product, not the upstream authentication federation that Azure AD SSO requires.

For your 8 US and Canadian entities, which today sit in separate QuickBooks Enterprise files with spreadsheet consolidation, NetSuite OneWorld keeps one shared chart of accounts and models each entity as a subsidiary. Each account record has a Subsidiaries field that limits the account to selected subsidiaries only. An account can be tied to one or more specific subsidiaries, which limits its availability to those subsidiaries. The Include Children box extends an account to all child subsidiaries of the selected ones. So a shared core of accounts can be posted by all entities while entity-specific accounts stay restricted. Entity-specific sub-segments come from Department, Class and Location plus Custom Segments. A department must be associated with a subsidiary before it can be selected on that subsidiary's transactions. Custom segment values can be filtered by location, class and department, and by subsidiary in OneWorld accounts. Custom segments with GL impact can be tagged on individual GL posting lines, like standard segments. Because everything sits in one ledger, the same structure feeds NetSuite's consolidated reporting across subsidiaries, so intercompany eliminations and consolidation no longer depend on spreadsheet mapping. This happens at the GL setup stage, before AP invoice coding.

For your 8 US and Canadian entities, Campfire runs all of them in one ledger rather than separate company files like QuickBooks Enterprise. Per its site, entities and currencies roll up into one view, updated in real time, and it advertises unlimited entities. Instead of a multi-part account string, it codes GL lines with a chart-of-accounts account plus a department and tags, which can be grouped into tag groups. Its API shows these fields on journal lines, and journal entries carry an entity, account, department and tags. Third-party sources describe unlimited custom dimensions (unlimited custom tags and dimensions) and say the system automatically maps entity level accounts to the consolidated chart of accounts. A reseller page says each entity can keep its own chart of accounts, but this is not confirmed in Campfire's own documentation. Net effect: you get a shared ledger with department and tag dimensions and a consolidation mapping, which covers the move off spreadsheet consolidation.

For your 8-entity US and Canada group, Rillet uses one organization-level chart of accounts shared by all subsidiaries. The API returns the chart of accounts for the organization tied to the API credentials, and each account record carries an id, code, name, type, subtype, status and an intercompany flag. Rillet describes the shared accounting model as a chart of accounts, a reporting calendar and standardized mappings, and dimensions or segments such as entity, department, class, location, project or custom segments sit on top of it for slicing. Entity-level detail comes from those dimensions and from Flexible GAAP Reporting categories, which teams use to standardize rollups across subsidiaries while preserving entity-level detail. This covers the unified part of your requirement and the consolidation and elimination step. It operates at the GL and reporting layer, not at pre-processing.