Purchasing > Invoices > Invoices 

The purpose of this function is to check all invoices and credit memos coming from the suppliers.
After recording invoices, you can generate the corresponding accounting entries directly by clicking Validation, or program the validation for later using the corresponding function.
SEEREFERTTO See the documentation on the Invoice validation for further information.

Various elements can be managed by this option:

  • The invoices, referring to orders and/or receipts. These invoices are checked by reconciliation with:
    • receipts already entered,
    • orders not received yet,
    • orders without receipts (general purchases).
  • Additional invoices, which can be allocated to ordered products (except on subcontract orders), or to shipped, received and/or invoiced products. These invoices can only come from:
    • the supplier of the goods in the case of an additional invoicing, for instance,
    • a business partner other than the supplier of the goods, in which case the invoices must be assigned to products (e.g.: for freight charges or customs expenses).
  • Credit memos. It can be:
    • a total credit memo. This credit memo corresponds to an invoice cancellation. The stock valuation of products remains the same as the receipt valuation.
    • a partial credit memo in the event of a dispute on the invoiced price or invoiced quantity. The stock valuation is adjusted.
    • a credit memo on return related to a recorded return. For information, a credit memo on return linked to a supplier receipt always impacts the stock entry of the original receipt (and not the stock issue relative to the return).

When the Fixed assets module is managed in the folder, the invoice validation triggers, when all the conditions are met, the automatic creation of an expense for each purchase invoice line (the expense creation terms are detailed below). The Linked expenses list displays the generated expenses. After selecting an expense in this list, you directly access the expense management function.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

The layout of the entry screen depends on the setup of the chosen transaction.

If only one transaction is set up, no choice is provided. If several transactions are set up, a window displays the list of the transactions you are authorized to use

The recording of supplier invoices is subdivided into three stages:

  • The entry of the general information in the invoice header, including the invoicing elements (charges, freight, packing, discount, rebate etc.), the total excl. tax of the product lines and the total amount of taxes.
  • The entry of those lines that can be limited to a single taking into account, in full or in part, of the orders, receipts returns or invoices. You can easily select these entries in the dynamic lists of the selection panel.
    After taking this into account, the invoice lines are preloaded with the information on the concerned orders, receipts, returns or invoices. The manual creation of specific lines along with the modification or deletion of the preloaded lines are always an option.
    SEEINFOFor additional invoices, you cannot use the selection panel lists: you can either enter the lines manually or simply preload the lines from the Actions icon.
  • Final checking with discrepancy management and potential posting or putting on hold.

Header

Presentation

In this header, enter the general information of the invoice such as the invoicing site, supplier code, date, etc.

Close

 

Fields

The following fields are present on this tab :

Block number 1

Code of the invoicing site, initialized by default with the financial site associated with the operator's purchase site. This site must be an accounting site. The proposed site is modifiable and can be chosen from the list of sites authorized for the operator. This field MUST be assigned.

The invoice type is used to identify the invoice category and define different invoice categories.
For example: Invoice France and invoice export.

The invoice type is associated to a type of journal for which a counter (manual or automatic) is specified.

A control is performed in order to verify the consistency between the legislation/the group for which the specified invoice type is defined, and the legislation and group of the company of the invoicing site.
SEEREFERTTO For further information, click here.

  • Entry number (field NUM)

The order number allows the order to be identified in a unique way.
It is automatically generated at the end of the document creation according to the setups of the counter associated to the invoice type.

SEEINFO Remarks:

  • 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).
     
  • When 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 thecounter assignement table.
  • Accounting date (field ACCDAT)

This date represents the accounting date of the original transaction.
The accounting date makes it possible to determine the posting period of the accounting entries. It is initialized by default to the current date and it can be changed depending on the value of the PIHACCDAT - Accounting date modification parameter (ACH chapter, INV group).
This date is systematically controlled in order to verify that it belongs to an open and existing fiscal year.
If a problem occurs during the control, the user will need to enter a new date, irrespective of the parameter value.

This date corresponds to the date of the accounting entry. The accounting date makes it possible to determine the posting period for the accounting entries.

It is initialized by default to the current date and it is modifiable based on the value of the parameter PIHACCDAT - Accounting date modification (ACH chapter).

A checking is systematically performed on this date in order to make sure that it belongs to an existing, open fiscal year.
If a problem arises during checking, the entry of a new date is requested irrespective of the value of the parameter.

SEEINFOComments 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 theinvoice typespecified.
  • The entry of invoices, credit memos or additional invoices, can be limited, for a user, to a range of dates defined by theACHSTRDAT - Purchasing start dateandACHENDDAT - Purchasing end dateparameters, when they are entered.
  • Date modification is authorized only if the new date applies to the same accounting period. This control is performed when theFRADGI - French fiscal regulationparameter is set to 'Yes' and the period component belongs to the counter.
  • In the Distribution and A/P-A/R accounting modules, an entry which is at the origin of an invoice, a credit memo or an additional invoice cannot have a date greater than the date of this invoice, credit memo or additional invoice.
    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.
    You can use an entry point to disable this control, by defining a specific parameter:
    CTLDATORI - Document date control (TC chapter, INV group).
  • Intercompany (field BETCPY2)

 

Block number 2

This field indicates the invoicing supplier issuing the invoice.

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

  • Company name (field BPRNAM1)

This field indicates the company name of the invoicing supplier. It cannot be modified.

  • Pay approval (field PAZ)

This field is initialized by the level of the user's payment approval and it can be modified provided that it has been assigned a corresponding value at at lower level.
The modification can only take place after creation of the invoice lines.

  • Reason (field LIBPAZ)

This field contains the possible reasons for the variances that can exist between the supplier invoice and the invoice calculated by the system.

  • Original document no. (field ORIDOCNUM)

 

Close

 

Tab Management

Presentation

In this section, you can find the sales conditions displayed in the invoice header, such as the payment terms, delivery method, carrier, etc.
Most of this information is initialized by default and is modifiable.

Load and Sales accruals

The start and end fields for the service provision period are used in the accounting processing of Accruals.

These fields can be accessed in the header and their content is automatically transferred to the invoice lines if the SVC - activity code is activated.

Interactions between the header and line dates:
  • In line creation, the values entered in the header are reused.
  • In creation or modification of an invoice, if there is at least a line, a message to confirm the update is displayed:
      • when confirming the update, all service provision dates of the lines reuse the values entered in the header.
      • otherwise, only the invoice lines without dates are concerned.
  • The modification of the dates of a line does not have any impact.

If the SVC - Periodic accruals activity code is active and the SVCFLG - Accruals generation parameter (TC chapter, SVC group) is Yes, the following conditions apply:

  • In the header, you cannot modify the period start and end date fields.
  • in the line, it is possible to:
      • You can enter the values for the start and end dates, number and period type.
      • Select Period accruals from the Action icon menu and enter values in the Accruals managementscreen.

Close

 

Fields

The following fields are present on this tab :

Source

  • field BPRDAT

This field indicates the date of the supplier invoice: the date mentioned on the received invoice provided by the supplier.

  • field TYPVCR

 

  • field CLSVCR

 

  • field SCUVCR

 

  • field SEQVCR

 

  • Supplier doc no. (field BPRVCR)

This field displays the invoice number mentioned on the supplier invoice.
A check is carried out to prevent entering the same number for the same invoicing supplier several times.

This field is initialized with the paid supplier stemming form the supplier record or with the paid supplier present on the first document selected by picking.

This field indicates the currency in which the invoice prices are expressed.
The default currency is the currency of the supplier BP record. But it can be changed into the currency present on the first document selected in the invoice.

  • Rate type (field CURTYP)

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

  • Rate (field RAT1)

An exchange rate between the movement currency and the company currency can be directly entered. The values porposed are those croming from the exchange rate type and the invoice date.
To reset the rate, click Init rate from the Actions icon. The exchange rates entered are used during the posting of the invoice.

  • field RAT2

 

 

  • Original invoice (field INVNUM)

This field is only entered for credit memos. It contains the invoice number on which the credit memo automatically displayed on each line of the credit memo.

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 an order, a receipt or an invoice, the incoterm code is initialized with the incoterm code defined by default for the supplier or with the original document.

It is possible to access, by tunnel, to the management function of the incoterm. However, the choice of the incoterm can no longer be modified if a product managed with a cost structure is entered in the document.
 Concerning the case of the orders, receipts and invoices, 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.

SEEINFO The incoterm code and city/town can also be accessed via menuOptions / Customs information.

  • field ICTCTY2

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

  • SCD date (field SPACUSDAT)

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

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

It makes it possible to enter the date on which the operation is carried out through customs.

SEEINFOWhen the field can be entered, it can still be changed, even though the invoice has been validated.

  • SCD reference (field SPACUS)

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

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

It makes it possible to enter the name of the customs agency through whom the operation is carried out.

SEEINFOWhen the field can be entered, it can still be changed, even though the invoice has been validated.

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

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

It makes it possible to enter the supplier of the original invoice received by customs.

SEEINFOWhen the field can be entered, it can still be changed, even though the invoice has been validated.

  • field SPACUSNAM

 

Payment and management

Use this field to enter a project code.
The management of this code depends on the value of the CTLOPPCOD - Mandatory project control parameter (TC chapter - MIS group).

  • 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.
    You can use the Selection icon to display the list of available project codes.

The project code you enter on the document header is used to initialize the project code of the document lines and can be modified. In case of document transformation, the project code entered on the header is only used as the default values of lines with no project code. If you modify the header project code, a dialog box opens and suggests 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
  • Yes if same value: the project code is only transferred to the lines associated to the former project code.
The PJTSNGDOC - One project per document parameter (TC chapter, MIS group) does not apply in invoice management: invoices, additional invoices and credit memos are only managed in multiple-project mode. A supplier must indeed be able to issue grouped invoices related to various orders/receipts applying to different projects.

When an analytical dimension type is used in the Project management tracking, any modification of the project code on the document header leads to reinitializing the dimension code of this dimension type on the document header and on the invoicing elements, based on the Default dimensions setup. If the project code is used onto the lines, the dimension code of impacted lines is also reset.

Inter-company specificities: for inter-company invoices, the project code is not recovered from the sales invoice but from the purchase receipt or source purchase order.

  • Internal reference (field INVREF)

This field contains the internal reference of the supplier invoice. This free field is used to enter a number or an indication to identify the invoice. For instance: a counter number assigned to the invoice upon its arrival in the company.

  • Due date basis (field STRDUDDAT)

This date is used as the basis to calculate the open items. A code at supplier level is used to mention whether this date is initialized by default to the receipt date or to the invoicing date.
Should the date be initialized to the receipt date, it will only be initialized after entering the lines taking the first receipt that occurred in time.

  • 1st due date (field DUDDAT1)

It is the date of the first deadline for the invoice.

The payment conditions describe the calculation rules of the open item dates in journal entry (orders, invoices and credit memos). The calculated open items can be multiple and with multiple payment modes.
The payment conditions define:

  • the payment method,
  • a percentage of the total of the journal (when there are multiple open items),
  • an open item calculation rule in months, days, etc.,
  • a payment type (open item, pre-payment, tax deduction at source).

The date used as the calculation starting point can vary with the context (invoice date or receipt date) and it is modifiable in entry mode. It remains modifiable on entry.
The default payment conditions are attached to the BP and are modifiable in entry mode. The payment condition is initialized using the payment condition of the invoicing supplier or the payment condition entered on the first document selected.
Only a discount code consistent with the legislation and company group of the document site can be entered.
SEEREFERTTOThe general principles linked to the multi-legislation setup are detailed here.

Specificities linked to inter-companies: for an intercompany invoice generated from a sales invoices, the payment condition is intialized from the one of the sales invoice.

The discount code is used to identify a series of discount and charge rates to be applied to a payment according to a number of early or late days with respect to the due date.
The discount code is initialized using the discount code of the invoicing supplier. It can still be modified.
Only a discount code consistent with the legislation and company group of the document site can be entered.
SEEREFERTTOThe general principles linked to the multi-legislation setup are detailed here.

Specificities linked to inter-companies: for an intercompany invoice generated from a sales invoices, the payment condition is intialized from the one of the sales invoice.

This is the tax rule of the invoice. The tax rule is initialized by the tax rule of the invoicing supplier or by the tax rule entered on the first document selected.

A tax rule represents the tax territoriality principle, in other words, the calculation rules to be applied to determine the tax amount.

As a general rule, by crossing a tax rule linked to the BP with a Tax level, you can determine the tax code to be applied to the document line and so, to the entry line.

Specificities linked to inter-companies: for an intercompany invoice generated from a sales invoices, the tax codes of the purchase invoice lines are recovered from:

  • the tax rule of the purchase invoice initialized by the one of the sales invoice,
  • tax levels of the sales invoice created from the purchase invoice.

You can only enter one tax rule consistent with the legislation and group of the company at the given site.
SEEREFERTTOThe general principles linked to the multi-legislation setup are detailed here.


  • Fees declaration (field DAS2)

This field is initialized to yes if the selected supplier is a contractor.

  • Start service (field STRDATSVC)

Enter the start and end ranges of the service provision period.

SEEREFERTTO For more information on the entry and use of fields, see paragraph on the Accruals at the Purchase level.

  • End service (field ENDDATSVC)

 

  • 1099 form (field FRM1099)

The 1099 form type indicates that a supplier is reportable to the Internal Revenue Service for payments made. Possible valid values are: None. Misc, Dividend or Interest. This value defaults from the supplier to the invoice, but can be changed.

  • 1099 box (field BOX1099)

Default box number with respect to which payments must be printed on the 1099 record. Box numbers vary according the 1099 record at use. This value defaults from the supplier to the invoice, but can be changed. Inactive 1099 boxes are not available for selection.

  • Amt. subject to 1099 (field AMTSUBJ109)

Invoice amount subject to a 1099 declaration. This amount is automatically calculated based on the sum of the invoice ex-tax amounts for the detail lines having the 1099 field set to Yes.

  • VCS number (field BELVCS)

Field linked to the Belgian legislation. 
It is used to specify the VCS number on an invoice (VCS refers to transfers with structured format communication) and to facilitate bank reconciliation.

Reminder: the structured communication consists in specifying a single identifier on the invoices that will be used in all the banking exchanges.

The encoding number is made up of 12 numeric characters:

  • 10 digits (two characters defining the year + eight characters defining a sequence number),
  • 2 control digits calculated according to the check digit modulo 97 rule.

In the case of purchase invoices and supplier BP invoices, the encoding number is controlled and can be entered. It is performed:

  • If activity code KBE is abled
  • If the BELVCS parameter is set to 'Yes'
  • If the invoice does not have the pro forma type
  • If the supplier is Belgian.

SEEWARNING In case of a site modification, the display of the 'VCS number' field is reinitialized.

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

Grid Invoicing elements

This field indicates the number of the invoicing element identifying the associated amount (Charges, freight, packing, discount, etc.).
The list of the invoicing elements is drawn up by cumulating the lists of the invoicing supplier and their price list structure.
Other elements can be added to this list:

  • elements manually entered because only present on the supplier invoice,
  • elements added according to the source documents selected when the source documents contain elements that are not usually managed by the invoicing supplier.

SEEINFOOnly the elements manually added to the initial list can be deleted.

  • Invoice element (field INVDTALIB1)

This field indicates the short title of the invoicing element.

  • Amount (field INVDTAAMT1)

This field indicates the amount of the invoicing elements displayed on the suplier invoice.
These values must be manually entered to be then compared to the amount of the invoicing elements as calculated by the system.

Grid Analytical

This table is used to enter or view the dimension types, depending on the parameters of the invoice check entry transaction.

  • Description (field NAMDIE)

This field repeats the title of the dimension type.

These are the analytical dimensions initialized based on the setup of the default dimensions (PIH dimension code). These dimension codes can be modified manually if authorized by the transaction.
When an analytical dimension is used for project management tracking, any modification of the project code on the document header leads to the dimension code being reset based on the Default dimensions setup. If the project code is used onto the lines, the dimension code of impacted lines is also reset.

Amount and status

  • Invoice lines excluding tax (field TOTLINAMT1)

This field indicates the tax ex. total of the invoice lines entered using the information on the invoice provided by the supplier.
This amount is used in the final check of the invoice by comparing it to the ex-tax amount of lines as calculated by the system.

  • Tax total (field TOTTAXAMT1)

This field indicates the total amount of taxes entered using the information on the invoice provided by the supplier.
This entered amount is used in the final check of the invoice by comparing it to the tax amount as calculated by the system.

  • Invoice total including tax (field TOTATIAMT1)

The total tax-incl amount is the total amount calculated by the system using the elements from the system.

  • Invoice status (field STA)

This field indicates the status of the invoice:

  • pending (the invoice is not balanced yet),
  • to validate (the invoice is balanced),
  • validated.
  • Match status (field TWMSTA)

The Three-way match status field has the following values:

  • Unblocked: a user with unblock access can override the blocking.
  • Blocked: one or several lines are blocked (a warning may also be displayed).
  • Warning: one or several warnings, but no line is blocked.
  • Successful: matching is successful.
  • Not applicable: no matching is carried out.

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).
SEEINFOThe presence of this field depends on the entry transaction used.

Close

 

Tab Lines

Presentation

The fields to be entered depend on the entry transaction. The non-enterable fields are initialized to default values.
Invoice lines can be:

  • Preloaded automatically from a specified source document such as a receipt, shipment (only for additional invoices) or order
  • entered manually.

In both cases, the selection list for documents selection which constitutes the invoice excludes those which date is later than the invoice date.

Preloading of the lines:

The choice of the source document used for preloading lines depends on the type of invoice processed:

  • For an invoice, you can choose to preload:
    - The order lines
    - Or the receipt lines
    from the selection panel lists.
    SEEINFO The reconciliation with subcontract orders is not authorized.
  • For an additional invoice, click Additional invoice preloading from the Actions icon.You can choose to perform the preloading from:
    - existing invoice lines,
    And/or order lines, excluding subcontract lines without WO The displayed lines are only those that are not received, not invoiced and not closed.
    - and/or receipt lines.
    - and/or shipment lines.
    SEEREFERTTO For further information on the specificities of additional invoices, see Additional invoice preloading.
  • For a credit memo on an invoice or additional invoice, select the existing invoice/additional invoice lines in the Invoice selection panel.
  • For a credit memo on a return, the preloading is carried out from the return lines pending credit memos included in the Return list of the selection panel.

To filter the selection lists of documents, click Picking criteria to enter your selection criteria.

Direct entry of an invoice line:

When the user directly enters an invoice line without requesting an automatic pre-loading, they will need to enter additional information:

Origin

The source is used to stipulate the document type at the origin of the invoice line: order, receipt.
The 'miscellaneous' source is used to manage direct invoices. This can be a purchased or immediately consumed product with no link with an order or receipt. Example: a restaurant or vehicle-recovery bill.

Number

It is the original document number that can only be entered if the Source is: Miscellaneous.

Line

This field contains the number of the order, receipt or invoice line, depending on the source document. In the case of an open order line, you cannot enter this number directly: use the Action icon to select the relevant line.

Product,

The product reference can only be entered when there is no link to an existing document such as an order or a receipt. The contextual menu is used to select a product either via its internal reference or its reference at the supplier.

Quantity

When the line is pre-loaded, you can modify the invoiced quantity. An option is available to mention if:

  • it is a partial invoice,
  • The order/receipt line needs to be closed.

The New cost and Load information can be accessed in the case of an additional invoice.
For further information see above the Additional invoices preloading.

The other information such as the price, the analytical postings of the line, the purchase type etc. can also be modified depending on the transaction setup.

The Actions icon at the beginning of the line offers the following possibilities:

  • Zoom onto the original document

 

Fields

The following fields are present on this tab :

Block number 1

  • CAI number (field CAI)

 

  • CAI validity date (field DATVLYCAI)

 

Grid

  • Source (field TYPORI)

This field is used to stipulate the document type at the origin of the invoice line. In the case of a preloading, it is automatically assigned.
The various authorized values depend on the type of invoice being processed. A "Miscellaneous" origin is used to enter a line linked to no document.
This field only becomes accessible on creation of a line.
The possible values according to the invoice type are as the following:

  • Invoice: Order, Receipt and Miscellaneous,
  • Additional invoice: Order, Receipt, Invoice and Miscellaneous,
  • Credit memo: Invoice and Miscellaneous,
  • Credit memo on return: Return and Miscellaneous.
  • Number (field NUMORI)

This is the number of the original document (order, receipt, return, invoice) corresponding to the line to be invoiced.
In the case of a preloading, this field is automatically assigned.
This field only becomes accessible on creation of a line. This field can never be assigned if the origin is Miscellaneous.

  • If the invoice type is "Credit memo", this field is automatically assigned using the 'Original invoice' field of the management tab.
  • If the invoice type is "Additional invoice", the selection of an order as the original document is limited to the orders that have not been invoiced or closed, and it excludes the subcontract orders.
  • Line (field LINORI)

In this field, enter the line number of the document at the origin of the invoice line. In the case of a preloading, this number is automatically assigned.
For a open order line, you cannot enter this number directly. Click the Selection icon to select the relevant line.
This field only becomes accessible from the creation of the line.

  • Product (field ITMREF)

Help common to the Order, Invoice and Buyer plan functions.
The entry of a product reference is mandatory. This field offers several possibilities.
You can:

  • Directly enter a product reference.
    If the ITMFLG - Product/supplier ref. entry (ACH chapter, REF group) setup is active, you can enter either the internal reference of the product or the reference of the product at the supplier's.
    The existence of this reference is controlled in the Products file.
    The reference displayed is always the internal reference of the product and it must exist in the Product table, be active and of the Purchased product type. If the value of parameter BUYFLT - Filter by buyer (chapter ACH, group AUZ) is set to Yes, the product must be managed by the buyer. This filter is deactivated in invoice control.
    SEEINFOThe product code is not mandatory for a line with the type Miscellaneous.
  • Use the Actions menu to:
      • Select a product from the file.
      • Select a product from the list of supplier products.
      • Select a product from the list of supplier-site products. From this selection window, the cursor is set by default on the first product referenced by the supplier for the chosen receiving site. You can select a different product from any other site, if it belongs to the same legal company.
      • Create, according to the user's access rights, the product in the file.
  • View and take into account the responses to the existing RFQs if the transaction used allows this.
    Click the Actions after the entry of the product reference to restrict the list to requests for quotes specific to this product. If you choose one of the answers linked to a request for quote, the order line is automatically loaded and the information is initialized with the elements from the original request and the answer made by the supplier.
    The quantity ordered, the unit, the descriptions, the project code and the analytical dimensions are initialized by the request for quotes. The prices and discounts and the planned due date are initialized with the information saved in the answer made to the request for quotes by the supplier.
  • View and take into account the requirements related to the product (action not available in the invoice function). These requirements are expressed through purchase requests and suggestions created by the MRP calculation or the reordering schedules.
    In the Buyer plan function, you can display the requirement consideration window, even if the product reference is not entered. In all cases, all requirement types matching the selection are displayed, for all types of products. After selecting the lines and validating, the lines are automatically generated and display the proper product type, based on the origin of the requirement.
    In the Orders and Buyer plan functions, depending on the entry transaction used, the requirement consideration window can also open automatically. This window is displayed after entering the product reference, or if the product is of the Service category, after selecting the Product type (service or subcontract), when modifications are available.

The entry of the product is used to initialize the Description fields that can be modified.
After entering the product, the following messages may display:

  • When the product does not exist on the selected receiving site.
    This message allows you to create the site, depending on your user authorizations.
  • When the product is not referenced by the supplier.
    This message can be blocking or a simple warning according to the choice made at the level of the ITMBPS - Supplier referencing (ACH chapter, REF group) general parameter.
  • When the (receiving) product-site is not referenced by this supplier.
    This message can be blocking or constitute a simple warning according to the choice made at the level of the ITMBPSFCY - Supplier-site referencing (ACH chapter, REF group) general parameter.
    This control does not apply to inter-site orders.
  • When the product is blocked for the supplier, or for the supplier on the receiving site.
    This can be a blocking message or a simple warning according to the value of the blocking code in the Product-Supplier or Product-Site record.
  • The entered product is already subject to an open order.
    This message is a simple warning.
  • The product cannot be directly ordered but must previously have been the object of a purchase request.
    This message is blocking.

For products managed in stock, it is possible to take into account the suggestions coming from the MRP calculation or those from the statistical reordering calculations as well as the purchase requests.

For products not managed in stock, only potential purchase requests can be taken into account.

In the case of subcontract products, the subcontract orders generated by manufacturing releases are the ones to suggest what purchase to perform. To order a subcontract product, requirements must exist. Otherwise, an error message will display upon entering the product reference.

SEEINFOThe work order can be accessed from the Actions menu on the product line. This order line must apply to a sub-contract product.

Requirement selection

When entering an order and depending on the entry transaction used, if there are purchase suggestions, subcontract orders or purchase requests for the entered product, a window can automatically open to suggest that requirements be taken into account. This window is displayed after entering the product reference, or if the product is of the 'Service' category, after selecting the Product type (service or subcontract), when modifications are available.

Notes:

  • If the selected product type is 'Subcontract', the requirement consideration window opens regardless of the setup used in the entry transaction. In fact, the creation of an order line for a subcontract product can only be made by consuming subcontract requirements.
  • If the supplier is blocked at the Product-sitelevel, the receiving site field is emptied and the requirement consideration window still opens.

If you do not want to take into account the requirements, simply cancel this window to return to the line entry (except for sub-contract products where the selection of the requirement is mandatory).

If you want to take requirements into account, select them in the corresponding window. This window shows the supplier code and name and the product code concerned along with its standard description.


To view the requirements on all sites, including the sites where the product-supplier is blocked, select the All sites check box. Otherwise, leave the check box cleared or only the requirements of the receiving site will be displayed. If the receiving site is empty as a consequence of the supplier being blocked on the Product-site record, the requirements of the default receiving site are displayed.

Likewise, you can adjust the display of the requirement lines according to the criterion of back-to-back orders.

A date can also be entered to limit the proposition in time. This date will be applied by default to the requirement end date, but it can be applied to the requirement start date according to the Requirement selection section. If no date is specified, all suggestions, purchase requests or subcontract orders are suggested.

Click Criteria to enter sorting criteria and additional selection criteria, including the entry of ranges related to the project code, the document or the original document, and a filter on the suggestion type.

You must then enter the unit in which the requirements quantities must be expressed. By default, the stock unit is suggested but it can be modified if it was picked in one of the following units: Purchase Unit, Packing unit, Stock unit of the product. Requirement lines are then displayed with, for each one:

  • The start and end dates of the requirement, the site and the buyer code.
  • The requirement quantity as well as the considered quantity.
  • The quantity taken into account. This quantity can be initialized by default in two different ways:
    • by the requirement quantity when no supplier is assigned to the requirement or when the supplier specified in the requirement line is identical to the supplier in the order,
    • to zero when the supplier specified in the requirement line is different from the supplier in the order.
  • The 'Blocking' status being mentioned against the product-site-supplier.
    • If the line is blocked, the Blocking field is set to 'Yes'. The line cannot be entered and cannot be considered.
    • If the line is linked to a warning, the Blocking field is set to 'No'. The quantity is initialized to zero but you can still enter a quantity. You can only select this line manually. You cannot use the Include all action.
  • The Exclude all and Include all actions apply to all requirement lines, except from blocked lines and lines with a warning. They make it possible to reset the selected quantity to zero or to preload it. If there is a minimum quantity in the product-supplier record for the considered product, this quantity is suggested for the selected quantity, even if it is greater than the requirement quantity. A blocking message prohibits the entry of a quantity inferior to this minimum quantity.
  • Various information such as the weight and volume for the considered quantities, the purchase request line and number (if the requirement is related to a purchase request), the supplier, the order type and number in the WIP and the requirement origin (MRP, MPS, Purchasing or Manufacturing).
  • The supplier (or back-to-back supplier) is set to the default supplier (or default back-to-back supplier) defined on the Product-site record or Product-supplier record> (for more information on the supplier initialization rules, please refer to the documentation on the Product record).
  • If you modify the receiving site, a message is displayed suggesting that you search for the new default supplier (or default back-to-back supplier) for this product-site.
  • If the product is not referenced by the supplier, a blocking or warning message can be displayed based on the value of the ITMBPS - Supplier referencing parameter (ACH chapter, REF group).
  • If the (receiving) product-site is not referenced by the supplier, a blocking or warning message can be displayed based on the value of the ITMBPSFCY - Supplier-site referencing general parameter (ACH chapter, REF group). If this message is blocking, you can still proceed with your entry but the Receiving site field must be set as available for entry for the entry transaction. In this case, the Receiving site field is emptied. You must then enter a site where the product-supplier is referenced, or for which the ITMBPSFCY - Supplier-site referencingparameter is not defined as blocking.

After entering the unit, you can automatically enter the quantity to be taken into account, which is the only information that can be entered on this screen. If you want to sort the suggested list by requirement start date (default sort), by requirement end date or by site, you have to exit the entry mode and use the Actions icon to choose the required sort. At this stage, if the requirement line is taken from a purchase request, you can also tunnel access the purchase request for inquiry.

The suggested quantity taken into account can be modified on the condition that the quantity entered is less than or equal to the requirement quantity, which can be the case if, for instance, you wish to take into account only part of the requirement. If you wish to exclude requirement lines, enter a null quantity. Click the Actions icon to select the total requirement quantity.

For subcontract products, always enter the required quantity in the screen dedicated to the taking into account of requirements. In fact, the creation of an order line for a subcontract product can only be made by consuming subcontract requirements. It remains possible to order a quantity greater than the requirement expressed by the manufacturing service. To do so, modify the ordered quantity once the order line has been generated.

For products managed by direct back-to-back order, the quantity cannot be modified.

Purchase back-to-back orders are prohibited when the PURCTLPRI0 - Purchase price existence control parameter (ACH chapter, PRI group) is set to 'Control' and the product has no price:

    • the system has not found a purchase price list for the back-to-back order supplier,
    • no purchase base price is entered on the product record,
    • the product has no standard cost, or the PURPRICE - Price by default standard cost parameter (ACH chapter, PRI group) is set to 'No'.

Once this process is complete, if when entering the product, you have previously selected an invitation to tender response, an additional check is carried out and a warning message appears when the total requirement quantity is less than that mentioned in the response. You can cancel or proceed with your entry. In addition, another message allows you to decide if the order lines must be valued or not at the price entered in the request for quote response.

After validation, requirement lines taken into account are then sorted by product, by site, by supplier, and by project code and then lines are grouped by site, by analytical dimension, by project code and by description for generic products. Subcontract requirements are never grouped.

By using an entry point, it is possible to modify the grouping of the these orders (see the entry point ECLBESOINS).

For order lines generated from a requirement linked to a purchase request, after creating the order line, click the Actions icon to view all purchase request lines that have not be consumed. An inquiry screen appears and by tunnel it is possible to access each of the associated purchase requests.

When the requirements taken into account in an order line concern more than one purchase request, it will not be possible to reduce the order line quantity (however it can be increased). When the requirements concern a single purchase request and the quantity is reduced, this reduction will update the WIP quantity in the purchase request and the order, as well as the consumption information in the purchase request. It will also update the precommitments if necessary.

Inter-company specificities:

Inter-site orders:

You can only enter products of the Received / Deliverable type.

Inter-company orders:

You cannot enter a product of the Received / Not deliverable type.

For the same inter-company purchase order, the product of the first entered line determines the category of the generated sales order. A control is applied to the type of each product that you add so consistency is ensured at the level of the sales order category.

    • If the first product is Received / Deliverable or Non received / Non deliverable, the category of the generated sales order is 'Normal'. You can only add products:
      • of the Received / Deliverable type. These product lines use the Delivery/Sales invoice flow.
      • of the Not received / Not deliverable type. These product lines are invoiced using the invoicing schedule.
    • If the first product is Not received / Deliverable, the category of the generated sales order is 'Direct invoicing'. All lines are directly invoiced with no delivery. You can only add products:
      • of the Not received / Deliverable type,
      • of the Not received / Not deliverable type.

When creating a purchase order, even if you delete the product on the first line, the sales order category defined is kept as long as the table contains at least one line. In order to reinitialize the sales order and its category, you must delete all the entered lines.

When modifying a purchase order, if the sales order has already been generated, its category can never be modified, even if you delete all the purchase order lines. You can only enter products of a type compatible with the initial category. However, if the sales order has not been generated yet (e.g. if the signature management is active and the purchase order has not been signed yet), you can delete all the lines, enter a product line of any other type and finally modify the category of the sales order to generated, if needed.

The subcontract products are not allowed for this type of orders.

  • Description (field ITMDES)

This is the description translated into the supplier's language. When the order stems from an other document, the standard description is inherited from the source line.
This description will be printed on the invoice document.
SEEINFOThe 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.

  • Product type (field ITMKND)

You cannot enter the product type:

  • When picking documents, the product type is derived from this document: Standard, Serviceor subcontracting.
  • In direct invoicing, you cannot select the Sub-contracting product type. The product must be of the Standard or Service type.
  • When entering an additional invoice, the product type is derived from the source document line or from the product selected in picking, except if you entered the product before picking. In the latter case, all lines keep the same type as the one of the specified product.

Inter-company specificities: in the case of an inter-company invoice, the product type is derived from the source purchase document if this type specified. Otherwise, it is automatically determined as a Standard type or Service type, based on the given product.


The presence of this field depends on the entry transaction used.

This is the invoicing unit. This unit is fed by the supplier purchase unit or by the purchase unit of the original document.

  • Invoiced qty. (field QTYUOM)

This is the invoiced quantity expressed by default in purchase unit. The initialization value of this quantity depends on the PIHQTYAQR - Invoiceable quantity parameter (ACH chapter, INV group).
If the entered quantity is less than the quantity remaining to invoice, a window is displayed to specify whether the line must be subject to a partial invoicing.
If the entered quantity is greater than the remaining quantity, a warning message is displayed.
When picking receipt lines, completely returned lines which cannot be invoiced (the invoiced quantity is empty) are not displayed by default. These lines can be displayed by affecting the value Yes to the PIHQTYRET - Returned quantity invoicing parameter (ACH chapter, INV group).

  • Net price (field NETPRI)

This is the unitary net price for the receipt line calculated from the gross price affected by any discounts and charges. This information cannot be accessed.
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

If the entered price is null, a message appears to request confirmation. However, this message is not displayed for the components of a BOM, for free items and for deliveries not to be invoiced.

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 ‘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 save 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.

When there is a difference between the receipt cost and the invoice cost (if the invoice line comes from a receipt line) and if the invoice setup PIHCPR- Price adjustment has "With approximation coefficient" as value, the value that can be impacted on the stocks (if the management of the adjustments of the entry stock value) will be determined by impacting the net amount of the invoice line by the landed costs calculated in the receipt line.

  • Line amt. - tax (field AMTNOTLIN)

This field indicates the line ex-tax amount: if a quantity has been entered on the line, this field is the result of the multiplication of the net price per unit by the quantity.
This total can be modified to correct, for example, rounding variances. After modification, the unit price is adjusted if a quantity is entered.
A purely financial line without quantity can effectively be entered and in that case only the ex-tax amount of the line can be accessed.

This is the currency in which the amounts displayed in the previous columns are expressed. This information cannot be accessed.
When the invoice comes from an order line or a receipt line, the currency code inherits the currency code from the original document.
In the case of a direct invoicing line, the currency is loaded with the currency of the invoice header and corresponds to the currency of the supplier.

  • Landed cost coef. (field CPRCOE)

The management of landed costs makes it possible to quantify the routing costs of the goods ordered from a supplier and to allocate them to the products upon order, receipt or invoice. These costs are used for the calculation of the purchase cost and stock cost.
The evaluation of these costs can be performed according to one of the two following methods:

  • global method in which a Landed cost coefficient is applied and/or a Fixed cost per unit is taken into account,
  • method in which a set of costs detailed in a cost structure is taken into account.

Only one method can be used, the choice of this method is performed at the level of the product management.

This field is used to impact the net amount of the invoice line by including costs that have been previously estimated. The presence of this field depends on the entry transaction used.

The taking into account of landed costs in the invoice is however subject to parameter PIHCPR - Invoice price adjustment:

  • If this parameter is set to Without landed costs, the landed cost coefficient is automatically loaded with the value 1 in the case of an invoicing performed via the selection of an order or a receipt.
  • If this parameter is set to With landed costs, the landed cost coefficient is loaded with the value of the landed cost coefficient of the document originating the invoice in the case of an invoicing performed via the selection of an order or a receipt.

This information can never be modified.
To display this calculated landed costs amount, click Line cost from the Actions icon available on the line. This amount is presented on the Cost detail tab on the Undetailed costs table.

SEEINFONo landed cost coefficient is applied to additional invoices and credit memos.

  • Fixed cost per unit (field CPRAMT)

The management of landed costs makes it possible to quantify the routing costs of the goods ordered from a supplier and to allocate them to the products upon order, receipt or invoice. These costs are used for the calculation of the purchase cost and stock cost.
The evaluation of these costs can be performed according to one of the two following methods:

  • global method in which a Landed cost coefficient is applied and/or a Fixed cost per unit is taken into account,
  • method in which a set of costs detailed in a cost structure is taken into account.

Only one method can be used, the choice of this method is performed at the level of the product management.

The presence of this field depends on the entry transaction used. When it is displayed, this value is expressed in the company currency. It can never be modified.

The taking into account of landed costs in the invoice is however subject to parameter PIHCPR - Invoice price adjustment:

  • If this parameter is set to Without landed costs, the fixed cost per unit is automatically loaded with the value 0 in the case of an invoicing performed via the selection of an order or a receipt.
  • If this parameter is set to With landed costs, the fixed cost per unit is loaded with the value of the fixed cost per unit of the document originating the invoice in the case of an invoicing performed via the selection of an order or a receipt.

To display this calculated landed costs amount, click Line cost from the Actions icon available on the line. This amount is presented on the Cost detail tab on the Undetailed costs table.

  • Cost structure (field STCNUM)

The management of landed costs makes it possible to quantify the routing costs of the goods ordered from a supplier and to allocate them to the products upon order, receipt or invoice. These costs are used for the calculation of the purchase cost and stock cost.
The evaluation of these costs can be performed according to one of the two following methods:

  • global method in which a Landed cost coefficient is applied and/or a Fixed cost per unit is taken into account,
  • method in which a set of costs detailed in a cost structure is taken into account.

Only one method can be used, the choice of this method is performed at the level of the product management.

A cost structure details all the costs that are considered as fixed costs and can be identified at the time of the purchase. These costs are expressed in the currency of the company.
The presence of this field depends on the entry transaction used but the value it contains can never be modified.
To display the costs considered in the cost structure, click Line cost from the Actions icon available on the line. The costs are presented on the Cost detail tab on the Direct costs table.

SEEINFONo cost structure is applied to additional invoices and credit memos.

  • Purchase cost per unit (field CSTPUR)

This information, which cannot be modified, is displayed if the transaction authorizes it.

The purchase cost per unit, which cannot be modified, is expressed in the company currency. It is equal to the result of the following calculation:

Line purchase cost / Quantity (in STK)

SEEWARNING This amount is never calculated during the entry process but only when saving the document.

  • Purchase cost (field LINCSTPUR)

The purchase cost corresponds to the amount totaling the stock cost and the costs that remain payable by the buyer and are not used for stock valuation (transportation cost, non-deductible taxes, etc.).
It cannot be modified and is displayed only if the transaction authorizes it. It is expressed in the currency of the company.

SEEWARNING This amount is never calculated during the entry process but only when saving the invoice.
Its calculation method varies according to whether or not the landed costs are taken into account (parameter PIHCPR - Invoice price adjustment, chapter ACH, group INV).

Parameter PIHCPR is set to:'With landed costs':

  • Upon direct invoicing, the calculation mode of the purchase cost varies according to the method used to evaluate the landed costs. The calculation mode is the following:
     
      • Global method in which a Landed cost coefficient is applied and/or a Fixed cost per unit is taken into account:
        Purchase cost =
        [ Total of the line net price (line amount -tax) * Landed cost coefficient ]
        + total of the line fixed cost (fixed cost per unit * quantity in PUR)
        + total of the line invoicing elements
        + total of the line non-deductible taxes.
      • Method in which a set of costs detailed in a cost structure is taken into account:

        Purchase cost =
        Total of the line net price (line amount -tax)
        + total of the line product costs (originating from the cost structure)
        + total of the line invoicing elements
        + total of the line non-deductible taxes.
         
  • When the invoicing is performed by selecting a receipt or an order, the purchase cost is loaded with the stock cost per unit of the document originating the invoice provided the information related to the price and quantity is not modified.

Parameter PIHCPR is set to:'Without landed costs'

  • Upon direct invoicing, its calculation mode is the following:
    Total of the line net price (line amount -tax) 
    + total of the line invoicing elements
    + total of the line non-deductible taxes.
  • When the invoicing is performed by selecting a receipt or an order, it is not loaded with the purchase cost of the document originating the invoice; instead, it is recalculated without taking into account the landed costs of the original document.

SEEREFERTTO The non-deductible tax amount is displayed in the window entitled Line cost available on the Actionsicon.

SEEINFONo purchase cost is calculated in the case of additional invoices and credit memos.

  • Stock cost per unit (field CPR)

This is the stock cost per unit of the product, expressed in the currency of the company.
It can also be viewed in the stock detail window. 

Its calculation method varies according to whether or not the landed costs are taken into account (parameter PIHCPR - Invoice price adjustment, chapter ACH, group INV).

Parameter PIHCPR is set to: "With landed costs" :

  • Upon direct invoicing, its calculation mode varies according to the method used to evaluate the landed costs. The calculation mode is the following: 
      • Global method in which a Landed cost coefficient is applied and/or a Fixed cost per unit is taken into account:

        (Net price * Landed cost coefficient) + fixed cost per unit (expressed in PUR and converted into STK) + valued invoicing elements (for one stock unit) + non-deductible tax (if parameter NODVATSTO - Non-deductible taxes in stock is set to "Yes") for one stock unit.

        This result is converted into the currency of the company using the exchange rate type specified in tab "Management".
         
      • Method in which a set of costs detailed in a cost structure is taken into account:
  • When the invoicing is performed by selecting a receipt or an order, it is loaded with the stock cost per unit of the document originating the invoice.

Parameter PIHCPR is set to: "Without landed costs" :

  • Upon direct invoicing, its calculation mode is the following:
    Net price + valued invoicing elements
    This result is converted into the currency of the company using the exchange rate type specified in tab "Management".
     
  • When the invoicing is performed by selecting a receipt or an order, it is not loaded with the stock cost per unit of the document originating the invoice; instead, it is recalculated without taking into account the landed costs of the original document.

SEEWARNINGComments:

  • This amount is never calculated during the entry process but only when saving the document.
  •  No stock cost per unit is calculated for the lines originating from a return or a credit memo.

  • Stock cost (field LINAMTCPR)

This field, which cannot be modified, is displayed if the transaction authorizes it.
It displays the amount of the costs used for stock valuation, expressed in the company currency.

SEEWARNINGNotes :

  • When the order has the inter-site type, the stock cost calculation does not include the line amount, nor the non-deductible taxes. The invoicing elements are taken into account only if the BETFCYCST - Integration of invoicing elements parameter (ACH chapter, COS group) is set to 'Yes'.
  • This amount is never calculated during entry but only when saving the document.
  • Its calculation mode varies according to the method used to value the landed costs:

    • Global method where a Landed cost coefficient is applied and/or a method where a Fixed cost per unit is applied:

      Line amount -tax * Landed cost coefficient
      + fixed cost per unit (expressed in PUR and converted into STK) * quantity in PUR
      + total of the valued invoicing elements of the line (the elements taken into account are only the ones with the Stock valuation flag set to: 'Yes')
      + total of the non-deductible taxes of the line (if parameter NODVATSTO - Non-deductible taxes in stock is set to ‘Yes’).

      This result is converted into the currency of the company using the exchange rate type specified the Management section.

      Example for the calculation of the Stock cost of the line (without invoicing elements):

      - Hypothesis: the company currency and the document currency are identical (€).

      - Net price: €10/box
      - Landed cost coefficient: 1.3
      - Fixed cost per unit: €20
      - 1 box = 15 STK
      - Non-deductible tax: 16.9 % but the NODVATSTO parameter - Non-deductible taxes in stock is set to "No".

      --> For an order of 1 box:
      Stock cost = (10 * 1.3 ) + 20  = €33
      The stock cost per unit is the following: €33 /15 STK = €2.20

      --> For an order of 5 boxes:
      Stock cost = [(10 * 5) * 1.3 ] + (20 * 5)  = €165
      The stock cost per unit is the following: €165 / 75 STK = €2.20


      Example for the calculation of the stock cost of the line (with invoicing elements):

      - Hypothesis: the company currency and the document currency are identical (€).

      - Net price: €10/box
      - Landed cost coefficient: 1.3
      - Fixed cost per unit: €20
      - 1 box = 15 STK
      - Valued invoicing element (transportation): €10
      - Non-valued invoicing element (unloading): €7
      - Non-deductible tax: 16.9 % but the NODVATSTO parameter - Non-deductible taxes in stock is set to "No".

      --> For an order of 5 boxes:
      Stock cost = [(10 * 5) * 1.3 ] + (20 * 5) + 10 = €175
      The stock cost per unit is €70 / 75 STK = €2.33


      Example for the calculation of the stock cost of the line (with invoicing elements):

      - Hypothesis: the company currency and the document currency are different.

      Company currency: $
      Document currency: €    - Conversion: €1 = $1.40

      - Net price (in document currency): €10/box, converted into company currency --> $14/box
      - Landed cost coefficient: 1.3
      - Fixed cost per unit (in the currency specified in the Product record): $30
      - 1 box = 15 STK
      - Valued invoicing elements (transportation) (in document currency): €15, converted into company currency --> $21
      - Non-deductible tax: 16.9 % but the NODVATSTO parameter - Non-deductible taxes in stock is set to "No".

      --> For an order of 1 box:
      Stock cost = (14 * 1.3) + 30 + 21 = $69.20
      The stock cost per unit is the following: $69.20 / 15 STK = $4.61

    • Method in which a set of costs detailed in a cost structure is taken into account:

      Line amount -tax
      + costs of the cost structure
      + total of the valued invoicing elements of the line (the elements considered are only the ones with the "Stock valuation" flag set to: "Yes").
      + total of the non-deductible taxes (if the NODVATSTO parameter - Non-deductible taxes in stock is set to ‘Yes’)

      Example for the calculation of the stock cost of the line:

      - Hypothesis:
      - the company currency and the document currency are identical (€)
      - Incoterm Ex-Works (all the costs are paid by the buyer)

      - Net price: €10/box
      - Valued direct costs: 20 % of the net price
      - Non-valued direct costs (calculation mode: unit price per box): €20 per box
      - 1 box = 15 STK
      - Valued invoicing element (transportation): €10
      - Non-valued invoicing element (unloading): €7
      - Non-deductible tax: 16.9 % but the NODVATSTO parameter - Non-deductible taxes in stock is set to "No".

      --> For an order of 5 boxes:
      Line amount -tax: 5 boxes * €10 = €50
      + Valued costs of the cost structure: €50 * 20 % = €10
      + Total of the valued invoicing elements: €10

      Stock cost = 50 + 10 + 10 = €70
      The stock cost per unit is the following: €70 / 75 STK = €0.933

    This is the currency in which the stock is valued (accounting currency of the company). The stock cost per unit and the order unit price are expressed in this currency.
    SEEINFOThis information cannot be modified.

    • 1099 (field FLG1099)

    The 1099 flag is used to indicate whether a line is submitted to a 1099 declaration. If the supplier must be subjected to a 1099 declaration, the default value of this line will then be positioned to Yes. If a line for this supplier is not subject to 1099, then this flag can be changed to No and the line will not be included in reportable 1099 amount.

    The project code of the document line is initialized with the header code and in case of document transformation, with the code of the selected document lines. The following lines can have a different project code.
    You can only modify the project code of lines if entering this field is authorized by the chosen entry transaction.

    If you modify the header project code, a dialog box opens and suggests 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
    • Yes if same value: the project code is only transferred to the lines associated to the former project code.

    In modification mode, the management of this code depends on the value of the CTLOPPCOD - Mandatory project control parameter (TC chapter - MIS group).

    • 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.
      You can use the Selection icon to display the list of available project codes.

    The PJTSNGDOC - One project per document parameter (TC chapter, MIS group) does not apply in invoice management: invoices, additional invoices and credit memos are onl managed in multiple-project mode. A supplier must indeed be able to issue grouped invoices related to various orders/receipts applying to different projects.

    When an analytical dimension type is used for the Project management tracking, then any modification of the project code made at header level will be redistributed to the lines; if the modification applies to a document line, then the dimension code of the dimension type will be reset. This reinitialization is compliant with the Default dimensions setup.

    Inter-company specificities: for inter-company invoices, the project code is not recovered from the sales invoice line but from the purchase receipt line or from the line of the source purchase order.


    These fields indicate the purchase accounting accounts. The charts of accounts that can be accessed depend on the account core model associated with the company of the movement. If these fields are not entered the account will be automatically determined by the accounting code for the product according to the setups for the automatic journal.
    SEEINFO The presence of this field depends on the entry transaction used.
    These accounts are loaded by default according to the accounts displayed on the document line from which the invoice line is originated.
    SEEWARNING When no product code is displayed on the line the main account must be entered.

    When entering a direct invoice with a line of Miscellaneous type and without product code, the account is initialized by the purchase account of the supplier.
    The tax code and the purchase type are initialized in that case, according to the information of the account used (account of the main general ledger).

    • Type (field LINPURTYP)

    The presence of this information depends on the transaction setup.
    The purchase types are Purchase, Fixed assets and Service. When the invoice line originates from a document line, the purchase type is inherited from this document line.
    In the case of a miscellaneous invoice line, the purchase type will be initialized as a function of the posting of the tax associated with the general account entered.
    If the invoice line is the object of a credit memo, the purchase type will be displayed on the credit memo line.

    This is the allocation processing key for the invoice line.
    It can be directly entered on the line. When it is the case, the analytical dimensions possibly entered are deleted.

    When entering an invoice line, the analytical dimension are initialized based on the setup of default dimensions (PID code). These dimension codes can be modified manually if authorized by the transaction.

    If the invoice line originates from a document line, the analytical dimension types are loaded by the analytical dimensions on the source document.

    If analytical dimension types are not specified on the source document, an attempt to initialize these analytical dimension types is made according to the Default dimension code.
    When an analytical dimension is used for project management tracking, any modification of the project code on the document line leads to the dimension code being reset based on the Default dimensions setup.

    In the case of an inter-site or inter-company invoicing, analytical dimension types can also inherit from the sales invoice dimension types, based on the default dimensioncode on the invoice line (PID).

    This field is used to enter a first tax code to apply to the invoiced product.
    The tax codes (VAT, additional taxes, special taxes and/or provincial taxes) can be modified on the order line if the transaction authorizes it.
    Only the tax codes in phase with the legislation and the group of the site company can be entered.
    SEEREFERTTOThe general principles linked to the multi-legislation setup are detailed here.
    They are normally initialized according to the tax determination rules that most often stem from crossing the supplier tax rule with the tax levels of the entered product.
    If the return line has a document line as its origin, the tax codes will then be inherited from the document line.
    If the invoice line has a sales invoice as its origin, the various tax codes will be revaluated according to the context and will be inherited from the original purchase document.
    Upon transforming an invoice line into a credit memo line, the tax codes entered on the invoice line are transferred to this document. The right click is used to select a tax code for each tax level.

    This field is used to enter a second tax code to apply to the product ordered on the line. This concerns additional or special taxes.

    This field is used to enter a third tax code to apply to the product ordered on the line. This concerns additional or special taxes.

    This field is used to indicate the receipt tax to apply to the product.
    This tax stems from the tax determination parameters or is entered manually.
    SEEINFO Theactivity code linked to the provincial taxes must be activated beforehand.

    This field is used to indicate the issue tax to apply to the product.
    This tax stems from the tax determination parameters or is entered manually.
    SEEINFO Theactivity code linked to the provincial taxes must be activated beforehand.

    This field is used to indicate an additional tax to apply to the product.
    This tax stems from the tax determination parameters or is entered manually.
    SEEINFO Theactivity code linked to the provincial taxes must be activated beforehand.

    This field is used to indicate an additional tax to apply to the product.
    This tax stems from the tax determination parameters or is entered manually.
    SEEINFO Theactivity code linked to the provincial taxes must be activated beforehand.

    • Start service (field STRDAT)

    Enter the start and end ranges of the service provision period.

    SEEREFERTTO For more information on the entry and use of fields, see paragraph on the Accruals at the Purchase level.

    • End service (field ENDDAT)

     

    • Period number (field PERNBR)

    Enter the frequency(number of days, weeks, decades or months).

    • Period type (field PERTYP)

     

    • Quantity difference (field DIFQTY)

    This information indicates if there is a quantity variance between the entered invoice line coming from the supplier and the source document line.

    • Price difference (field DIFPRI)

    This information indicates if there is a price variance between the entered invoice line coming from the supplier and the source document line.

    This field displays the tolerance code of the order line. This field is loaded in the following way:

    • the program searches if a tolerance code is specified in the product/supplier record,
    • if no value is found by the program, a search is performed at the level of the product record,
    • finally, the control is carried out at the level of the supplier record,
    • if no code has been specified: no tolerance code is applied to the line.

    Field management (depends on the entry transaction setup)
    • If the entry transaction authorizes the entry of the tolerance code, the code can be modified as long as the order has not been closed.
    • If the entry transaction authorizes the display of the tolerance code, a default code is assigned and cannot be modified.
    • If the entry transaction does not authorize the display of the column, the default code is invisible.

    SEEINFO A tolerance code can be assigned by default whatever the purchase order type (back-to-back, manual or planning workbench).

    • Match status (field TWMSTAL)

     

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

    • New cost (field CSTMAJLIN)

    This field, subject to an entry transaction, is used only for:

    • Additional invoices.
      This field is set to Yes by default. The value of this field can also correspond to the value entered during the invoice line preloading.
      • Yes: the amount is considered as an additional cost in the calculation of the actual purchase cost of the various document lines (order and receipt) and in the stock valuation.
      • No: the amount corresponds to an update of the selected cost that is contained in the cost structure of the original documents.
    The value of this field on the additional invoice line also impacts the invoicing elements distributed on the lines:
    • If this field is set to Yes on the additional invoice line and the invoicing element is set to be valued in stock, then the invoice element amount is considered in the stock valuation.
    • If this field is set to No on the additional invoice line, then the invoicing element amount is not considered in the stock valuation, even if this invoicing element is set to be valued in stock.
    • Invoicing elements which are set up as not valued in stock are never considered in the stock valuation, regardless of the New cost field value on the additional invoice line.
    • Credit memos on additional invoices.
      This field recalls the setup used on the additional invoice.

    This field is displayed only for:

    • Additional invoices;
      It is specified if the invoice does not represent a "New cost" but a cost contained in the cost structure of the original document. By default, it is the cost entered during the creation of the additional invoice, but it can be modified.
    • Credit memos on additional invoices.
      It retrieves the cost specified in the additional invoice.

    Amount

    • Invoice lines excluding tax (field CUMLINAMT1)

    This is the total ex-tax amount for the invoice lines expressed in the invoice currency.

    Block number 4

     

    Action icon

    Line cost

    Click this action to display the detail of the valuation and cost elements for an invoice line. The information displayed by this action is the result of a calculation. Consequently, this action can only be accessed if the information of the invoice line has been previously saved.

    • The header displays the origin of the invoice line, the product code, the quantity as well as the gross price and the net price.
    • The Detail valuation section displays:
        • The discounts and charges applied to the invoice line
        • The various invoicing elements of the invoice distributed on the line. The total amount is displayed at the Cost detail section level.
        • The tax bases used to calculate the line taxes and tax details, with the deductible and non-deductible portions.
    • The Cost detail section displays the stock cost and purchase cost, with all the elements considered in the calculation of these costs, for instance:

      • The invoicing element total (the detail is displayed in the Detail valuation section, in the Undetailed cost table).
      • The total amount of the non-deductible tax (the detail is displayed in the Detail valuation section). This amount impacts the calculation of the purchase cost. According to the value of the NODVATSTO - Non-deductible taxes in stock parameter (chapter ACH, group VAT), this amount can also impact the stock cost amount.
      • The details on the method selected to calculate the landed costs applied to the product:
        - Either the landed cost coefficient and/or the fixed cost per unit, when the global method is used. The landed cost amount calculated from this information is displayed in the Undetailed cost table.
        - Or a cost structure reference. In this case, the list of costs included in the cost structure is displayed in the Direct cost table.
      • The Direct cost grid is used only when the landed costs are calculated from a cost structure. It contains the list of costs that make up the cost structure and specifies, for each cost, if the amount is considered or not in the stock cost calculation.
      • The Undetailed cost table contains, when applicable, the costs calculated from:

        - The landed cost amount when the costs are evaluated from a coefficient and/or a fixed cost per unit. This amount is always considered in the stock cost calculation.

        - The invoicing elements of the invoice, for which a distribution on the lines is defined in the setup. The setup of these costs determine if they are included in the stock cost calculation.

        - The additional invoices impacting the invoice in progress, either:
        -- > directly: additional invoices of the invoice line,
        -- > or indirectly: for example, the additional invoices of the order lines linked to the invoice line in the event of an order invoicing (based on the pro rata of the invoiced quantity with respect to the ordered quantity), the additional invoices of the receipt lines linked to the invoice line in the event of a receipt invoicing (based on the pro rata of the invoiced quantity with respect to the received quantity), etc.
        These are the additional invoices that meet the two following conditions: they are validated and considered in the calculation of the actual purchase cost (New cost flag is activated for these additional invoices).

      SEEINFOUnlike the header fields and the fields of the Detail valuation section, which are displayed in the currency of the document only, you can choose to display the fields of the Cost detail section in the currency of the document or in the currency of the company.
      In the event of an order or a receipt being only partially invoiced, the Stock cost and Purchase cost amounts are calculated based on the pro rata of the quantity actually invoiced, from the Stock cost total and Purchase cost total amounts of the order or the receipt, respectively.

    SEEREFERTTO For more details about the calculations, please refer to the following field helps:

    Affichage qtés facturation
    Text

    Click this action to enter text in the invoice line.

    Préchargement fact.complément.

    This function can be accessed for additional invoices only. It opens a window to preload lines by picking in the selection panels,of, either:

      • - existing invoice lines,
      • And/or order lines, excluding subcontract lines without WO The displayed lines are only those that are not received, not invoiced and not closed.
      • and/or shipment lines
      • and/or receipt lines.

    To complete the preloading:

    • Select the lines.
      To filter the selection lists of documents, click Picking criteria to enter your selection criteria.
    • Enter the amount.
    • Specify the distribution pro rata type. When saving the invoice, the entered amount is automatically distributed onto all the lines, based on the selected pro rata type.

      When the selected lines originate from documents that contain lines related to a subcontract order, the distribution terms are as follows:
      Amount distribution:

      - Pro rata distribution of quantities, weights or volumes: the total of quantities, weights or volumes of the parent product is distributed only onto the service. It is dependent on the quantities, weights or volumes of the source document.
      - Pro rata distribution of amounts: the total of the amounts of services and materials is distributed onto the services and materials.

      Distribution of the invoicing elements contained in the invoice. This distribution depends on the line type:
      - Pro rata distribution of quantities: the invoicing elements are distributed onto each line, except the 'Service' line. The calculated amount for the parent product is then reassigned to the associated service.
      - Pro rata distribution of amounts: the invoicing elements are distributed onto each line, except the 'parent product' line.
      - Pro rata distribution of weights and volumes: the invoicing elements are distributed onto the normal lines and onto the 'Parent product' lines. The calculated amount for the parent product is then reassigned to the associated service.
      The pro rata is calculated from the total of amounts, quantities, weights or volumes only from the lines to which the invoicing element applies.

      For example:
      Let us consider an additional invoice on a normal line and on the lines of a subcontract order with WO:
      - Line 1: normal product (line unrelated to the follwoing lines)
      - Line 2: Parent product
      - Line 3: Service
      - Line 4: Material supplied by the subcontractor
      The pro rata is calculated as follows:
      • The pro rata of the quantities is calculated from the total of the following quantities: line 1 quantity + line 2 quantity + line 4 quantity.
      • The pro rata of the amounts is calculated from the total of the following amounts: line 1 amount + line 3 amount + line 4 amount.
      • The pro rata of the weights is calculated from the total of the following weights: line 1 weight + line 2 weight.
      • The pro rata of the volumes is calculated from the total of the following volumes: line 1 volume + line 2 volume.
    • Specify if this is a New cost i.e. A cost that has not be planned in the landed costs.
      This check box is selected by default. It indicates that the additional invoice amount is included in the stock valuation (when the receipt is closed), in the Purchase cost calculation of the document to which this invoice is attached to and in the Actual purchase cost calculation of the related order.

      When the impact of this invoice has been anticipated and its amount is already covered by the landed costs, clear this check box so the amount of the invoice does not increment the Actual purchase cost.
      It can be:
      • A cost for which you had assessed the amount in a cost structure:

        - Specify the relevant cost: the Cost field can be accessed only if no line has been selected yet.
        - From the selection lists, pick one or several source documents that include this cost (order and/or shipment and/or receipt). In that case, the source document lines must be managed with a cost structure. A warning message is displayed if, for the same product and the same source document, this cost has already lead to an additional invoice.
        You cannot select an invoice line as a source document. Cost structures are not managed at a detailed level on invoices.
        The amount entered on the additional invoice corresponds to an update of the cost that is contained in the cost structure of the source documents. This update is performed by launching the STCREG - Cost matching query, either manually or as a batch recurring task.
        This query only processes closed orders and shipments but processes all receipts, whether there are invoiced or not.
        During the first reconciliation, the processing replaces the initial cost amount by the amount of the additional invoice. During the following reconciliations, the additional invoice amounts increment the cost amount on the source document and related documents: the purchase cost amounts and the stock cost are updated. The actual purchase cost is also updated on the initial order line linked to the document.
        At the end of each of these reconciliation processes, a stock movement is created if the product is managed with stock-receipt adjustment and if the cost is defined as being considered in the stock valuation.
      • Let us consider a cost for which you have assessed the amount by applying a coefficient and/or based on a fixed unit cost.
        - In this case, you do not specify the cost. The additional invoice is saved in the database and posted but its amount is not considered in the purchase cost calculation and stock cost calculated on the source document and related documents.
        - Select by picking the source documents in the selection lists.

    SEEINFO The impact of an additional invoice on the related documents is calculated pro rata of the related quantities. Examples of this impact are provided below, at the level of paragraph: Examples of the impact of additional invoices on documents

    CCA/PCA périodiques

    If the SVC - Periodic accruals activity code is activated, and if the SVCFLG - Accruals management parameter is set to Yes, you can generate analytical MOs spread out over time by invoice line. This staggering can only be carried out before the final validation of the invoice.

    In the Accruals management screen that opens, enter a start date and end dates and a frequency. The tax-excluded amount of the line is distributed onto each MO according to the number of generated entries. The automatic journal for this analytical MO generation is KIK4 - Expense accruals purchase inv.

    Purchase journal traceability

    Click this action to access the Purchase journal traceability inquiry function.

    Affichage situation ligne fac
    Commitments

    Used to access the de-commitment linked to the invoice line when it is posted. When the invoice line is not posted, the commitment linked to the original order can be accessed.

    Match results

    This option on invoice lines is used to:

    • display the matched lines (blocking or non-blocking match with warning),
    • directly access the Matching tolerance function,
    • display the detail of each line by selecting it in the Three-way match status grid.
    Product notes

    Click this action in order to open a window displaying the note(s) associated with this product.
    This information can relate to product availability, additional or substitute products, or a promotional message.
    This window could open automatically depending on the setup defined when creating the notes.

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

    For further information, see the documentation on Notes.

     

    Close

     

    Tab Control

    Presentation

    Use this section to perform a visual check of the invoice and, if necessary, to modify some elements of the invoice in case of rounding or entry errors.

    When an invoice originates from several documents and an invoicing element is contained in each of the selected documents with different tax codes, the system will display the invoicing element as many times as there are tax codes with a limit at four tax codes per element. If this limit is exceeded, the invoicing element is grouped with a tax code, which is not displayed on the last line of this invoicing element.

    If an invoicing element is added to the receipt from which the purchase invoice originated, the new invoicing element appears in the Control section of the purchase invoice.

    Close

     

    Fields

    The following fields are present on this tab :

    Grid Invoicing elements

    This field indicates the number of the invoicing element identifying the associated amount (charges, freight, packaging, discount, etc.).
    The list of the invoicing elements is drawn up by cumulating the lists of the invoicing supplier and their price list structure.
    Other elements can be added to this list:

    • elements manually entered because only present on the supplier invoice,
    • elements added according to the source documents selected when the source documents contain elements that are not usually managed by the invoicing supplier.
      In the case of a direct receipt, any modification applied to an invoicing element on the receipt will update the invoice.
    • Description (field INVDTALIB)

    This field indicates the short title of the invoicing element.

    • Entry amount (field INVDTAAMT)

    This field indicates the amount of the invoicing elements displayed on the suplier invoice.
    These values must be manually entered to be then compared to the amount of the invoicing elements as calculated by the system.

    • Currency (field AMTCODLIB)

     

    • Order footer amount (field INVORDAMT)

    This column indicates the calculated amount coming from the various orders concerned. This amount is calculated once the invoice lines have been entered. 

    If there is a difference between the value calculated in Sage X3 and the real value invoiced by the supplier, the value of the column 'Code footer amt" must be adjusted so as to balance the invoice control.

    When the invoice concerns direct receipts this column is fed by the value of the invoicing elements entered on the direct receipt. If an invoiced receipt concerns both direct lines and lines stemming from orders, the delta of invoicing elements between the order and the receipt will be added to this column according to the proportions of the impacted lines.

    • Rcpt. footer amt. (field RCPCPLAMT)

    This column is used to view the invoicing elements stemming from receipts. This information is displayed purely for information purposes when the receipt lines are displayed on the invoice. It indicates that invoicing elements have been added or updated on the receipt by comparison with the invoicing elements of the original order. The amount of added or modified invoicing elements is displayed in this column.

    • Amount lines (field INVLINAMT)

    This field indicates the amount of the invoicing element when the invoicing element is calculated using the document lines.
    SEEINFOThe 'Amount' field cannot be accessed for this type of invoicing element.

    • Variance (field INVDIFAMT)

    This field displays the variance existing between the amount of the invoicing element as displayed on the supplier invoice, entered in column 'entered amount', and the amount of the invoicing element as calculated by the system, entered in column 'order footer amt'.

    • DR/CR (field DEBCDT)

    This field indicates the sign of the invoicing element.

    • credit in the case of a discount,
    • debit in the case of a charge.

    This field indicates the tax code of the invoicing element.
    An invoicing element with 'product rate' or 'line amount' as tax calculation rule does not display a tax code and forbids the modification of this tax code.
    This invoicing element can appear in the table with up to five different tax codes. It can happen when the same invoicing element stems from several original documents with different tax codes.

     

    This field indicates the analytical processing key of the invoicing element.
    It can be directly entered on the line.

    These are the analytical dimensions intialized based on the setup of the Default dimensions (PIV dimension code), linked to the invoicing elements management. These dimension codes can be modified manually if authorized by the transaction. Use the Actions icon to change the dimension codes of the dimension types.

    When an analytical dimension is used for project management tracking, any modification of the project code on the document header leads to the dimension code being reset, except if a distribution key has been entered.

    • Increase/Decrease (field INCDCR)

     

    • Subject to discount (field DEPFLG)

     

    Grid Taxes

    • No. (field NOTAX)

     

    • Description (field LIBTAX)

    This field contains the title of the tax code present on the lines of the document or in the invoicing element table.

    • Tax basis (field BASTAX)

    This field indicates the basis liable to tax. It is comprised of the ex-tax amount of the invoice lines and/or the amount of the invoicing elements.

    • Tax amount (field AMTTAX)

    It is the total tax calculated from the lines and/or the invoicing elements. This total is modifiable in order to correct possible errors due to a calculation variance or rounding differences. The correction is automatically passed on to all the elements concerned (lines and/or invoice elements subject to this tax).


      • Type (field PURTYP)

      When the tax is related to:

      • the document line, the tax type recovers the purchase type of the document line: Purchase, Fixed assets or Service.
      • an invoicing element, the tax type always takes the value: Purchase.
      • Subject to tax (field VATCHA)

       

      • Gross basis (field VATGRO)

       

      • Discount basis tax excl. (field BASDEPNOT)

       

      • Discount basis tax incl. (field BASDEPATI)

       

      • Extra tax amount (field VATSUPAMT)

       

      Lines excluding tax

      • Invoice - tax (field TOTLINAMT)

      This field indicates the tax ex. total of the invoice lines entered using the information on the invoice provided by the supplier.
      This amount is used in the final check of the invoice by comparing it to the ex-tax amount of lines as calculated by the system.

      • Calculated - tax (field CLCLINAMT)

      This is the total ex-tax amount of the invoice lines, calculated by the system.

      • Variance - tax (field DIFLINAMT)

      This field indicates the variance existing between the ex-tax amount of the invoice lines as calculated by the system and the total ex-tax amount of the lines of the supplier invoice.

      Currency

      • field CUR2

       

      Tax total

      • Tax entered (field TOTTAXAMT)

      This field indicates the total amount of taxes entered using the information on the invoice provided by the supplier.
      This entered amount is used in the final check of the invoice by comparing it to the tax amount as calculated by the system.

      • Tax variance (field DIFTAXAMT)

      This field indicates the variance existing between the amount of taxes from the supplier invoice and the amount of taxes calculated by the system.

      Lines including tax

      • Invoice + tax (field AMTATI)

      This is the total tax-incl amount stemming from and entered using the supplier invoice.

      • Variance + tax (field DIFAMTATI)

      This field indicates the variance existing between the tax-incl amount of the supplier invoice and the tax-incl amount calculated by the system.

      • 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:

      Close

       

      Tab Costs

      Presentation

      This section is available based on the selected entry transaction.
      It displays a summary of the costs related to the whole document, both in the currency specific to the document and the currency of the company.
      This section is populated only if the document has been previously created, since the displayed information is the result of a calculation. If an existing document is modified, the data is updated, but only after the modification has been saved.

      For the document, the Purchase cost block displays:
      - the total of the tax excl. lines,
      - the total of the various cost types involved in the purchase cost calculation
      - the total of the additional invoices (and credit memos on additional invoices) impacting the document in progress, either directly or indirectly. These are the additional invoices that meet the two following conditions: they are validated and included in the actual purchase cost (New cost flag activated).
      - the total of the invoicing elements increasing or decreasing the total amounts.

      Note:
      - The product cost total is loaded only if the current document is linked to at least one product for which landed costs are managed with a cost structure.
      - The landed cost total is only loaded if the current document is linked to at least one product for which landed costs are managed with a landed cost coefficient and/or a fixed cost per unit.
      - In the event when an order or a receipt is partially invoiced, the various amounts are calculated based on the pro rata of the quantity actually invoiced, from the amounts of the order or the receipt, respectively.

      SEEINFOAll this information can also be viewed in theInvoice inquiry, which can be accessed from the Options menu.

      Close

       

      Fields

      The following fields are present on this tab :

      Block number 1

      Grid Purchase cost

      • Description (field LIB)

       

      • field TOTDOC

       

      • field TOTSOC

       

      Close

       

      Examples of the impact of additional invoices on documents

      The addition of additional invoices on a document directly impacts this document.
      This also impacts the purchase and stock costs of the related documents, pro rata of the relevant quantities.

      Additional invoice on order

      1/Additional invoice of €100 for an order of 100 IPAD.

      Use case: additional cost, not expected when creating the order (e.g.: a service provider adds transportation fees to your invoice).

      • Creation of an order of 100 IPAD that cost €200 each, for a total of €20,000.
      • An additional invoice of €100 is created for this order line. Follow these steps: preload the lines, select the New cost flag and enter the amount of €100. When posting the invoice, the additional invoice total and the actual purchase cost of the original order are updated.
      • When receiving the complete order line for 100 IPAD, the valuation of the goods, excluding the additional invoice, is generated, in other words, €20,000 in stock movements.
      • Closing the order line triggers the update of the valuation for the 100 IPAD by allocating the €100 included in the additional invoice to the order, increasing the cost from €20,000 to €20,100 in stock movements.
      The €100 amount of the additional invoice is displayed on the order Line cost as a non-detailed cost. It is also displayed on the receipt. This amount is broken down pro rata of the received quantity if several receipts are completed. However, the additional invoice amount on the order line can only be included in the stock valuation if the order line is closed. If you partially receive this order line and close the order line, the whole additional invoice amount is allocated to the received quantity in the stock valuation.

      2/Additional invoice on an order with product cost matching

      Use case: cost expected when creating the order ultimately higher or lower than expected (e.g. the service provider invoices two additional days of storage on the transit warehouse where the goods are located).
      • The IPAD product has been set up with a cost structure including a product cost COST021 of €100 for the overall transport.
      • Creation of an order of 100 IPAD that cost €200 each, for a total of €20,000 (+ total of product costs COST021 of €100).
      • Creation of an additional invoice for this order line, matching the overall transport cost to €120 following these steps: preload the lines, disable the New cost flag, select the COST021 cost, select the order line and enter an amount of €120. When posting the invoice, the additional invoice total and the actual purchase cost of the order are not impacted.
        The complete receipt of the order line of 100 IPAD triggers the valuation of the goods with a receipt movement of €20,000 + total product cost COST021 of €100, for a total of €20,100.
      • In order to update the valuation and match the COST021 product cost, you must close the order line and launch the STCREG - Cost matching task to adjust stocks.
      • From the receipt line, click Cost structure detail from the Actions menu: the product cost amount COST021 is displayed with an amount adjusted to €120 (against the amount calculated to €100), the Reconciled field is set to Yes for this cost. The stock movements (CONSSMV) display the price adjustment with the €20 additional difference.
      Product costs can only be matched when the product is managed with a cost structure already including the product cost when creating the order. In order to create the additional invoice with cost matching, in the line preloading screen, the New cost flag must be disabled and the cost to match of the Cost field must be defined. This information makes it possible to apply a control on the order lines when performing a picking in the selection panel. A message is displayed if the cost is not displayed on the picked order line.
      In order to distribute the amount of the additional invoice, the STCREG - Cost matching task performs an adjustment but only if the order line has been closed. This task is only used in the case of cost matching.
      3/ Additional invoice on order (flag New Cost = No) and deletion of a receipt.

      Use case : you save an additional invoice on order (New Cost flag disabled) after performing several receipts on order.
      You then delete one of the receipts. A message warns you that reconciled costs exist.
      You save a new receipt.
      This new receipt is valued without considering the additional invoice on order. It is valued as a normal receipt.
      • Creation of an order of 10 products with a unit price of €100, and a cost amount of €100.
        The stock cost per unit is €110.
      • Creation of a first receipt with 4 products.
      • Creation of a second receipt with 6 products.
      • Recording of an additional invoice on order (New Cost flag disabled) with an amount of €200.
        You run the STCREG batch task to refresh the cost amount and update the stock valuation.
        The stock cost per unit is now €120.
      • Deletion of the second receipt.
        The stock cost per unit of the first receipt is still €120.
      • Creation of a new receipt.
      • This new receipt is valued without considering the additional invoice. Its stock cost per unit is €110.
      • Recording of an invoice on order.
        The calculation of the stock cost per unit takes into account the cost amount for the various receipts and calculates the average unit cost of the two receipts. The calculation is as follows:
        • For the first receipt: the cost amount per unit is €20.
        • For the second receipt: the cost amount per unit is €10.
      The amount of valued costs on the invoice is:
      (20 * 4) + (10 * 6) = €140, corresponding to a unit amount of €14.
      The stock cost per unit is therefore 100€ + €14 = €114.
      The two receipts are thus valued at €114.
      When an invoice on receipt is concerned, each invoice inherits from the cost amount of the receipt it is associated to. In this example, the product stock cost per unit for the invoice related to the first receipt would be €120, and the product stock cost per unit for the invoice related to the second receipt would be €110.

      Additional invoice on shipment

      4/ Additional invoice of €100 for a shipment of 100 IPAD.

      Use case: new costs linked to the shipment are invoiced by a partner or supplier.
      • Creation of an order of 100 IPAD that cost €200 each, for an order line of €20,000.
      • Creation of a shipment and selection of the order line of 100 IPAD.
      • Creation of an additional invoice of €100 for this shipment line. Follow these steps: preload the lines, select the New cost flag and enter the amount of €100. When posting the invoice, the total of additional invoices and the total shipment cost of the Shipment.
      • The complete receipt of the shipment line for the 100 IPAD triggers the shipment line closing and generates the valuation of the goods for €20,000 and simultaneously allocates the additional invoice amount to the shipment for €100, for a total stock movement of €20,100.
      The €100 amount of the additional invoice on shipment is recovered on the order line cost as a non-detailed cost. The additional invoice total and the actual purchase cost of the order are also updated.
      If the shipment line has been received multiple times, the €100 amount on the additional invoice is broken down pro rata of the received quantity. However, this additional invoice amount on the shipment line only impacts the stock valuation if the shipment line is closed (through the complete receipt of the shipment or manual closing of the shipment line). If you partially receive this shipment line and close the shipment line, the whole additional invoice amount is allocated to the received quantity in the stock valuation.

      5/ Additional invoice on shipment with product cost matching

      Use case: cost expected when creating the shipment but ultimately higher or lower than expected (e.g. the service provider invoices two additional days of storage on the transit warehouse where the goods are located).
      • The IPAD product has been set up with a cost structure including a product cost COST021 of €100 for the overall transport.
      • Creation of an order of 100 IPAD that cost €200 each, for a total of €20,000 on the order line (+ total of product costs COST021 of €100).
      • Creation of a shipment and selection of the order line of 100 IPAD.
      • Creation of an additional invoice for this shipment line, matching the overall COST021 transport cost to €120 following these steps: preload the lines, disable the New cost flag, select the COST021 cost, select the shipment line and enter an amount of €120. When posting the invoice, the total of additional invoices and the actual purchase cost of the Shipment.
      • The complete receipt of the shipment line of 100 IPAD triggers the valuation of the goods with a receipt movement of €20,000 + total product cost COST021 of €100, for a total of €20,100.
      • The total receipt of the shipment line automatically triggers the closing of the shipment line.
      • In order to update the valuation and match the COST021 product cost, you must close the shipment line and launch the STCREG - Cost matching task to adjust stocks.
      • From the receipt line, click Cost structure detail from the Actions menu: the product cost amount COST021 is displayed with an amount adjusted to €120 (against the amount calculated to €100). The Reconciled table is set to Yes for this cost. The stock movements (CONSSMV) display the price adjustment with the €20 additional difference.
      Product costs can only be matched when the product is managed with a cost structure already including the product cost when creating the shipment. In order to create the additional invoice with cost matching, in the line preloading screen, the New cost flag must be disabled and the cost to match of the Cost field must be defined. This information makes it possible to apply a control on the shipment lines when performing a picking in the selection panel. A message is displayed if the cost is not displayed on the picked shipment line.
      In order to distribute the amount of the additional invoice, the STCREG - Cost matching task performs an adjustment but only if the shipment line has been closed. This task is only used in the case of cost matching.

      6/ Additional invoice with no variance (no new cost and no product cost matching)

      Use case: invoicing costs on a shipment with no stock valuation but with an accounting tracking.

      • Creation of an order of 100 IPAD that cost €200 each (with or without product costs).
      • Creation of a shipment and selection of the order line of 100 IPAD.
      • Creation of an additional invoice for this shipment line:
        • You can use the line preloading in order to select shipment lines using the following setup: disable the New cost flag, clear all costs (no selection) and leave the amount blank. After validating the selected shipment lines in the picking screen, enter an excluding-tax line amount on the invoice lines.
        • You can also directly select Shipment from the additional invoice origin instead of preloading lines and indicate the shipment lines to be invoiced. Enter an excluding-tax line amount on each invoice line.
      • The complete receipt of the shipment lines triggers the closing of the shipment line but does not generate any stock movement.

      Reports

      By default, the following reports are associated with this function :

       PBONFAC : Invoice control notes

       PINVOICEE : Purchase invoice list

       PINVOICEL : Detail purchase invoice list

      This can be changed using a different setup.

      This setup is performed at the Customization level of the current object, by associating a report code or a print code to it.
      It is possible to further specify this setup:

      • By specifying a given report at transaction entry level. If this report matches a print code, the list of reports associated with this print code is also submitted.
        The report entered at transaction entry level and the reports associated with the print code are automatically submitted in creation mode only.
      • At a more detailed level, by associating a print template with the BP. This template mentions the report to be used in priority for the printing of each document, as well as the expected number of copies.
        SEEINFOIf the number of copies is not specified, or if there is no print template associated with the BP, the number of copies defined for the Destinationprinter is chosen. If the number of copies is not specified for the destination printer, then a single copy is printed by default.

      Specific actions

      The following fields are included on the window opened through this button :

      Grid Open item edit

      • No. (field NUMLIG)

       

      • Due date (field DUDDAT)

      Open item payment due date.

      If the MAXPD - Maximum period (companies) activity code is activated, a warning message is displayed if the last due date is greater than the period specified, depending on the case, at the level of the following parameters or of the Contractual period possibly specified at the BP level.

      Payment method associated with the due date line.
      The payment method defines the payment means (check, cash, bank card, instrument etc.).
      It is managed in the payment methods table.


      • Amount (field AMTCUR)

      Amount of the open item line


      Code used by default for the current BP to identify a series of early discount and late charge rates (up to 12) to be applied to a payment according to a number of days early or days late with respect to the open item date.

      • Statement (field SOI)

      Statement indicator
      If this indicator is set to 'Yes', the open items calculated from the payment conditions are taken into account by the automatic generation processing of customer statements.


      • Pay approval (field FLGPAZ)

      Level of payment approval.

      Code identifying the unpaid dispute.

      • VCS number (field BELVCS)

       

      This field displays the pay-to supplier or the pay-by customer specified on the invoice. You can modify this information. If the open item line is split, the value on the first line is used.

      • Business partner address (field BPAPAY)

       

      • Payments (field PAYCUR)

       

      • Provisional payment (field TMPCUR)

       

      • Statement number (field SOINUM)

       

      • Bank account (field BIDNUM)

      The value of this number defaults from the business partner profile and the address code. The bank account number format is dependent on the bank location.

      For example, for an IBAN format, this field only contains the bank account number starting with the 5th character of the full IBAN.The prefix containing the country code and a control key is not included.

      To change the bank account number, select the Business partner from the Actions icon available in the field to access the business partner profile, and select or enter a different bank account.

      • IBAN code (field IBAN)

      This field displays the full IBAN, including a prefix with the country code and a control key, followed by the bank account number. If the IBAN prefix does not exist, this field remains empty.

      • Paying bank (field PAB)

      This field displays the paying bank linked to the Bank account field.

      Block number 2

      • Document total (field AMTTOT)

       

      • Payment total (field PAYTOT)

       

       

      Close

      Click this action to view or modify the open items of the current invoice.

      Click this action to:

      • Validate an invoice and post it to accounting. Only the matched invoices, in other words those that do not present any balance or discrepancy between the entry performed at header level and the sum of the lines that can be posted.
        In the event of additional invoices: unlike additional invoices posted to receipts, those posted to orders do not immediately generate stock movement adjustments: stock valuation will be adjusted when closing the order line.
      • Validate a credit memo and post it to accounting. Depending on whether the credit memo is expressed in value or in quantity, the stock adjustment conditions are detailed in the documentation entitled Basic principles for the valuation of the stocks.
      • If the PRIFLG - Full stock valuation parameter (ACH chapter, REC group) is set to Yes, a record is created in a dedicated table (PTDSTKVAL). This record tracks the history of the links between this invoice or credit memo and the other purchase documents (orders, shipments and receipts). In addition it saves all the valuation data, such as the quantity and the stock cost per unit calculated using the document values. These data are used in the stock valuation calculation, for example. The stock cost per unit is defined at receipt level using all the invoices, credit memos and additional invoices associated with the documents, irrespective of which documents arrived first.
      • Automatically create an expense for each purchase line upon validation of the purchase invoice, if the Fixed assets module is managed. The creation is carried out as follows. The expenses thus created can be viewed from the Linked expenses selection panel.
      Conditions for the automatic creation of an expense

      For a purchase invoice line, an expense is created when the following conditions are met:

      • Accounting postings are specified for the line.
      • The Legal account and the IAS account are tracked (in the definition of the Accounts table: the check boxes Fixed asset tracking and Expense creation must be activated and an accounting nature must be specified for this account).
      • In addition, if the line contains a product, this product must be capitalizable (the Fixed asset check box must be activated in the Product setups). If the product is not capitalized, the expense is created after validation of a warning message.

      An expense is also created for each invoicing element for which no invoice line distribution has been requested. This setup is carried out at the level of the Invoice type. However, when a distribution is requested, no expense is created for the invoicing element. In this case, the amount of each created expense is increased or reduced by the distributed part of the invoicing element according to the distribution terms defined at the invoicing element level.

      Populating of the expense fields

      The LAYOUTFAS expense table is loaded from the following tables:
      - Invoice header: PINVOICE
      - Invoice line: PINVOICED
      - Accounting and analytical postings: CPTANALIN

      LAYOUTFAS

      Table

      Field

      Rule

      Company

      CPY

      PINVOICE

      CPY

       

      the site,

      FCY

      PINVOICED

      FCYLIN

      Site of the invoice line if it is a financial site

      PINVOICE

      FCY

      Site of invoice header (always financial) if FCYLIN is not financial. The site of the line is kept in GEOFCY (geographical location) 

      Product reference

      CODLOF

      PINVOICE

      NUM

       

      Line number

      LINLOF

       

       

      Incremental number

      Invoice reference

      BPRVCR

      PINVOICE

      BPRVCR

       

      Product ranges

      ITMREF

      PINVOICE

      ITMREF

       

      Supplier,

      BPR

      PINVOICE

      BPR

       

      Journal

      JOU

      PINVOICE

      JOU

       

      Exchange rate type

      CURTYP

      PINVOICE

      CURTYP

       

      Currency

      CUR

      PINVOICE

      CUR

       

      the invoice date

      DATVCR

      PINVOICE

      BPRDAT

       

      Allocation date

      DATIMP

      PINVOICE

      ACCDAT

       

      Invoice type

      TYPVCR

      PINVOICE

      INVTYP

       

      Geographic site,

      GEOFCY

      PINVOICED

      FCYLIN

       

      Currency rates,

      RATCUR

      PINVOICE

      RATMLT(0)

       

      Description 1

      DES

      PINVOICE

      <invoice type> + BPRNAM

      When no product description

      PINVOICED

      ITMDES1

      When product description not empty

      Description 2

      DES2

      PINVOICE

      INVNUM

      When it is a credit memo

      Granted

      FLGGRA

       

       

      1

      Subsidy amount

      FLGAMTGRA

       

       

      1

      Link asset

      FLGLIKAAS

       

       

      1

      Main expenditure

      FLGLOFMAI

       

       

      1

      Addition source

      CPMCREORI

       

       

      1

      CoA account

      GAC

      GACCOUNT

      GAC

      GAC = legal account

      Original CoA account

      GACORI

      GACCOUNT

      GAC

      GAC = legal account

      CoA nature

      GACACN

      GACCOUNT

      GACACN

      GAC = legal account

      IAS account

      IASACC

      GACCOUNT

      GAC

      GAC = IAS account

      Original IAS account

      IASACCORI

      GACCOUNT

      GAC

      GAC = IAS account

      IAS nature

      IASACN

      GACCOUNT

      GACACN

      GAC = IAS account

      Order reference

      ORDBUY

      PINVOICED

      POHNUM

       

      Product ranges

      ITMREF

      PINVOICED

      ITMREF

       

      Unit

      UOM

      PINVOICED

      UOM

       

      Quantity

      QTY

      PINVOICED

      QTYUOM

       

      Invoiced VAT rate

      RATVAT

      TABRATVAT

      VATRAT

       

      Collected VAT rate

      RATVATREC

      TABRATVAT

      DEDRAT

       

      Ex-tax amount

      AMTNOTCUR

      PINVOICED

       
       
       
       
       
       AMTNOTLIN
       
       
       

       AMTNOTLIN + Distributed amount (DISCRGAMT1  DISCRGAMT2, ...)

      According to the setup used at the level of the Invoice type:

      - If no distribution of invoicing elements

      - If distribution of invoicing elements on the invoice lines

      VAT amount

      AMTVATCUR

      PINVOICED

      AMTTAXLIN1

       

      Collected VAT amount

      AMTVATRCUR

      PINVOICED

      DEDTAXLIN1

       

      Allocation

      DSP

      CPTANALIN

      DSP

       

      Analytical dimensions

      CCE(0..20)

      CPTANALIN

      CCE(0..20)

       

      Fixed asset group

      ACGGRP

      ITMMASTER

      ACGGRP

       

      Detail line source

      LIGORI

      PINVOICED

      PIDLIN

       

      Validated

      FLGVAL

       

       

      1

      Creation user

      CREUSR

       

       

      GUSER

      Creation date

      CREDAT

       

       

      Date$

      Entry origin

      CREORI

       

       

      4

      SEEINFO Notes:

      • When the product has a fixed asset group, theSection associations are carried out upon expense creation.
      • When the company is submitted to the French legislation and that the VAT collection rate does not equal 100% and that the setup VATAUTVAL - VAT Automatic validation is set to No, the user must validate the VAT coefficients on the expense so that this latter become capitalized. The validation is carried out byactivating the Validatedcheck box available and visible only on the expense as long as the validation has not been carried out.

      The following fields are included on the window opened through this button :

      • ISR reference line (field BVRREFLINE)

      Enter the ISR reference number from the ISR form of the invoice.

      If you use an ISR reading device, it must be configured to return the complete code line including spaces and control characters like "+" and ">".
      Refer to your ISR reading device user manual for more information.

      • Amount + tax (field TOTAMT)

      This field displays the amount in the ISR reference line from the Incl tax amount field.

      You can only enter an amount for an ISR +. That is, if the ISR does not include an amount. Or, you can manually enter the total tax amount in the Input tax total field.

      • Input tax total (field TOTVAT)

      Use this field to enter the total tax amount if there is no value for the Amount +tax field.

      • Bank account number (field BVRBID)

      This field displays the bank details associated with the invoice.

      Close

      Click this action to open the ISR reference line entry screen. This is only available if the SWIPURBVR - Swiss ISR usage purchasing parameter (LOC chapter, SWI group) is set to Yes.

      This information entered is used to populate invoice fields and to search for the corresponding supplier BP account.

      If an ISR reference line already exists for a purchase invoice (GESPIH), this reference line is displayed for informational purposes only and cannot be changed. For a supplier invoice (GESBIS), the ISR reference line can be changed, but this re-initializes the invoices.

      Automatic processing of the ISR reference line
      1. Enter the ISR reference line from the ISR slip (ISR form) of the invoice in the ISR reference line field. If you use an ISR reading device, it must be configured to return the complete code line including spaces and control characters like "+" and ">".

        Refer to your ISR reading device user manual for more information.

      2. Validate the ISR reference line field by pressing Tab or clicking into the next field.
      3. The system analyses the reference line for type and format. If there are any errors, you receive a blocking message.
      4. For purchase invoices:
        The amount coded in the reference line is displayed in the Amount +tax field. You can only enter an amount for an ISR +. In other words, it is an ISR that does not include an amount. Or, you can manually enter the total tax amount in the Input tax total field.
        This value is used later to calculate the net total invoice amount.
      5. Click OK when you are done.
      6. Upon close, the automatic search for the supplier BP starts: The ISR customer no. in the ISR reference line is compared to those entered in the pay-to suppliers bank details. If a matching pay-to supplier is found, the search tries to find a matching supplier BP.
        Note: For a successful search, the pay-to supplier’s ISR customer no. must already exist in the supplier's bank data.
      7. Depending on the result of the supplier BP search, different actions are possible.
        • If several possible BPs are found, a selection screen displays where you can select the correct supplier BP account.
        • If no supplier BP is identified, the standard management screen of supplier BPs opens. In this screen, you can select a supplier or create a new one.
        • If only one supplier BP is returned by the search, no additional action is necessary.
      8. The invoice entry screen populates with the BP account which was found or manually selected. In addition, the supplier field is automatically validated.
      9. The validation of the supplier account field populates several other fields like payment term, etc. This follows the same behavior as if the supplier account had been entered manually.
      10. In the final step, the automatic processing performs the following actions depending on the context:
        • For purchase invoices (GESPIH): The total, net, and gross invoice amounts are calculated according to the values in the ISR reference line entry screen. They are automatically entered in the corresponding fields on the Management section.
        • For supplier BP invoices (GESBIS): The tax information and the calculation of the net and gross amounts are based on the standard tax rule for the supplier. A detail line for the invoice amount is automatically inserted on the Lines section. The G/L account for this line is taken from the supplier accounting code line 17

      You can now continue to enter additional details for the invoice as necessary.

      Implications on the payment process

      When using ISR forms for payments, you must include the following payment information:

      • The ISR reference number in the payment information.
      • The ISR customer number as the recipient’s bank account.

      For that purpose, there are specific processes for the ISR payments in the Sage X3 payment generation process if Swiss bank files are created:

      • The payment mode linked to the payment term must be ISR. The default payment term is taken from the supplier account settings, but can be changed manually for the invoice.
        It is not possible to use a payment term linked to an ISR payment method without entering an ISR reference line if the SWIPURBVR – Swiss ISR usage purchasing parameter (LOC chapter, SWI group) is set to Yes on the site.
      • When the bank file is created, the ISR reference line from the invoice is checked and the reference number is written to the bank file.
        The ISR customer no. is automatically be used as the recipient‘s bank account in the bank file.
        This overrides the BP default bank account or a manually selected BP bank account if the ISR customer no. belongs to a different bank ID.
      • The ISR reference no. cannot be transmitted for grouped payments, (i.e., paying several open items in one payment). Because of this, you receive a warning message in the Payment proposal if you select grouping of payments when Swiss sites and/or ISR payment methods are involved.

      This action is available if the KSW - Swiss legislation activity code is active and if the current site SWIPURQRC - QR code entry parameter (LOC chapter, SWI group) is set to Yes.

      Click this action to import the QR code content read by an ISR/QR reader. The data is verified and the gross amount is displayed, but cannot be modified. You can enter an input tax that can be used later to calculate the net amount.

      When you click OK, Sage X3 identifies the pay-to BP. If more than one bank account is found, you need to select one from the list. If no bank account could be found with the customer number or QR-IBAN, you can access the supplier maintenance and select or enter a new pay-to BP (and add the customer number in the bank details, if necessary).

      See the Swiss localization guide for detailed information on QR-bills.

      An ISR/QR reader or scanner is not provided by Sage nor is it a component of Sage X3.

      Particular cases

      Distribution of footer elements on credit memos:

      It is possible to create credit memos that only concern footer elements. Based on their setups, these elements can be distributed in proportion to the quantities, the weights, the volumes or the amounts.

      For that purpose, it is necessary to mention on the credit memo all the invoice lines on which the invoice footer needs to be distributed. If the distribution of the footer elements is carried out in proportion to the quantities, all the lines must be given a null quantity. The distribution is then performed in proportion to the quantities on the lines of the original invoices. In the same way, if the invoice footer is performed in proportion to the amounts, a net null price must be entered for each line. The distribution is then performed in proportion to the amounts on the lines of the original invoices.

      Caution, if there are lines whose quantity or amount are different from zero, the distribution will only take place in proportion to the lines whose quantity or amount is different from a null value.

      Distribution of the footer elements on additional invoices:

      On an additional invoice, it is possible to distribute a footer element on invoice lines. From the pre-loading screen, the user chooses the invoice lines that need to be posted.

      On the other hand, like for credit memos, all the lines must be positioned to a null value or a null quantity for the distribution of the footer element ( if set up as being distributed in proportion to lines or quantities) to take place in proportion to the quantities or amounts of the lines of original invoices.

      As for credit memos, if there is at least one line whose quantity or amount is different from the null value, the distribution type will only be in proportion to the lines having a value.

      Over-invoicing
      Credit memos on invoices when the PIHCPR - Invoice price adjustment parameter is set to With landed costs
      Credit memos expressed in value and credit memos expressed in quantity

      Stock adjustments concerning the cases below are explained in details in the following documentation: Basic principles for the valuation of the stocks

      Menu bar

      Text Menu

      Texte entête

      Click this action to:

      • enter invoice header text at any stage of the creation process,
      • modify this text in invoice modification.

      During the transformation of a document, this text is never propagated to the other documents.

      Footer text

      Click this action to:

      • enter invoice footer text at any stage of the creation process,
      • modify this text in invoice modification.
      During the transformation of a document, this text is never propagated to the other documents.

      Address menu

      Invoice address

      Click this action to modify the address of the invoicing supplier.

      Payment adress

      Click this action to:

      • Modify the address of the paid supplier by choosing a new address code. You can change the details only for 'Miscellaneous' suppliers.
      • Enter content as follows:

      Options menu

      Picking criteria

      Click this action to enter selection criteria and refine the search of original documents.
      You can use the following criteria:

      • Order number,
      • Receipt number,
      • Supplier BI number,
      • Return number,
      • Invoice number (in the case of a credit memo, the original invoice number cannot be selected, it corresponds to the number which has been entered, if needed, at the level of the Management section).
      • Product reference

      SEEINFOYou can use the selection wildcards (*, ?).

      In the case of a partial receipt, you can invoice for a single order line, the order line and the line from the receipt. The quantity suggested in picking depends on the order selected between the order and the receipt.

      Let us consider the following case:

      • An order with an order line for a quantity of three units
      • A partial receipt linked to this order line of two units

      If the receipt is selected first, the system suggests the two receipt units.
      If the supplier invoice relates to three units and if the order for the balance is selected, the system suggests the uninvoiced balance of the order, that is to say a unit (the two other units are selected for the receipt).

      However, if the order is selected first, the system suggests the total quantity of the order, that is to say three units.
      If this quantity is reduced to one unit, the system considers that this is the invoicing for the receipts that are not invoiced yet, and not the balance of the order line that is not received yet.

      If the receipt is selected secondly, the system suggests a unit because the previous unit is considered as invoiced for the order line that is already selected.

      In the Distribution and A/P-A/R accounting modules, an entry which is at the origin of an invoice, a credit memo or an additional invoice cannot have a date later than the date of this invoice, credit memo or additional invoice. The picking lists and selection windows are filtered accordingly.

      Customs information

      Fields

      The following fields are included in this window :

      Transport

      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.

      • Incoterm town (field ICTCTY)

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

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

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

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

      • Forwarding agent address (field FFWADD)

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

      Intrastat information

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

      • Intrastat transp. location (field EECLOC)

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

      This information is not used in the French declaration.

      • Intrastat transport mode (field EECTRN)

      The transport method by which the goods are presumed to leave their national territory on shipment (export) or to have arrived in on receipt (import). This information is used in the Customs document file.

      Physical flow

      This is the economic information on the performed transaction. The nature of the transaction is used in the Intrastat.
      This information is initialized using the physical flows where it can be modified. This information can also be accessed from some financial flows (sales invoices and credit memos).
      The transaction nature is initialized according to the setup of the correspondence table for the Movement rules and natures. This table is used to associate an EU rule and an EU transaction nature to each flow type. This setup can be adjusted by rule, country and group of companies.

      The EU or statistical rules are used to specify the nature of the EU transaction from a tax or statistical point of view. The EU rule is used in the Intrastat.
      This information is initialized using the physical flows where it can be modified. This information can also be accessed from some financial flows (sales invoices and credit memos).
      The initialization of the nature of the transaction is carried out according to the parameters of the comparison table for the Movement rules and natures, which is used to associate an EU rule and an EEU transaction nature to each type of flow. This setup can be adjusted by rule, country and group of companies.

      Close

      This window contains the customs information and the information necessary to the creation of the Customs Document File. On creation, some data originates from the order or the receipt and, if not, is initialized using the information in the Supplier record.

      • Incoterm negotiated as well as the Incoterm city, when needed.
      • When the goods transit via a forwarding agent, code and address of the forwarding agent responsible for the export and located in the European Union: information also used for the Customs Document File concerning the transportation of the goods to their export location.

      The EU Information used only for the Intrastat is linked to the Intrastat activity code (DEB):

      • EU identification number of the customer (or EU tax number), EU transport location and EU transport method.

      Information linked with the Physical flows: EU rule andTransaction nature, linked to the DEB activity code, too, comes from the setup carried out at Movement rules and natures function level.

      It remains possible to modify this information as long as the invoice has not been validated.

      Options / Consultation des factures

      Click this action to access the inquiry of the various supplier invoices.

      Options / Transaction

      Click this action to view the invoice entry transaction used.

      Options / Document traceability

      Click this action to access the Document traceability inquiry function. This function is used to view and browse through the hierarchy of journals at the origin or coming from the document.

      Zooms / Pièce comptable

      Click this action to directly access the journal entry generated upon invoice validation.

      Zooms / Pièce analytique

      Click this action to directly access the analytical entry generated upon invoice validation.

      Fonctions / Annulation comptable

      Click this action to delete the journal entry generated by a posted invoice.
      The records created in the PTDSTKVAL table on posting the invoice are also canceled (when the PRIFLG - Full stock valuation parameter is set to Yes). Similarly, potential adjustments related to stock valuation are reversed.
      This feature can only be accessed:

      Fonctions / Déblocage erreur rapprochement

      Limitations

      It is not authorized to enter an additional invoice on a subcontract order.

      Error messages

      In addition to the generic error messages, the following messages can appear during the entry :

      No sequence number counter has been assigned to this document

      This message is displayed when the assignment of sequence numbers for the Purchasing module has not been carried out. To correct this problem, it is necessary to check that the required sequence numbers do exist (if this is not the case, they should be created), then assign them to the different documents using the appropriate function (see the Pre-requisites paragraph of this documentation).

      This document does not exist

      This message is displayed when the user is not in creation mode and the order number entered does not exist in the table. To correct this problem, it is possible to use a selection window to search more easily for the correct code.

      Incorrect date

      This message is displayed when the accounting date is controlled, and the entered date is incorrect or it belongs to a fiscal year that has not been created yet for the company. To correct this problem, you can enter a new date or create and open the fiscal year and the periods for the relevant company.

      Inconsistent invoice number versus previous invoice date

      This message is displayed when the entered date is prior to the date of the document that has the previous journal number, and the chronological control is activated on the sequence number used on the journal type associated with the entered invoice type.

      The document number is not defined over the same period.

      This message is displayed when modifying the accounting date if the new date does not belong to the same accounting period, and the period component belongs to the counter used and the FRADGI - DGI N° 13L-1-06 regulation parameter is set to Yes.

      Date prohibited for the module Purchasing

      This message is displayed when the date entered is not contained in the authorized date range defined by the ACHSTRDAT - Purchase start date and ACHENDDAT - Purchase end date user parameters.

      Fiscal year not open

      This message is displayed when checking the accounting date, and this date belongs to a fiscal year that is not open for the company. To correct this problem, you can enter a new date or create and open the fiscal year and the period for the relevant company.

      Period not open

      This message is displayed when checking the accounting date, and the date belongs to a period that is not open for the relevant fiscal year. To correct this problem, you can enter a new date or open the relevant period.

      Closed Period

      This message is displayed when checking the accounting date, and this date does not belong to a closed period for the relevant fiscal year. To correct this problem, you can enter a new date or reopen the impacted period provided that the fiscal year is still open. Please refer to the recommendations for the message ‘The impact on the stocks valuation can be significant’.

      The impact on the stocks valuation can be significant

      This message is displayed as a warning. You have changed the invoicing value for a product on this invoice. You are advised to manually adjust the value of stock for this product as the fiscal period during which the product was received into stock has been closed.

      Nonexistent control account

      This message is displayed on entering the call code of the control account and the code entered does not exist or it is not compatible with the BP code entered (for example, customer collective code type).

      Insertion not possible

      This message is displayed if you try to insert or duplicate a line although the maximum number of lines for an invoice has been reached, as defined by the appropriate activity code.

      Validity dates exceeded

      This message is displayed on entering the accounting date.

      Your operator rights do not authorize this value

      The code of the entered payment approval is higher than the maximum code mentioned in the operator recording, Payment approval level field. To correct this problem, you must enter a payment approval code with a lower level.

      Only an element that has been added manually can be deleted!

      This message is displayed when you try to delete an invoicing element. The list of invoicing elements is drawn up by the list of elements of the invoicing supplier and the list of the price list structure of this invoicing supplier. These elements cannot be deleted. If one of these elements is not used, simply reset the corresponding amount to zero. Other additional elements can be added during entry: they can be deleted.

      Invoicing element already present in the list!

      This message is displayed when you try to add an invoicing element that is already part of the list: the same element can only appear once in the list.

      No invoice line to be invoiced

      This blocking message is displayed when you manually create an additional invoice line and the invoice table does not contain any invoice. The additional invoices must be entered after the invoices to which they are related.

      Order XXXXXXXXXX No line to be invoiced

      This blocking message is displayed when you manually create an invoice line linked to an order and all the order lines whose numbers have already been entered are already invoiced.

      Receipt XXXXXXXXXX No line to be invoiced

      This blocking message is displayed when you manually create an invoice line linked to a receipt and all the receipt lines are already invoiced.

      Return XXXXXXXXXX No line to be invoiced

      This blocking message is displayed when you manually create an invoice line linked to a return and all the return lines are already invoiced.

      No record selected

      This message is displayed when you interrupt the selection of lines to be invoiced for the orders, the receipts, the returns and the invoices at the same time.

      Product XXXXXXXXXX: No order line to be invoiced
      Product XXXXXXXXXX: No receipt line to be invoiced
      Product XXXXXXXXXX: No return line to be invoiced
      Product XXXXXXXXXX: No invoice line to be invoiced

      This blocking message is displayed when you manually create an invoice line after having entered the product reference, and the number or the line of the original document has not been entered. It means that for the relevant product, all the lines of the source document have been invoiced.

      Line already invoiced or closed

      This blocking message is displayed when you manually create an invoice line after you have entered the line number of the source document. It means that the selected line has already been invoiced or has been manually closed for products without receipt.

      Order not fully signed!

      This blocking message is displayed when you manually create an invoice line and the entered order is not completely signed.

      The return is not validated.

      This blocking message is displayed when you manually create a credit memo line and the return is not completely validated yet.

      It does not belong to the same legal company

      This blocking message is displayed when you manually create an invoice line and the original journal number entered does not belong to the same company as the invoicing site mentioned in the header.

      Different invoicing supplier!

      This blocking message is displayed when you manually create an invoice line and the invoicing supplier of the original journal entered is not the same as the invoicing supplier mentioned in the header.

      Modification in process on another workstation

      This blocking message is displayed when the invoice that you are trying to modify or delete is being used on another workstation. Wait until this invoice has been released or select another invoice.

      $PORDER XXXXXXXXXX Modification in progress on another workstation
      $PRECEIPT XXXXXXXXXX Modification in progress on another workstation
      $PRETURN XXXXXXXXXX Modification in progress on another workstation
      $PINVOICE XXXXXXXXXX Modification in progress on another workstation

      This blocking message is displayed when the selected original entry is being used on another workstation. Wait until the record has been released or select another one. This message can also be displayed during an update. In that case, the transaction is canceled and it is necessary to re-enter the invoice in progress.

      The product is on hold [Continue End]

      This message is displayed when you manually create an invoice line after you have entered the product reference. It depends on the value given to the blocking code (No/Warning/Blocking) mentioned in the product-supplier. If the blocking code is set to Warning, you can Continue or Abort the creation.

      No line entered. Update impossible.

      This blocking message is displayed when you try to create a invoice without having entered a line.

      XXX Problem when retrieving the sequence number

      This message is displayed in creation mode when the read of the specified sequence number is invalid and the system has been unable to retrieve a sequence number.

      There are credit memos or additional invoices. Deletion prohibited!

      This blocking message is displayed when you try to delete an invoice linked to credit memos or additional invoices. You need to delete these first, before deleting the invoice.

      Invoice posted, modification or deletion prohibited!

      This blocking message is displayed when you try to modify or delete an already posted invoice. A posted invoice can no longer be modified.

      Payments carried out, deletion prohibited!

      This blocking message is displayed when you try to delete an invoice associated with recorded payments.

      Social and IAS accounts can be considered as fixed assets and the product cannot be considered as a fixed asset
      Do you want to create the expense upon validation?

      This warning message is displayed upon validation when the following conditions are met:
      The Fixed assets module is managed
      The accounts are tracked
      The line has a product but the product is not capitalized.
      The expenditure is created by clicking on Yes. When No is chosen, the expenditure is not created without an error generation.

      No expense will be created for the line
      Social and IAS accounts cannot be considered as fixed assets and the product can be considered as a fixed asset
      The DBS directory is in read-only mode, remote SYSDBA connections are impossible.

      This warning message is displayed upon validation when the following conditions are met:
      The Fixed assets module is managed
      - the product is capitalized
      The accounts are not tracked
      When Yes is chosen, the expenditure is not created but no error is generated. When clicking No, the validation stops and an error occurs.

      No expense will be created for the line
      Social account not tracked and IAS account tracked (or) Social account tracked and IAS account not tracked
      The DBS directory is in read-only mode, remote SYSDBA connections are impossible.

      This warning message is displayed upon validation when the following conditions are met:
      - The Fixed assets module is managed
      - One account is tracked and the other is not
      When Yes is chosen, the expenditure is not created but no error is generated. When clicking No, the validation stops and an error occurs.

      'Field error' 'Invoice Type'
      'IN1 [LEG 1] : Document type IN2 : Record does not exist for the current legislation [LEG 1]'

      This message is displayed when the legislation of the entry type linked to the invoice type does not match the invoice legislation.

      No ABN number is assigned to this supplier. Please check the Supplier record before posting the invoice.

      This message is displayed when the following conditions are met: the KAU - Australia activity code is activated, the AUSABNWRN - Warn supplier without ABN parameter (LOC chapter, AUS group) is set to Yes and the selected supplier is not linked to an ABN code (this code is entered on the Supplier record in the SIRET code field).


      Tables used

      SEEREFERTTO Refer to documentation Implementation