Supplier Invoice Posting
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.
Prerequisite
Refer to documentation Implementation
Screen management
Entry screen
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:
- the company, the site
- the user
- the type of involved journals
- a date range
- a number range
Mention if a log file is requested. This trace file draws up the list of the posted invoices.
Criteria
All companies (field ALLCPY) |
No help linked to this field. |
Company (field CPY) |
Legislation (field LEG) |
All sites (field ALLFCY) |
No help linked to this field. |
Site (field FCY) |
All users (field ALLUSR) |
User (field USR) |
All types (field ALLTYP) |
Invoice type (field SIVTYP) |
Start date (field STRDAT) |
End date (field ENDDAT) |
From invoice (field VCRDEB) |
To invoice (field VCRFIN) |
Generation
Log file (field TRC) |
No help linked to this field. |
Conditions for the automatic creation of an expenditure
For a supplier BP invoice line, an expenditure 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 Expenditure creation must be activated and an accounting nature must be specified for this account).
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 the company is subject to the French legislation, the recovery VAT rate is not 100 per cent and the parameterVATAUTVAL - Automatic VAT validation(AAS chapter, VAT group) is set to No, you need to validate the VAT rates on the expense for it to be capitalized.The validation is performed by activating the Validated check box, which is only available and displayed on the expense as long as the validation has not been carried out.
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.
Batch task
This function can be run in batch mode. The standard task BPSINV is provided for that purpose.
Error messages
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.