Sales >  Invoices >  Contract invoice generation  

Display all Hide all

This function is used for invoice generation from service contracts and their scheduled invoices.

The invoicing of service contracts can be carried out in two ways:

 From invoice generation with the picking of service contracts

 From this automatic contract invoice generation function

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

Presentation

All the fields in this screen have optional entry. This information is used to target the invoicing to a group of contracts.

The system will in certain cases try to group open items and/or contracts so that they can be invoiced together, according to the invoicing mode selected.

Close

 

Fields

The following fields are present on this tab :

Selection criteria

 

The automatic creation of invoices is made from a single sales site at a time. 
This information is mandatory. You need to specify the site chosen for the process.
By default, it is the sales site associated with the operator. A control checks user authorizations.

  • Invoices until (field NEXSHIINV)

This date, if it is assigned, is used to select only the contracts that are valid at this date (the contract end date must be prior to or equal to this date), having an open item to be invoiced and where the next invoice issue date is also prior to this date.

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.

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

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

The invoice type is associated to a type of journal for which a counter (manual or automatic) is specified.
SEEINFO 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.
SEEINFO 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).

Date of invoices

  • Reference date (field INVDATFLG)

This information is used to choose 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.
  • field INVDATINV

Enter the date used on each created invoice.
This date is initialized to the current date. It 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 scheduled invoices.
Refer to the Scheduled invoices until field help for further details.

Invoicing mode

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

Sales site

Bill-to customer

Sold-to customer

Currency

Price type

Pay-by customer

Postal code for invoicing address

Town for invoicing address

County/state for invoicing address

Product description

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

Start - end range

  • From bill-to customer (field BPCINVDEB)

Use these ranges to filter the selection to only obtain a single bill-to customer or those bill-to customers having a reference 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)

 

Printing

  • Invoice (field PRNFLG)

Select this 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

Enter the standard document code to be printed.

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

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

  • Printer (field PRNIMP)

Default printer.



Close

 

Batch task

This function can be run in batch mode. The standard task FUNAUTINVC is provided for that purpose.

Specific Actions

Error messages

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

Site XXX: Record does not exist

This message appears during the entry of the sales site in the selection screen when the code entered does not correspond to a valid site. 

Sales site: Mandatory field

This message appears if no sales site has been specified.

Customer invoice types: XXX The record does not exist

This message appears if the invoice type entered does not correspond to a valid invoice type.

Invoice type: Mandatory field

This message appears if no invoice type has been specified.

Incorrect date 

This message appears if the invoice date or the reference date ranges are incorrect. This message also appears if the reference date falls in a non-open period. In this case the message is more precise: Fiscal year not open, period not open, period closed.

Messages found in the log file associated with the generation

No contract processed

This message appears if the system has not found any contracts to be invoiced as a function of the selections.

Change In Progress on another workstation

This message appears when another user is already in the process of modifying the order or the contract currently being processed.

Validated main mandate not found or invalid for the pay-by BP Please update invoice before validation

This message is displayed when the payment terms have the SDD type and no mandate reference has been initialized by default on the invoice (no main "Validated" Mandate defined for the company, Pay-by BP pair). However, the reference of the mandate is mandatory on the invoice. The invoice is still created but its validation will be prohibited as long as the reference of the mandate has not been entered manually on the invoice.

Tables used

SEEREFERTTO Refer to documentation Implementation