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.

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<>"",
[F:DAE]DES)+string$([F:DAE]DES="","NA")

Prerequisites

Refer to the documentation on Implementation

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

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.
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.

After saving an invoice, select Open items action to view the open items and the status of the related payment.

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.

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.

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

Open items

Select this action to display or modify the open items associated with the current supplier invoice.

Payment methods associated to open items cannot be modified from: a Sage Exchange Processing payment method towards a payment other than Sage Exchange, a payment method other than Sage Exchange towards a Sage Exchange Processing payment method.

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.

After the invoice is 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.

Validation Select this action to perform the accounting posting of the current supplier invoice in order to have its entry.
QR-data

This action is available if the KSW - Swiss legislation activity code is active and if the current site SWIPURQRC - QR code entry parameter (LOC chapter, SWI group) is set to Yes.

Select this action to import the QR code content read by an ISR/QR reader. The data is verified and the gross amount is displayed, but cannot be modified. You can enter an input tax that can be used later to calculate the net amount.

When you select OK, Sage X3 identifies the pay-to BP. If more than one bank account is found, you need to select one from the list. If no bank account is found with the customer number or QR-IBAN, you can access the supplier maintenance and select or enter a new pay-to BP and add the customer number in the bank details, if necessary).

See the Swiss localization guide for detailed information on QR-bills. An ISR/QR reader or scanner is not provided by Sage nor is it a component of Sage X3.

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.

Tables used

Refer to the documentation on Implementation