Customers

This is the category associated with the customer.
You can

• Add a BP classification.
• Define default values.
• Assign an automatic numbering to BPs according to a counter associated with the customer category or supplier category.

Use this field to activate or deactivate a customer.
By default new customers are active.

 You can make a customer inactive even though transactions are still in progress. Making a customer inactive does not prevent transactions from completing. For example, you can generate a delivery for a customer made inactive after entering the order. When a customer is inactive, you cannot create a document that is part of a complete transaction.

Enter a unique code used to identify the customer.

For an existing customer, you can enter or select it from the Customer table.
 This customer list is not exhaustive, any customer not present in this list can still order the product.

Enter the customer's corporate or company name. For existing customers, you cannot edit the name here.

Title used in some screens or reports when there is not enough space to view the long title.

By default the short title, the long title, or the column header of a data are saved in the connection language of the user.

You can add your translation in another language by using the Translation function.

• Select Translation from the Actions icon in the corresponding field.
• In the Translation window, add a new language code with the translation in this language.

A user who logs on with this language sees the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions are available in the folder language.

The connection language needs to be defined as a default language for the folder.

Business partner's acronym.

Business partner company name.

When selected, it means the customer is a physical person. If not, it is a corporation.

If the BP is corporation, you must enter the VAT identification number and the Site tax ID number if required for their country.

Select this option to prevent mail from being sent to this customer.

This code is used to identify the Country and determines the following formats and if they are required or not for the country:

• The phone number
• The number format that identifies a company or an activity, such as tax ID number, NAF in France
• The postal code
• The VAT ID number
• The Bank ID code

Enter or select the default language.

This code is used to identify the currency of a site, a BP, etc. It is controlled in the currency table.
The currency suggested by default is budget currency.

Unique identification number for the company.

It is mandatory to enter this number if both the following conditions are satisfied:

• It is required by the country.
• Customer is a corporation.

The entry format depends on the setup carried out at the level of the Country record.

In France, this number, assigned by the INSEE on registering a company with the national registrar of companies, contains 9 numbers, is unique and cannot be changed. This is used by all public organizations and the administrations in contact with businesses.
See BP ID validation for details on this functionality.

This fields displays the SIC code (subject to activity code KFA), according to the French company's activity codification.

This is VAT identification number. The EU tax number depends on the BP country and the associated validation process.
You can associate a VAT identification number according to the delivery address in function (a BP can be identified in different countries according to the VAT).

Note: This field is only available if a web service is identified in the EVCSERVICE – Webservice for EU VAT ID parameter (CPT chapter, VAT group) and the sender's EU VAT ID is set in the EVCCOMPANY—EU VAT ID source company parameter (CPT chapter, VAT group)

Select the Validation action to interactively validate your EU VAT ID or GB VAT number.

A message box displays with the validation results. The exact content varies by check result and web service used.

• If the validation was successful, you receive a confirmation message and the Verified checkbox is selected.
• For an unsuccessful validation, you receive a message that displays the reason for the failed validation.
• If no full validation could be performed (for example, if only the VAT ID was validated and not the address), you have the option to accept the results as valid or not. If you select Yes, the Verified checkbox is selected.

Note: Successful validation results are stored in a table.

If a previously-validated VAT ID is modified, the Verified checkbox is cleared.

Validation levels:

A Qualified validation verifies the EU VAT ID and company name and address. All data must be valid.

An Unqualified or simple validation only verifies the EU VAT ID. Note that the EU validation web service performs only unqualified validations.

Address management:

Results are recorded with the original address code.

For the main EU VAT ID, the standard company address is used.

You can manually revalidate IDs using the EU VAT ID revalidation function (EVCBAT).

If a previously-validated VAT ID is modified, the Verified checkbox is cleared.

A message box displays with the validation results. The exact content varies by check result and web service used.

• If the validation was successful, you receive a confirmation message and the Verified checkbox is selected.
• For an unsuccessful validation, you receive a message that displays the reason for the failed validation.
• If no full validation could be performed (for example, if only the VAT ID was validated and not the address), you have the option to accept the results as valid or not. If you select Yes, the Verified checkbox is selected.

Note: This field is only available if a web service is identified in the EVCSERVICE – Webservice for EU VAT ID parameter (CPT chapter, VAT group) and the sender's EU VAT ID is set in the EVCCOMPANY—EU VAT ID source company parameter (CPT chapter, VAT group)

Select this checkbox to indicate if this is an intersite BP:

• The intersite customer or supplier BPs are used for multisite exchanges.
• A customer BP is a purchase site or a financial site.
• A supplier BP is a sales site or a financial site.

The site code for a BP within the frame of multisite exchanges.

The following data needs to be entered:

• The requesting site (purchase or financial sites) at the level of the customer BP.
• The supplying site (sales or financial sites) at the level of the supplier BP.
• For the customer, a warehouse site, belonging to the same company, will identify each ship-to address.

This field is automatically selected when the BP is a customer.

This field is automatically selected when the BP is a sales representative.

This field is automatically selected when the BP is a prospect.

This field can be accessed if the MAXPD - Maximum period (companies) activity code is activated.

Select this checkbox to specify that the BP is a public sector organization. In that case, the maximum number of days for the last payment due date of an invoice is defined by the DMAXPAYP - Maximum period (Public sector) parameter (TC chapter, RSK group).

If this BP is a private sector company, the period for the last payment due date of an invoice defined by the DMAXPAY - Maximum period (companies) parameter (TC chapter, RSK group). However, you can have a special agreement with this BP and grant them a longer period. Enter this period In the BP function in the Contractual period field (PAYDAY), on the BP/Company tab.

This field is automatically selected when the BP is a supplier.

This field is automatically ticked when it concerns a miscellaneous BP.
A miscellaneous BP is only used in accounting.

This option is used to include a BP among the list of after-sales service providers.

An after-sales service provider is an organization that may be called on to conduct

an intervention to be carried out for a service request (Repair, advice, audit, quote etc...)

For each service provider, it is possible to register their skills, their geographic intervention area,

their price list conditions for invoicing.

This field is automatically selected when the BP is a carrier.

The contractor represents the actual customer for whom a service request is made.
When a service request does not include any contractor, the service is supplied on behalf of the direct customer of the current organization.
By contrast, when a service request includes a contractor, the service is provided to the customer but is is made on behalf of the contractor. The customer receiving assistance is not the organization's customer but the contractor's.
Regarding invoicing, the data loaded by default is the contractor's (invoiced customer, pay-by BP, ...). Therefore, it is mandatory to create a customer record for the contractor.
This option makes it possible to discern the contractor population.
This option is also mandatory to be able to link customers to their contractor(s).

Address code of the business partner (BP).

This code is used to identify the various addresses associated with the current record.
Each address code is unique to a given record.
In general, you need to enter an address for each record, and one of them needs to be the default address.

You cannot modify or delete an address code when it is used for a Bank ID number or for a contact.
To modify or delete an address code, you need to remove it from the Bank ID number or contact.

Enter information linked to the address.

Enter or select the country code, managed in the Country table.

The country determines certain formats including:

• Phone number
• Company ID and activity code
• Postal code and the geographical subdivision
• Bank ID number
• The IBAN management

Title associated with the previous code.

This table lists the various address lines. The title and entry formats are defined in the country table.

Enter the postal code for the city according the country-specific format, as defined in the Country table.

If defined, when the postal code is changed or entered, the city name automatically displays. The reverse is true is you enter the city name.

Specific cases:

• For ANDORRA, enter 99130.
• For MONACO, enter 99138.
• For the other countries, enter the INSEE country code or 99999 if not known.

The control of this information is required if the POSCOD - Nonexistent postal code alert parameter (SUP chapter, INT group) is Yes.

Enter the city. If defined in the Country function, the postal code automatically displays.

If the CTY - Nonexistent city alert parameter (chapter SUP, group INT) is set to Yes, a control warns you that the postal code is missing.

Notes:

• The format is defined in the country record setup.
• Depending on this setup, the city name can automatically be converted into uppercase.
• To make selections easier without taking into account the format (accented characters, uppercase or lowercase), the selection window available on this field proposes a column dedicated to the search, where the names of the cities are displayed in uppercase. The control that is carried out is case-insensitive because it is carried out with respect to the city name stored in uppercase.

Select to open a mapping site and locate the entered address.

This field contains the geographical subdivision corresponding to definition of the postal address. It could be a department, province, state, and so on.

The description and format are defined in the Country function.

This field loads automatically after you enter the postal code and city based on the Postal codes settings.
If the field is controlled, the control is carried out with respect to the Geographical subdivision table.

Enter a website for the customer.

You can enter a stock variable identifier, which can be used for specific processing.
For example, when generating international transfer files in XML format, the content of this field identifies the credited BP or when the SIRET number is missing for a French customer. See Bank files for more information.

When selected, this checkbox indicates that the address is the default address. Only one of the addresses in the selected record can be selected. This always corresponds to one of the BP's addresses.
The customer's default address can be different from the BP's default address.

Select to send an address to the Sage Sales Tax (SST) address validation service. If this address is found, it is updated according to the US Postal Service format.
This field is only available when the LTA activity code is activated.

 The SST address validation service is defined in the Sage Sales Tax settings.

If selected, it means the address was validated with SST address validation service. If not selected, the address is unknown.

The format depends on the country.
The level of control applied to the entered number format depends on the CTLTEL - Phone number control parameter (SUP chapter, INT group).

Enter an email address of the contact.

Select a code to identify the ABC category of a business partner.
The ABC category is designed to classify business partners according to their importance in the turnover, for example.
Because a new business partner has no statistical data available, the default value is D.

Minimum tax excl. amount, expressed in folder currency, below which customer orders cannot be saved.

This is the folder currency.

This information, initialized by the sold-to customer, is used to authorize or not the closing of a line or the order. This information is modifiable on order entry if the transaction allows this.

This indicator is designed to define whether a loan of goods for this customer is authorized.
The product concerned also has to be authorized for the loans and has to be managed by location.

This information, initialized by the sold-to customer, is used to prohibit the grouping of several orders in the same shipment. This information is modifiable on order entry if the transaction allows this.

This information, initialized by the sold-to customer, is used to specify how the order is delivered. There are three possible values:

• Authorized means that the order can be partly delivered.
• Complete line means that the order can be partly delivered if the complete line is delivered.
• Complete order means that the order must be delivered in full (a single delivery).

This also means that a partial allocation cannot be performed on an order line or order if the stock is insufficient to cover the full line or order: the Partial Allocations option must be displayed on the order or in the mass allocation options. When entering the quantity to be allocated to the line or when performing a Manual allocation on the line, a warning message displays if the delivery is partial.

Note: When you select Complete line or Complete order, you can ignore this warning message and force the partial delivery.

Select this checkbox if the prices of products (sales invoices) and amounts (customer BP invoices) include or exclude taxes. This affects the price list search. Only those price lists defined in a mode or those accepting a price conversion are included.

The document price/amount type excludes or includes tax depending on the type defined at customer level.

If the supplier is connected with a customer category, this information is initialized by the amount type defined at the level of the field Price type/Amount type of the category.

Determine if freight is invoiced to the customer or not.

Or you can select which thresholds are defined in the carrier record.

For more details, see the FRENUM - Carrier invoice element (VEN chapter, INV group) parameter settings.

This information is initialized by the sold-to customer and is used to define the customer's invoicing mode. This invoicing mode is used subsequently to invoice the delivery notes or the direct invoicing orders by regrouping or splitting them. This information is used in the automatic invoicing process and in the manual invoicing function, where a control is performed with respect to this information.

The available invoicing modes and their impact on the delivery invoice are as follows:  

• One/slip: A separate invoice is generated for each delivery created.
• One/closed order: One invoice is generated that includes all the deliveries for a completed order, where all the invoices for this order are validated. All the deliveries need to belong to the automatic invoicing selection.
• One/order: One invoice is generated for all the deliveries for an order that are validated when the invoicing process is run. One invoice is generated grouping all these deliveries.
• One/ship-to: One invoice is generated for all the deliveries concerning the same ship-to customer when the automatic invoicing process is run. There also is a control performed upon manual invoicing of the deliveries.
• One/period: One invoice for all the deliveries based on the invoicing frequency defined by the customer. For example, if the frequency is weekly, all the deliveries during week 32 (according to the shipment date or delivery date based on the INVREFDAT - Origin date for invoicing parameter setting). There is a specific feature linked to the invoicing frequency when it is Per request. Deliveries with this kind of frequency will be grouped together. A control is also carried out in manual delivery invoicing mode to only enable the grouping together of deliveries with an invoicing mode by period and a manual invoicing mode.
• Manual: Invoices are not generated automatically. Invoicing will be manual on invoice entry.

How your selection affects delivery generation: orders with One/order or One/closed order are never grouped on the same delivery.

In addition to these invoicing modes, information that varies from one delivery to the next prohibits the grouping two deliveries. See automatic delivery invoicing.

How your selection affects direct invoicing orders:

• One/slip: This invoicing mode requires the existence of a separate invoice for each direct invoicing delivery. On the other hand, an order can be only partly invoiced by the automatic invoicing function from the moment that the order delivery mode is not Complete order. If the order delivery mode is Complete order, all the order lines need to be invoiced and the stock-managed order lines need to be allocated, otherwise the invoice is not generated. On manual invoicing of an order of this type, there are no constraints with respect to the delivery mode, and it will be possible to draw up a partial invoice even if the delivery mode is Complete order.
• One/closed order: This invoicing mode requires the existence of a separate invoice for each direct invoicing delivery. An order will have however to be fully handled in order to be invoiced using the automatic invoicing function. There will thus be only one invoice for this order. In manual invoicing it isn't necessary to follow this rule; it is possible to partially invoice an order of this type.
• One/order: For the orders with direct invoicing, this invoicing mode corresponds to the invoicing mode previously described: 1 invoice / DN. 1 invoice / DN:
• One/ship-to: This invoicing mode is used to create an invoice for all the orders with direct invoicing concerning the same ship-to customer on a single invoice when the invoicing process is run. If order lines concern various ship-to customers within a single order there will be as many invoices as there are delivery addresses on the lines. There also is a control performed upon manual invoicing of the orders.
• One/period: This invoicing mode is used to create an invoice for all the orders based on the invoicing frequency defined by the customer. For example, if the frequency is weekly, all the orders during week 32, relating to the requested delivery date in the order header, are grouped on a single invoice. There is a specific feature linked to the invoicing frequency when the chosen value is Per request. The orders with this kind of frequency are grouped together.
• Manual: Invoices are not generated automatically. Invoicing will be manual on invoice entry.

Select when invoices are generated:

• Per request

• Daily

• 10-day period

• 2-week period

• Monthly

Use this field to specify the Invoicing term. This information is optional.
This filed initializes the entered invoicing term on the customer order, when the order is linked to a Service or Generic product with a Sold and not Deliverable flow type.

Select which date to use when calculating open items.

Commission category used to select the commission rate of the sales representative record for the commissioning calculation.

Code of the sales representative associated with the customer and controlled in the sales representative table. The sales representative of the sold-to customer has priority over the sales representative of the ship-to customer.

An activity code is used to define the number (maximum of 2) of sales representatives submitted as the default value for an order.

This is the code for the invoicing element.

This is the short title for the invoicing element.

This is information relative to the invoicing footer. The invoicing elements correspond to the category of customer used or to the elements set up to be displayed on the customer record if no category has been associated to the customer.
When the invoicing elements come from a setup with a default value, this value is used and converted into the customer's currency using its rate type and the current date of the system.

This column specifies if this is a percentage, an ex-tax amount, or a tax-incl. amount.

This is the customer currency.

This checkbox is selected if an order text exists for this customer. This text is used on each order so it can be printed on the order acknowledgment.

This checkbox is selected if an invoice text exists for this customer. This text is used on each modified invoice.

Select this checkbox if receipt acknowledgements need to be printed for orders.

Enter a print template listing the reports to use and the number of copies with the documents used in commercial management. You can specify the reports and to assign them to specific BPs.

To enable an electronic invoicing for Portuguese legislation, you mustneed to select a PDF print template code or invoice report compatible with Portuguese legislation. The archive destination for the template in PDF format is determined by the EFATPRT – Default destination for EFAT parameter (LOC chapter, POR group) setting.

Select this checkbox to send an electronic invoice to the customers who agreed to receive electronic invoices.

To activate the electronic invoicing feature, you need to select an archive Print template code.

This field only applies to Portuguese legislation and is available when the EFAT activity code is active. The electronic invoice is in compliance with the legal requirements of the Portuguese tax authorities.

Please refer to the EFAT communication documentation for further information.

You can only enter a contact with a valid email address linked to the customer record.

This field is only available if the Electronic invoice checkbox is selected.

This field is only available when the Electronic invoice checkbox is selected.

You can select Normal or Miscellaneous. Normal is the default value.
When you select Miscellaneous, an address entry window opens for all the commercial documents. These customers type are not distinguished in accounting.

The number under which the company is known as a supplier for the customer.
This information is indicative only.

This is the rate type used to determine the default rate to determine the posting rate of sales documents. You can modify the standard values.

This field is used to qualify the economic activity of the customer with a level of segmentation adapted to the segmentation needs of the commercial team.

This field is used to record the commercial channel at the origin of the identification and qualification of a business partner.

This field is used to specify the date from which the BP has been a customer of the company.

• When creating or copying a customer, this date is automatically loaded with the current date.
• In the case of the conversion of a prospect into a customer from the orders, this date is automatically loaded with the order date.

This field displays the total number of tokens credited by the customer as a result of their different orders.
This total does not take into account the points credited as a result of a manual addition of points specified in the next field.
Reminder: The tokens are the bonuses that each customer can credit upon different successive orders.

This field is used to perform a manual addition of points (tokens) for the customer, independently of the receipt of a sales order.
It is essentially used when a customer has passed an order that gives them nearly all the necessary points to obtain the gift. In this case, the sales team can decide to offer several missing points (tokens) by entering them directly in the customer record.
The latter carrying the manual points is always saved for information purposes.

This field displays the total number of tokens credited by the customer as a result of their different orders.
This total also includes the tokens credited from the manual addition of points.
When this total exceeds the number of necessary tokens indicated further on or in the service contract template, a contract is offered to the customer.

You can enter a point debit rule directly for a customer.
The debit indicated in the customer record is applied only for the contractual debit. All additional debits are specified at the level of the point debit rule.
From the Actions icon, select Point debit to view or define a Point debit rule.
The entry of a value in this field leads to the creation of a point debit rule where only the customer component is entered.

This option is used to block the tree of rules for debiting points during the analysis of a service request coverage.
In other words, this is used to block all consumption of points for service requests pertaining to this customer.

This field is used to indicate the service contract template that will be automatically offered to the customer each time enough tokens have been accumulated.

This field displays the minimum number of tokens necessary for a customer to be offered a service contract.

This information has priority over its equivalent in the service contract template.

Select the type of control that you want to apply on the customer credit amount:

• Check: The control is carried out in real time when creating the order, during the allocation and during the delivery, based on the authorized credit level. The customer can receive deliveries if their credit level is lower than their authorized credit level. This control can be performed:
• By company or by folder, based on the value of the OSTCTL - Credit control level parameter (TC chapter, OST group).
• With an archived or updated rate, based on the value of the OSTCHGTYP - Rate origin WIP ctrl. parameter (TC chapter, OST group).
  If the control is performed based on an updated rate, the rate type to be used is the one set by OSTTYPCUR - Rate type updated rate ctrl parameter (TC chapter, OST group).
  When the control on credit is done at the folder level, the control is always applied based on the updated rate, regardless of the OSTCHGTYP- Rate origin WIP ctrl. parameter value.

The WIP is controlled with respect to the risk BP of the customer. If the risk BP is shared by several customers, it means that the WIP of each customer will be controlled the same way with respect to the risk BP by cumulating the total of the different customers movements.
When the customer is associated to a different risk BP, the amount of the authorized WIP cannot be accessed. It can be viewed on the risk BP record. The displayed WIP is the risk BP.

• No check: The customer can always receive deliveries.
• Hold: The customer can no longer receive deliveries.

Maximum credit amount authorized for this customer. This amount is expressed in the currency of:

• The folder when the control is at folder level
• The site of the user when the credit control applies at the company level

This is the total credit amount, which is calculated automatically.
This amount includes:

• Orders in progress (excluding loan orders and delivery requests) if the OSTORD - On order in order total parameter (VEN chapter, OST group) is set to Yes.
• Deliveries in progress (excluding non billable deliveries).
• The delivered but not invoiced elements.
• Loan orders and delivered loan orders in progress when the parameter OSTLND - Loan in order total (VEN chapter, OST group) is set to Yes.
• The invoiced but not posted elements.
• The accounting balance.
• The notes payable/receivable, based on the OSTDRAFT - Customer credit note P/R amt. parameter (TC chapter, OST group).

On the relevant documents, the credit amount:

• Considers the total of calculated taxes on all lines of these documents,

Does not include:

Invoicing elements

Global VAT adjustment.

Amount of the insurance secured to cover the customer risk in case of default. This amount is expressed in the folder currency.

End date of the insurance secured to cover of the customer risk in case of default.

The insurance company is defined as a miscellaneous BP. This information field is designed to associate essential descriptive details to the insurance companies (titles, addresses, contacts, etc.).

Select this icon to:

• Enter information on the customer as a note. This information is available for inquiry in the functions that have been selected at the Note category level.
• Define a validity period for the note.
• Specify it the note needs to be displayed automatically.
• Create multiple notes for the same customer, and indicate if they need to be displayed as a priority.

Notes are limited to a screen inquiry and cannot be printed.

For more information, see the documentation on Notes.

You can enter a code to link a statistical group to the customer. This code is controlled in the table of statistical groups. It can be used in statistics, price list settings, or as a selection criteria in specific automatic processes.

It is the code for the bill-to customer, which is initialized by default with the customer code entered in the header.
This customer can be another customer chosen from the customer table.

It is possible to search a customer or several customer grouped under the same criteria by selecting 'Quick customer search'. A list of matching items is generated on tabulating to the next field.
For a more advanced search, all fields present in the block can be entered. The list of matches is narrowed down with each tabulation.

This field is designed to indicate an invoicing address code for the selected invoiced customer. It is the default address of the customer.
When entering sales document, this address code will be proposed. If needed, it is modifiable.

This field is used to enter the pay-by customer code, initialized by default to the customer code entered in the header. The invoice payment schedule will be allocated to this BP.
This customer can be another customer chosen from the customer table.

This field is designed to indicate a payment address code for the selected pay-by BP. It is the default address of the customer.
When entering sales document, this address code will be proposed. If needed, it is modifiable.

Code of the factor proposed as a default value on the invoices for this customer.
The presence a Factor code in an invoice indicates that this invoice is transferred to a factoring organization and that the payment must be made in favour of the Factor.

The group customer code is initialized by default to the customer code entered in the header.

Code of the customer on which the credit control is performed.
This customer is initialized with the bill-to customer, the pay-by customer or the group customer depending on the value taken by the common data parameter INIBPRRSK - Risk BP initialization. It can be modified: It can be the value of the customer itself or any other customer selected in the customer table.

This field is designed to specify the accounting code of the BP.
The accounting code is a default value used when creating accounting documents.
It refers to a table that lists a certain amount of elements (collective accounts, accounts or parts of accounts) that can be used for the determination of the documents that will be posted.

The account structure is not compulsory data.
If a structure is loaded, it is submitted to be applied upon the creation of a customer invoice (once the invoice tax excl. amount has been entered).

Enter the code linked to the current BP by default, and which is used to determine:

• The payment conditions
• The payment method
• The open item type
• The payment schedule, such as one or several open items: immediate credit, 30 days, end of the month, and so on

When managing this table, it is possible to simulate the calculation rules that will be applied in entry mode.

The payment days in the payment terms are replaced by the payment days introduced in the customer record.
The value entered must be a date in the month (between 1 and 30), or 99 which corresponds to the last day of the month.
The use of this date is used to automatically postpone the due date calculated up to the nearest day of the month.
There can be up to six dates for each customer.

In this field a predefined unavailable period can be indicated. In this case, the calculated due dates for this customer cannot be in this unavailable period. They are then postponed to the first available date.

Enter the code linked by default to the current BP, which is used to identify the early discount and late charge rates (up to 12). These rates will be applied to a payment depending on a number of early or late days compared to the due date.

• The automatic payment proposal processing automatically assigns this bank account to all the payments of this BP.
• This bank code is used in the Bank field of the Data tab in the Cash forecasts function.

  This code is controlled in the table of Bank accounts.

Reminder group with which the customer is associated.

The reminder group is used to define a group of management rules that are applicable during the launch of the reminder letters.
The Type of reminder and the Reminder threshold is by default recovered from the reminder group during the creation of the record (but not re-initialized if allocated to a different group of characteristics).
However it is the values from the customer record that prevail over those of the group or the category for these two fields, if they are different.
A customer that is not attached to a reminder grouped is not considered.

Type of reminder process for the customer.

 The reminder type, and reminder threshold, taken into account by the reminder report are those of the customer record (and not those of the reminder group which are only used upon initialization).

This field is controlled by a local menu and can take the following values: 
No reminder: The customer is never reminded.

By invoice: The customer receives as many reminder letters as invoices that are late for payment.

Global: A single reminder level is addressed to the customer for all the late invoices.

Global by level: The open items are grouped by identical level and the customer receives a reminder letter by level. Each reminder level contains all the open items overdue for a given level.

Global by date: The open items are grouped by late open item ranges (for example, all open items that are overdue by 30 to 60 days).

The customer receives one reminder letter per late open item range, or more, depending on the reminder group.
Each reminder letter contains all the overdue open items for a given late range. The values for the late range can be modified via the parameters.
In this way, it is possible that for a given customer to pass from a reminder letter for level 1 to a level 3 reminder letter if the number of days variance justifies it.

Minimum amount below which a reminder letter is not issued for this customer.
This amount is expressed in the common currency defined in the CURSHRFLD - Common field currency parameter (TC group, CUR group) setting.
This minimum amount means the minimum amount of the due date or the global minimum amount of the reminder letter. One of these options can be selected when setting up the reminder groups.

This field displays the currency of the reminder threshold, based on the value of the CURSHRFLD - Common field currency parameter.

Flag used to determine the frequency of the open item statements for this customer.
The frequency of these statements can be every week, every 10 days, every fortnight, every month or upon request.

Select the Credit card icon to open the Payment gateway customer data window. Use this function to add and maintain multiple payment cards for a customer.

This button is available if the SEPP - Credit card integration activity code is activated.

A tax rule represents the tax territoriality principle, in other words, the calculation rules to be applied to determine the tax amount.
As a general rule, by crossing a tax rule linked to the BP with a Tax level, you can determine the tax code to be applied to the document line and so, to the entry line.
In this field, you enter the tax rule associated with the BP: this tax rule will be suggested by default in all the transactions used by this business partner.

This field is designed to enter the number assigned to the tax exemption.

Once checked, this box is used to specify that the provincial taxes must be applied to the selected customer.

If this box is checked, the customer is subject to VAT. This box is checked by default when the BP country is Belgium.

The dimension types that are preloaded in the grid match the default dimension types associated with the customer base data.

The setup determines if the analytical dimensions can be modified. They are initialized based on the setup of the default dimension.

In creation mode, if no order line has been entered and the project code is modified, the analytical dimensions are reset based on the setup of default dimensions.

In creation mode, as in modification mode, if an order line is entered and the project code is modified, the analytical dimensions are not reset.

This fields is designed to specify the provinces for which provincial taxes exist.
This grid is depends on the Argentine legislation.

This is the title of the province.

This field is used to define whether the tax applies upon entry in the region, upon exit, or always.

This field is designed to specify if the customer is a tax collector for this provincial tax.

This field can only be entered when the following conditions are met:

• The KPO - Portuguese activity code is active
• The customer country is Portugal

You use this field to indicate if the customer is subject to article 23 of the Portuguese law 71/2013 on VAT rules. If yes, all invoices sent to this customer will go through a specific process at the payment level, once the invoices have been settled. The payments must indeed be subject to a tax return, which means that the customer must be provided with a special payment notice listing all VAT amounts by tax level.

This field is mandatory when the customer is subject to article 23 of the Portuguese law 71/2013 on VAT rules.
You use it to enter the date as of which the law is enforced for the customer.

Use this field to codify the shipping address of the ship-to customer.
You can only use an address from the predefined addresses of the Address tab.
By default, the customer's default address is suggested as the shipping address.

It is the code for the delivery address unavailable in this context.

Description of the address (for internal usage). For instance: temporary address, principal warehouse address, and so on.

This checkbox is used to specify if the delivery address is active or not.
When an address is inactive, it cannot be used on a new sales document.

This code indicates the language of the delivery address, used in the reports linked to this delivery.
This code is controlled in the table of languages.

This checkbox is selected to indicate that this is the default customer.
The ship-to corresponding address is proposed for this customer in the quotes, orders, deliveries and invoices

It is the company name for the delivery address mentioned in both fields.

It is the company name for the delivery address mentioned in both fields.

Enter the tax rule associated with the ship-to customer. This tax rule is controlled in the table of tax rules.

When creating a sales document, the tax rule applying to the delivery address is suggested by default, if this address uses a specific tax rule.

Enter the Entity/use code to calculate the precise tax amount for the customer. This tax code is compatible with the Avalara system and makes it possible to determine the customer type for fiscal purposes.

This field is available for all countries. The Entity/Use code can be entered for any delivery address when a document is being processed for a country that is tax-exempt. When the Calculate all documents connection with SST is set to No and an Entity/use code is entered, the document is exempt from tax and not subject to processing costs.

Enter the codes of the sales representative associated to the delivery address and controlled in the sales representatives table.
The customer's sales representatives, when defined, have priority on the sales representatives of the delivery address.
An activity code is used to define the number (maximum of 2) of sales representatives submitted as the default value upon order.

Enter the codes of the sales representative associated to the delivery address and controlled in the sales representatives table.
The customer's sales representatives, when defined, have priority on the sales representatives of the delivery address.
An activity code is used to define the number (maximum of 2) of sales representatives submitted as the default value upon order.

This is the storage site code from which the customer is generally delivered. This site, which is controlled in the site table, must be identified as a warehouse.

This information can only be accessed if the order is of the inter-company or inter-site type. It is used to indicated which shipping site will be used by the sales company that the intersite/inter-company supplier identified. It will then serve to initialize the shipment site for each line of the purchase order. It is mandatory in this context.

The shipment site is initialized by order of priority, as follows:

• Usual shipment site defined in the delivery address identified by the receiving site previously calculated is used. It must belong to the supplier's company
• Site identified by the supplier if it is a warehouse site

If after this search, the site is still not identified, you must then manually enter it. A control is applied to check if the entered site belongs to the same company as the supplier site and if the site is a storing site. The Actions icon is used to view all the sites available for selection.

Automatically-generated purchase orders: If the shipment site is still not identified after the execution of the previous steps, the shipment site is initialized using the first warehouse site found, in alphabetical order, in the list of storage sites for the company identified by the supplier.

When generating the corresponding sales order, the shipping site of the sales order header is equal to the site defined here.

This is the storage site code where the customer is generally delivered.
This site is used when the customer is inter-site. It corresponds to the receipt site.
The receipt site can only be entered for an intersite customer. It is controlled in the sites table and must be identified as a warehouse (Warehouse flag for the site is set to 'Yes') belonging to the same company as the customer.

Name of the location where the products will be transferred to when validating a loan delivery (location change) to identify the loan products.
Within the framework of a loan, the goods remain the site's property. To materialize the goods transfer, the dedicated locations are used.
The location type must be Customer.
The loan quantity of a product is displayed in the totals of the table Product-sites.
This notion of location is only used for the loan deliveries.
This field is only available if a shipping site is entered on the delivery address. The location needs to be attached to this site.

In this field, enter a location by subcontract supplier address (where the supplier is defined as a customer). This location must be of the Sub-contractor type and will be used for sub-contractor deliveries.

This filed is only available if a shipping site is entered on the delivery address. The location necessarily belongs to this site.

Number of the round, controlled by a local menu.
This information is used when generating picking tickets or allocation lists to select the orders or deliveries linked with a carrier round.

In this field, specify the delivery priority (Normal, Urgent, Very urgent). The priority is used to classify orders during the delivery preparations.
It is initialized by the customer delivery address. It is used on the order lines by default where it can be modified if the delivery method for the order is not Complete. If you modify this information and order lines already exist, the system will suggest that you apply this modification to the order lines.
This information is used in the automatic allocation processing of orders to determine the priority of the orders.

The order lines applying to non-deliverable products are not impacted by this information.

Enter the code used to define the information related to the transport and delivery. This code is managed in the table of delivery methods.

Enter the delivery lead-time for this customer, expressed in a number of days. This lead-time is used to calculate the shipment date according to the delivery date requested by the customer.

This code identifies the carrier in charge of the carriage to determine the costs linked with the goods transportation at the customer.

This box, when selected, is used to specify that the delivery notes must be edited for this customer.

This box, when selected, is used to specify that the picking tickets must be edited for this customer.

This indicator is used to identify which days of the week are work days for the customer.
If a day is declared as a work day, the customer can receive a delivery on that day.
If the calculation of the delivery date results in a day that is not worked, this date is automatically moved to the first available work day.

Use this code to specify the unavailability periods of the business partner, such as vacation days or holidays. During the order process, the delivery date is automatically moved to the first available date.

This code is controlled in the table of unavailable periods.

The Incoterm® codes, set by the International Chamber of Commerce, standardize the terms the most used in the international commerce by defining the respective responsibilities of the seller and the buyer for the sales contract by a unique word similarly understood throughout the world.

The Incoterm® code, controlled in Incoterm® table is used in the INTRASTAT file (Exchange of goods declaration). It can also be used to define the price lists.

It is the city associated to some types of Incoterm®. For example: FOB Le Havre. A selection window is used to choose a city listed in the system. It is however possible to enter a city that is not listed.

The forwarding agent field is used to identify a BP appointed by the sender or the recipient to ensure transport continuity when the goods need to undergo several successive transports. The forwarding agent is controlled in the Carriers table.

The forwarding agent and their address are used in the Intrastat file to declare the flows of goods between the forwarding agent’s address and the sender’s address, or between the forwarding agent’s address and the recipient’s address.

For example, this situation applies to the shipment of goods abroad, since customs formalities are performed by a forwarding agent in another EU country. An Intrastat declaration needs to be submitted for the transfer of goods to this other EU country.

This is the address code of the forwarding agent. It is initialized with the default address of the BP corresponding to the forwarding agent. This address is used to determine whether submitting an Intrastat document is necessary for this flow.

This is the VAT identification number of the buyer.
If the country of the ship-to address is different from the usual customer's country and if this customer is identified with the VAT of the ship-to country, then it is necessary to enter the VAT number.

This field is subject to the Exchange of goods declaration (Intrastat).

This conversion factor is used in the Intrastat declaration for the exchange of goods. It is used in supplier invoices and applied to the fiscal value of the product line to obtain the statistical value.
It is initialized by either the increase conversion factor entered on the product-supplier record or the supplier record.

Note: This field is only available if a web service is identified in the EVCSERVICE – Webservice for EU VAT ID parameter (CPT chapter, VAT group) and the sender's EU VAT ID is set in the EVCCOMPANY—EU VAT ID source company parameter (CPT chapter, VAT group)

Select the EU VAT ID validation action to interactively validate your EU VAT ID or GB VAT number.

A message box displays with the validation results. The exact content varies by check result and web service used.

• If the validation was successful, you receive a confirmation message and the Validated checkbox is selected.
• For an unsuccessful validation, you receive a message that displays the reason for the failed validation.
• If no full validation could be performed (for example, if only the VAT ID was validated and not the address), you have the option to accept the results as valid or not. If you select Yes, the Validated checkbox is selected.

Note: Successful validation results are stored in a table.

If a previously-validated VAT ID is modified, the Validated checkbox is cleared.

Validation levels:

A Qualified validation verifies the EU VAT ID and company name and address. All data must be valid.

An Unqualified or simple validation only verifies the EU VAT ID. Note that the EU validation web service performs only unqualified validations.

Address management:

Results are recorded with the original address code.

For the main EU VAT ID, the standard company address is used.

You can manually revalidate IDs using the EU VAT ID revalidation function (EVCBAT).

If a previously-validated VAT ID is modified, the Validated checkbox is cleared.

A message box displays with the validation results. The exact content varies by check result and web service used.

• If the validation was successful, you receive a confirmation message and the Validated checkbox is selected.
• For an unsuccessful validation, you receive a message that displays the reason for the failed validation.
• If no full validation could be performed (for example, if only the VAT ID was validated and not the address), you have the option to accept the results as valid or not. If you select Yes, the Validated checkbox is selected.

Note: This field is only available if a web service is identified in the EVCSERVICE – Webservice for EU VAT ID parameter (CPT chapter, VAT group) and the sender's EU VAT ID is set in the EVCCOMPANY—EU VAT ID source company parameter (CPT chapter, VAT group)

A transport location must be specified in the EU exchange declaration. It is combined with the Incoterm code in order to determine the delivery conditions referring to the sales contract terms that specify the respective obligations of the buyer and seller.

This information is not used in the French declaration.

Use this action to create a text that will be loaded in all pick tickets linked to this ship-to address. The SALTEXPRP parameter is used to set up the assignment of this text.

Use this action to create a text that will be used on all packing slips related to this ship-to address. The SALTEXDLV parameter is used to set up the assignment of this text.

Use this menu to view the market sector associated with the address code of the ship-to customer based on a sector code.

This field specifies the address code of the bank ID number, controlled in the address codes of the managed entity (company, site, customer, supplier, etc.).

This address code is used to define the default bank ID number in payment contexts where an address is known.

This code is used to identify the Country and determines the following formats and if they are required or not for the country:

• The phone number
• The number format that identifies a company or an activity, such as tax ID number, NAF in France
• The postal code
• The VAT ID number
• The Bank ID code

The IBAN is an internationally agreed standard of identifying bank accounts in a structured format.
IBAN can be used in national and/or international payment transactions (country-specific).
The IBAN code consists of: 

• A 4-digit IBAN prefix composed of:
  - a country code (2 letters),
  - two check digits
  This prefix is displayed. It is calculated automatically upon the bank account information entered in the Bank ID field.
• The bank account information (country-specific, up to 30 characters).

 Not all countries support IBAN. The IBAN format applied to bank accounts is controlled by the IBAN management option, defined in the Countries function.

This number identifies the bank account of a given bank, for a given country.
The entry format of a Bank ID number is dependent on the country where the bank is domiciled.

For the entry of the Bank ID number to be correct, it is necessary to predefine the entry format in the Country table and to activate the option IBAN management for those countries supporting the IBAN format.

 In case of an IBAN, this field only contains the bank account, beginning from the 5th character of the IBAN. The first 4 characters of the IBAN (country code and check digits) are calculated automatically and displayed in the IBAN pref field.

This field indicates that the Bank ID number is used by default for payments (in the absence of a more precise rule).

This code is used to identify the currency associated with the bank account.
It is managed in the currency table.

It is recommended to use the ISO coding during the creation of a new currency.

This field requires the KSW – Swiss localization activity code to be active. You use it to enter the ISR customer number for the given bank account. This number is used for payments with ISR number (inpayment slip with reference numbers).

For suppliers, the ISR customer no. is also used to search for a matching BP account if support for ISR code line entry on purchase invoices is active in the SWIPURBVR - Swiss ISR usage purchasing parameter (LOC chapter, SWI group).

Refer to the Swiss legislation guide on the How to tab for more details regarding payment and ISR setup.

This field, which is mandatory for payments, defines the paying bank related to the account number. The first line contains the name of the bank.

This field identifies the bank account's beneficiary (physical or moral person).

To perform the automatic processing of payment requests, the sender's bank needs the BIC code of the recipient's bank. This code is an ISO identifier managed by the international banking system, and namley the SWIFT system, the Society for Worldwide Interbank Financial Telecommunication.

The BIC code is the only standardized bank identifier at international level. All banks can have a BIC code, even if they do not belong to the SWIFT network.

The BIC code can be comprised of 8 to 11 characters. In both cases, the first 8 characters of the BIC code generally designate the bank's head office and are structured under the form BBBB PP AA, which correspond to the following information:

• BBBB is the bank code.
• PP is the ISO country code.
• AA stands for a service code often to serve a geographic purpose.

In some commercial exchanges, upon the request of Business Partners or payment issuing banks, an intermediary bank is sometimes used. For that purpose, the identifiers of this bank must be entered (BIC code, paying bank, country). This information remains optional (it does not need to be entered if no intermediary bank is mandatory).

Use this window to enter the bank details in your local format. The information entered is then automatically recovered in the fields of the Bank details section.

This window automatically opens when leaving the Country field, but only if the following conditions are met:

• This window exists for the selected country.
• The window code is specified in the Bank detail window of the Country function.
• The user parameter LOCSCRACT - Bank detail screen activation (TC chapter, INT group) is set to Yes.

Each contact associated with the record is identified by a unique key, which is used to share contacts common to several records.

This code defines the unique key in the contact record. This key can be manually assigned or if it is not entered, it can be defined via the CCN sequence number counter.

By default, this counter is constructed of a sequence number made up of 15 characters. To ensure the correct functioning of the Contact object, it is strongly advised to conserve these standard characteristics.

Indicates the family name of the contact.

Each contact associated with the record is identified by a unique key, which is used to share contacts common to several records.

This code defines the unique key in the contact record. This key can be manually assigned or if it is not entered, it can be defined via the CCN sequence number counter.

By default, this counter is constructed of a sequence number made up of 15 characters. To ensure the correct functioning of the Contact object, it is strongly advised to conserve these standard characteristics.

This field associates a closing sentence with a contact's family name.
This information can be used on documents to be sent to contacts.

Indicate the family name of the contact.

First name of the contact.

This field specifies the position of the contact to choose from a pre-defined list.
The local menu 233 lists all the possible positions.

This text field indicates the department to which the contact is attached.
No table controls this information.

This field, used for information purposes, makes reference to the codes entered in miscellaneous table 906.

This fields specifies the language of the contact.

Birthday of the contact, only present for information reasons.

The value of the contact's address code, controlled in the address codes of the supported entity, is for information purposes only. This code is used to link the contact to one of the addresses of the relevant entity.

Title associated with the previous code.

This field is used to specify the email address of the contact.

This field indicates the phone number. Its entry format depends on the country.
The level of control applied to the entered number format depends on the general parameter CTLTEL - Phone number control (SUP chapter, INT group).

This field specifies the fax number where the entry format is identical to that of the telephone and is dependent on the country.

This field indicates the mobile phone number with an entry format that depends on the country.

This indicator is designed to specify that the contact cannot be selected in a mailing.

When this box is checked, the selected contact becomes the default contact.

Order acknowledgment

Use this menu to enter a text that will be printed by default in the order acknowledgments for this customer (see the SALTEXORD parameter).

Invoice

Use this menu to enter a text that will be printed by default on the invoices for the customer (see the SALTEXINV parameter).

Notes P/R not due 1

Use this action to display the query windows that give you access to the financial risk information, in particular the notes payable and receivable not due.

Reminder: Three types of notes payable and receivable can be managed. This is defined in the setup of the payment transactions. When an intermediate posting is performed, you must go to the Steps section to indicate if a group, or "portfolio", of notes payable/receivable not due must be updated and, if yes, which one (for the group of notes P/R number 1).

Notes P/R not due 2

Use this action to set up the second type of notes payable/receivable (see "Notes P/R not due 1" in this documentation).

Notes P/R not due 3

Use this action to set up the third type of notes payable/receivable (see "Notes P/R not due 1" in this documentation).

Doubtful receipts

Use this action to view the detail of the doubtful payments if any.

Extensions

Use this action to view information on extensions when some notes payable and receivable have been postponed.

Quotes

Use this action to view the list of quotes for the selected customer (with filtering criteria on the company, site, customer, converted quotes, non-converted...). For more information see the help on the Quote inquiry function.

From each line, an action is available to jump to the corresponding quote.

Quote line

Use this action to view the quote lines for this customer.

Orders

Use this action to view the list of orders for the customer (with filtering criteria on the company, site, customer, order category, shipped orders, open orders...). For more information see the help on the Order inquiry function.

From each line, an action is available to jump to the corresponding order.

Order line

Use this action to view the order lines for this customer.

Deliveries

Use this action to view the deliveries for the customer (with filtering criteria on the company, site, customer, shipment type, confirmed shipments, non-confirmed...). For more information see the help on the Shipment inquiry function.
From each line, an action is available to jump to the corresponding delivery.

Delivery line

Use this action to view the quote lines for this customer.

Invoices

Use this action to view the list of invoices for the customer (with filtering criteria on the company, site, customer, validated invoices, non-validated...). For more information see the help on the Invoice inquiry function. 
 BP invoices are also displayed in this inquiry.
From each line, an action is available to jump to the corresponding invoice.

Invoice line

Use this action to view the quote lines for this customer.

Accounts

Use this action to view the customer account (all the control accounts together by default). For more information see the help on the Account inquiry function.
From each line displayed, an action is available to jump to the corresponding journal entry.

Installed base

Use this action to jump to the Customer base function and filter the customer base records on the selected customer. For more information, see the help on the Customer base management.

Installed base by address

Use this action to view the installed customer base for a specific address.
This inquiry gives you direct access to a customer base object, and provides a selection list filtered based on the selected customer code and address.

Aggregated installed base

Use this action to view the customer base, according to a set of criteria.
This inquiry gives you access to a criteria selection screen for the selected customer, with options such as the company code, site code, address code as well as an "aggregation" (grouping) criteria.
Use the aggregation criteria to group the information based on this criteria. The product reference used in the customer base is used by default.
Once you have entered your criteria, click the Search action to launch the inquiry.

BP situation

Use the BP situation action to get an overview of the customer based on their assigned due dates, financial and commercial credit levels and the last operations they performed.

Risk analysis

While the BP situation action provides you with an overview of the customer status (financial, commercial, due dates, performed operations...), the Risk analysis action gives you direct access to information on customer financial risk.

Last operations

While the BP situation action provides you with an overview of the customer status (financial, commercial, due dates, operations performed...), the Last operations action gives you direct access to information on the last operations performed by the customer.

Aged balance

Use this action to access the aged balance for this customer at this date.

Associate order givers

Use this action to define if the selected customer is an internal customer, a customer of an order-giver (or service caller), or both. If the customer is internal, select the Internal customer check box. If the customer is not an internal customer, enter all the order-givers that the customer is linked to. To do so, enter the Service caller field, or use the Selection icon to choose from the list of available service callers defined as BPs.

Market segments

Use this action to view the market sector associated to the address code in the customer record based on a sector code.

Points debit

This function is used to access the points debits points debit rule currently in use for the customer. It is possible to manage both the contractual rules and the additional points debits.

History

This function is used to view all the Pre-sales and After-sales activity for the current customer. The actions carried out are sorted from the most recent to the oldest, whilst the actions to be carried out are sorted in the opposite direction.

All the following record types are grouped within this history:

• Tasks
• Calls
• Appointments
• Projects
• Mass-mailing
• Service requests
• After-sales interventions

A contextual menu, Detail, is available on each line in the grid. This is used to access the complete record for each action displayed in the history.

Projects

This function is designed to directly access the projects object.
The access via this function is designed to obtain in the left list the processed projects for the current customer.
If the user uses the New button, the project will be pre-loaded with the customer information.

BP ID validation

This validation functionality is available in several functions. It is limited to French companies, which are listed in the French government SIRENE database. You can use it to confirm data related to an existing BP and to help build an accurate BP record when creating a new BP.

You can access this functionality from the Site tax ID no. field or from the Actions menu in these functions:

• BPs (GESBPR)

• Carriers (GESBPT)

• Customers (GESBPC)

• Prospects (GESBPP)

• Sales Rep (GESREP)

• Suppliers (GESBPS)

How to validate a BP

This only applies to French BPs registered in France.

For an existing BP: You can compare data in your record with the SIRENE database. The BP information block displays data in the current record that is compared against the SIRENE database.

For a new BP: You can find information about a new BP to complete the new record. In this case, the fields in the BP information block are empty.

In the Site tax ID no. field, select BP ID validation from the More actions icon. Or select BP ID validation from the Actions menu.

In the BP ID validation screen that opens, you can search the SIRENE database according to the search criteria you enter. You can search by 1 or up to all 4 criteria. All entered criteria are considered in the search. For example, if you search by a company name and a city, results match both inputs. If you enter a Company name, you can search for all companies that begin with the characters entered in that field or for all companies that contain those characters.

The Company information grid displays results, if any, found in the database based on all criteria entered.

The Site information grid displays a list of sites with unique SIRET numbers that share the same SIREN number. If you search by Company tax ID no. and Site tax ID no., there is only 1 result in the grid because SIRET numbers are unique for each company site.

Working with search results

The Company information and Site information grids display results from the search of the SIRENE database. Each grid only displays up to 200 records. If there are more than 200, you need to refine your search criteria to reduce the number of results.

The grids highlight fields where the data in your record and the database do not match. If a field is highlighted in yellow, the SIRENE data does not match your records. If you are creating a new BP, the columns are highlighted yellow but there are no reasons. If a row is highlighted in red, that company is listed as closed in the SIRENE database. The Reason column details why a field or fields are highlighted such as

• A closed site or company

• A duplicate SIRET number

• A different name, postal code, or city

In the Site information grid, select a site with an address that is a match for the company you want to validate. The matching company in the Company information grid is automatically selected and the Site information grid only displays the site or sites for that company.

For an existing BP: If the records are different, you can select Update to overwrite the current BP record with the data from SIRENE.

For a new BP: Selecting Update populates the new BP record with the data from SIRENE.

Plan/Appointments

It is possible to plan an appointment/meeting from a customer record. The information relative to the customer is automatically initialized if an appointment is created with this function.

The appointments displayed in the different left lists are those related to the customer.

Plan/Call

It is possible to plan a call from the customer record. It will be by default an out-going call. The information relative to the customer is automatically initialized if a call is created with this function.

The calls displayed in the different left lists are those relative to the customer.

Plan/Task

It is possible to plan a task from a customer record. The information related to the customer is automatically initialized if a task is created with this function.

The tasks displayed in the different left lists are those relative to the customer.

Create/Quote

This function is designed to directly access the quotes object.
The access via this function is designed to obtain in the left list only the quotes carried out and remaining to be carried out for the current customer.
If the user uses the New button, the quote will be pre-loaded with the customer information. It is then considered that what is being carried out is a quote.

Create/Order

This function is designed to directly access the orders object.
The access via this function is designed to obtain in the left list only the orders carried out and remaining to be carried out for the current customer.
If the user uses the New button, the order will be pre-loaded with the customer information. It is then considered that what is being carried out is an order.

Create/Invoice

This function is designed to directly access the invoices object.
The access via this function is designed to obtain in the left list only the invoices carried out and remaining to be carried out for the current customer.
If the user uses the New button, the invoice will be pre-loaded with the customer information. It is then considered that what is being carried out is an invoice.

Create/Appointments

This function is designed to directly access the appointments object.
The access via this function is used to obtain in the left list only those appointments carried out and remaining to be carried out for the current customer.
If the user uses the New button, the appointment will be pre-loaded with the customer information. It is then considered that it is an appointment that is carried out.

Create/Call

This function is designed to directly access the calls object.
The access via this function is used to obtain in the left list only those calls carried out and remaining to be carried out for the current customer.
If the user uses the New button, the call will be pre-loaded with the customer information. It is then considered that it is an outgoing call that is carried out.

Create/Task

This function is designed to directly access the tasks object.
The access via this function is used to obtain in the left list only those tasks carried out and remaining to be carried out for the current customer.
If the user uses the New button, the task will be pre-loaded with the customer information. It is then considered that it is a task that is carried out.

Create/Project

This function is designed to directly access the projects object.
The access via this function is designed to obtain in the left list the processed projects for the current customer.
The user accesses the function directly in creation mode and the project will be pre-loaded with the customer information.

Create/Service request

It is possible to save a service request from a customer record.
Access via this function is used to obtain in the left list only those service requests concerning the current customer.
If the user uses the New button, the service request will be pre-loaded with the customer information.

Create/Warranty request

It is possible to save a warranty request from a customer record.
Access via this function is used to obtain in the left list only those warranty requests concerning the current customer.
If the user uses the New button, the warranty request will be pre-loaded with the customer information.

Create/Service contract

It is possible to save a service contract from a customer record.
Access via this function is used to obtain in the left list only those service contracts concerning the current customer.
If the user uses the New button, the service contract will be pre-loaded with the customer information.