Carillon ERP Is an Acumatica Alternative for Companies That Want More Control

Acumatica states that Acumatica Cloud ERP is sold exclusively through its partner channel and that Acumatica matches customers with one of its 350+ Value Added Resellers to deliver service from planning through deployment and ongoing support.

Acumatica’s own implementation-partner guidance says successful implementation depends as much on finding the right partner as finding the right software.

Acumatica’s public support materials state that its international network of experienced resellers helps customers with the evaluation, implementation, training, and ongoing support of Acumatica ERP. Acumatica’s Direct Support terms separately state that support plans do not include training, consulting, or implementation services, and that customers should contact their Acumatica partner for those services.

That makes partner evaluation a critical part of the Acumatica buying decision and should be considered as importantly as the software.

Buyers should consider the partner’s longevity, staffing depth, Acumatica certifications, industry knowledge, data-conversion experience, reporting capabilities, and documentation practices before committing to the relationship.

That matters because even Acumatica's optional direct "Premier" support does not offer implementation services including training, data conversion and other implementation services. Also be aware that Acumatica publicly states it utilizes a global workforce.

Although changing Acumatica partners is apparently possible, it is like starting over with someone who is likely not familiar with your business.

Carillon takes a more direct approach. Carillon ERP clients receive direct access, both on-site and via Microsoft Teams including voice, screen sharing, and text, to the United States-based team responsible for developing, implementing, and supporting the system.

Using screen sharing in Microsoft Teams, Carillon can provide support faster than a local Acumatica reseller can drive to your site.

Third-party Authorized Consultants may assist, but direct access to the Carillon support team is built into the client relationship and always available.

That difference matters over the life of the ERP system. Training, data conversion, reporting assistance, implementation services, configuration guidance, integrations, workflow, security, and ongoing support all depend on the capabilities and continuity of the people providing those services.

Sources: Acumatica, “About Us”; Acumatica, “Support”; Acumatica, “Direct Support Programs”; Acumatica, “Choosing an ERP Implementation Partner”; Acumatica ESG materials.

Acumatica’s current public licensing materials describe two primary models for Acumatica Cloud ERP: SaaS Subscription and Private Cloud Subscription. According to Acumatica’s public licensing materials, both models are subscription-based and grant use of Acumatica Cloud ERP for the life of the subscription.

Acumatica previously offered Private Cloud Perpetual licensing, but Acumatica’s April 2022 Licensing Guide states that Private Cloud Perpetual was no longer available for new sales effective April 1, 2022. Consequently, for new buyers, Acumatica’s generally available public licensing path is subscription-based rather than perpetual-use licensing.

Acumatica’s SaaS agreement reflects a term-based subscription commitment. The standard agreement states that the initial term is one year unless otherwise stated in the customer’s Acumatica Order Form, and that the agreement automatically renews for additional one-year terms unless otherwise stated in the order form. Acumatica’s FAQ also states that after the first year, customers may cancel Acumatica SaaS service at the time of renewal with a minimum of 30 days’ written notice.

Carillon provides a distinct alternative. For organizations prioritizing flexibility, Carillon’s SaaS license is month-to-month and can be canceled with 10 days’ notice. For organizations prioritizing long-term ownership, Carillon continues to offer a perpetual use license with a one-time upfront payment, granting the right to use the software permanently without mandatory ongoing SaaS subscription fees.

This distinction is important. When evaluating ERP software, a company is also choosing a long-term commercial framework. Carillon gives buyers a choice between a flexible SaaS model and a perpetual-use license. Acumatica’s current public materials direct new buyers toward subscription licensing.

At Carillon, we believe customers should choose the licensing model that aligns with their business strategy, cash-flow preferences, ownership philosophy, and long-term technology plan. Carillon’s goal is to retain customers through the continued value of the system, supported by the freedom of a licensing model that fits the customer’s specific needs.

Sources: Acumatica, “Agreements and Guides”; Acumatica Licensing Guide, April 2022; Acumatica Subscription SaaS Agreement, September 2025; Acumatica FAQ.

With Carillon's SaaS license, the relationship is straightforward. A customer can opt out with 10 days' notice. When the SaaS license ends, there are no remaining SaaS license fees and no third-party financing obligation created by Carillon. If the customer chooses a perpetual license instead, the customer makes a one-time payment and receives the right to use the software permanently.

Acumatica's public SaaS agreement reflects a term-based subscription commitment. The agreement states that the initial term is one year unless otherwise stated in the customer's Acumatica Order Form, and that the agreement automatically renews for additional one-year terms unless otherwise stated in the order form.

Acumatica's SaaS agreement also states that termination for any reason other than Acumatica's uncured material breach does not relieve the customer of the obligation to pay all future amounts due. In other words, monthly billing, if offered, is not the same as month-to-month licensing.

That difference matters when evaluating ERP risk. A buyer should understand whether it can leave on short notice, whether fees remain due through the end of the subscription term, and whether the licensing model matches the company's tolerance for long-term contractual commitments.

In Carillon's view, ERP customers should know exactly what happens if they decide to stop using the system. Carillon's SaaS model gives customers a clear exit path, while Acumatica's public SaaS agreement reflects a term-based subscription commitment.

Source: Acumatica Subscription SaaS Agreement, September 2025.

If you are an Acumatica customer who wants to move to Carillon but is still contractually obligated under an existing Acumatica agreement, Carillon will waive its SaaS license fee for the duration of your remaining Acumatica subscription term. You can begin implementing and using Carillon immediately - with no Carillon SaaS license fee - while you fulfill your remaining Acumatica obligation.

Acumatica's public SaaS agreement reflects a term-based subscription commitment. The agreement states that the initial term is one year unless otherwise stated in the customer's Acumatica Order Form, and that the agreement automatically renews for additional one-year terms unless otherwise stated in the order form. The agreement also states that termination for any reason other than Acumatica's uncured material breach does not relieve the customer of the obligation to pay all future amounts due.

Carillon's offer is designed to help companies move forward without paying two SaaS license fees at the same time. Professional services, data conversion, implementation support, training, report writing, and other services are available at standard rates. The waiver applies to the Carillon SaaS license fee only. It does not pay, assume, or cancel any obligation the customer may have to Acumatica, an Acumatica partner, or any other third party.

Carillon makes this offer because no business should have to delay a better ERP decision simply because an existing subscription term has not yet expired. If Acumatica is not the right long-term fit for your business - whether due to functionality, support structure, licensing, cost, implementation experience, or any other reason - Carillon wants to help you get unstuck.

To discuss your situation, contact us directly. Every circumstance is different, and we are happy to have that conversation.

Source: Acumatica Subscription SaaS Agreement, September 2025.

When an Acumatica customer needs functionality that does not exist in the core product, that functionality may be developed as a customization. Acumatica's own documentation describes a customization project as "a set of changes to the user interface, configuration data, and functionality of Acumatica ERP" developed using the Acumatica Customization Platform.

That flexibility can be valuable, but it can also create long-term maintenance responsibility. Acumatica's documentation recognizes that customized instances require upgrade attention. Before upgrading a customized Acumatica instance to a new version, the Acumatica Customization Platform validates the compatibility of the code included in currently published customization projects with the application code of the update version. Acumatica also directs users upgrading between versions to review technical release notes for breaking changes.

Carillon works on a different principle. When a client needs functionality that does not yet exist and Carillon determines that the functionality belongs in the core product, Carillon builds it directly into the core system. The development cost is absorbed once, and the benefit becomes available as part of Carillon ERP rather than maintained as a separate customer-specific customization layer.

Carillon believes this model makes the product stronger over time. Each client engagement can improve the system for the broader customer base, and customers are not left managing a separate customization layer that must be reviewed, validated, and maintained through future upgrades.

For ERP buyers, the question is not whether customization is possible. The question is who owns the long-term maintenance burden. In Carillon's view, functionality that belongs in the ERP system should become part of the ERP system.

Sources: Acumatica, “Customization Projects: General Information”; Acumatica, “To Resolve Issues While Upgrading a Customized Website”; Acumatica, “To Use the Technical Release Notes to Find the Breaking Changes”; Acumatica, “Acumatica 2026 R1: Latest Acumatica AI-Enabled Product Release Delivers Intelligence.”

Carillon operates on a direct-data-access philosophy. Carillon ERP runs on Microsoft SQL Server 2025 and supports all editions of Microsoft SQL Server 2025. Carillon clients have direct access to their own ERP database using standard SQL tools. Carillon also supports SQL Server failover capabilities available in Microsoft SQL Server 2025, including Always On availability groups in editions that support them.

Carillon normally uses Windows Authentication for SQL Server database access. A Carillon user can receive SQL Server CONNECT rights individually or through membership in an Active Directory security group. Carillon also supports SQL Server Authentication, but it is rarely used because of the potential security risk. For Carillon Everywhere, Microsoft Entra authentication is used.

That means Carillon customers can design their SQL Server environment around their own availability, reporting, security, performance, and data-residency requirements. With Carillon, the customer controls where its Microsoft SQL Server database is located, including the country in which the database resides. Customers can connect reporting tools, analytics tools, Power BI, auditors, IT staff, and internal developers directly to the ERP database using standard SQL Server tools.

According to Acumatica’s published SaaS FAQ, Acumatica SaaS currently uses Microsoft SQL Server, but Acumatica SaaS no longer allows ODBC access and directs customers to Acumatica’s development platform APIs instead. Acumatica identifies reasons for that model, including avoiding the need to learn complex database structures, protecting system stability, reducing upgrade-maintenance risk, and enforcing security policies.

That SaaS limitation is easier to understand when viewed alongside Acumatica’s multitenant architecture. In Acumatica terminology, a “tenant” is a logical data partition inside an Acumatica application/database environment. According to Acumatica’s published documentation, multiple tenants can use the same Acumatica application instance, with each tenant having isolated data. Acumatica documentation also describes configurations where one Acumatica application instance can give multiple tenants web access to the same database.

In practical terms, multiple companies’ or tenants’ data can reside in one physical SQL Server database, with separation defined and enforced logically by Acumatica. In Carillon’s view, that represents a distinct data-control model from Carillon’s approach, where each customer has direct access to its own Microsoft SQL Server database.

Acumatica Private Cloud is different from Acumatica SaaS. Based on Acumatica’s public licensing documentation, Private Cloud Subscription customers may deploy and manage the software on their own premises, through their own physical servers, or have the software hosted or managed by a VAR or third party. In that model, database and infrastructure access may depend on how the customer, VAR, or hosting provider configures and manages the environment.

Acumatica has publicly announced support for SQL Server 2025. However, we were unable to determine from Acumatica’s public documentation which editions of Microsoft SQL Server 2025 Acumatica supports.

For ERP buyers, the issue is not just whether the system stores data in SQL Server. The issue is whether the customer has direct, standard access to its own ERP database without depending on a SaaS API-only access model, application-enforced logical separation in a shared database architecture, or deployment-specific access arrangements. In Carillon’s view, ERP data should be directly accessible to the customer in a database format the customer’s own IT team, analysts, auditors, and reporting tools can use.

Sources: Acumatica FAQ; Acumatica, “Managing Tenants by Using the Web Interface”; Acumatica Licensing Guide, October 2025; Acumatica Community, “Important Update: Deprecation of SQL Server 2019 and Added Support for SQL Server 2025”; Microsoft Learn, “Basic Always On availability groups.”

Acumatica prominently markets “Unlimited Users” and says customers pay for functionality, “not for user seats.” But Acumatica’s current licensing materials show that the user-count story depends on the licensing model. Acumatica Essentials is capped by named-user limits, while Acumatica’s transaction-tier model shifts the scalability issue from user count to commercial transaction volume.

1. The “Named User” Hard Cap

Acumatica’s “Unlimited Users” message is not universal. Acumatica Essentials is a named-user product with a hard 10-user maximum.

The Restriction: According to the current Acumatica Licensing Guide, Acumatica Essentials includes access for five named users and can be upgraded to ten named users. Table 5 lists Essentials with five named users included and a maximum of ten named users.

The Upgrade Barrier: The current Acumatica Licensing Guide says Essentials includes access for five named users and can be upgraded to ten named users. It does not describe an option to add an 11th Essentials user. Instead, Acumatica’s current product structure moves beyond Essentials to Select, Prime, and Enterprise, and the guide says that if a customer’s needs change during the initial subscription term and require an increase in users or a higher-level edition, the upgrade is priced for the remainder of the initial subscription term.

2. The Transaction Tier Consumption Model

For customers using Acumatica’s transaction-tier model, the pricing pressure shifts from user seats to commercial transaction volume.

The Metric: According to the current Acumatica Licensing Guide, Transaction Tier Consumption Licensing is based on Monthly Commercial Transaction Volume (CTV). Monthly CTV is the single highest monthly volume among eight transaction types: sales orders, shipments, AR invoices, customer payments, purchase orders, purchase receipts, AP bills, and AP payments.

The Tier Pressure: While the users may be “unlimited” under the transaction-tier model, the Transaction Tiers are capped. The Acumatica Licensing Guide says exceeding the maximum CTV in any given month creates an out-of-compliance situation that may require increasing the Transaction Tier level mid-contract. The Acumatica EULA, Section 2.8, also says that exceeding licensed transaction volumes for any three months during the trailing twelve-month period is a material breach. For a seasonal or growing business, higher transaction volume can therefore become a licensing issue even when user count is not.

3. Carillon is a whole lot simpler.

Unlimited internal and external users, and no transaction-tier consumption pricing.

Sources: Acumatica Pricing page ; Acumatica Licensing Guide — October 2025 ; Acumatica End-User License Agreement — January 2026, Section 2.8, Use Reporting .

Acumatica’s “Private Cloud” option allows customers to choose their own hosting provider or deploy on-premises, which is often marketed as a way for users to maintain control over the software environment. However, Acumatica’s legal and technical requirements ensure that “Private” does not mean “Isolated.” The software is contractually required to monitor and transmit usage and business-activity metrics back to Acumatica, such as user counts, transaction volumes, resource-level utilization, license-key numbers, server IP addresses, and other information. Those transaction volumes include core ERP activity such as sales orders, shipments, AR invoices, customer payments, purchase orders, purchase receipts, AP bills, and AP payments.

1. The Mandatory “Unblocked” Transmissions

Acumatica’s EULA imposes a strict requirement for the software to transmit usage and business-activity metrics to Acumatica, such as user counts, transaction volumes, resource-level utilization, license-key numbers, server IP addresses, and other information. Those transaction volumes include core ERP activity such as sales orders, shipments, AR invoices, customer payments, purchase orders, purchase receipts, AP bills, and AP payments. Even in a private environment, the customer is contractually prohibited from blocking the required transmissions.

The Mandate: The Acumatica EULA, Section 2.8, Use Reporting, states that the customer “agrees not to block, electronically or otherwise, the transmission of data required for the monitoring of compliance.”

The Consequence: For businesses with high-security requirements or those that prefer an air-gapped ERP environment, this requirement prevents Acumatica from being fully isolated from Acumatica’s license-use reporting. The customer must allow the required transmissions, even when Acumatica is deployed in a private cloud or on the customer’s own premises.

2. Granular Monitoring of Core ERP Activity

Because Acumatica licensing can be tied to transaction volume, the software acts as a persistent monitor of core ERP activity.

The Scope of Surveillance: According to the Acumatica Licensing Guide and the EULA, the software monitors transaction volumes, user counts, resource-level utilization, license-key numbers, server IP addresses, and other information. The Licensing Guide defines Monthly Commercial Transaction Volume as the single highest monthly volume among eight transaction types: sales orders, shipments, AR invoices, customer payments, purchase orders, purchase receipts, AP bills, and AP payments.

The “Big Brother” Effect: This gives Acumatica a recurring license-reporting window into your business activity. Your private database is, by design, reporting internal operating metrics to an external third party, including transaction volumes tied to sales orders, shipments, invoices, payments, purchase orders, receipts, AP bills, and AP payments.

3. Acumatica’s Rights After Data Is De-Identified or Aggregated

Acumatica’s Platform Privacy Statement says Acumatica automatically collects product usage data, including which activities and features are used in the services, customer storage configuration settings, and technical data relating to devices and service performance. Acumatica’s EULA separately says the software monitors usage and business-activity metrics, such as user counts, transaction volumes, resource-level utilization, license-key numbers, server IP addresses, and other information. Those transaction volumes include core ERP activity such as sales orders, shipments, AR invoices, customer payments, purchase orders, purchase receipts, AP bills, and AP payments.

Acumatica’s Platform Privacy Statement also says Acumatica may use personal information for testing, research, analysis, product development, and improving its services, and may share personal information with group companies, affiliates, and service providers assisting in the operation, management, improvement, research, and analysis of the services. The same statement says personal information under California law does not include de-identified or aggregated consumer information.

That creates an important question for customers: once usage or transaction-pattern data is de-identified or aggregated, what contractual limit prevents that information from being used for Acumatica’s own business analysis, benchmarking, product development, or ecosystem benefit?

4. Carillon is a whole lot simpler.

Operational privacy without mandatory vendor use reporting.

At Carillon, “private” means your ERP usage is not being reported back to Carillon. Carillon has no reporting connection that monitors your transaction volumes. Your business data, and the metadata describing how you work, stay within your control, with no “unblocked” reporting requirement tied to your sales orders, shipments, invoices, payments, purchase orders, receipts, AP bills, or AP payments.

Sources: Acumatica End-User License Agreement — January 2026, Section 2.8, Use Reporting ; Acumatica Licensing Guide — October 2025 ; Acumatica Platform Privacy Statement .

A well-designed ERP system should be able to answer questions across the full history of the business. What did we pay for this item ten years ago? What did this customer buy over the last decade? How did gross margin change across product lines, customers, branches, or time periods? These are not archive questions. They are business questions, and the ERP system should be able to answer them from live, queryable history.

1. The Pressure to Purge

Acumatica’s own documentation acknowledges that database growth has to be managed. Its database-maintenance documentation says tenant and snapshot data may take a lot of space, that the database size available for an Acumatica ERP instance is limited by the license, and that administrators may need to monitor, optimize, and clean up the database so users have sufficient space to perform needed operations.

2. The “Reference-Only” Archive Model

Acumatica documents an archive model where archived documents become reference records instead of fully usable operational records.

Limited Utility: According to Acumatica Help, an archived document is “not fully usable,” can only be viewed for reference, and most boxes, buttons, and actions are disabled by default.

The Extraction Hurdle: To make the document fully usable again, it must be extracted from the archive.

That distinction matters. Historical ERP data is most valuable when it remains part of the live system: available for reporting, analysis, investigation, customer service, purchasing decisions, pricing decisions, audit support, and long-term trend analysis. A record that must be extracted from an archive before it becomes fully usable is not the same thing as live business history.

3. Carillon: Built for Permanent Online History

Carillon was built on a different premise. Carillon keeps long-term transaction history live in the ERP database.

No Purge Required: Carillon clients with over 20 years of transaction history online have not had to purge or archive their data.

Live Querying: Some database tuning may be required as data grows, but the history stays in the system: live, queryable, and available for reporting and analysis.

Your history is part of your business. It should not become a reference-only archive record. It should remain online, accessible, and ready to answer the questions your business needs to ask.

Sources: Acumatica Database Maintenance Documentation ; Acumatica Help — Archiving Documents .

Beverage alcohol companies have requirements that go beyond ordinary inventory, purchasing, sales order, warehouse, and manufacturing transactions.

A wine, spirits, and/or beer distributor or manufacturer needs to manage proof, alcohol by volume, vintage, varietal, appellation, country of origin, bottle size, case-to-bottle conversions (several layers deep for miniatures), repacked assortments, bonded warehouse inventory, bonded cost, landed cost for imported finished goods, landed cost for raw materials, production orders, bills of material, kitting, and finished-goods costing.

The Acumatica Distribution Edition materials reviewed do not list beverage-alcohol-specific distribution features such as proof, alcohol by volume, vintage, varietal, appellation, country of origin, case-to-bottle conversion, repacked assortment tracking, bonded warehouse inventory, or bonded-cost pricing.

Acumatica publishes Manufacturing Edition materials that also list no special features that are unique to this industry.

After reviewing Acumatica’s publicly available materials, Acumatica appears to have some lot-tracking capability. However, the materials reviewed do not make clear whether Acumatica can trace a recalled ingredient, such as a spice used several levels deep in a recipe, through production into finished goods and then identify all customers to whom those finished goods were shipped.

Acumatica documents landed cost processing for purchased or transferred stock items. Its help materials state that landed cost amounts can be allocated to purchase receipts or transfer receipts, and its landed-cost-code documentation identifies examples such as freight or other shipping costs, insurance, customs duties, and other taxes. The Acumatica landed-cost materials reviewed do not document allocating costs to a shipping container that has been through multiple consolidators and includes goods sourced from multiple suppliers.

The Acumatica materials reviewed do not identify proof, alcohol by volume, vintage, varietal, appellation, country of origin, bottle-size-specific inventory handling, case-to-bottle conversion, repacked assortment tracking, bonded warehouse inventory, bonded-cost pricing, beverage-alcohol production, beverage-alcohol finished-goods costing, or container-level landed-cost allocation through multiple consolidators and multiple suppliers as native Acumatica core functionality.

Carillon documents these beverage-alcohol requirements directly.

Carillon’s beverage-distribution brochure and website page state that Carillon tracks item information including proof, vintage, and grape varieties. They also list beverage-distribution functionality including multiple units of measure, item-specific unit-of-measure conversions, case unpacking and repacking, tracking cases with assortments of repacked items, staging areas and loading zones, route scheduling and delivery, bonded-cost pricing, production capabilities, kitting, bills of material, importing and receiving, up to 10 additional costing factors for landed cost calculations, container-level costing, multiple consolidators per container when calculating landed cost, and duty calculations.

Carillon’s production-order materials state that production orders are integrated with inventory, account for standard and actual yields and waste factors, and update production and inventory information.

Carillon’s bill-of-material, or recipe, materials state that Carillon supports unlimited-level bills of material and operations/tasks performed in workcenters.

Carillon can also trace an ingredient lot, such as a recalled spice used several levels deep in a recipe, through production into finished goods and identify the customers who received those finished goods.

The documented difference is that Carillon publishes the beverage-alcohol-specific item attributes, repacking, bonded-cost, importing, landed-cost, production, kitting, recall-traceability, and finished-goods-costing functionality as part of its own beverage and manufacturing materials.

Sources: Acumatica Distribution Edition Datasheet ; Acumatica Manufacturing Edition Datasheet ; Acumatica Inventory Management Datasheet ; Acumatica Help — Processing Landed Cost Documents ; Acumatica Help — Configuration of Landed Cost Codes .

Carillon multicompany accounting is built around transactions that involve separate legal entities. In Carillon, a single customer invoice, customer payment, vendor invoice, vendor payment, or journal entry can involve more than one company.

On a customer invoice, different line items can be assigned to different companies. When the invoice is saved, Carillon automatically creates the intercompany receivables and payables needed to keep each company’s books correct.

Carillon also handles multicompany customer payments. Company 1, Company 2, and Company 3 may each invoice the same customer. The customer may send one check payable to Company 1. Company 1 deposits the check. In Carillon, that one receipt can be applied to the invoices from all three companies. The invoices for Companies 2 and 3 are shown as paid, Company 1 records the intercompany payables to Companies 2 and 3, and Companies 2 and 3 record the intercompany receivables from Company 1.

In accounts payable, different line items on the same vendor invoice can be charged to different companies during voucher entry. When the voucher is saved, Carillon records the voucher and automatically creates the intercompany receivables and payables between the companies.

Carillon also allows one company to pay vendor invoices owed by multiple companies. If Vendor 1 sends invoices to Company 1, Company 2, and Company 3, Company 1 can write one check to pay those invoices. In Carillon, the invoices are recorded as paid, and the intercompany receivables and payables are created between the companies.

Carillon also allows a single journal entry to include debits and credits for multiple companies. If only two companies are involved, Carillon can automatically create the related intercompany receivable and payable entries. If more than two companies are involved, the system cannot know which company should be due to or due from which other company without direction from the user. In that situation, Carillon allows the complete multicompany journal entry to be entered as one journal entry, with the intercompany debits and credits entered explicitly.

The Acumatica public materials reviewed document intercompany funds transfers, intercompany sales, and account-mapping rules that can generate balancing entries in certain circumstances. Acumatica’s funds-transfer documentation describes transferring funds between companies and states that when an intercompany funds-transfer transaction is posted, the system adds balancing entries to the batch according to account-mapping rules.

Acumatica also documents intercompany sales. In that workflow, the selling company creates an accounts receivable document where the purchasing company is the customer, and the corresponding accounts payable document identifies the selling company as the vendor. Acumatica’s setup activity states that the system can create the AP bill automatically based on the AR invoice when the intercompany sales functionality is configured.

Those documented Acumatica functions are not the same as the Carillon multicompany transaction workflows described above. The Acumatica public materials reviewed do not document one customer invoice with line items assigned to different legal entities, one customer payment deposited by one company and applied to invoices from multiple legal entities, one vendor invoice with line items charged to different legal entities, one company paying vendor invoices owed by multiple legal entities, or one journal entry containing lines for multiple legal entities as the same kind of direct transaction workflow Carillon supports.

The documented difference is that Carillon supports multicompany accounting inside the operating transactions where the activity occurs. Acumatica’s public materials reviewed document intercompany funds transfers and intercompany sales, but they do not document the same practical multicompany customer-invoice, customer-payment, vendor-invoice, vendor-payment, and journal-entry workflows across separate legal entities.

Sources: Acumatica Help — Intercompany Funds Transfers ; Acumatica Help — Intercompany Sales ; Acumatica Help — Intercompany Sales Setup ; Acumatica Help — Account Mapping for Balancing Entries .