This section provides details on third-party entities that interact with organizations.
These entities include Customers, Suppliers, and Employees.

Resources

Customer

Represents individuals or businesses that purchase goods or services from the organization.
It offers the option to add contacts and their details within third-party entities, as well as the ability to define default payment conditions.

img

Supplier

Represents sources for the goods and services that the organization sells or utilizes.
It offers the option to add contacts and their details within third-party entities, as well as the ability to define default payment conditions.

img

Employee

Represents the workforce of the organization, contributing to various functional areas.
It offers the option to add contacts and their details within third-party entities.

img

Every Third-party must have a code, which, depending on the organization’s settings, can be manually entered or automatically generated.
In the DE (German) legislation, automatic numbering is mandatory.

Shared Features Among Third Parties

While Customers, Suppliers, and Employees are distinct objects within the system, they share some common elements in their definition and usage :

  • Addresses & Contacts: All three entities—Customers, Suppliers, and Employees—utilize the same resource structure for Addresses and Contacts. This standardized approach ensures consistency in how location and communication details are managed across these third-party types.

  • Commonalities Between Customers and Suppliers: Customers and Suppliers share many similarities in their configuration and usage within the system. They both utilize many of the same configuration parameters and are often managed through similar processes and workflows.

This design allows for greater ease of use and streamlines various organizational tasks that involve these third parties.

Configuration Parameters

These are the parameters commonly used to configure the behavior of third parties within the organization.

Business areas

Defines the specific categories of customers or suppliers within an organization, such as Trading or Services.
Examples : Trading, Services (can also be used to indicate the legal status) It can also be used to indicate the legal status.
Known as BusinessArea in the API context and Category in the product interface.

These business areas are customizable for each organization and are relevant only in the context of third-party customers and suppliers.

img

Job areas

Refers to the specific departments or areas where a contact within an organization works. Examples include Administration, Warehouses, Purchases, Accounting, Direction, Finance, Research and Development, Logistics, and more.
Known as JobArea in the API context and Contact information / Area in the product interface.

These job areas are customizable for each organization and are relevant only in the context of contacts.

img

Payment methods

Represents the various Banks accounts known as PaymentMethod in the API context and Bank accounts and cash in the product interface.
Each element is associated with a Journal Type and a bank account.
The payment methods are notably used by the Open Items Settlement action.

img

Payment means

Represents the various means of payment used by payment terms within an organization, known as PaymentMean in the API context and Payment Method in the product interface.

Examples include Cash, Check, Bank Transfer, Direct Debit, and more.

These payment means are customizable and local to each organization, allowing for flexibility in defining the ways payments can be received or made.

img

PaymentTerms

Used to define different templates of list of payment terms for a customer or supplier

Example of a template :

  • Advance payment by check 30%
  • 30% by transfer at 30 days net
  • the balance of 40% by bank transfer at 60 days end of month

Within the PaymentTerm, the specific conditions of payment are detailed under paymentTerms/lines.

img