Customer BP Invoices
Use this function to manage customer invoicing outside the typical sales cycle.
In this context, you do not manage the order or the receipt note for the stock issue. When issuing the invoice, the data required for accounting is recorded.
For customer tracking, such as open item statements, reminders, payment management, and so on, the process is the same for invoices that come from the complete cycle or that come from entering a BP invoice.
- In this document, the term invoice has a generic meaning: It can be an invoice, a credit note, a debit note, or a credit memo.
- Invoices generated from recurring invoices cannot be deleted if they are used as a reference template (first recurring invoice/original recurring invoice).
In addition, the invoice must not be changed if it is also used as reference invoice. - For the Fixed Assets module:
When the SALINV - Sale invoice to generate parameter (AAS chapter, FAS group) is set to Yes, a BP customer invoice is generated automatically after validating the Asset disposal with a Sales reason. When the issue applies to a main asset and its components, only one customer invoice is generated with as many lines as there are sold assets.
Each asset concerned can be identified using its reference displayed at the level of the Comment field in the invoice line.
The values of some fields taken from the information entered during the asset disposal cannot be modified: The accounting date, the currency and customer of the Header section and the amount, as well as all tax elements of the Lines section.
On the Legal data screen in the Company function, you need to select the VAT on debit checkbox to display the required legal information when printing invoices. The required text displays in the Legal mention field when the checkbox is selected.
French electronic signatures for sales invoices and journal entries
In compliance with French and Portuguese antifraud legal requirements and to ensure data security, electronic signatures are automatically generated when a customer invoice or journal entry is posted or set to Final, respectively. After the electronic signature is generated, further modifications to any of the fields identified below can be easily detected.
You can use the Electronic signature control function (FRADSICTL) to review the current electronic signature and highlight any inconsistencies.
See the “French electronic signature how to guide” or the "SVAT certification for Portuguese legislation guide" for details on implementing this feature.
Exceptions
Data from invoices or journal entries posted before activating the electronic signature feature is not added to the DKSDATAFRA table and therefore no electronic signature is created.
Legislations other than French or Portuguese do not need to generate electronic signatures.
The electronic signature is a record in the Electronic signatures table (DKSDATAFRA) that includes data from the following fields in the Sales invoice (SINVOICE) and Account entries (GACCENTRY) tables:
Field code |
Description |
Data source: SINVOICE |
Data source: GACCENTRY |
ORIDOC |
Origin of the document |
1 |
2 |
DOCTYP |
Journal |
SINVOICE.SIVTYP |
GACCENTRY.TYP |
DOCNUM |
Journal description |
SINVOICE.NUM |
GACCENTRY.NUM |
TOTTAX(9) |
Total by tax rate |
SIH.AMTTAX(i) + SIH.BASTAX(i) |
|
AMTATI |
Invoice amount with VAT |
SIH.AMTATI |
|
DATTIM |
Date and time of the signature |
Datetime$ |
|
INVSNS |
Document type |
Evaluate SIH.SNS |
|
CPYNAM |
Company name |
CPY.CPYNAM |
|
POSCOD |
Company postal code |
BPA.POSCOD |
|
CPYEECNUM |
Company VAT number |
CPY.EECNUM |
|
BPRNAM |
Customer name |
SIH.BPRNAM(0) |
BPARTNER.BPRNAM |
BPREECNUM |
Customer postal code |
SIH.POSCOD |
|
JOU |
Journal code |
GACCENTRY.JOU |
|
DESTRA |
Journal description |
GACCENTRY.DESTRA |
|
FNLPSTNUM |
Final number |
GACCENTRY.FNLPSTNUM |
|
ACCDAT |
accounting date |
SINVOICE.ACCDAT |
GACCENTRY.ACCDAT |
ACC |
Account code |
GACCENTRYD.ACC |
|
BPR |
BP |
SINVOICE.BPR |
GACCENTRYD.BPR |
LIN |
Journal entry line |
GACCENTRYD.LIN |
|
LINDES |
Line description |
string$([F:DAE]DES<>"", |
Prerequisites
Limitations
When the invoice is entered in tax-inc. mode and an additional or special tax code is entered or automatically loaded from the account, the amounts of the three tax levels must be entered manually.
Screen management
Header
Block number 1
Site (field FCY) |
Enter the site code. The site must be a financial site. This determines the site and the company for the entry posting. |
Company (field CPY) |
This field displays the company for the selected site. |
Name (field CPYNAM) |
This field displays the company for the selected site. |
Invoice type (field SIVTYP) |
Enter the invoice type code to reference the invoice category and the entry structure used when validating the invoice. Only an invoice type with a legislation and company group consistent with those of the company linked to the given site can be entered. Learn more about working with legislations.
|
Document no. (field NUM) |
If the number is left blank, it is automatically assigned upon saving. |
Block number 2
Accounting date (field ACCDAT) |
Enter a date to define the accounting date for the generated journal. This field defaults to the current date. This date is not necessarily the same date entered for the Source document. For example, for a supplier invoice, the Source document date reflects when the invoice was created by the supplier. In that case, the Accounting date would be different. |
Customer (field BPR) |
No help linked to this field. |
Address code (field BPAINV) |
This field displays the address code for the customer. |
Name (field BPRNAM) |
This field displays the customer name. |
Control (field BPRSAC) |
Enter the code for the customer or supplier control account is set by default with the accounting code for the BP invoice. The initialization of the code for the Control field depends on whether or not the BP/Company tab is present in the BP record (GESBPR). |
Account (field SACACC) |
If a control account is entered, this field displays the account code. |
Header tab
Invoice characteristics
Some fields in the header are used to complete the invoice:
- Amount -tax and Amount +tax fields
By default, entering an amount in either field is optional. This is controlled by the HEAAMTBPC – Cust. inv. header amt. ctrl parameter (TRS chapter, INV group).
When you enter amounts on the invoice lines, these amounts automatically display in the corresponding fields on the Header. If the amounts are different, a warning message displays to alert you that the totals are different from header. Use the WRNMSGBPC – Customer inv. warning msg. parameter (TRS chapter , INV group) to disable the display of this message. - The link between a credit memo and the original invoice using this invoice number, or the link between the credit memo and the credit memo request number from the customer, etc.
- The default analysis for this invoice is then applied to the payments for the BP accounts:
You can define the default dimensions in the invoice header.
Open item characteristics
Use the remaining fields to define the open items in the invoice with respect to payment management (pay-by BP identification, payment conditions), to the open item statement management, and to the reminder process.
After saving an invoice, select Open items action to view the open items and the status of the related payment.
Detail
Source document date (field BPRDAT) |
Enter the invoice date. This field defaults to today's date. |
Source document (field BPRVCR) |
This field is used to record the number or the reference of the source invoice. |
Spanish invoice type (field INVTYPSPA) |
This field is only available when the sales site is linked to a Spanish company. Use this field to select the type of issued invoice. This information will be sent to the online portal of the Spanish fiscal authorities when transmitting fiscal data from the SII monitoring function. When creating a credit memo, the default credit memo type is determined by the SIIABTYP - SII credit memo type parameter (LOC chapter, SPA group).
|
Currency (field CUR) |
This field indicates the invoicing currency. All amounts are entered in this currency. |
Rate (field RAT1) |
field LABEL |
field RAT2 |
field CURMLT |
Amount - tax (field AMTNOT) |
This field displays a control amount that is compared to the line total during the recording. This amount is mandatory when the HEAAMTBPC – Cust. inv. header amt. ctrl parameter (TRS chapter, INV group) is set to Ex-tax and Tax -incl. amounts to be entered. |
Amount + tax (field AMTATI) |
Invoice number (field INVNUM) |
This invoice is the one to which the credit memo is allocated. Depending on the value of the INVCAN - Cancellation invoice parameter (TC chapter, INV group), the document in progress can be of the 'Cancellation invoice' type. In this case, the credit memo and invoice are matched, regardless of the value of the LETAUTCNO parameter.
|
DER code (field SPADERNUM) |
Project (field PJTH) |
After invoice validation, the project reference the invoice is allocated to can no longer be modified. |
VCS number (field BELVCS) |
Field linked to the Belgian legislation. Structured communication consists in specifying a single identifier on the invoices that will be used in all the banking exchanges.
The encoding number is made up of 12 numeric characters:
In the case of sales invoices and customer BP invoices, this number is automatically generated and cannot be modified. The generation of the encoding number is performed:
The field is not loaded if the invoice is of proforma type.
If the invoice type is a direct credit memo, the encoding number remains empty. If the invoice type is a credit memo linked to an invoice, the VCS number of the invoice is attached to it. If you modify a site, the VCS number field resets.
In the case of a credit memo linked to several invoices, a control prevents the credit memo from being attached to the various invoices. You need to create as many credit memos as there are invoices. |
Field 40 - reason (field FLD40REN) |
The KPO - Portuguese localization activity code needs to be active for this field to display. It is used to specify the VAT adjustment reason for the field 40, upon generation of the VAT declaration. When choosing the reason, the possible values are the values contained in Miscellaneous table 8300. |
Field 41 - reason (field FLD41REN) |
The KPO - Portuguese localization activity code needs to be active for this field to display. It is used to specify the VAT adjustment reason for the field 41, upon generation of the VAT declaration. When choosing the reason, the possible values are the values contained in the miscellaneous table 8301. |
Original document no. (field ORIDOCNUM) |
Period start date (field PERDEB) |
To (field PERFIN) |
Block number 3
Status (field STA) |
Printed (field STARPT) |
Tax rule (field VAC) |
Enter the VAT management type associated with the customer invoice. This field is automatically entered if a tax rule is specified in the record of the supplier of the current invoice. This is used, among other things, to obtain a print conditioned by the type of legislation. |
Amount type (field SALPRITYP) |
These two radio buttons, defined by the BP, are used to define whether the amounts on the invoice lines are entered as Tax excl. or Tax inc. The choice between Ex-tax or Tax-incl. is only possible upon invoice creation.
If the DEPMGTMOD - Discount management mode parameter (TC chapter, INV group) has the value Rebate on VAT, the type of amount is Ex-tax by default, regardless of the value of parameter SALPRITYP - Amount/Price type (TC chapter, INV group). You cannot select Tax-incl.. |
Entity/Use (field SSTENTCOD) |
Enter the Entity/use code to calculate the precise tax amount for the customer. This tax code is compatible with the Avalara system and makes it possible to determine the customer type for fiscal purposes. This field is available for all countries. The Entity/Use code can be entered for any delivery address when a document is being processed for a country that is tax-exempt. When the Calculate all
documents connection with SST is set to No and
an Entity/use code is entered, the document is exempt from tax and not subject to processing costs. |
Open items
Factor (field BPRFCT) |
If the invoice is to be factored, enter the code for the factor that will collect for this invoice. You need to enter a factor with a company and/or site that is compatible with the company and/or site of the open item. By default, the factor code is defined in the customer record. For example:
|
Factor name (field BPRFCTNAM) |
Statement (field XSOI) |
Indicates if the generated open items need to be inlcuded on the statement or not. |
Reminder (field XFLGFUP) |
Indicates if the generated open items need to be relaunched or not. |
Payment
Pay-by (field BPRPAY) |
This BP indicates the pay-by or paid BP |
Address code (field BPAPAY) |
Due date basis (field STRDUDDAT) |
This is the date from which the payment schedule is calculated. |
Payment term (field PTE) |
This field indicates the payment conditions that will be applied in order to determine the invoice schedule. The latter can be manually modified later on. |
Due date (field DUDDAT) |
Early discounts/Late charges (field DEP) |
Code used by default for the current BP to identify a series of early discount and late charge rates (up to 12) to be applied to a payment according to a number of days early or days late with respect to the open item date. Only a discount code consistent with the legislation and company group of the document site can be entered. The general principles linked to the multi-legislation setup are detailed in the GRPLEG field help. |
Comments (field DES) |
You can enter up to three comments. You can add content from the first comment to the Comment field on the Lines tab by entering // in that field.
|
VAT declaration no. (field DCLEECNUM) |
This field is displayed only if the following conditions are met:
This field displays:
It can still be modified if it is set up to accept entries at the entry transaction level and if the invoice is not validated. |
Mandate reference (field UMRNUM) |
If the company and/or the pay-by BP is modified, the mandate reference is modified accordingly.
|
ISR/QR reference number (field BVRREFNUM) |
This field displays the ISR reference number created for an invoice if the SWICUSBVR - Swiss ISR usage Sales (LOC chapter, SWI group) parameter is set to Yes. If a new invoice is created, the ISR reference number is calculated when the invoice is saved. When the SWICUSBVR parameter is set to Yes, this field only displays a value if an ISR payment term is used and the invoice currency is CHF. If you copy an invoice, the existing ISR number is removed. A new number is created when the copied invoice is saved. Refer to the Swiss legislation guide on how to use the ISR.
|
Payment bank ISR/QR (field PAYBAN) |
This field displays the ISR payment bank determined for the invoice if the SWICUSBVR - Swiss ISR usage Sales (LOC chapter, SWI group) parameter is set to Yes and only displays a value if an ISR payment term is used and the invoice currency is CHF. The payment bank information is used to print the necessary sender’s bank account information on ISR payment forms. Use this bank account as the destination account when paying the invoice. The ISR payment bank is only considered in the ISR process.
The ISR payment bank for the invoice is determined by the Payment bank ISR/QR field in one of the following functions. Information is taken from the first entry found.
If you copy an invoice, the existing payment bank is removed and the payment bank determination is repeated when the copied invoice is saved. Refer to the Swiss legislation guide for a comprehensive overview of setup and usage of this function.
|
Analytical grid
No. (field NUMLIG2) |
Dimension type (field DIE) |
Dimension (field CCE) |
The dimensions entered here will be used as default values for invoice lines. |
Lines tab
The grid in this section is used to characterize each of the invoice lines from an accounting point of view:
Nature
If the account is subject to dimensional accounting, it is necessary to define its nature. At general accounts level, it is possible to define a nature linked automatically to an account. The nature field cannot then be modified.
On the other hand, if a nature screen has been defined, it is possible to choose a different analytical nature conforming to the screen.
Analytical dimensions
If the accounting amount is not distributed over several analytical dimensions, the allocation field cannot be assigned. The entry is achieved directly in the following columns, in the dimension concerned, for each of the dimension types.
Default dimensions can be defined at the level of the nature, but those defined by the default dimension processing have priority.
Details grid
No. (field NUMLIG) |
It is the line number. |
Site (field FCYLIN) |
The site of each line can be different from the header site. In this case, the generated journal will be balanced site by site using inter-site link accounts. Refer to the documentation Reciprocal accounts for further explanations.
By default, the site proposed is that defined in the invoice entry header. Intercompany invoices (GESBICI and GESBISI functions) are protected by the INTCO - Intercompany transactions activity code. When entering intercompany invoices, this field only displays the site of the companies that were defined in Intercompany account mapping.
|
Company (field CPYLIN) |
Ctrl. (field SAC) |
This checkbox is only available if the Control checkbox is selected in the Chart of accounts function (GESCOA). Select this checkbox to indicate that the account is associated with a BP. |
field ACC1 |
In certain fields, access codes are used to restrict access to data by certain users. For a users to have access to a field, this code needs to be in this table. Depending on user rights and permissions, they can then view or modify the field. The access codes are equally used to restrict access to perform certain actions. You need to assign each access code defined in the grid.
|
BP (field BPRLIN) |
The choice of accounting allocation is determined by:
|
Settlement discount (field FLGDEP) |
This field is used to specify if an invoice line is subject to a discount.
|
Amount - tax (field AMTNOTLIN) |
Enter the amount not including tax for the recorded operation. The invoice cannot have a negative ex-tax and tax-incl. total. It is possible for some ex-tax amounts on a line but the ex-tax amount of the header is always positive.
|
Tax (field VAT) |
When the account on the line is liable for tax, the tax field is accessible for entry. It displays the tax code associated with the account or with the tax code associated with the rule. Refer to the documentation on the SAITAX - Tax Code Mandatory parameter (CPT chapter, VAT group).
Based on the context, it is necessary to verify that this tax code corresponds to the tax actually applicable, or it should be modified. The Enter tax option is available from the Actions icon. You can specify the taxes other than VAT (additional and/or special taxes) likely to affect the VAT calculation and therefore the tax excl. and tax-inc. amounts.
Only one tax code consistent with the legislation and the group of the site company can be entered. |
SST tax code (field SSTCOD) |
Define the default value of the Sage Sales Tax (SST) tax code. This tax code is recognized Avalara and is used to identify line types for fiscal purposes. All document costs are sent to SST in the form of document lines. It can include for example transport costs, handling costs and on-line product costs. This field is only available when the LTA activity code is activated. |
Tax amount (field AMTVAT) |
Enter a tax amount if the standard calculation for the tax amount on the line does not apply. If the tax code changes, these amounts are reset. |
Amount + tax (field AMTATILIN) |
No help linked to this field. |
Sales type (field SALTYP) |
This field is currently no longer used. |
Comment (field DES) |
You can enter a comment or add content from another field using the following characters: / displays the account title = displays the comment from the previous line // displays content from the first Comment field in the Header section. For an invoice generated automatically after validating the sales of fixed assets, this field contains the reference of the sold fixed asset and cannot be modified. |
Unit (field UOM) |
The work unit entry is defined is determined when setting up an analytical account. It is associated with a unit specifying its default value (in reporting currency). This unit is reused on journal entry. See the documentation on Natures for further information.
|
Quantity (field QTY) |
The quantity is automatically calculated by dividing the ex-tax amount (converted into reporting currency) by the work unit value. This value can be modified. |
Project (field PJTLIN) |
After invoice validation, the project reference allocated to the invoice line can no longer be modified. |
Cost type (field PCCCOD) |
Distribution (field DSP) |
This field is used to define the allocation methods for the line amount on the different dimensions of each dimension type.
For example: On a basis of 100, a coefficient of 10 is read as 10%. For these cases, it is possible to predefine the allocation with an existing key. The final display is $. |
field CCE1 |
The setup determines if the analytical dimensions can be modified. They display based on the setup of the default dimension. When creating an invoice, if no order line was entered and the project code is modified, the analytical dimensions are reset based on the setup of default dimensions. When creating or modifying an invoice, if an order line is added and the project code is modified, the analytical dimensions are not reset. |
Totals
Discount basis (field BASDEP) |
The discountable base is only displayed if the two following conditions are met:
The discountable basis depends on:
If you want to add a discount after saving the invoice, the discount code addition can be performed by selecting Open items. The Discount and Discount basis fields are hidden and the discountable basis is equal to the tax incl total. |
field CUR3 |
Total excluding tax (field TOTNOT) |
field CUR1 |
Total including tax (field TOTATI) |
This field indicates the tax-incl. result including the tax calculation by tax basis. This information appears when printing report ARCTTC2. The detail of the tax incl. calculation is obtained by right click on the total amount. The detailed calculation is stored in tables SVCRVAT and SVCRFOOT. To access the detailed tax statistics based on Sage Sales tax (SST). Select the link in the Tax-incl. total field. This option is only available if the document is issued by Sage Sales Tax (SST). If SST is used, the recording and cancelling a fiscal document are taken into account when:
If the tax is not calculated, the invoice is not created.
|
field CUR2 |
Account
field AFFICHE |
Amount type (field SALPRITYP) |
Account Inquiry |
Select this option to access the account inquiry for the account on the line. |
Statistical Codes |
Select this option to associate up to three statistical codes to each invoice line and the posting. |
Periodic accruals |
Select this option to open the Accruals management screen to post the line amount, or the tax excluded amount to analytical or general accounting according to a specific schedule. To take advantage of this, you need to activate the SVC - Periodic accruals activity code and the SVCFLG - Accruals generation parameter (TC chapter, SVC group) must set to Yes. |
Account Structures |
Select this option to assign an account structure for the line. The account structure is used to predefine the group of accounting and analytical postings for a journal and to load them directly on entry. Applying an account structure can be proposed by default after entering the tax excluded invoice amount. The structure used is the one defined in the customer record in the Financial section. See the documentation on Account structures for further information.
As for the amounts, from the assignment coefficients defined in the structure, they are automatically calculated from the tax-excl. amount of the invoice. |
Customer notes |
Select this option to display the note or notes associated with this customer. This window could open automatically depending on the setup defined when creating the notes. Notes are limited to a screen inquiry and cannot be printed. See the Notes documentation for more information. |
Reports
By default, the following reports are associated with this function :
BPCINV : Customer BP invoice
BPCINV2 : Customer BP invoice
BPCINVFIN : Final invoice
BPCINVPRE : Prepayment invoice
BPCINVTAX : Customer BP invoice
SIMFACCLI : Simulation customer invoices
FACTRSC : BP invoice list
This can be changed using a different setup.
Specific buttons
Validation | Select this action to perform the accounting posting of the current supplier invoice in order to have its entry. |
Menu bar
Use this to access the accounting journal generated after posting the invoice. |
When you define accruals management for an invoice by selecting Periodic accruals on the line, the analytical journals can be accessed in display mode according to the automatic journal referenced in the GAUKIK1 - Revenue accruals customer inv. parameter (TC chapter, SVC group). |
Accounting cancellation is not allowed for payments processed through Sage Exchange or Sage Pay. |
Use this action to transform an invoice into a credit memo. You need to confirm this action. Header
Line
|
Use this action to select and process transactions. This window opens when the payment method tied to the payment entry transaction is set up for credit card processing. Block number 1
Account information
Authorization
|
This field displays the default billing address for the customer. You can change the address for this invoice if needed. |
This field displays the default payment address for the customer. You can change the address for this invoice if needed. |
Error messages
XXX: This is not a financial site
The site selected for the invoice record is not defined as a financial site. Therefore it cannot receive accounting entries.
Period not open
The posting date for the invoice is incorrect because it does not fall in an open period range for the company.
Incorrect date
The invoice posting date is incorrect because it falls in a fiscal year that is not yet created or it does not correspond to an actual date. This same message also appears if the start/end dates for the duration of the service (see the Lines tab) are inconsistent.
: Parameter code does not exist
This message appears when a parameter required for the generation of an account posting is missing.
For example, this can arise when the setup of the document type (for example: customer invoice) is incomplete (no number sequence number for the documents).
BP incompatible with the control account
The choice of the control account for the invoice posting is incorrect because it must be of Customer type rather than Supplier, Sales Rep, etc.
Similarly, at the invoice line level, the BP and the control account must be of a compatible type.
Nonexistent control account
The control account used does not correspond to existing/referenced data.
Credit memo without invoice number
This is a simple warning message that the credit memo being entered has not been linked to an invoice. Indeed, it is not mandatory to link a credit memo to an invoice, no matching is generated upon credit memo validation.
Invoice in currency XXX
The invoice identified as the source of the credit memo is invalid because the characteristics of these two elements must be identical as far as the currency is concerned.
Invoice of customer XXX
The credit memo cannot be linked to an invoice where the bill-to customer is different.
Invoice on the control account XXX
The credit note cannot be linked to an invoice whose control account is different.
Invoice on site XXX
The site to which the credit memo posting invoice is attached does not correspond to the site of the credit memo.
Invoice not validated
The choice of the credit memo posting invoice is not correct as long as the invoice is not validated in accounting.
Dimension n Line: 'Dimension mandatory on dimension type X'
The analysis having been defined as mandatory for dimension type X and since the account structure called and executed does not contain any analysis for this dimension type, the invoice lines are pre-loaded without the analysis even though they should contain it.
XXX: Account reserved for site XXX
The site linked to the account is not compatible with the invoice posting site.
Account class prohibited on this journal type
The account selected for the invoice line posting must not be of type Exceptional, that is to say Revenue, Expenses or BP, etc.
Impossible to determine the control account
As soon as the invoice line relates to a BP, it is necessary to define the auxiliary BP and the associated control account.
XXX: Validity dates exceeded
The account/nature/distribution key/dimension validity dates are incompatible with the invoice posting date.
VAT type tax
In the Tax 1 and Tax 2 fields in the VAT entry screen for the line, only the Additional or Special type tax codes can be used.
This is not a VAT type tax
Conversely, in the VAT field of this entry screen, as well as in the VAT field of the invoice line, the only VAT codes that are authorized are those of the VAT type.
XXX: Nature reserved for site XXX
The site linked to the nature is not compatible with the invoice posting site.
Distribution reserved for site XXX
The site linked to the analytical distribution is not compatible with the invoice posting site.
Distributions total incorrect
The analytical distribution (amount) that has been entered cannot be validated because the total of the distributed amounts does not correspond to the invoice line amount.
Distribution line no 1: YYY Dimension reserved for site XXX
The choice of analytical allocation key is incorrect because one of the dimensions contained in it is linked to a site different to the invoice's.
XXX: Prohibited with the nature
The analytical dimension used is not accepted because the combination of this dimension with the analytical nature of the line has been defined as prohibited.
XXX: Prohibited with dimension XXX
The analytical dimension entered is not compatible with the other dimension entered. The combination of these two dimensions has been defined as prohibited.
Mandatory dimension on dimension type X
The posting on dimension type X having been defined as mandatory, the field must be entered.
Mandatory field
Some of the fields must be entered for the invoice posting to be carried out: the site, the customer code, the invoicing currency, the pay-by BP.
Tax incl. inferior to the Ex-tax
This non-blocking warning message simply warns the user that the ex-tax amount entered in the invoice header is inferior to the entered tax inc. amount. Both amounts can be modified as long as the journal is not performed.
One invoice per credit memo (Parameter BELVCS)
In the case of a credit memo linked to several invoices, a control prevents the credit memo from being attached to the various invoices. The user must create as many credit memos as there are invoices.
'Field error' 'Invoice Type'
'IN1 [LEG 1] : Document type IN2 : Record does not exist for the current legislation [LEG 1]'
This message is displayed when the legislation of the entry type linked to the invoice type does not match the invoice legislation.
Mandatory ex-tax or tax-incl. amount
When creating the invoice, this message is displayed if the Amount -tax field, or Amount +tax field, is not entered and the HEAAMTBPC - Cust. inv. header amt. ctrl. parameter (TRS chapter, INV group) is set to Ex -tax and Tax -incl. amounts to be entered. Entering the Amount -tax and Amount +tax is mandatory.
You can change the HEAAMTPBS parameter to Ex -tax and Tax -incl. amounts optional if you do not want these amounts to be mandatory for the selected company.
Mandatory ex-tax amount and tax-incl. amount
When creating an invoice, this message displays if the HEAAMTPBC – Cust. inv. header amt. ctrl. parameter (TRS chapter, INV group) is set to Ex -tax and Tax -incl. amounts to be entered. Entering the Amount -tax and Amount +tax is mandatory.
Totals different from header
This message displays if the if the Amount -tax and Amount +tax fields do not match the line summary amounts in the Total excluding tax and Total including tax fields when creating an invoice.
Whether this message displays is controlled by the WRNMSGBPC – Customer invoice warning msg. parameters (TRS chapter, INV group).
BP invoice creation impossible: Inconsistent invoice number versus previous invoice date
This error message displays when you try to sell a fixed asset with inconsistent invoice dates. The date sold entered in a BP customer invoice cannot be earlier than the date on the previous AR invoice, which is noted in the error message. This control is enforced when the Chronological control checkbox is selected in the Sequence number definition (GESANM) for the entry typed linked to the specified invoice type. As a result, the fixed asset is not sold.