This function is used to perform the mass posting of the supplier invoices that have already been entered in "Supplier Invoicing", if they have not been each posted when they were entered, in order to generate the accounting documents corresponding to these invoices.
When the Fixed assets module is managed in the folder, the invoice validation generates, when all the conditions are there, the automatic creation of an expenditure for each BP supplier purchase invoice line (the expenditure creation terms are detailed below).
The invoices transmitted by the "Distribution" module have already been posted in this module.
Refer to documentation Implementation
Presentation
This processing performs a mass validation of supplier BP invoices.
Once the validation processing has been started:
- a journal is created for each validated invoice.
- an expenditure is automatically created if the Fixed assets module is managed. The creation is carried out as follows.
A dialogue window is displayed to select the invoices that are going to be posted, according to the following criteria:
Mention if a log file is requested. This trace file draws up the list of the posted invoices.
Close
Fields
The following fields are present on this tab :
Criteria
|
No help linked to this field. |
|
  |
|
  |
|
No help linked to this field. |
|
  |
|
  |
|
  |
|
  |
|
  |
|
  |
|
  |
|
  |
|
  |
Generation
|
No help linked to this field. |
Close
For a supplier BP invoice line, an expenditure is created when the following conditions are met:
Feeding of the expenditure fields
The LAYOUTFAS expenditure table is loaded from the following tables:
LAYOUTFAS | Table | Field | Rule | |
Company | CPY | PINVOICE | CPY |
|
Site | FCY | PINVOICE | FCY |
|
Reference | CODLOF | PINVOICE | NUM |
|
Line number | LINLOF |
|
| Incremental number |
Invoice reference | BPRVCR | PINVOICE | BPRVCR |
|
Product | ITMREF | PINVOICE | ITMREF |
|
Supplier | BPR | PINVOICE | BPR |
|
Document | 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 | PINVOICE | FCY |
|
Currency rate | RATCUR | PINVOICE | RATMLT(0) |
|
Description 1 | DES | PINVOICE | <invoice type> + BPRNAM | |
Description 2 | DES2 | PINVOICE | INVNUM | When it is a credit memo |
Granted | FLGGRA |
|
| 1. |
Subsidy 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 | PINVOICE | INVNUM |
|
Unit | UOM | BPSINVLIG | UOM |
|
Quantity | QTY | BPSINVLIG | QTYUOM |
|
Invoiced VAT rate | RATVAT | TABRATVAT | VATRAT |
|
Collected VAT rate | RATVATREC | TABRATVAT | DEDRAT |
|
Ex-tax amount | AMTNOTCUR | BPSINVLIG | AMTNOTLIN |
|
VAT amount | AMTVATCUR | BPSINVLIG | AMTTAXLIN1 |
|
Collected VAT amount | AMTVATRCUR | BPSINVLIG | DEDTAXLIN1 |
|
Allocation | DSP | BPSINVLIG | DSP |
|
Analytical dimensions | CCE(0..20) | BPSINVLIGA | CCE(0..20) |
|
Detail line source | LIGORI | BPSINVLIG | PIDLIN |
|
Validated | FLGVAL |
|
| 1. |
Creation operator | CREUSR |
|
| GUSER |
Creation date | CREDAT |
|
| Date$ |
Entry origin | CREORI |
|
| 4. |
Note:
When an invoice line is submitted to a manual analytical distribution (the $ character is displayed in the "Distribution" field), this does not create one expense only for this invoice line, but as many expenses as there are manual distribution lines for this invoice line.
This function can be run in batch mode. The standard task BPSINV is provided for that purpose.
In addition to the generic error messages, the following messages can appear during the entry :
"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 expenditure.