Invoices

• Sales site (field SALFCY)

The sales site is initialized by the sales site associated with the user. The sales site can be modified (as long as no line has been entered on the document) provided it has been chosen from the list of sales sites authorized to the user.

• Type (field SIVTYP)

The customer invoice type is used for the Sales and BP Customer invoices. It identifies a category of invoice (invoice, credit memo etc.) along with a posting structure for the posting of the invoices.

On invoice entry, only an invoice type with a legislation and company group consistent with those of the company linked to the sales site can be entered.
 For further information, click here.

The invoice type is associated to a type of journal for which a counter (manual or automatic) is specified.
 If no counter is specified in the journal type and no journal number is manually specified on invoice entry the program will attribute a journal number according to the counter set up in the counter assignment table.
 When no journal type is associated to the invoice type the journal type specified on the automatic journal will be used (as well as the associated counter).

• Invoice no. (field NUM)

Invoice number. This number is used to identify the invoice in a unique way. It is entered upon each creation or automatically generated depending on the counter associated with the invoice type.

• If the invoice sequence number is manual, the invoice number must be entered.
• If invoice sequence number is automatic, a number is assigned on creation.

• Reference (field INVREF)

This free field is used to enter a number or an indication to identify the invoice. For instance, it can be the internal reference of the supplier invoice in the company.
When the invoice is created by picking orders, this information is initialized by the reference of the first original order invoiced (even upon invoicing deliveries coming from orders).

• Date (field INVDAT)

This is the customer date. It is initialized to the current date and it can be modified. If it is modified, after at least one line has been entered or saved, a question is asked suggesting that the prices and discounts on all the lines of the document be recalculated.  This message is suggested only if it is an invoice or direct credit memo. If the invoice or the credit memo refers to original documents, the latter is not suggested.

 Comments on the DGI conformity:

• The entered date cannot be inferior to the one of the document (invoice, credit memo or additional invoice) marked with the previous number. This control is: performed when the Chronological control is activated in the sequence number counter used by the entry type which is linked to the invoice type entered.
• Entering the invoices, credit memos or additional invoices can be limited, for a user, to a range of dates defined by the parameters VENSTRDAT - Sales start date and VENENDDAT - Sales end date, when they are entered.
• Date modification is authorized only if the new date applies to the same accounting period. This control is carried out when the parameter FRADGI - Regulation DGI N° 13L-1-06 is positioned to Yes and that the period component belongs to the counter.
• To ensure the chronology of events, an additional control is applied when entering or generating an invoice or a credit memo (entries coming from the Distribution and A-P/A-R accounting modules). This control checks that there is no entry with a date greater than the period end date of the current entry. This control is submitted to parameter CTLPERINV - Period invoice date control (chapter TC, group INV), delivered with the value 'Yes' for the French legislation, and not modifiable.
  This is the same for any new company created which is subject to the French legislation.
• In the Distribution and A/P-A/R accounting modules, a journal which is at the origin of an invoice or a credit memo cannot have a date greater than the date of this invoice or credit memo.
  For instance, the date of an invoice displayed on a credit memo cannot be greater than the date of this credit memo.
  Likewise, a delivery note displayed on an invoice cannot have a shipment date greater than the date of this invoice.
  A control is carried out to check the dates. The picking left lists and selection windows are filtered accordingly. 
  An entry point makes it possible to disable this control, by defining a specific parameter CTLDATORI - Document date control.

• Currency (field CUR)

• Bill-to customer (field BPCINV)

Code of the customer requesting the invoice in the case of a direct invoice.
It is managed in the customer table. It must be active. It can be of normal or miscellaneous type. It cannot be modified after the lines are entered. In the case of an order or delivery invoice, it is the original invoice customer. It cannot be modified.

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.

• If the customer entered is of the Miscellaneous type, a window automatically opens to enter or modify their address and SIRET number. You can also view and modify this information by clicking Invoice address from the Action panel.
• If the entered customer is of the Normal type and the customer is entered, you can view and modify the invoicing address using the Actions icon or by clicking Invoice address from the Actions panel. The customer SIRET number is pulled from the BP record and cannot be modified.

When creating an invoice, you can select:

• one or several delivery notes,
• one or several order lines when the approval circuit is managed (APPSOH - Order approvals management setup), the sales orders following the established approval rules are not taken into account as long as they are not Totally signed,
• one or several contracts (a service contract can be invoiced if it is not paid or terminated and if the notice date of the next invoice open item has been reached (the date of the next invoice minus the invoicing notice must be below the date of the invoice)),
• a service request (a service request can be invoiced if it is closed and if consumptions can be invoiced).

In the case of service contract invoicing, the creation date triggers the execution of processes related to service contracts:

• Next invoice date: The system recalculates a new invoicing due date on the basis of the invoicing frequency and the invoicing notice.
• Contract re-evaluation: From the re-evaluation frequency mentioned in the service contract, the system determines if the annual fee for the contract must be re-calculated. In order to re-evaluate an annual fee basis, the system compares the value of the index used at the time of the last re-evaluation with the last index value saved in the application. The fee basis is reduced or increased according to the evolution recorded in the index. The amount of the next invoice due date is re-calculated. This amount directly depends on the invoicing frequency and weighting coefficient for the annual fee basis.

The documents are exclusive to one another. You cannot invoice both delivery notes and orders.

When creating a credit memo, it is possible to select:

• one or several invoice lines,
• one or several return lines (a return can lead to a credit memo if a credit memo has yet to be emitted and if the return line is awaiting credit).

Here, too, the documents are exclusive to one another.

When creating a cancellation invoice, you can select one or several invoices. The cancellation applies to each invoice as a whole and you cannot select lines one by one or modify them.

If you cannot select two documents of the same type for the same invoice, it is mandatory to specify the following information for these two documents: sales site, currency, pay-by customer, group customer, price type, tax rule, project code, payment terms, discount code.

• field BPINAM

• Original document no. (field ORIDOCNUM)

This field must contain a slash character (/) separating the sequential number specific to the series (on the left) and the sequential number itself (on the right).

• Sequence number (field SIHNUMEND)

• Electronic signature (field SIHCFMFLG)

• Spanish invoice type (field INVTYPSPA)

• Sold-to (field BPCORD)

Code of the customer requesting the order, the direct delivery or the direct invoice. This code:

• must be managed in the customer table,
• must be of normal, miscellaneous or inter-company type,
• can be modified as long as no line has been entered on the document.

• field BPCNAM

• Pay-by (field BPRPAY)

Paying customer loaded by the bill-to customer.

• Group customer (field BPCGRU)

The group customer is initialized by the group customer code associated to the sold-to customer in the latter's record. This information is used for the generation of statistics. It is also involved in the grouping of invoices during the automatic generation of invoices. There is the possibility to modify the group customer if necessary.
From this field, it is possible to select a customer or access customer management by tunnel if the user's authorizations allow it.

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.

• Delivery address (field BPAADD)

The delivery address is initialized:

• by the default address code associated with the bill-to customer in the case of a direct invoice if any, otherwise, it is the first address code in the list that is proposed,
• by the address code of the first document selected in the case of the invoicing of an order, of a delivery, etc.

From this field, you can directly enter an address code whose existence is controlled or use the Actions icon to:

• Select a delivery address from the displayed list
• Based on the authorizations you were granted, create a new address code for the bill-to customer
• Modify the detail of the address corresponding to the code entered

If the address code is modified during entry, the sales representatives on the invoice header associated with the shipment address are automatically reassigned by the sales representatives codes for the new address. If the value of the LINREP - Sales rep on detail parameter is Yes, a message suggests the replacement of the sales reps of the invoice lines with the new sales reps on the header. If the value of the LINREP - Sales rep on detail parameter is No, the reassignment is performed automatically.

Once the invoice has been created, the address code can no longer be modified, but it is possible to display the detailed address information by clicking the Address field from the Actions icon.
Comment: the address can be modified via the Address/Delivery menu. If the modification impacts the country and/or the geographic subdivision, provided the invoice has not been validated, a dialog box is displayed and asks whether to recalculate the prices and discounts. The answer Yes generates a price list search, based on the new country code and/or the new geographic subdivision code, for all the lines of the document.

• field BPDNAM

• Project (field PJT)

This field contains the reference of the project for which the information has been entered.
This field is not controlled in a table.

• In a request for quotes, this field is empty by default.
• in a purchase order, this field can be initialized by default using the Project reference of the previous line or that of the request for quotes considered.

It is possible to enter a free code or a project code defined in the Project object in the CRM activities module. In this latter case, the user has two possibilities to enter such a code:

• the first contextual menu, Selection, is used to select a project from a selection list containing all the projects defined in object Projects,
• the second contextual menu Projects is used to directly access the Projects object, according to the user's authorizations, and then to carry out a selection.

If the order arises from a requirement and this requirement has a project code, the project code of the order will be initialized with this project code.

• Sales rep (field REP)

The sales reps are initialized by the customer sales reps, then by those of the ship-to customer, if no sales rep exists in the customer record. In the case of a prospect, the representatives of the prospect are not considered. These sales rep codes are copied to the document lines. If a representative is modified in the document header upon creation or when lines exist in the document, the system suggests to copy the modification to all the lines that already exist.

• Source (field SIHORI)

• field SIHORINUM

In this section of the tab, the information used to identify the origin of the invoice are displayed. This is the document number based on which the invoice/credit memo/pro-forma invoice was created.
This field is entered only if the original document is unique. For example, if the invoice is attached to a single shipment, the corresponding shipment number is displayed.
The same goes for invoices or Pro formas linked to orders, service contracts, invoicing open items of orders, service requests or inter-company stock transfer notes or for credit memos linked to invoices or returns. A jump to the document number is used to access the original document.
When managing a credit memo, this concerns the invoice that the credit memo is allocated to.
Upon accounting validation and according to the value of the LETAUTCNO - Auto match inv ->credit note parameter (CPT chapter, MTC group), the credit memo and invoice can be matched together.

Based on the value of the INVCAN - Cancellation invoice parameter (TC group, INV chapter), the current documentcan be of the Cancellation invoicefolder. In this case, the credit memo and invoice are matched, regardless of the value of parameter LETAUTCNO.

• Memo reason (field CNOREN)

This field can be entered in the case of credit memos: enter the reason for the credit memo in this field.

• Method of correction (field METCOR)

• Purchase invoice no. (field PIHNUM)

This is the purchase invoice number generated from the sales invoice when in inter-company.

• VAT declaration no. (field DCLEECNUM)

This field is displayed only if the following conditions are met:

• The KPO - Portuguese localization activity code is active.
• The company to which the invoicing site is linked manages the Portuguese VAT (the value of the company parameter PORVAT - Portuguese VAT (LOC chapter, POR group) is "yes").
• This field is not set up as hidden at entry transaction level.

 This field is initialized:

• on the first line: with the supplier EU VAT number indicated in the invoice header,
• on each of the next lines: with the EU VAT number indicated on the line preceding the current line or, if not, with that of the supplier indicated in the invoice header.

It can still be modified if it is set up to accept entries at entry transaction level and if the invoice is not validated.

• Period start date (field PERDEB)

The date ranges are only displayed if the document is a credit memo and the KPO activity code - Portuguese localization is activated. They are used to specify the period which the credit memo refers to.
They must be entered if the credit memo is not linked to any source document. The control is carried out at when the function is [posted].

• Period end date (field PERFIN)

• VCS number (field BELVCS)

• Tax rule (field VACBPR)

This information is used to indicate the tax rule for the document. This code is controlled in the tax rule table and is initialized by the corresponding code in the BP record. It can be modified.
This information is mandatory and remains accessible provided the delivery has not been confirmed.
Only a tax rule with a legislation and group that are consistent with those of the document can be entered.
The general principles linked to the multi-legislation setup are detailed here.

• Entity/Use (field SSTENTCOD)

• Price - / +tax (field PRITYP)

The value of this field (Ex-tax or Tax-incl.) is defined by the general parameter SALPRITYP - Price/Amount type (TC chapter, INV group).

When the general parameter NOTATI - Ex-tax and tax-incl. amount/price (TC chapter, INV group) is set to No you cannot modify this information.

• Field 40 - reason (field FLD40REN)

Field subject to activity code: KPO - Portuguese localization
It is used to specify the VAT adjustment reason for the field 40, upon generation of the VAT declaration.
When choosing the reason, the possible values are the values contained in the miscellaneous table 8300.

• Field 41 - reason (field FLD41REN)

Field subject to activity code: KPO - Portuguese localization
It is used to specify the VAT adjustment reason for the field 41, upon generation of the VAT declaration.
When choosing the reason, the possible values are the values contained in the miscellaneous table 8301.

• Stock transaction (field STOMVTFLG)

Stock movement flag that indicates if the invoice is managed with stock update.

• Shipment site (field STOFCY)

The 'delivery site' is initialized by default with the normal storage site for the user.
It can be modified provided that the chosen site is defined with an active 'stock' indicator. The chosen site must belong to the same legal company that the sales site.

• Warehouse (field WRHE)

• Dock location (field SRGLOCDEF)

In the case where the receipt transaction authorizes a dock receipt (parameter active in the transaction setup), a dock location field appears in the receipt note header. This makes it possible to enter a location of the 'dock' type which will then be transferred by default as the return location for all receipt note lines. The specified dock location must be associated with the warehouse, when the latter is specified.

A dock location corresponds to a location of the type "pending storage". This authorizes the entry of stocks whose characteristics of lot, sub-lot, and serial number are not necessarily immediately identified. This type of receipt is used to rapidly book the goods and to then later to more precisely identify them and put them away. This put-away process is performed in the function Put-away plan.

• Stock movement group (field TRSFAM)

Movement group, initialized by the movement group of the transaction being used.

• Incoterm (field EECICT)

The Incoterm codes, set by the International Chamber of Commerce, seek to standardize the terms the most used in the international commerce by defining the respective responsibilities of the seller and the buyer agreed upon on establishement of 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.

When creating a quote, an order, a delivery or an invoice, the Incoterm code is initialized to the Incoterm code defined by default for the ship-to customer.

This Incoterm code can be modified. Concerning the quotes and orders, the Incoterm code is unique for the document as a whole. When transforming a document, the Incoterm code is passed on to the child document.

• Incoterm town (field ICTCTY)

It is the city associated to some types of incoterm. For instance: 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.

• Status (field INVSTA)

This information cannot be modified and specifies the status of the invoice:

• not posted,
• not used,
• posted (i.e. accounting entries generated).

• Printed (field STARPT)

• Intercompany (field BETCPY)

This information is not accessible, it specifies that the invoice or credit memo concerns a company within the group.
For an invoice to have the type "Inter-company", it is necessary:

• that the bill-to customer be defined as "Inter-site" customer; the associated site must be a financial site and must belong to a different company than the sales site of the invoice,
• that the sales site be declared as supplier: the sales site must be associated with the supplier record (setup performed in the "Management" tab of the Supplierrecord).

• Registration (field LICPLATE)

License plate of the vehicle carrying goods.

• Trailer license plate (field TRLLICPLAT)

Enter the trailer license plate.

• Departure date (field DPEDAT)

• Departure time (field ETD)

• Arrival date (field ARVDAT)

• Arrival time (field ETA)

• Currency (field CUR)

This is corresponds to the currency of the order, delivery or invoice.
It is initialized by default with the bill-to customer currency and can be modified. In this case, it can only be modified in creation and duplication modes and is controlled in the currency table.

It is possible to choose the currency for the delivery transaction as well as to define (depending on the value of the 'Excl. tax and Incl. tax Prices' parameter - TC Chapter / INV/NOTATI group) if the prices are expressed excluding tax or including tax. When the delivery comes from an order, this information is automatically loaded and cannot be modified. When it is a direct delivery, this information is no longer modifiable once at least one delivery line is entered. It is inherited in this case from the invoiced customer information.

• Rate type (field CURTYP)

This field is initialized by the invoicing supplier exchange rate type.

• Rate (field RAT1)

• field LABEL

• field RAT2

• field CURMLT

• Factor (field BPRFCT)

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.

• Control (field BPRSAC)

Enter the code for the BP (customer or supplier) control account initialized by default with the accounting code for the BP invoice.

The initialization of the code for the Control field depends on whether or not the BP/Company tab is present in the BP record (GESBPR).

No BP/Company  tab on the BP record.

When the customer or supplier code is specified, the Control account defined on the Financial tab on the first line of the accounting code is used.

P BP/Company tab present on the BP record.

For a document, the site and the customer or supplier code are the first information entered. The BP record is searched on the BP/Company tab to see if an exception line has been created for the entry site company and, if required, finds the customer or supplier accounting code.

The account of the first line of the accounting code is then used. When the exception line is absent for the entry site company, the Financial tab of the BP record is referenced to identify its code.

• Due date start (field STRDUDDAT)

This information is initialized as a function of the original open item defined on the bill-to customer. It is used to calculate the open items (based on the payment condition) by taking as the original date the date of the invoice or the shipment date. This date is modifiable (this will trigger a re-calculation of the open items) and it can be prior to the invoice date if necessary. 

• Terms (field PTE)

The payment terms define the payment code and the distribution rules of the various pre-payments and open items.
It is initialized from the payment code associated with the bill-to customer if it is a direct invoice or by the original document.
This information remains modifiable and its modification will trigger a recalculation of the open items.

From this field, it is possible to directly enter a payment code whose existence is controlled in the corresponding table or to use the contextual button to:

• select a payment code from the table,
• create, according to the user's authorizations, a payment code in the table,
• simulate a calculation and a distribution of the open items through the button [Simul].

If the invoice is linked to a service contract, the payment condition is that of the service contract and not that of the order that may have created the service contract.
If SDD is managed in the payment terms, the field "Mandate reference" must be entered. The selection of a SDD-type payment term is prohibited if the "Pay-by BP" is a "Miscellaneous BP".

Only a discount code consistent with the legislation and company group of the document site can be entered.
The general principles linked to the multi-legislation setup are detailed here.

• Mandate reference (field UMRNUM)

This field, subject to an entry transaction, is displayed only if the activity code SDD - SDD management is active and if the company parameter SDDMGT - SDD management (chapter TC, group SDD) is set to "Yes".

Upon direct invoice creation, it can be entered and is mandatory only if the payment term is an SDD-type one. It is used to enter the reference of the SDD mandate.
When a "Validated" mandate has been identified as "Main mandate" for the [Company ; Pay-by BP] pair, the reference of this mandate is loaded by default but can be modified. Only a mandate reference whose status is "Validated" can be entered.
If the company and/or the pay-by BP is modified, the mandate reference is reinitialized accordingly.

When the invoice is created through an automatic creation process, this field is not initialized if no "Validated" main mandate has been defined for the company/pay-by BP combination. However, In this case, the invoice is created, but it can not be validated until a mandate reference is entered.

During a credit memo entry by invoice picking, the mandate reference is populated by the reference of the mandate on the first selected invoice.

• Settlement discount (field DEP)

This information is entered in the quote, is initialized by the discount code of the bill-to customer and can still be changed. It makes it possible to determine a series of early discount or late charge rates (up to 12) according to the early or late payment relating to the due date (see Discounts Documentation).
From this field, it is possible to directly enter a discount code whose existence is controlled in the corresponding table or to use the contextual button to:

• select a discount code in the table,
• create, according to the user's authorizations, a discount code in the table.

Only a discount code consistent with the legislation and company group of the document site can be entered.
The general principles linked to the multi-legislation setup are detailed here.

The amount of the discountable base is displayed on the "Valuation" tab.

• Service start date (field STRDATSVC)

Indicates by start and end date ranges, the part of the service to be carried forward to the next period or fiscal year.
These fields are only activated if the "Accruals" (SVC activity code) option is set to "Yes". The expense or revenue with apportionment is generated by means of the Accruals generation option.

• Service end date (field ENDDATSVC)

• ISR reference number (field BVRREFNUM)

This field displays the IRS reference number created for an invoice if the SWICUSBVR - Swiss ISR usage Sales (LOC chapter, SWI group) parameter is set to Yes. If a new invoice is created, the ISR reference number is calculated when the invoice is saved.

When the value of the SWICUSBVR parameter is set to Yes, this field only displays a value if an ISR payment term is used and the invoice currency is CHF.

If you copy an invoice, the existing ISR number is removed. A new number is created when the copied invoice is saved.

Refer to the Swiss legislation guide on the How to tab on the Online Help Center for more details on how to use the ISR reference numbers.

• Payment bank ISR (field PAYBAN)

This field displays the ISR payment bank determined for the invoice if the SWICUSBVR - Swiss ISR usage Sales (LOC chapter, SWI group) parameter is set to Yes.

When the SWICUSBVR parameter is set to Yes, this field only displays a value if an ISR payment term is used and the invoice currency is CHF.

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 is only considered in the ISR process.

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.

1. On the BP/Company tab of the BP function (GESBPS)
2. On the Financial tab of the Customers function (GESBPC)
3. On the Detail tab of the Sites function (GESFCY)

If you copy an invoice, the existing payment bank is removed and the payment bank determination is repeated when the copied invoice is saved.

Refer to the Swiss legislation guide available at the online help center for a comprehensive overview of setup and usage of this function.

• Comments (field DES)

This field is used to enter comments where the first line can be taken as a label for the posting according to the parameters of the automatic journal (PIHI for the purchase invoice or SIHI for the sales invoice).
The presence of this field depends on the entry transaction used.

• Dimension type (field DIE)

This table is used to enter or view the dimension types, depending on the setups of the delivery entry transaction.

• Description (field NAMDIE)

• Dimension (field CCE)

The setup determines whether the analytical dimensions can be modified. They are initialized in accordance with the setup of the default dimensions (rules defined in the financials module). 
If a document is the origin of the invoice, the analytical dimensions will be those inherited from the original document and the non specified dimensions will be completed.

• Short description (field SHO)

The invoicing elements that appear in this tab are those that have been defined as needing to appear on the invoice.
They are initialized and can be modified based on the choices made during their definition (see the Invoicing elements documentation).
If the invoice concerns a service contract generated by an order, the invoicing elements will be those that come from the contract. 

• % or amount (field INVDTAAMT)

The values relate to the invoicing footer. This information can stem directly from the setups of the invoice footer elements or from the record of the concerned customer or the selected order.
 See the Invoicing elements documentation for further information.
The footer values can be modified. The ex-tax and tax-incl. amounts of the document are directly impacted by these values.
 Modification of an invoice by adding/deleting either a delivery, an order, or an order line: the amounts of the invoice elements are not recalculated by taking into account the added/deleted deliveries, orders, or order lines. The share of the invoicing elements relating to these lines or documents is not added/subtracted from the modified invoice.
The same principle applies to the modification of the credit memoes by addition/deletion of an invoice or invoice line.

• field INVDTATYP

The system specifies whether the invoicing element is a percentage or a tax excl. or tax incl. amount.

• SST tax code (field SFISSTCOD)

Enter the code to use in order to override the default SST tax code from the product or invoice element. This tax code is recognized by Sage Sales Tax and is used to identify line types for tax purposes. This field is available only if the LTA - Local taxing activity code is activated, and the USATAX - Tax system use parameter is set to Yes.

For invoicing elements designated as the SST document discount for a company, you cannot remove the SST tax code value on the document.

• Product (field ITMREF)

It is the product reference for which a document line is recorded. Specifying it is mandatory.

It is possible to:

• directly enter a product reference or a Product/Customer reference. The existence of this reference is controlled in the Product/Sales and Product/Customer records. If a Product-customer reference is entered, the system will return the internal product reference. A blocking message can be returned during a product entry if prohibited price lists have been set up for some customers ( see price list setup).
• use the contextual button to:
• select a product from the file of sold products,
• select a product from the list of customer products,
• create, according to the user's access rights, a product in the file,
• view the price lists for the product.

The entry of the product is used to initialize the Description and Sales unit fields, which can be modified. The sales unit can be modified on the condition that it is chosen from the suggested list that contains the sales and packing units from the product and product-customer records.

A warning message can appear to inform the user of the replacement of the entered product by the substitute product. This automatic substitution takes place if certain conditions are met:

• The fieldArticle of substitution of the plug article has been entered,
• the document date is greater than or equal to the substitution date.

 Once the line is entered, it will no longer be possible to modify the product code. It is necessary to delete the line and recreate it to modify the code.

• Description (field ITMDES)

This is the product description translated into the customer language. This description is the one that will be printed on the document. If the translation does not exist in the customer language, the un-translated product description is used. This description is also transferred to the next document.

The product record can be accessed from this field using a tunnel.

• Standard description (field ITMDES1)

This is the description entered on the product record. This description is transferred from the sales invoice to the purchase invoice in case of inter-company invoicing. When the invoice stems from another document, the standard description is inherited from the source line.

• Major version (field ECCVALMAJ)

This field displays the major version of the product.

The major version number can be accessed if:

• the major versions tracking is active at the level of the product setup (in the Management tab of the Product function, the Stock version field is set to 'Major').
• the invoice is a direct invoice with stock movements.

If the preloading of versions is active at the product/customer level (in the Customers tab of the Product function, the Version preloading box is checked), or by default, at the product/sales level (in the Sales tab of the Product function, the Version preloading box is checked), then the last active major version is preloaded automatically. Otherwise, the last major version with the 'Stopped' status will be preloaded.

For a delivery invoice or a service request invoice, the version numbers are loaded when adding a direct line.

When the invoice is created from other documents, the following actions are carried out:

• Orders picking with transfer and control of versions on the invoice.
• Transfer and control of versions for the automatic invoicing of orders (if the version is not correct, an information message is displayed in the log file). There is no version transfer for the automatic invoicing of deliveries, the automatic invoicing of service requests and the automatic invoicing of transfers.

The Major version field display depends on the setup of the entry transaction (hidden, displayed, entered).

• Minor version (field ECCVALMIN)

This field displays the minor version of the product.

The minor version number can be accessed if:

• the major and minor versions tracking is active at the level of the product setup (in the Management tab of the Product function, the Stock version field is set to 'Major and minor').
• the invoice is a direct invoice with stock movements.

If the preloading of versions is active at the product/customer level (in the Customers tab of the Product function, the Version preloading box is checked), or by default, at the product/sales level (in the Sales tab of the Product function, the Version preloading box is checked), then the last active minor version is preloaded automatically.

For a delivery invoice or a service request invoice, the version numbers are loaded when adding a direct line.

When the invoice is created from other documents, the following actions are carried out:

• Orders picking with transfer and control of versions on the invoice.
• Transfer and control of versions for the automatic invoicing of orders (if the version is not correct, an information message is displayed in the log file). There is no version transfer for the automatic invoicing of deliveries, the automatic invoicing of service requests and the automatic invoicing of transfers.

The Minor version field display depends on the setup of the entry transaction (hidden, displayed, entered).

• Percentage (field INVPRC)

This is the invoiced percentage corresponding to the scheduled invoice. This percentage is linked to the invoiced quantity.

• You can enter a percentage larger than the percentage of the schedule line as long as the total percentage of lines does not exceed 100%. Modifying the percentage cannot lead to over-invoicing. A message is displayed suggesting that you consume all subsequent scheduled invoices. You can accept by clicking Ok or Cancel.
  
• You can enter a percentage lower than the percentage of the schedule line: this triggers the addition of a scheduled invoice line at the end of the schedule. This line has the same characteristics as the modified line and a percentage equal to the difference from the modified line. The status of this line is: To be invoiced Modifying the percentage triggers the recalculation of the invoiced quantity.
  
  The schedule, displayed using the Actions icon on the scheduled invoice line, specifies for each schedule line if it has been invoiced, included in the invoice or if it needs to be invoiced.

• SAL (field SAU)

The sales unit is initialized by the sales unit defined in the Product-customer record, if it exists, otherwise it will be initialized by the sales unit of the product. It is possible to enter another unit using a selection window. The units proposed other than those mentioned previously, are the packing units for the product and the packing units defined in the "Product-customer" record. When necessary and if the user has the appropriate authorizations, it is possible to access the units table.

Once the line is entered, it is no longer possible to modify the sales unit. It is necessary to delete the line and to recreate it to modify the unit.

• Invoiced qty. (field QTY)

The invoiced quantity is expressed in sales unit.
For direct invoices, it must be superior to the minimum quantity and inferior to the maximum quantity from the product-sales.

For scheduled invoices:

• the entry of a quantity greater than the quantity on the schedule line triggers a message suggesting that you consume the extra quantity on the next scheduled invoices. If you answer Yes, you cannot pick and add the next scheduled invoices subject to this extra consumption unless you have saved the modification. If you answer No,, the quantity increase is considered as over-invoicing.
  
• the entry of a quantity lower than the quantity on the schedule line triggers the addition of a scheduled invoice line at the end of the schedule. This line has the same characteristics as the modified line and a quantity equal to the difference from the modified line. The status of this line is: To be invoiced.
  
  The schedule, displayed using the Actions icon on the scheduled invoice line, specifies for each schedule line if it has been invoiced, included in the invoice or if it needs to be invoiced. A flag indicates if any excess is invoiced (over-invoicing), displaying this excess amount and/or quantity.

When the invoiced quantity is entered, a price list search processing is automatically carried out. The objective of this search is to recover:

• The gross price as well as the associated reason
• The charges and discounts in percentages or in amounts to be applied to the line level as well as the associated reasons
• Any free product(s)
• The weighting coefficient for the sales representatives' commission rates

The price list search processing can be triggered in different ways depending on the product type entered:

• If the product entered has the Normal type, the search processing is automatically launched.
• If the product entered has the Kit parent product or BOM parent product type, an initial price list search is launched for the parent product. Then, before triggering the price list search for the components, the BOM file is read in order to identify whether different alternatives of the Commercial type exist, in which case they are displayed in a window. If the product has only a single BOM code, it will be taken into account automatically.
  

After choosing the BOM code, different cases can occur according to the construction of the product BOM:

• Each component of Normal type is automatically selected.
  
  It is automatically replaced by the substitute product if it was entered at the level of the Product record if the document date is later than or equal to the substitution date.
  For the other types of components mentioned below, when a substitute product is used, the original product description is displayed at the level of the components selection window.
• For each component with the Normal type(with formula), a window displays all the products returned by the selection formula. If a component of the type Normal has also been recorded in the same sequence, this component also appears in the list. By default, it is automatically selected but it is possible to clear this selection. Its quantity cannot be modified.
  It is possible to select one or several other components of the selection. The Include all and Exclude all buttons are available for this purpose. Therefore, if no component is selected, the Criteria button becomes available so as to narrow the selection when the number of lines in the table is too large (the number of lines presented depends on the number of lines that still can be inserted in the document).
• For each component of type Variant, a window opens displaying the set of variants listed at the same BOM level or coming from a selection. It is mandatory to choose one.
• For each component of the type Option, the option is suggested and the user must accept it or refuse it. When several options are possible for a same BOM level or when a selection formula is defined, a window opens for the user to select one or more options or to refuse all of them.
• For each component of type Multiple option, a window opens displaying the set of components listed at the same BOM level or coming from a selection formula. You can select several components or refuse all. The Include all and Exclude all buttons are available for this purpose. If no component is selected, the button [Criteria] becomes available in order to narrow the selection when the number of table lines is too important.

The lines corresponding to the different BOM components are then generated:

• If the product has the Kit component type, all the component lines are automatically generated. These lines are now completely dependent on the parent component. They appear on the screen but they cannot be accessed. The component quantity is automatically calculated from the parent product quantity. If the parent product quantity is modified, the quantities of all the components are automatically recalculated. If you delete the parent product, all the components are automatically deleted.
• If the product has the BOM parent product type, all the component lines are submitted and can be modified (except the sales unit). They become independent from the parent product. If you modify or delete the parent product, you are asked whether or not to transfer the modification or deletion onto the components.

In both cases, a price list search for the component type is then automatically triggered and for each order line generated, a value is assigned to the type of line:

• Kit option or BOM option for an Option type component
• Kit Variant or BOM Variant for a Variant type component
• Kit component or BOM component for a Normal type component

Controls are carried out on exiting this price list search processing:

• If the price is defined as including tax, the tax-excluded price is calculated
• Control on the calculated net price: if the calculated net price is lower than the threshold price stored in the product record, a message is displayed
• Control on the profit margin: if the percentage margin is lower than the minimum margin percentage (or margin rate) stored in the product record, a message is displayed.

These various messages can be blocking messages depending on the value of the SDACLOCK - Price, margin, qty non-blocking ctrl user parameter. They will be deactivated in the case of credit memos.

• SAL-STK conv. (field SAUSTUCOE)

This is the conversion factor between the sales unit and the stock unit. This coefficient can be modified in certain cases. It can be edited if the sales unit of the product has been specified as 'editable', or if the chosen packing unit has also been specified as 'Editable' (See Product record). It cannot be edited if the unit used is a unit defined for the customer. If units are used where the factor is modifiable, it is necessary to define for the product concerned, only prices expressed in stock unit. In addition, if a basic price list has been defined for the sales unit, the modification of the conversion factor for the sales unit does not trigger a recalculation of the unit gross price.

 Once the line entered, it is no longer possible to modify the conversion factor. The line must be deleted and recreated so as to modify the factor.

• STK (field STU)

This field indicates the product management unit in which are expressed:

• The stock
• The standard price
• The BOM link quantity, etc.

This information is always displayed, regardless of the transaction used. It cannot be modified.

• Gross price (field GROPRI)

This is the unit gross price (in sales unit) of the product expressed tax-excluding or tax-including (depending on the price type). It comes from a price list search, or from the base price of the sales product if the price list search did not return any result.

If the sales unit is different to that of the price list line:

- The price list amount is converted if the Unit conversion is set to Yes in the Price list setup. This conversion is based on the table of unit conversion factors. If no conversion is set up for these units, the price list amounts are considered by applying a conversion rate of 1.

- The price list is not used if the Unit conversion is set to No in the Price list setup. The gross price is set to 0.

Click the Actions icon to:

• View the reasons associated with the price as well as the different discounts and charges fields;
• View the list of the last 10 order prices;
• View the price lists;
• Get an explanation on how the net price was obtained from the gross price and the different discounts.

If the entered price is null, a message is displayed to request confirmation.

This message is displayed neither for the components of a BOM nor for free items.

A processing for Free items is triggered at the end of the document line. This processing generates all the free product lines (Gross price and discounts set to 0). If the parameter FOCPRI - Free product valuation (chapter VEN, group PRI) has the value Yes, a price list search is triggered for the free item so as to assign it a gross price. The assigned price is compensated for, either by a line discount in percentage or a line discount in amount (according to the order of discounts) to obtain a zero net price.

The original line number of the free item is mentioned in each free item line generated in the quote line file (information not displayed on the screen). The Origin information is displayed on the line that created the free items in the Free field. For the free item line, this information is set to Yes. All free item lines are accessible in modification mode (except the price and discounts fields). It should be noted that the management of free items is not taken into account for components.

When creating the document, if the setup manages grouped price lists (GRPPRI - Management of grouped price lists), a question is asked about whether to carry out a new price list search (for the grouped type) that is used to determine the specific conditions linked to the whole quote. At the end of this process, you may get the following, on some product lines:

• A new gross price or new discounts or new charges for the line;
• Free products that are not associated with a specific line.

• field DISCRGVAL1

Discounts and charges columns are displayed.
They depend on the setup of the Price list structure code associated with the supplier in the supplier record (see documentation Price list structure).

They can be initialized by the use of the price lists (see the Price list setups and Price list entry documentations). Access to these columns can depend on the setups of the reasons associated with the price lists as well as the value of the reason given to the UPDPRISAL setup for Sales and to the UPDPRIPUR setup for Purchase.

These discounts or charges are defined in amount or in percentage and they are applied with a totaling or cascading method to the gross price to determine the net price of the document line.

The contextual button is used to:

• view the reasons associated with the price as well as the different discounts and charges fields,
• modify, if necessary, the reasons allocated to each column.

• Net price (field NETPRI)

From this field, use the Actions icon to:

• view the reasons associated with the price as well as the different discounts and charges fields,
• view the list of the last 10 order prices,
• View the price lists;
• have a detailed explanation available describing how the net price is obtained.

When the entered price is null, a message is displayed asking for confirmation. This message is not displayed for the components of a BOM, for free items and for nonbillable deliveries.

A process for the Free items is triggered at the end of the delivery line. This processing generates all the free product lines (Gross price and discounts set to 0). If the value of the FOCPRI - Free product valuation parameter (VEN chapter, PRI group ) is set to Yes, a price list search is triggered for the free item to assign it a gross price. The assigned price is compensated for, either by a line discount in percentage or a line discount in amount (according to the order of discounts) to obtain a zero net price.

When you click Create to record the delivery, and based on the value of the GRPPRI - Grouped price lists parameter, a message can be displayed, suggesting that a new price list search is run to determine the specificities globally linked to the delivery. At the end of the processing, the following can be generated on some product lines:

• A new gross price or new discounts or new charges for the line;
• free products that are not associated with a specific line.

• Line amt in value (field AMTLIN)

• Cost price (field CPRPRI)

The cost price is loaded by default by the valuation of the product chosen for the margin calculation (see the valuation methods defined for the Product-Site record) at the time of the creation of the document line and is expressed in sales unit. The different choices possible for the cost price valuation are: Standard price, Revised standard price, Last price, Weighed average price, FIFO price, Lot average price and LIFO price. If the valuation method happened to return a zero value, a fall value can be used by specifying another valuation method contained in the list previously described. This value is stored in the document line.

It is possible to pre-load this information as a function of the document transaction used.

The 'cost price' is systematically recalculated upon: 

• modification of a quote turned into an order,
• delivering an order, 
• validating a delivery,
• invoicing of an order.

In quote management, the 'lot average price' always returns a null value. The alternative default is used in this case. During the delivery confirmation, the Lot average price is used again to recalculate the margin and thus obtain a real margin depending on the shipped lot(s).

Specificities related to credit memos:
When a credit memo is created with a customer return or an invoice as its origin, the cost price proposed is the cost price from the original document. If it is a direct credit memo, the cost price is calculated from the margin calculation rule defined by the Product-site valuation method.

• Margin (field PFM)

This field displays the margin in sales unit, calculated based on the difference between the net price and the cost price.

During the gross margin calculation, a control can be carried out to verify that this margin is not below the minimum threshold defined in the Sales tab in the Product record. This control can be blocked according to the value attributed to the user parameter SDACLOK - Non block. control price, prof, qty (VEN chapter, AUZ group). The calculation carried out to control the margin rate is the following:

(Ex-tax price - Cost price) / Total ex-tax price) *100 >= percentage of the minimum margin.

No control is carried out on nonbillable deliveries.

• Tax level 1 (field VACITM1)

This field indicates the tax level applied to the selected product.

The tax level, when crossed with the document tax rule, is used to determine the tax rate to be applied on the document line.

There are three tax levels for a document line.

The first level is compulsory and it corresponds to the VAT.

The other two levels concern additional and special taxes that can be submitted to the VAT or not, and be applied to the ex-tax basis or any other evaluated formula.

The tax levels for the document line will be loaded by default with the values associated with the product record (Accounting tab). These values can be modified depending on the transaction. You can also, if the user's authorizations permit it, access the tax level management.

The parameter CTLTAX - Tax codes control (VEN chapter, VAT group) is used to control that the tax codes linked to the tax level are consistent. Using this control, the system checks that the tax level:

• is specified,
• is activated,
• has a legislation and company group consistent with the ones of the document.

• SST tax code (field SSTCOD)

Enter the code to use in order to override the default SST tax code from the product or invoice element. This tax code is recognized by Sage Sales Tax and is used to identify line types for tax purposes. This field is available only if the LTA - Local taxing activity code is activated, and the USATAX - Tax system use parameter is set to Yes.

For invoicing elements designated as the SST document discount for a company, you cannot remove the SST tax code value on the document.

• Project (field DPJT)

The project code in document line is initialized by the one entered in the header or, in the case of a document transformation, by the one of the selected document lines (in picking or in mass processing, if the project code on a document line is inactive, the line cannot be selected).
It can only be modified if one of the two following conditions are met:

• the PJTSNGDOC - one project per document parameter (chapter TC - group MIS) is set to No,
• the entry of this field is authorized by the entry transaction being used.

In modification mode, the project code management depends on the value of the CTLOPPCOD - Mandatory project control parameter.

• When the value is No, it may be a code selected freely.
• When its value is Yes, an existence check is systematically applies to the entered project code.

When the entry is controlled, depending on the context, a project or one of its entities can be picked (a budget batch or task), using its posting code:

• The project allocation code is composed of:
  - for projects, the project counter number,
  - the concatenated project sequence number with the budget batch code, in the case of a project budget batch,
  - the concatenated project sequence number with the number of tasks, in the case of a project task.
  
• You can only select one Active posting code, depending on the status of the relevant entity. If it becomes inactive after the creation of the document, the control is performed and blocks the modification of the document.

In selection, there are two possibilities:

• The Selection contextual menus (CRM projects, Projects, Budget batch or projects only linked to the BP) are used to select a project in a selection list.
• The CRM projects and Projects contextual menus are used to directly access the chosen management function and then carry out a selection or create a project.

When the project code of the document header is modified, this project code is automatically transferred to the lines, except when the multi-project management is authorized. In this case, a dialog box would open and suggest to transfer this code to the lines of the document, according to the following options:

• Yes: the project code is transferred to all lines.
• No: the project code is not transferred to the lines.
• Same value: the project code is only transferred to the lines associated to the previous project code.

Sales documents: quotes, orders, deliveries and invoices:
- In case lines were impacted, a dialog box opens and suggests to recalculate the prices and discounts. The answer Yes causes a price list search, based on the new project code, for all the lines of the document.
- In the event the project code were modified in the line, this same price list searching system is applied to the line.
Depending on the processed document, the recalculation is performed only if the following conditions are met:

• For a quote: the item line is not ordered and is not free.
• For an order: the item line is not closed, not delivered, not invoiced nor free.
• For a delivery: the item line is direct and not free.
• For an invoice or a direct credit: the document is not validated, the item line is direct and not free. For direct credits, the quantity is different from 0.

• Warehouse (field WRH)

• Lot (field LOT)

For invoices, specify the lot to be issued.
Specifying it is not necessary in the following cases:

• the issue is multi-lot,
• not all the characteristics of the stock to be issued are specified (lot, sub-lot, serial number, location).

If the product is managed with serial numbers, only this number is necessary to determine the stock to issue.

If not, the lot, sub-lot and location (conditioned by the product management method) are needed.

For credit memos, if the product is not managed by lot, this field cannot be accessed. If the product is managed in mandatory or optional lot, the field availability depends on:

• the settings of the Credit memo entry transaction used,
• The lot management rule linked to the Delivery return movement defined in the product Category or in the stock management rules. At this level, it is possible to specify the type of lot entry and to assign a default value to the lot.

At the end of the entry, if no lot number has been entered, several cases can arise:

• the movement management rule allocates the document number,
• the system uses the lot sequence number for the product to allocate a new lot number. If no sequence number for the lot has been specified for the product and the lot is mandatory, a blocking message is displayed.

• No. of sublots (field NBSLO)

This field contains the number of sub-lots concerned by the stock transaction.

• Sublot (field SLO)

This field specifies the sub-lot to be issued. When the lot is selected, the sub-lot is immediately initialized.
Specifying it is not necessary in the following cases:

• the issue is multi-lot,
• not all the characteristics of the stock to issue are known (lot, sub-lot, serial number, location).

If the product is managed with serial numbers, only this number is necessary to determine the stock to issue.
If not, the lot, sub-lot and location (conditioned by the product management method) are needed.
For credit memos, this field specifies which sub-lot is involved in the receipt movement.

• Ending sublot (field SLOF)

This field indicates the last sub-lot on which the stock movement is applied.

• Supplier lot (field BPSLOT)

The supplier lot number can be entered for information purposes in the receipt transactions.
It is stored in the stock file, and it matches the internal lot number, which guarantees the traceability of the origin of the goods.
It can be displayed on the screen for information purposes in the stock issue transactions.

• Starting serial number (field SERNUM)

For invoices, indicate the start serial number to be issued. The end serial number is automatically calculated.
It is not necessary to enter the start serial number when the serial numbers to issue are not in a row.

If the product is managed with serial numbers, only this number is necessary to determine the stock to issue.
If this is not the case, the lot, sub-lot and location (depending on the management method for the product) are necessary.

For credit notes, specify the first serial number that is involved in the receipt movement. This serial number must exist in the database but it is possible to enter a serial number which does not exist.

• Ending serial number (field SERNUMF)

This field contains the end serial number.

• Identifier 1 (field PALNUM)

Use this field to enter additional information, if necessary.

• Identifier 2 (field CTRNUM)

This field indicates the first recorded identifier.

• Status (field STA)

• For invoices, specify the status of the stock to be issued.
  Specifying it is not necessary if all the characteristics of the stock to be issues are not specified (lot, sub-lot, serial number, location).

• If the product is managed with serial numbers, only this number is necessary to determine the stock to issue.
• If not, the lot, sub-lot and location (conditioned by the product management method) are needed.
  
  
• For credit memos, specify the status of the receipt movement stock.
  When the original invoice triggered a stock movement, the status and location are not issued from the original invoice, contrary to the other stock information. Both pieces of information can be accessed from and initialized by the stock receipt rules.
  When the credit memo line is direct, the status and location can be accessed from and loaded by the stock receipt rules.

The management rule attached to the product category is used to determine the authorized statuses and sub-statuses as well as a default status.

• Loc. type (field LOCTYP)

The location types are used to codify the warehouse locations according to their storage characteristics: size, authorized statuses, technical constraints etc.
They are associated with the products by site, and are used in this way to geographically group the products with similar characteristics.
According to the stock transaction parameterization, the location type for the product is proposed by default and can be modified in the transaction entries.

• Location (field LOC)

For invoices, specify the location that is the origin of the issue. To select a location, use the selection window available from the Actions icon.
Specifying the location is not necessary if:

• an issue from several locations is performed,
• not all the characteristics of the stock to be issued are specified (lot, sub-lot, serial number, location).

If the product is managed with serial numbers, only this number is necessary to determine the stock to be issued.
If not, the lot, sub-lot and location (conditioned by the product management method) are needed.

For credit memos, the access to the field depends on the settings of the Credit memo entry transaction used.

When the original invoice triggered a stock movement, the status and location are not issued from the original invoice, contrary to the other stock information. Both pieces of information can be accessed from and initialized by the stock receipt rules.

When the credit memo line is direct, the status and location can be accessed from and loaded by the stock receipt rules.

If the product is managed by location, a default location will be initialized according to the management rule assigned to the movement type Delivery return, and to the locations set up in the Product/site record. The semantic identifying a location category is used to associate in the Product/site record a location type and a potential location. The location type and the location defined in the Product-site record can refer to a group of location types and/or locations if the wild cards (?,*) are used in their definition (see the Location types and Product-site documentations). In the case of some location types, the assignment depends on their availability or their capacity (replenishment management). These pieces of information can be modified.

If the customer credit memo transaction allows it, a dock type location can be entered in the credit memo header. If this is the case, this location is suggested by default. The locations of the type dock are not suggested in the selection if the customer credit memo transaction does not specify receipts to dock.

In some cases, the user may choose not to enter the location type and/or location, because the goods to return will be distributed across different storage locations. This distribution is specified in the stock detail window. If a $ symbol appears in these fields at the end of entry, it means that different location types and/or locations have been assigned and that a sub-detail exists for the stock lines.

• Order price (field PRIORD)

This is the unitary amount by stock unit that can be used to value the stock (if the valuation method for a customer return is Order price).

The valuation method of the stocks is defined per product category depending on a storage site.
It can be:

• set up by transaction type,
• manually modified if necessary, if the transaction authorizes it.
• viewed in the stock detail window.

The order price is initialized as follows:

• if the credit memo line with stock transaction has as its origin an invoice line with stock transaction, then the order price is equal to the value of the stock issue in the invoice. The order price is not modifiable in this case,
• if it is a direct credit memo with stock transaction, the order price is initialized but can be modified.

• Movement description (field MVTDES)

The description of the transaction is a text free to enter and registered in the stock journal for each credit memo line transaction. This information can be modified in the stock detail window. If it has been modified, it is recovered and registered in the invoice line of this field.

• Sales rep 1 (field REP1)

The sales reps on the document line are initialized by the sales reps entered in the document header. If the latter are not entered, the sales reps in the line are initialized by the sales reps for the customer, by those for the ship-to customer if there are no sales reps in the customer record.

If the parameter LINREP - Sales rep on detail allows it (chapter VEN, group MIS), the sales reps can be modified on the document line. It is possible, based on the user's authorizations, to access the sales representative record.

• Commission rate 1 (field REPRAT1)

The commission rate for the sales representative is initialized on the line based on the commission category for the customer and the commission rate for the sales representative by category. This commission rate can be weighted by a modifiable weighting factor that can be initialized by the price list setup. This information comes from the invoice header in the case of a direct invoice or the original document.

• Sales rep 2 (field REP2)

• Commission rate 2 (field REPRAT2)

• Commission factor (field REPCOE)

This coefficient is used to weight the commissioning rate of the sales representatives for this document line upon commision calculation.
This information is initialized using the price list search: some price lists are used to define a weighing coefficient for the commissioning rate of the sales representatives.

• field CCE1

Based on the setup, the analytical dimensions can be modified since they are initialized in accordance with the setup of the default dimensions.

• Service start date (field STRDAT)

Start and end period for the service provision.

• Service end date (field ENDDAT)

• Period number (field PERNBR)

Number of periods

Used in Finance to distribute the Accruals.

• Period type (field PERTYP)

Frequency(number of days, weeks, decades or months).

Used in Finance to distribute the Accruals.

• Line type (field LINTYP)

This information characterizes the line type by distinguishing a classic product from a kit or a BOM product.
It can take the following values:

• Normal,
• Fixed kit,
• Kit Component,
• Kit Option, Kit Variant,
• Flex kit,
• BOM component,
• BOM Option,
• BOM Variant.

• Free (field FOCFLG)

This information specifies whether the line concerns a free item or is at the origin of the generation of one or more free items.
On exiting the line grid, all the totals are carried out as well as any calculations of the tax calculation bases.
In the lower section of the tab, the Ex-tax and Tax incl. totals are displayed (they cannot be modified) as well as the total margin for the invoice.

• Physical flow (field EECFLOPHY)

This field is used to specify whether the line identifies a physical flow playing a role in the Customs document file statement. An invoice line not linked to a physical flow can be declared for regulation if an EEC rule and/or an EEC transaction nature is entered on the invoice (Customs information option).
The initialization of this field is carried out differently whether it concerns a product managed in stock or not:

1/ Product managed in stock

• If it concerns direct invoices/direct credit memos without stock movements the physical flow is initialized to No and remains modifiable.
• If it concerns direct invoices/direct credit memos with stock movements the physical flow is initialized to Yes and remains modifiable.
• If it concerns invoices stemming from a delivery or an order the physical flow is initialized to Yes and cannot be modified.
• If it concerns invoices stemming from a delivery or an order to which additional lines have been added the physical flow is initialized to Yes and cannot be modified.

2/ Product not managed in stock

• If it concerns direct invoices without stock movements the physical flow is initialized to No and remains modifiable.
• If it concerns direct invoices with stock movements the physical flow is initialized to No and remains modifiable.
• If it concerns invoices stemming from a delivery or an order the physical flow is initialized to Yes and remains modifiable.
• If it concerns invoices stemming from a delivery or an order to which additional lines have been added the physical flow is initialized to Yes and cannot be modified.

• Total margin (field PFMTOT)

This is the total margin of the document calculated from the margins on the document lines.

• Excluding tax (field INVNOT)

This field indicates the ex-tax result including the various invoicing elements of the selected products.
These information is displayed when printing the report SBONFACP2
 The calculation detail is stored in tables SVCRVAT and SVCRFOOT.

• Including tax (field INVATI)

This field indicates the tax-including total, which includes:

• the various invoicing elements of the selected products,
• the tax calculation by tax basis.

This information is displayed when printing the DEVTTC report.
The detail of the calculation is stored in the SVCRVAT and SVCRFOOT tables.

• No. (field NOLIGV)

• Tax (field XVSHO)

This field contains the description of the tax present on the lines of the document.

• Amount - tax (field XVNOT)

This field indicates the ex-tax amount totaled for all the product lines having a tax basis corresponding to the first column.

• Subject basis (field XVSMI)

This field indicates the ex-tax basis liable to VAT. It is made up of the ex-tax amount to which any additional or special taxes are added (entered in the product lines) liable to VAT.

• Tax (field XVTAX)

This field contains the tax code present on the document lines.

• Rate (field XVRAT)

This field indicates the tax rate corresponding to the tax basis.

• Tax amt (field XVAMT)

This field contains the amount of the tax obtained by applying the tax rate to the liable basis.

• Other taxes (field XVSUP)

This field contains the additional or special taxes applied to this tax basis.

• Amount + tax (field XVATI)

• No. (field NOLIGF)

• field XFSHO

This field indicates the short title of the invoicing element.

• Amount - tax (field XFNOT)

• Subject basis (field XFSMI)

This field concerns the basis subject to tax of an invoicing element for which the including tax calculation basis is equal to the including tax amount.
The basis of an invoicing element with an excluding tax calculation basis is equal to the excluding tax amount of the invoicing element.
When the invoicing element has a product rate tax rule, you can display the distribution of the basis subject to product tax using the Actions icon.

• Tax (field XFTAX)

This field indicates the tax code applied to this invoicing element.

• Rate (field XFRAT)

This field indicates the tax rate applied to this invoicing element. If the calculation basis of the invoicing element is tax-incl. or the tax rule of the invoicing element is product rate, this information is not displayed and the corresponding tax code either.
When the invoicing element has a product rate tax rule, you can display the various tax rates by subject basis using the Actions icon.

• Tax amt (field XFVATAMT)

This field indicates the tax amount calculated for this invoicing element from the liable basis and the tax rate to be applied.
If the calculation basis of the invoicing element is Tax incl, this information will not be displayed.
When the invoicing element has a product rate tax rule, you can display the distribution of the various tax codes by liable basis using the Actions icon.

• Amount + tax (field XFATI)

This field indicates the tax-incl. amount of the invoicing element.

• Allocation processing (field DSP)

Analytical distribution key of the invoicing element. The key can be modified from the Actionsmenu.
The allocation processing key entered in this field is used to load the associated dimension types. It is made up of one to ten alphanumerical characters.
The allocation processing keys are used to automatically distribute the amount of a financials posting line on several analytical lines. This distribution is carried out according to weighting coefficients.

• field SFICCE1

This refers to the analytical dimensions of the invoicing element.
The dimension codes of the various dimension types can be modified using the Actions icon.

• Excluding tax (field INVNOT)

This field indicates the ex-tax result including the various invoicing elements of the selected products.
This information appear upon printing of the DEVTTC report.
 The detail of the calculation is stored in the SVCRVAT and SVCRFOOT tables.

• field INVNOTRPT

• field DEVRPT1

• Discount basis (field BASDEP)

The discountable base is only displayed if the two following conditions are met:

• a discount code (including at least one line determining a discount) is entered on the invoice, 
• the DEPMTMOD - Discount management mode parameter does not have the value "VAT distribution (account level)".

The calculation of the discountable bas depends on:

• the scope of the Discount code (ex-tax or tax incl) linked to the invoice,
• the setup of the invoicing elements,
• the management mode of discounts defined by the DEPMGTMOD - Discount management mode parameter.
  

• Including tax (field INVATI)

This field indicates the tax incl. total, which includes:

• the various invoicing elements of the selected products,
• the tax calculation by tax basis.

This information appear when printing the report:

• ARCTT2 for the Orders function.
• BONLIV for the Deliveries function.
• DEVTTC2 for the Quotes function.
• DEVTTC for the Invoices function.

The detail of the calculation is stored in the tables SVCRVAT and SVCRFOOT.

You can access the Sage Sales Tax screen from the Actionsmenu.

• field INVATIRPT

• field DEVRPT2

• Tax type (field JURTYP)

A tax code can be used to identify several tax types:

• VAT (Value Added Tax): based on the tax excluded amount
• Additional Tax: this tax is based on the tax excluded amount, on the quantity or any other item of a document line
• Special Tax: this tax is based on the tax excluded amount, on the quantity or any other item of a document line
• Local tax: See below.

In the case of a Special tax or Additional tax, select the Subject to tax box if this type of tax is submitted to this tax.

Local tax

Application

This type of tax is not managed in France.
It applies to Canada and Argentina.

Prerequisites

The PTX - Tax rates implementation activity code must be activated beforehand.
To manage Argentine local taxes, the KAG - Argentinean activity code must be active.

Principle

Taxes on the document footer are applied according to the region of origin and/or destination.
This feature can be extended to other cases: The local taxes depend on information from the TAXLINK table. They can be used as additional taxes in the document footer. This particular case is useful for preventing the tax from being transferred directly into the table.

Location

• In the Sales module, the local tax is displayed directly on the invoice footer.
• In the Purchasing module, the four additional tax codes are displayed on the line and can be modified.
  If the number of taxes is limited for sales, you cannot specify more than four taxes in purchasing lines.

• Description (field JURNAM)

• Taxes (field TAXNAM)

• Tax basis (field BASTAX)

• Rate (field TAXRAT)

Use this field to specify the tax rate that can be applied to this tax.

• Tax amount (field AMTTAX)

• Tax date (field TAXDAT)

• Country (field PAYS)

• Element (field DTA)

• Tax type (field DTAJURTYP)

A tax code can be used to identify several tax types:

• VAT (Value Added Tax): based on the tax excluded amount
• Additional Tax: this tax is based on the tax excluded amount, on the quantity or any other item of a document line
• Special Tax: this tax is based on the tax excluded amount, on the quantity or any other item of a document line
• Local tax: See below.

In the case of a Special tax or Additional tax, select the Subject to tax box if this type of tax is submitted to this tax.

Local tax

Application

This type of tax is not managed in France.
It applies to Canada and Argentina.

Prerequisites

The PTX - Tax rates implementation activity code must be activated beforehand.
To manage Argentine local taxes, the KAG - Argentinean activity code must be active.

Principle

Taxes on the document footer are applied according to the region of origin and/or destination.
This feature can be extended to other cases: The local taxes depend on information from the TAXLINK table. They can be used as additional taxes in the document footer. This particular case is useful for preventing the tax from being transferred directly into the table.

Location

• In the Sales module, the local tax is displayed directly on the invoice footer.
• In the Purchasing module, the four additional tax codes are displayed on the line and can be modified.
  If the number of taxes is limited for sales, you cannot specify more than four taxes in purchasing lines.

• Description (field DTAJURNAM)

• Taxes (field DTATAXNAM)

• Tax basis (field DTABASTAX)

• Rate (field DTATAXRAT)

Use this field to specify the tax rate that can be applied to this tax.

• Tax amount (field DTAAMTTAX)

• Tax date (field DTATAXDAT)

• Country (field DTAPAYS)

• Valuation - tax (field TOTINVNOT)

• Valuation + tax (field TOTINVATI)

• Company name (field BPRNAM)

Business partner name.

• Address (field BPAADD)

• 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 used to identify a company or activity (SIRET, SIC) and whether the entry is mandatory,
• 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.

• field CRYNAM

Name of the country used in the addresses and in all the documents where the country code is entered.

• field BPAADDLIG

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

• Postal code (field POSCOD)

The postal code, whose entry format is defined in the Country table, is used to define the town/city and the geographical subdivision if it is defined for the country.
When the postal code is changed the city/town corresponding to the new code is automatically displayed. The principle is the same for the geographical subdivision if it is present for the country. 
It is also possible to manually enter the town/city name. If the town/city is already defined, the associated postal code is automatically displayed.

The control of this information and its mandatory nature depend on the setup performed in the country management. In order for the control to be applied, the POSCOD - Nonexistent postal code alert parameter (SUP chapter, INT group) must also be set to "Yes".

Specific cases:

- for ANDORRA, indicate 99130
- for MONACO, indicate 99138
- for the other overseas countries, indicate the INSEE code of the country or 99999 if not known.

• City (field CTY)

The city automatically proposed is the one associated with the postal code previously indicated. It is also possible to manually enter the name of a town/city:

• if the town/city is already defined, the associated postal code is automatically displayed, 
•  if the city does not exist and the postal code control has been set up in the Country record, a warning message is displayed but the continuation of the entry is authorized. In addition, the CTY - Nonexistent city alert parameter (SUP chapter, INT group) needs to have the value "Yes" for this control to apply.
• if the city does not exist and the postal code is not entered, a blocking message is displayed when the postal code is set up as mandatory for the country.

Notes:

• Its format is defined in the Country record setup.
• Depending on this setup, the entered town/city can automatically be converted into uppercase after it has been entered.
• In order to make selections easier without taking into account the format (accented characters/uppercase letters/lowercase letters), the selection window available on this field proposes a column dedicated to the search, where the names of the towns/cities are displayed in uppercase. The control which is carried out is case-insensitive since it is carried out with respect to the town/city name stored in uppercase.

• field ITINERAIRE

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

• field SAT

This field contains the geographical SDL TEST subdivision corresponding to definition of the postal address. For example, a 'department' for France, and a state for the United-States.

The description of the geographic subdivision, as well as the control on the information entry, are defined in theCountries setup.

This field is automatically loaded after the postal code and town/city have been entered, based on the Postal codes setup.
If the field is controlled, the control is carried out according to the Geographical subdivision table.

• Site tax ID no. (field CRN)

The SIRET number of the site associated with the invoice customer is displayed if it has been entered on the BP record.
You can only modify this number when the invoice customer is a Miscellaneous one. The entered number must be compliant with the format defined on the Country record.

• Person to contact (field CNTNAM)

Contact number.

• EU VAT no. (field EECNUMX)

• Address validation (field VALADR)

Click on this button to send the entered address to the Sage Sales Tax (SST) address validation service. It is also possible to send the entered address by clicking on the [OK] button.

• If the address is found, the "Validated" checkbox is automatically checked.
• If the address is not found, the "Validated" checkbox is unchecked and cannot be accessed.

• This field is only available when the activity code Local tax (LTA) is active.
• The validation service of SST addresses is defined in the parameters related to Sage Sales Tax.

• Validated (field ADRVAL)

This box is checked automatically if the address is processed by the validation service of Sage Sales Tax (SST) addresses when the "Address validation" box is checked. The box is not checked and cannot be accessed if the address is not found.

• This field is only available when the activity code Local tax (LTA) is active.
• The validation service of SST addresses is defined in the parameters related to Sage Sales Tax