- Company sizes or stages where this product is over-provisioned or inappropriate
- Early-stage or small organisations that primarily require simple general ledger, payables, and receivables functionality may find SunSystems more complex and costly than necessary.
- Industries or use cases where competitors are preferable
- Organisations seeking an all-in-one suite with extensive out-of-the-box CRM, commerce, or industry apps may prefer NetSuite or a full ERP suite.
- Organisations standardised on Microsoft technologies seeking rapid adoption and tight Office integration commonly select Business Central.
- Technical requirements that the product may not meet efficiently
- Projects that require low-code extensibility and minimal partner involvement may find customisation and reporting tasks require specialist skills.
- Budget constraints that make alternatives more appropriate
- Organisations with constrained budgets that require straightforward accounting features may prefer lower-cost products such as Business Central or QuickBooks.
- Specific workflows or integrations where the product has shown limitations
- Organisations requiring extensive plug-and-play integrations may find competing ecosystems have broader pre-built connector sets; SunSystems integration capability is available but often requires configuration.
- Red flags in the procurement process
- Quote-based pricing and partner-dependent delivery increase procurement risk; confirm partner capability during vendor selection.
- Current limitations acknowledged by the vendor
- Infor documentation notes concurrency and locking behaviours: several SunSystems modules may cause application locking when run concurrently, and these modules should not be executed at the same time. Examples include Ledger Revaluation, Payment Run, Calculate Depreciation, Transaction Matching, and others. This limitation affects parallelisation of batch processes during close activities.
- Features on the roadmap (not yet available)
- Roadmap details were not publicly disclosed in the documentation pages captured in this research set.
- Scale limitations (at what volume/size does it degrade?)
- No explicit volume thresholds were found in the sourced materials. Some community commentary references large or resource-intensive SunSystems databases, but no vendor-published benchmarks were located in this run.
- Security or compliance gaps
- Product-scoped SOC/ISO certification scope is not publicly documented; purchasers should request audit reports and confirm scope via Infor Concierge.
- Audit functionality requires configuration to be operationally useful in some deployments, according to reviewer feedback.
- Technical debt or architectural constraints cited by reviewers
- The user interface and multi-step navigation suggest accumulated UX design limitations relative to newer cloud-native finance tools.
- Reports of patch regressions in some deployments suggest maintenance and upgrade risk that should be managed through change-control processes.
- API limitations or integration constraints
- API Gateway usage requires membership in the API Gateway security group.
- Report models must be synchronised after maintenance operations to avoid report or API errors.
- BOD-based integrations require careful configuration; some patterns are discouraged for certain message types.