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 (etc.). When issuing the invoice, the data required for accounting is recorded.
As for customer tracking (open item statements, reminders, payment management, etc.), the process is the same for invoices that come from the complete cycle or that come from entering a BP invoice.
Notes:
- 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 the invoices are used as the reference template (first/original recurrence).
Additionally, the invoice should not be modified if it is also used as the reference invoice. - For the Fixed Assets module:
When the SALINV - Sale invoice to generate (AAS chapter, FAS group) parameter is set to Yes, a BP customer invoice is generated automatically after validating the Asset disposal with a Sales reason. If 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 issue cannot be modified: the accounting date, the currency and customer of the Header tab and the amount, as well as all tax elements of the Lines tab.
French electronic signatures for sales invoices and journal entries
In compliance with French 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” on the How-to tab for details on implementing this feature. This document is intended for administrators and consultants who maintain and update Sage X3.
Exceptions
Data from invoices or journal entries posted before activating the electronic signature feature is not added to the DKSDATFRA table and therefore no electronic signature is created.
Legislations other than French do not generate electronic signatures.
The electronic signature is a record in the Electronic signatures table (DKSDATFRA) 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
Refer to documentation Implementation
Limitations
When the invoice is entered in tax-inc. mode and an additional or special tax code is present (entered or automatically loaded from the account), the amounts of the three tax levels must be entered manually.
Screen management
Posting customer BP invoices involves three tabs containing the characteristics of each part of the invoice body.
Header
Presentation
First, the key accounting information of the invoice must be entered:
- the site,
- the invoice type which determines the document category (invoice/credit memo/debit note/credit note), the automatic journal, the journal and journal type that will be used during document posting,
See the documentation on the customer invoice type.
- the document number (where a manual numbering range is authorized),
- the document posting date, by default that of its receipt in the folder,
- the customer identification code and the control account on saving the document.
These tabs are used to define:
- the invoice header,
- the invoice lines.
Once this information is entered, the invoice can be passed to accounting using the [Post] button
Specific options
STATISTICAL CODES
It is possible to associate statistical codes to each line of the invoice (and therefore the posting) to facilitate the gathering of statistics. A contextual menu provides this option once the line is entered.
SERVICE PERIOD
It is possible to stage the line amount (or the ex-tax amount) in analytical or general accounting according to a specific calendar.
This functionality can be accessed using the right click menu once the line is entered. To be operational, this functionality must be activated (activity code KIK and the general parameter ITAPRE) and the automatic journal KIK1 (Staging of Customer BP services) must exist.
ACCOUNT STRUCTURE:
Applying an account structure can be proposed by default after entering the ex tax invoice amount. The structure used is the one defined in the customer record, Financial tab.
A contextual menu provides this option at the very start of the invoice line entry.
The account structure is used to pre-define the group of accounting and analytical postings of a journal, and to pre-load them directly on invoice or journal entries. 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.
INVOICE => CREDIT MEMO
It is possible to transform an invoice directly into a credit memo. This option is available via the menu Tool bar \ Function \ Invoice --> Credit memo.
Close
Fields
The following fields are present on this tab :
Block number 1
|
This site, which must be a financial one, determines the site and the company for the entry posting. |
|
|
|
|
|
Invoice type code referencing the invoice category as well as the entry structure used upon accounting validation of the invoice. |
|
If the number is left blank, it will be automatically assigned upon validation. |
Block number 2
|
This date determines the accounting date of the generated journal. |
|
In this field, enter or select the customer for the invoice using the Lookup tool. To search using the auto select option, enter several characters of the customer name or code and press the Tab or Enter key. The selection window opens with a list of customers based on those characters. The results include active and inactive records. Auto selection is available if the AUTOSEL – Auto selection parameter (SUP chapter, INT group) is set to Yes. |
|
|
|
Enter the code for the BP (customer or supplier) control account initialized 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). No BP/Company tab on the BP record.When the customer or supplier code is specified, the Control account defined on the Financial tab on the first line of the accounting code is used. P BP/Company tab present on the BP record.For a document, the site and the customer or supplier code are the first information entered. The BP record is searched on the BP/Company tab to see if an exception line has been created for the entry site company and, if required, finds the customer or supplier accounting code. The account of the first line of the accounting code is then used. When the exception line is absent for the entry site company, the Financial tab of the BP record is referenced to identify its code. |
|
|
Close
Tab Header
Presentation
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 by default: Totals different from header. Use the WRNMSGBPC – Customer inv. warning msg. (TRS chapter, INV group) parameter to disable the display of this message. - The link between a credit memo and the original invoice via 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.
See the documentation on Default dimensions.
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.
Once the invoice has been saved, you can click Open items action to view the open items and the status of the related payment.
Close
Fields
The following fields are present on this tab :
Detail
|
This date is the source invoice's. |
|
This field is used to record the number or the reference of the source invoice. |
|
|
|
This field indicates the invoicing currency. All amounts are entered in this currency. |
|
|
|
|
|
|
|
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. |
|
|
|
Tis invoice is the one to which the credit memo is allocated. |
|
|
|
After invoice validation, the project reference the invoice is allocated to can no longer be modified. |
|
Field linked to the Belgian legislation. Reminder: 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:
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.
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 subject to activity code: KPO - Portuguese localization |
|
Field subject to activity code: KPO - Portuguese localization |
|
|
|
|
|
|
Block number 2
|
|
|
|
|
Enter the VAT management type associated with the customer invoice. |
|
These two radio buttons, initialized from 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.. |
|
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
|
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:
|
|
|
|
Indicates if the generated open items will have "to be put on the statement" or not. |
|
Indicates if the generated open items will have "to be relaunched" or not. |
Payment
|
This BP indicates the pay-by or paid BP |
|
|
|
This is the date from which the payment schedule is calculated. |
|
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. |
|
|
|
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 in advance or days late with respect to the open item date. |
|
You can manually enter up to three comments. Note: You can add content from the first comment to the Comment field on the Lines tab by entering // in that field on the Lines tab. |
|
This field is displayed only if the following conditions are met:
This field is initialized:
It can still be modified if it is set up to accept entries at entry transaction level and if the invoice is not validated. |
|
If the company and/or the pay-by BP is modified, the mandate reference is modified accordingly.
|
|
This field displays the IRS 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 value of 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.
|
|
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. 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. 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 for the invoice is determined by the Payment bank ISR field in one of the following functions. The system pulls the information 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.
|
Grid Analytical
|
|
|
|
|
The dimensions entered here will be used as default values for invoice lines. |
Close
Tab Lines
Presentation
The grid in the second tab 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. See the documentation on General accounts for further information.
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. See the documentation on the default dimensions.
Close
Fields
The following fields are present on this tab :
Grid Details
|
It is the line number. |
|
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. Specificities linked to intercompany invoices (GESBICI and GESBISI functions protected by the activity code INTCO - Intercompany transactions):
|
|
|
|
This check box is only available if the Control check box is selected in the Chart of accounts function (GESCOA). Select this check box to indicate that the account is associated with a BP. |
|
In certain fields on the screens, use of access codes have been incorporated. These codes are used to restrict access to data by certain users. In order that a field can have an access code available to a user, it is necessary that this code is present in this table. As a function of the rights which are assigned to the user, he/she can then consult or modify the field. The access codes are equally used to restrict access to certain functions started by buttons on the screens. It is necessary to assign each access code defined in the grid.
|
|
The choice of accounting allocation is determined by:
|
|
This field is used to specify if an invoice line is subject to discount.
|
|
Enter in this field the ex-tax amount of the recorded operation. |
|
When the account on the line is liable for tax, the tax field is accessible for entry. It is initialized with the tax code associated with the account or with the tax code associated with the rule. Based on the context, it is necessary to verify that this tax code corresponds to the tax actually applicable, or it should be modified. |
|
Indicate the default value of the tax code Sage Sales Tax (SST). This tax code is recognized by the Avalara system and is used to identify line types for fiscal purposes. |
|
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 reinitialized. |
|
No help linked to this field. |
|
This field is currently no longer used. |
|
You can manually enter a comment or add content from another field using the following characters:
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. |
|
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). |
|
The quantity is automatically calculated by dividing the Ex-tax amount (converted into reporting currency) by the work unit value. |
|
After invoice validation, the project reference the invoice line is allocated to can no longer be modified. |
|
This field is used to define the allocation methods for the line amount on the different dimensions of each dimension type.
For instance:
|
|
The setup determines whether the analytical dimensions can be modified. These are initialized in compliance with the default dimension setup.
In creation mode, as in modification mode, if an order line has been entered and the project code is modified, analytical dimensions are not reset. |
Totals
|
The discountable base is only displayed if the two following conditions are met:
The discountable basis depends on:
|
|
|
|
|
|
|
|
This field indicates the tax-incl. result including the tax calculation by tax basis. This information appear upon printing of the ARCTTC2 report. The detail of the tax incl. calculation is obtained by right click on the total amount.
To access the detailed fiscal statistics based in 'Sage Sales tax' (SST), click on the link of the tax-incl. total field. This option is only available if the document is imposed using SST. If SST is used, the recording and cancellation of a fiscal document are taken into account during the:
If the tax is not calculated, the invoice is not created.
|
|
|
Account
|
|
|
|
Close
Action icon
Account Inquiry
This button is used to access the account inquiry, and by default the account of the current line.
Statistical Codes
This button is used to associate statistical codes to each line of the invoice (and therefore the posting) to facilitate the gathering of statistics.
Prepayment apportionment
This button is used to stage the line amount (or the ex-tax amount) in analytical and general accounting according to a specific calendar. To be operational, this functionality must be activated [activity code KIT - and the general parameter ITAPRE - Analytical apportionment (LOC chapter, ITA group)] and the automatic journal KIK1 (BP customer analytical apportionment) must exist.
Account Structures
This button is used to assign an account structure for the line. The account structure is used to pre-define the group of accounting and analytical postings of a journal, and to pre-load them directly on entry. See the documentation on entry 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
Click this action in order to open a window displaying the note(s) associated with this customer.
This window may open automatically depending on the setup defined when creating the notes.
Notes are limited to a screen inquiry and cannot be printed.
For further information, see the documentation on Notes.
Close
Reports
By default, the following reports are associated with this function :
BPCINV : Customer BP invoice
BPCINV2 : Customer BP invoice
SIMFACCLI : Simulation customer invoices
FACTRSC : BP invoice list
This can be changed using a different setup.
Specific Buttons
|
|
The following fields are included on the window opened through this button : Grid Open item edit
Block number 2
Close This button is used to display or modify the open items associated with the current supplier invoice. Payment methods associated to open items cannot be modified from:
The open item lines are updated if there is a modification of the mandate reference in the header of a customer BP invoice. However, a modification of the mandate reference in an open item line does not cause a modification on the header mandate reference. Once the invoice has been validated, the mandate reference can still be modified in the open item entry grid, but not in the header. If an open item has been entirely or partially paid, it is not possible to modify the SDD payment method. This is because the mandate reference has already been used to pay a part of the payment. It is thus necessary to split the open item schedule to be able to change the payment method. |
|
This button is used to perform the accounting posting of the current supplier invoice in order to have its entry. |
Menu Bar
Zoom / Accounting Journal
This function is used to access the accounting journal generated further to the posting of the current supplier invoice.
Zoom / Analytical Journal
When a customer invoice plans a services spreading (at line level, right-click on 'Service provision period entered'), the analytical journals thus generated can be accessed in display mode [according to the automatic journal referenced in the GAUKIK1 - Customer invoice: services parameter (TRS chapter, ACC group)].
Functions / Accounting Cancellation
Accounting cancellation is not allowed for payments processed through Sage Exchange or Sage Pay.
Functions / Invoice Credit memo
This function is used to directly transform an invoice into a credit memo. X3 then requests the confirmation of the 'Creation of an credit memo invoice' and proposes:
Header
- An 'Invoice type': the invoice type is initialized by default with the 1st 'Credit memo' invoice type found in the Invoice type table;
- A 'document no.' that is empty can be entered (case where a manual range is reserved) or will be automatically assigned on creation of the invoice
- An automatic loading of the 'Invoice number' field with the original invoice number.
- Other header information can be modified such as in the case of the modification or copying of the invoice.
Line
- An automatic pre-loading of the lines with GLs, the VAT postings and the analytical postings from the source invoice.
- The line information can be modified such as the modification or copying of the invoice.
- It is also possible to completely delete one or more lines.
Functions / Credit card processing
Presentation
AFC/GESPRH/80/40
Close
Fields
The following fields are present on this tab :
Block number 1
|
This field displays the document number. |
|
This field displays the amount remaining to be authorized for the document. |
|
This field is used to display the customer that will be used upon adding or saving payment cards. |
|
This field is used to display the company linked to the processing code. |
Account information
|
This check box is automatically selected if a saved payment card does not exist on the customer record. If the customer record is assigned a default card, this check box is cleared and the primary card information for the account nickname displays. If a saved payment card exists on the customer record, but a default card does not exist, this check box is cleared and the account nickname must be entered or selected. If the customer's BPC type is miscellaneous, this check box is automatically selected. Select the check box for One time use card to add a payment type to use one time for this order or shipment. The data for payment and billing information is not stored and you do not need an Account nickname. |
|
Enter a unique account nickname to identify this payment card. You can select an existing payment card for this customer or you can create a new payment account by entering a new account nickname.
|
|
Enter a processing code defined by the user. This code identifies the link to the company and account defined in the Payment gateway setup.
|
|
This field is used to display the payment type used. The valid values include Visa, MC, AMEX, and others. |
|
This field displays the last four numbers of the payment card. |
|
This field displays the expiration date of the payment card. |
Authorization
|
Select this check box to enter transaction information for Sage Exchange transactions that are processed manually outside of Sage X3. This field is available only if the parameter MANAUTH is set to Yes at the user level. |
|
This field displays the authorized amount of the payment card processed by Sage Exchange. |
|
This field displays the authorization code for the transaction. |
|
This field displays the authorization date of the payment card. |
|
This field displays the status of the transaction by payment card. |
Billing information
|
Enter the cardholder name. If a saved payment card is selected, the cardholder name displays and cannot be changed. If the One time use card check box is selected, the cardholder name must be entered and the information is saved to the payment card transaction. |
|
Check this box to display the default billing address of the customer.
|
|
Enter the country of the invoicing address of the cardholder.
|
|
Enter the billing address of the cardholder.
|
|
Enter the invoicing status of the cardholder.
|
|
Enter the postal code of the cardholder.
|
|
Enter the town of the invoicing address of the cardholder.
|
|
This field displays the contact e-mail address of the customer from the transaction. |
Payment
|
This field displays the payment amount to be applied to the payment card during the invoice allocation. |
|
This field is used to display the payment date used during the transaction. |
|
Payment number associated with the transaction. |
Grid History
|
This field displays the document number that was processed against the selected payment card. |
|
This field displays the sequence number counter of the document, processed or the selected payment card. |
|
This field displays the transaction type of the document, processed for the selected payment card. |
|
This field displays the invoiced amount of the document processed for the selected payment card. |
|
This field displays the amount of the document that was originally authorized or, if it was rejected, the amount attempted to authorize. |
|
This field displays the processing date of the transaction for the selected payment card. |
Close
Address / Billing address
Address / Payment address
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
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.
: setup code does not exist
This message appears when a setup 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.
Non existent 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 A/R invoice, which is noted in the error message. This control is enforced when the Chronological control check box 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.