Setting Up Business Relations > Overview > Segregation of Duties
  
Segregation of Duties
Since important financial information, such as accounts and credit limits, is associated with customers, end users, and suppliers, these records are created and maintained within the Accounts Payable and Accounts Receivable modules. Employees are associated with entities and defined with other corporate setup data. This supports segregation of duties requirements mandated by many regulatory bodies.
However, customers and suppliers are also used in operational functions such as manufacturing, sales, and purchasing. End users and employees are used in the Service/Support Management (SSM) module. End users are referenced on calls, contracts, and service returns; employees are set up as service engineers who respond to calls.
Typically, financial staff do not have the expertise to define the data related to these operational functions. For this reason, additional operational data can be set up in supplementary maintenance functions:
Customer Data Maintenance (2.1.1)
Supplier Data Maintenance (2.3.1)
End User Data Maintenance (11.9.1)
Engineer Maintenance (11.13.1)
To facilitate the collaboration required when defining new customers, suppliers, end users, and employees, e-mail notifications are sent to specific user roles when new records are created:
CustomerNotify for customers
SupplierNotify for suppliers
EndUserNotify for end users
EmployeeNotify for employees
The members of these roles are then responsible for ensuring that the supplemental information required for operations is added. For details about setting up role membership, see QAD Security and Controls User Guide.
Important: New customer and supplier records cannot be referenced in operational functions until this additional data has been specified. Adding operational data marks the record as complete.
This is not true of end-user and engineer records; they do not need to be completed before being referenced in SSM functions.
The following table lists all of the records in the system that reference business relations for address data.

Records Referencing Business Relations
 
Record
Created
Related Data
Type
E-Mail
Bank
GL Account Create (25.3.13.1)
N/A
Headoffice
No
Carrier
Carrier Maintenance (2.17.1)
N/A
Headoffice
No
Company Address
Company Address Maintenance (2.12)
N/A
Headoffice
No
Customer
Customer Create (27.20.1.1)
Customer Data Maintenance (2.1.1)
Headoffice
Yes
Dock
Dock Maintenance (7.3.1)
N/A
Dock
No
Employee
Employee Create (36.1.7.1)
Engineer Maintenance (11.13.1)
Headoffice
Yes
End User
End User Create (27.20.3.1)
End User Data Maintenance (11.9.1)
Enduser
Yes
Entity
Entity Create (36.1.1.2.1)
N/A
Headoffice
No
Fixed Asset Location
Fixed Asset Location Maintenance (32.1.13)
N/A
Headoffice
No
Salesperson
Salesperson Maintenance (2.5.1)
N/A
Headoffice
No
Ship-To
Customer Ship-To Create (27.20.2.1)
N/A
Ship-To
No
Supplier
Supplier Create (28.20.1.1)
Supplier Data Maintenance (2.3.1)
Headoffice
Yes
Customers and suppliers are associated with shared sets, which in turn can be associated with one or more domains. This lets you maintain customers and suppliers for multiple domains in a single location.