SyteLine Multi-Company Setup and Administration
Multi-company SyteLine environments support organizations operating multiple legal entities, divisions, or sites within a single database or across linked databases. Configuration choices made during multi-company setup have far-reaching implications for intercompany transactions, financial consolidation, master data governance, and user administration. Getting this architecture right at the outset saves enormous rework compared to restructuring an established system.
Multi-Company Architecture Options
SyteLine supports multi-company through two primary architectures: multiple companies within a single database, or separate databases linked through intercompany configurations. Single-database multi-company shares master data naturally and simplifies administration but limits company-specific customization. Separate databases provide full isolation but require explicit data synchronization and more complex intercompany transaction processing.
- Use single-database multi-company when entities share most master data and business processes
- Choose separate databases when entities have fundamentally different chart of accounts or customizations
- Document the intercompany transaction flow for sales, purchases, and inventory transfers explicitly
- Plan the consolidation reporting approach before choosing architecture—it constrains your options
Intercompany Transaction Configuration
Intercompany transactions in SyteLine automate the creation of corresponding records in the trading partner company. A sales order in Company A automatically generates a purchase order in Company B, with intercompany pricing and transfer pricing rules applied. Configuration requires matching item cross-references, defining intercompany customer and vendor relationships, and setting up automatic pricing rules that comply with transfer pricing regulations.
- Configure intercompany customer/vendor pairs with matching item cross-references for automated order flow
- Implement transfer pricing rules that comply with your jurisdiction's arm's-length requirements
- Set up automatic intercompany invoice generation to eliminate manual reconciliation between entities
- Test intercompany transaction chains end-to-end including financial elimination entries for consolidation
Master Data Governance Across Companies
Master data management is the most challenging aspect of multi-company SyteLine. Shared master data (items, customers, vendors) must be synchronized when using separate databases, with clear ownership rules defining which company is the master for each data domain. Even in single-database environments, company-specific overrides for pricing, costing, and planning parameters need governance to prevent conflicts.
- Designate a master company for each data domain: items, customers, vendors, chart of accounts
- Implement data synchronization jobs for shared master data in multi-database environments
- Define approval workflows for master data changes that affect multiple companies
- Audit master data consistency quarterly to identify and resolve cross-company discrepancies
Setting up multi-company SyteLine? Our architects design scalable multi-entity configurations.
Related Resources
SyteLine Security Roles Best Practices
Design SyteLine security roles for least-privilege access. Role architecture, form permissions, IDO security, and audit compliance for CloudSuite Industrial.
Infor SyteLineSyteLine Financial Close Process Automation
Automate SyteLine financial close processes. Month-end procedures, reconciliation, posting automation, and close cycle reduction for CloudSuite Industrial.
Infor LNInfor LN Multi-Site Planning & Optimization
Optimize Infor LN multi-site planning with AI. Cross-plant scheduling, intercompany transfer optimization, and global demand balancing.