This function is used to validate the invoices saved with the Invoice control function in order to generate the accounting and analytical entries for these invoices.
When the Fixed assets module is managed in the folder, the invoice validation generates the automatic creation of an expense for the purchase invoice line when all the conditions are met (the expense creation conditions are detailed below).
Refer to documentation Implementation
Presentation
This processing performs a batch validation of those purchase invoices that have been saved and checked.
Once the validation processing has been started:
- a journal is created for each validated invoice.
An expense is automatically created if the Fixed assets module is managed. The creation is carried out according to the following rules.
The invoices are selected on the basis of the following criteria:
The "log file" flag is used, if checked, to obtain a summary of all the validated journals at the end of the processing.
Close
Fields
The following fields are present on this tab :
Criteria
|
  |
|
This field specifies on which company the process is carried out. |
|
  |
|
This field is used to carry out the process on the assigned site. |
|
  |
|
Operator code used to sort out the entries to be processed. |
|
  |
|
This is used to carry out the process on a specific invoice category. There are five invoice categories: - Invoice - Credit memo - Debit note. - Credit note. - Pro forma. |
|
Start date used to select the records to be processed. |
|
End date used in the selection of the records to be processed. |
|
Initial invoice number used to select the records to be processed. |
|
End invoice number used to select the records to be processed. |
Generation
|
Select this check box to generate a log file after running the process. |
Close
For a purchase invoice line, an expense is created when the following conditions are met:
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) | ||
Reference | CODLOF | PINVOICE | NUM |
|
Line number | LINLOF |
|
| Incremental number |
Invoice reference | BPRVCR | PINVOICE | BPRVCR |
|
Product ranges | ITMREF | PINVOICE | ITMREF |
|
Supplier, | BPR | PINVOICE | BPR |
|
Document | JOU | PINVOICE | JOU |
|
Exchange rate type | CURTYP | PINVOICE | CURTYP |
|
Currency | CUR | PINVOICE | CUR |
|
Invoice date | DATVCR | PINVOICE | BPRDAT |
|
Allocation date | DATIMP | PINVOICE | ACCDAT |
|
Invoice type | TYPVCR | PINVOICE | INVTYP |
|
Geographic site | GEOFCY | PINVOICED | FCYLIN |
|
Currency rate | 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. |
Grant amount | FLGAMTGRA |
|
| 1. |
Link asset | FLGLIKAAS |
|
| 1. |
Main expense | 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 | QTE | PINVOICED | QTYUOM |
|
Invoiced VAT rate | RATVAT | TABRATVAT | VATRAT |
|
Collected VAT rate | RATVATREC | TABRATVAT | DEDRAT |
|
Ex-tax amount | AMTNOTCUR | PINVOICED | 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 operator | CREUSR |
|
| GUSER |
Creation date | CREDAT |
|
| Date$ |
Entry origin | CREORI |
|
| 4. |
Notes:
This function can be run in batch mode. The standard task FUNPIH is provided for that purpose.
In addition to the generic error messages, the following messages can appear during the entry :
Non-referenced triggering table
Incorrect number of arguments
Incorrect key
Error on field validation
Incorrect link on ...
Sequence number counter exceeded
No exchange rate
Transaction canceled
No line
Unbalanced journal
Unbalanced distribution
When all these error messages appear, the invoice will not be validated. These messages are mostly the result of a setup error at automatic journal level. Check the setup of the PIHI and PIHC automatic journals.
"Social and IAS accounts can be considered as fixed assets and the product cannot be considered as a fixed asset"
This validation error message is generated because of the following conditions:
- the Fixed assets module is managed
The accounts are tracked
The line has a product but the product is not capitalized.
See above the Conditions for the automatic creation of an expense.
"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"
This validation error message is generated because of the following conditions:
- the Fixed assets module is managed
The product is capitalized
- the accounts are not tracked.
See above the Conditions for the automatic creation of an expense.
"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"
This validation error message is generated because of the following conditions:
- the Fixed assets module is managed
- an account is tracked and the other is not.
See above the Conditions for the automatic creation of an expense.