Automatic contract invoice generation

• Company (field CPY)

• Sales site (field SALFCY)

The automatic creation of invoices is made from a single sales site at a time.
You must specify the site chosen for the process.
By default, the sales site associated with your user profile is used.

• Invoices until (field NEXSHIINV)

Enter a date to only select the contracts that meet the following criteria:

• The contract is valid at this date (the contract end date must be prior or equal to this date)
• The contract includes an open item to be invoiced
• The date for sending the next invoice is also prior to this date.

By default, the date in this field is initialized to today’s date.

• Invoice type (field SIVTYP)

This information will be used to determine the invoice type used in the generation of invoices associated with contracts. This information is initialized by the SIVTYP - User invoice type (chapter VEN, group INV) Sales parameter.

This information is compulsory.

The invoice type suggested by default is linked to the SIVTYP - User invoice type parameter. You can modify it if necessary by choosing an invoice type from the list of invoice types that have been defined.
The customer invoice type:

• is used for the Sales and BP Customer invoices;
• identifies a category of invoice (invoice, credit memo etc.) along with a posting structure for the posting of the invoices;
• is associated with a type of journal for which a counter (manual or automatic) is specified.
  Notes:

• If no counter is specified in the journal type and no journal number is manually specified on invoice entry the program will attribute a journal number according to the counter set up in the Counter assignment table.
• When no journal type is associated to the invoice type the journal type specified on the automatic journal is used (as well as the associated counter).

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

• Reference date (field INVDATFLG)

Select the date that will be associated with each invoice created:

• Reference date. The date associated with the invoices will be the reference date entered. By default the reference date is initialized to the current date. This date must fall into an open period (a check is carried out).
• Next contract invoice date: The date associated with the invoices will be the next invoice date present in each contract to be invoiced. In the case of multiple grouped contracts, it is the next invoice date of the first contract.

This process does not consider the setup of the DATREFCON - Service contract invoice date parameter (HDK chapter, INV group). If this parameter is set to: Today's date and you select Next contract invoice date: an information message is displayed and the invoices will be generated on the next invoice date (not today's date).

• field INVDATINV

Enter the date used on each created invoice.
This date is set to the current date and is submitted to an existence check in the period table and the fiscal year table. The fiscal year and the period must be open.

This date is also used to filter the selected invoicing open items.
Refer to the Scheduled invoices until field help for further details.

• Invoicing mode (field IME)

Each open item in the contract can be invoiced separately or grouped with other open items and/or other contracts.
This grouping is done according to the invoicing method, which can take the following values:

• Single open item 
  No open item grouping is performed.
  When open items are invoiced gradually, this invoicing method is the same as the "1 invoice/open item" method.
  When there are open items with late invoicing for a contract, only the 1st open item (the oldest one) remaining to be invoiced is processed. The remaining open items are not invoiced during this processing. Therefore ,the processing needs to be relaunched for each open item that remains to be invoiced. If not, there will remain open items with late invoicing for the contract.
   
• 1 invoice/open item. 
  No grouping of open item is performed.
  When open items are gradually invoiced, this invoicing method is the same as the "Single open item" method. 
  Each open item on the contract is the object of an invoice. Thus, when there are open items with late invoicing for a contract, all the open items are invoiced during this processing. On processing completion, it is therefore not possible to still have open items with late invoicing on a contract. 
   
• 1 invoice / contract  
  Each contract is individually invoiced. All the open items in this contract are grouped on the same invoice.
   
• 1 invoice / customer 
  Maximum grouping. All the contracts (and thus all the open items associated with the contracts) for a customer are found in the same invoice.

The grouping also depends on the following homogeneity conditions (if one of these is not common, there will be no grouping) :  

• Product description (field TYPITMDES)

This field is used to specify which description will be indicated on the product description of the invoice: either the translated description of the product, which is linked to the contract line, or a description of the invoiced open item.

• From bill-to customer (field BPCINVDEB)

Use these ranges to filter the selection on a single bill-to customer or on the bill-to customers whose reference is contained within these ranges.

• To bill-to customer (field BPCINVFIN)

• From contract no. (field CONNUMDEB)

Permet une sélection sur le numéro de contrat.

• To contract no. (field CONNUMFIN)

• Invoice (field PRNFLG)

Select this check box to print the document (pick ticket, packing slip or invoice) after delivery or invoice creation.

In that case, you need to specify:

• The document: it defaults to the report code linked to the object being used
• The print server, if any
• The printer, if any

• Document (field PRNNAM)

Enter the standard document code to be printed.

• Destination (field PRNDEN)

Enter the document or report destination.
The destination must exist in the Destinations table, which is where its characteristics are defined (issue type, printer, server etc.).

• Server (field PRNSRV)

This field is used to define the print server.
This setup is sent at the print request from a Crystal Reports report.

• Printer (field PRNIMP)

Default printer.