BPs

• Category (field BRGCOD)

This is the customer category or supplier category associated with the BP.

This category makes it possible to:

• have an additional BP classification,
• have default values upon creation,
• assign an automatic numbering to BPs according to a counter associated with the customer category or supplier category.

When converting a BP into a customer or a supplier, using the same category as the one used for the BP makes it possible to assign to the customer or supplier a code identical to that of the BP.

• BP (field BPRNUM)

Enter the BP code or use the Lookup tool to search from the BP table.

• Short description (field BPRSHO)

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 recorded (on creation/update) in the connection language of the user.
You can add your translation in another language using the Translation function:

• Click 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 will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

The connection language must be defined as a default language for thefolder.

• Acronym (field BPRLOG)

BP's acronym.

• field BPRNAM

Business Partner company name.

• Natural person (field LEGETT)

When it is activated, this indicator makes it possible to specify that the BP is a physical person. When it is not activated, it is a corporate body.
If the BP is a corporate body, it is mandatory to enter the "VAT identification number" and the "Site tax ID number" if their entry has been set up at country level as mandatory.

• Mailing prohibited (field BPRFBDMAG)

• Country (field CRY)

This code is used to identify amongst other things, the Country of a BP.
This is important information, associated with a number of characteristics useful for performing controls on other linked information, in particular:

• the telephone number format,
• the format of the number that identifies a company or an activity (site tax ID number, NAF in France), and whether its entry is mandatory or not,
• the postal code format of the town and also the code of the geographic subdivision, and whether their entry is mandatory,
• whether the VAT number of this community is mandatory,
• the Bank ID code format.

• Language (field LAN)

Code controlled in the language table making it possible to define the language of a business partner.

• Currency (field CUR)

This code is used to identify the currency of a site, a BP, etc. Is is controlled in the currency table.
 It is recommended to use the ISO coding upon creation of a new currency.

• Site tax ID no. (field CRN)

Single identification number for the company.
It is mandatory to enter this number if both the following conditions are satisfied:

• its entry is set to mandatory by setup of the country record,
• the BP is a corporate body.

Its 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 bodies and the administrations in contact with businesses.

• SIC code (field NAF)

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

• Doc. type (field DOCTYP)

This field is displayed only when the KSP activity code is activated.
It is used to identify the type of fiscal identification for the BP.

• EU VAT no. (field EECNUM)

This is the VAT identification number of the BP. 

This European VAT number must be entered on all the invoices destined to or coming from the European Union. This number starts with two letters identifying the business partner country followed by a number depending on the country.

In France the number is comprised of FR, then 2 numbers identifying the tax office of the place where the company conducts its activities, followed by the Company tax ID no.(SIREN) of the company.

This information must necessarily be entered if the Company Registration number is set up as being mandatory for the country of the company.

• EU VAT ID validation (field EVCVAL)

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)

Click the Validation action to interactively validate your EU VAT ID.

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 Validation check box 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 Validation check box is selected.

Note: Successful validation results are stored in a table.

If a previously-validated VAT ID is modified, the Validation check box 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).

• Verified (field EVCVALDON)

If a previously-validated VAT ID is modified, the Validation check box 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 Validation check box 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 Validation check box 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)

• VAT number (field VATNO)

• Registration number (field REGNUM)

• EORI number (field EORINUM)

If the Country profile for this entity has the EROI identification field selected, you can enter an EORI number, which is prefixed with the country's ISO code.

Note: This number is needed for entities doing business within the UK and for EU companies importing and exporting goods and services with UK companies.

• Intersite (field BETFCY)

This flag is designed to indicate if this is an inter-site BP:

• The inter-site customer/supplier BPs are used for multi-site exchanges.
• A customer BP is a purchase site or a financial site,
• a supplier BP is a sales site or a financial site.

• Site (field FCY)

Site code that has to be identified as a BP within the frame of multi-site exchanges.

The following data need 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.

• Customer (field BPCFLG)

• Sales rep (field REPFLG)

• Prospect (field PPTFLG)

• Public sector (field BPPFLG)

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

Select this check box to specify that the BP is a public sector organization. In this case, the maximum number of days for the last payment due date of an invoice destined to this BP 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 destined to this BP is defined by the DMAXPAY - Maximum period (companies) parameter (TC chapter, RSK group). However, you can have an special agreement with this BP and grant them a longer period. Enter this period at the level of the Contractual period field (DAYPAY), available in the BP/Company tab.

• Supplier (field BPSFLG)

• Miscellaneous BP (field BPRACC)

Miscellaneous business partner (for Sales and Purchase ledger accounting).

If this box is ticked, the document type and accounting code fields become active.

• Service supplier (field PRVFLG)

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.

• Carrier (field BPTFLG)

• Service caller (field DOOFLG)

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).

• Ship-to (field PTHFLG)

Field reserved for Argentina (KAG activity code) designed to specify the VAT collector.

• Grantor (field CCNFLG)

This tick-box is designed to list the BP as Grantor; thus, the BP will be listed as Grantor in concession agreements.

• Address code (field CODADR)

Address code of the business partner (BP).

• Address code (field XCODADR)

• Description (field XBPADES)

• Country (field XBPACRY)

• Description (field XCRYNAM)

• field XADDLIG1

• field XADDLIG2

• field XADDLIG3

• Postal code (field XPOSCOD)

• City (field XCTY)

• field ITINERAIRE

Click this icon to open a mapping site and locate the entered address.

• field XSAT

• Website (field XFCYWEB)

• External identifier (field XEXTNUM)

• Default address (field XBPAADDFLG)

• field XTEL1

• field XTEL2

• field XTEL3

• field XTEL4

• field XTEL5

• field XWEB1

• field XWEB2

• field XWEB3

• field XWEB4

• field XWEB5

• Accounting code (field ACCCOD)

This field is used to specify the accounting code of the BP.
The accounting code is a default value used in the creation of 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.

• Consolidation group (field GRUGPY)

Consolidation area: field under control of the CSL activity.

Choose the group of companies for which consolidations are to be carried out.

• Consolidation (field GRUCOD)

This code is used during the data extraction operation in prevision of the consolidation. Used to identify the company from which the entries are extracted.

• Report access code (field ACS)

Access code used as a filter for accounting reports.

• Fiscal code (field FISCOD)

Fiscal code (for Italy only).

• IVA partita (field VATNUM)

Field reserved for Italy to enter the VAT number.

• Item type for expense account (field BPRGTETYP)

The document type (3 alphanumeric characters) makes reference to the Document type record that characterizes the documents generated in the Sales and Purchase ledger accounting.

A selection and a tunnel are available from the contextual menu.

• Cash excluded (field CFOEXD)

• Leave as 'No' to include the BP in the cash forecast management.
  You can, however, exclude the BP from the forecasts for specific companies using the BP/Company tab.
• Set to 'Yes' to exclude the BP from the cash forecast management.
  If a document refers to this BP (as a pay-by BP or pay-to BP), the latter is not taken into account in the automatic generation of cash forecasts.
  It is still possible to take the BP into account in the manual creation of cash forecasts.

This field defaults to 'No', meaning the BP is taken into account in the forecast management.

• CFONB payment (field MODPAM)

This field is used to indicate the payment method.
Four payment methods are possible, according to the following codes:

• '0': transfer or other, except cheque,
• '1': bank cheque to the order giver,
• '2': bank cheque to the recipient,
• '3': funds put at disposal after identification.

This information is taken into account upon generation of the bank files.
 If no value is specified at BP level, the value '0' ('transfer or other, except cheque') will be applied by default.

• Related company (field CPYREL)

• Partner (field CSLBPR)

• Address (field BIDBPAADD)

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.

• Country (field BIDCRY)

This code is used to identify the country associated with the bank account.

The country table, containing this code, gathers information that is useful to perform controls, and namely:

• the telephone number format,
• the format of the number identifying a company or an activity (SIRET, NAF in France),
• the postal code format,
• the format of the Bank ID number code.

• IBAN prefix (field IBAN)

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).
• 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 theCountries setup.

• Bank acct. number (field BIDNUM)

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 Countrytable and to activate the option IBAN managementfor those countries supporting the IBAN format.

 In case of an IBAN this field has to contain the bank account part only, 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 field IBAN pref.

• Default (field BIDNUMFLG)

Use this field to specify that this bank account number is used by default for payments, for the selected address.

• Currency (field BIDCUR)

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

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

• ISR customer no. (field BVRNUM)

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.

• Nonresident (field ACCNONREI)

Select Yes if the account is not located in the country where the owner lives. This identifies the BP account as a nonresident account.

No is the default value.

A nonresident account is used to enter the Economic reason code in payments when the following conditions are met:

• The threshold payment balance defined in the AMTVIR1-Threshold 1 payment balance or AMTVIR2 - Threshold 2 payment balance parameter is met (PAY chapter, RGL group).
• In Economic reasons codes (PBDECOCOD): enter values for the company legislation.
• In Economic reason/BP groups (PBDBPGRP ): enter values for the legislation and the BP code used for payments.
• The PBDDEFGRU - Payment balance default BP group parameter (TRS chapter, PBD group): enter the default BP group code used in payments or for migration for the related legislation.
• The payment entry type (GESTPY) used for the payment must have the Bank account numbercheck box selected.

• Paying bank (field PAB1)

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.

• Beneficiary (field BNF)

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

• Paying bank 2 (field PAB2)

• Paying bank 3 (field PAB3)

• Paying bank 4 (field PAB4)

• BIC code (field BICCOD)

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 mnemonic identifier;
• PP is the ISO country code;
• AA stands for a service code often to serve a geographic purpose.

• Intermediary bank (field MIDPAB1)

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).

• Paying bank 1 (field MIDPAB2)

• Paying bank 2 (field MIDPAB3)

• Paying bank 3 (field MIDPAB4)

• BIC code (field MIDBICCOD)

• Country (field MIDCRY)

• Contact code (field CCNCRM)

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.

• Last name (field CNTLNA)

Indicate the family name of the contact.

• Contact code (field KCCNCRM)

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.

• Title (field KCNTTTL)

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

• Last name (field KCNTLNA)

Indicate the family name of the contact.

• First name (field KCNTFNA)

First name of the contact.

• Function (field KCNTFNC)

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

• Department (field KCNTSRV)

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

• Role (field KCNTMSS)

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

• Language (field KCNTLAN)

• Date of birth (field KCNTBIR)

Birthday of the contact, only present for information reasons.

• Category (field KCNTCSP)

• Address (field KCNTADD)

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

• field KADDNAM

Title associated with the previous code.

• Email (field KCNTWEB)

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

• Telephone (field KCNTTEL)

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).

• Fax (field KCNTFAX)

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

• Mobile phone (field KCNTMOB)

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

• Mailing prohibited (field KCNTFBDMAG)

• Default contact (field KCNTFLG)

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

• Company (field CPY)

Company for which the BP exception is applied.

This exception can concern:

• the business partner tax rule and/or
• the payment conditions, and/or
• the discounts and charges, and/or
• the accounting code, and/or
• the entry of accounting entries on the BP
• the contractual period for the last open item.

• Customer tax rule (field VACBPC)

The customer tax rule by default is stored in the Customer record.
In the case of a multi-companies management, the same customer can be subject to a different tax rule according to the company they deal with.
Use this field to enter exceptions and to set the customer tax rule by company.
Only the tax rules in phase with the legislation and the group of the indicated company can be entered.
The general principles linked to the multi-legislation setup are detailed here.

• Supplier tax rule (field VACBPS)

The supplier tax rule by default is stored in the Supplier record.
In the case of a multi-companies management, the same supplier can be subject to a different tax rule according to the company they deal with.
Use this field to enter exceptions and to set the supplier tax rule by company.
Only the tax rules in phase with the legislation and the group of the indicated company can be entered.

The general principles linked to the multi-legislation setup are detailed here.

• Customer pymt. terms (field PTEBPC)

The customer payment conditions are stored in the Customer record.
In the case of a multi-companies management, the same customer can have different payment conditions according to the company they deal with.
Use this field to enter exceptions and to set the customer payment conditions by company.
A control is performed in order to verify the consistency between the legislation/the group for which the payment condition selected is defined, and the legislation and group of the company indicated.
For further information, click here.

• Supplier pymt. terms (field PTEBPS)

The supplier payment conditions are stored in the Supplier record.
In the case of a multi-companies management, the same supplier can have different payment conditions according to the company they deal with.
Use this field to enter exceptions and to set the supplier payment conditions by company.
A control is performed in order to verify the consistency between the legislation/the group for which the payment condition selected is defined, and the legislation and group of the company indicated.
For further information, click here.

• Customer early disc. (field DEPBPC)

The customer discounts and late charges are stored in the Customerrecord.
In the case of a multi-companies management, the same customer can have different early discounts and late charges according to the company with which this customer deals.
Use this field to enter exceptions and to set the customer discounts and charges by company.
Only the early discount/late charge codes in phase with the legislation and the group of the site company can be entered.
The general principles linked to the multi-legislation setup are detailed here.

• Supplier early disc. (field DEPBPS)

The supplier early discounts and late charges are stored in the Supplier record.
In the case of a multi-companies management, the same supplier can have different early discounts and late charges according to the company they deal with.
Use this field to enter exceptions and to set the supplier early discounts and late charges by company.
Only the early discount/late charge codes in phase with the legislation and the group of the site company can be entered.
The general principles linked to the multi-legislation setup are detailed here.

• Customer acct. code (field ACCBPC)

The customer accounting codes are stored in the Customer record.
The accounting code is a default value used in the setting up of accounting journals. It refers to a table in which a certain number of elements can be found (control accounts, standard accounts or parts of accounts) that can be used to determine the accounting journals that will be posted.
In the case of multi-companies management, the same customer can be associated to different accounting codes according to the company the customer deals with. Use this field to enter exceptions and to set the customer accounting codes by company.

• Supplier acct. code (field ACCBPS)

The supplier accounting codes are stored in the Supplier record.
The accounting code is a default value used in the setting up of accounting journals. It refers to a table in which a certain number of elements can be found (control accounts, standard accounts or parts of accounts) that can be used to determine the accounting journals that will be posted. In the case of multi-companies management, the same supplier can be associated to different accounting codes according to the company the supplier deals with. Use this field to enter exceptions and to set the supplier accounting codes by company.

• Authorized entry (field ACEAUZ)

The entry of commercial documents or accounting entries is authorized for all business partners, by default.

For a multi-company management, you can set this field to No to disable the entry for the business partner on specific companies.

Particular cases: Prospects
By default, a prospect BP cannot be entered in accounting. If an exception should be made for a prospect for a given company, enter this exception by setting the authorization code to Yes.

• Cash excluded (field CFOEXDCPY)

• Contractual period (field PAYDAY)

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

It is relevant only if the BP is a private sector company, not a public sector organization.
In this case, you can have an agreement with this BP and grant them a longer period for the last payment due date than the period defined in the DMAXPAY - Maximum period (companies) parameter (TC chapter, RSK group).
Enter the contractual period in this field.
This period cannot exceed the period imposed by the current legislation and specified in the DMAXAGR - Maximum contractual period parameter (TC chapter, RSK group).

• Payment bank ISR/QR (field PAYBANBVR)

This field is related to the SWICUSBVR - Swiss ISR usage Sales (LOC chapter, SWI group) parameter.

The payment bank information is used to print the necessary sender’s bank account information on ISR payment forms. Use this bank account as the destination account when paying the invoice.

The ISR payment bank for the invoice is determined by the Payment bank ISR field in one of the following functions. The system pulls the information from the first entry found:

• On the BP/Company tab in the BP function (GESBPS)
• On the Financials tab in the Customer function(GESBPC)
• On the Detail tab in the Sites function (GESFCY)