Customer situation

• BP (field BPR)

The open items to inquire are filtered by entering:  

• a paying BP, a movement BP or a risk BP.
• a company/a site or a group of companies. The site is optional.

The reference date is used to classify and totalize the amounts by intervals in the open item schedule.

• Payment BP (field BPRPAY)

• Risk BP (field BPRRSK)

• Company (field CPY)

The information to be shown on screen are refined by entering a Company / Site or a group of Companies. The site is optional.

• The field Company can include a homogeneous or heterogeneous group of Companies.
• If the field Company is left empty, the search will be carried out on all Companies.

• Site (field FCY)

• field DAT

This field is used to specify a reference date: the time ranges will be calculated from this date.

• Function (field FNCCNT)

This drop-down menu is used to select the contact function.
Changing the function makes it possible to display the name and telephone number of the first contact associated with this criteria.

• Contact (field CNT)

This automatic field indicates the main contact person for the displayed BP, along with its title and telephone number.

• Telephone (field TEL)

Telephone number.

The format depends on the country.

• Recalculation (field RECALC)

• Type (field TYP)

Each accounting journal entered is linked to a given type. The journal type corresponds to the nature of the entered posting: customer invoice, miscellaneous operations, cash receipt, etc.

This information comes with management rules relating to VAT, reminders, etc. It is one of the key elements of the journal entry.

The setup of the selected journal type determines if you can open or close the propagation to the manual ledgers.

The journal type prevails and interrupts the propagation to the other ledgers of the company of the entry site.

• Order no. (field NUM)

This field represents the unique identifier of a journal in a journal type.
The journal number is generated automatically via a counter linked to the journal type. This number can also be entered manually, if such an option has been defined when creating each journal type.
If the entry of the journal number is authorized and this number is blank, the journal number is generated according to the setup of the sequence number counter associated with this type of journal.

• Currency (field CUR)

Transaction currency.

• Due date (field DUDDAT)

Open item payment due date.

If the MAXPD - Maximum period (companies) activity code is activated, a blocking message is displayed if the last due date is greater than the period specified, depending on the case, at the level of the following parameters or of the Contractual period possibly specified at the BP level.

• DMAXPAYP - Maximum period (Public sector) (TC chapter, RSK group) when the BP is a public sector organization.
• DMAXPAY - Maximum period (companies) (TC chapter, RSK group) when the BP is a private sector company.

• Bill-to/Order BP (field BPR)

Code identifying the BP that can have various roles based on the context:

• Customer,
• Supplier,
• Carrier,
• Sales rep,
• Miscellaneous BP,
• Prospect,
• Service provider

• Pay-by (field BPRPAY)

Paying customer loaded by the bill-to customer.

• Accounting date (field ACCDAT)

Date on which the transaction is posted. The fiscal year and the accounting period are determined starting from this date.

• Risk BP (field BPRRSK)

• Group BP (field BPRGRU)

• Source document (field BPRVCR)

It is the number printed on the supplier invoice. A check accompanied with a warning message is carried out so as to avoid entering the same number several times. This field can be deactivated by the entry transaction.

• Document date (field BPRDATVCR)

Enter the invoice date. This field defaults to today's date.

• Internal number (field ACCNUM)

• Payment method (field PAM)

The payment method defines the payment means (check, cash, bank card, instrument etc.).

• Early discount/Late charge (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.

• Paid (field PAYCUR)

Amounts of the payments or equivalent (matching) having gone through the first posting phase, expressed in transaction currency.

• Company paid (field PAYLOC)

Amounts of the payments or equivalent (matching) having gone through the first posting phase, expressed in the bookkeeping currency.

• Provisional (field TMPCUR)

Amounts of the payments that have not gone through the first posting phase, expressed in transaction currency.

• Company provisional (field TMPLOC)

Amounts of the payments that have not gone through the first posting phase, expressed in the bookkeeping currency.

• Reminder (field FLGFUP)

Reminder indicator

• Reminder level (field LEVFUP)

Reminder level

• Reminder date (field DATFUP)

Date of the reminder issue day.

• Dispute code (field DPTCOD)

• Pay approval (field FLGPAZ)

Level of payment approval.

• Statement (field SOI)

Statement indicator
If this indicator is set to 'Yes', the open items calculated from the payment conditions are taken into account by the automatic generation processing of customer statements.

• Statement number (field SOINUM)

• Prepayment deducted (field DINAMT)

• Prepayment to deduct (field IBDAMT)

Amount of the prepayments to be deducted from the initial open item.

• Tax (field VAT)

This field is used to specify a tax code.
This code can be accessed by right click or by tunnel and is linked to the tax type specified in the screen (additional tax, provincial tax, etc.): For instance, when you select the provincial tax, the tax rates associated to this type of tax will be those specific to the provincial tax.
 The rule set up in the tax code must be identical to the one specified in this screen.

• Expected issue date (field EXPSENDAT)

Date on which the open item issue has been planned.

• Issue date (field SENDAT)

Prepayment issue date

• Prepayment issued (field SENINS)

Flag indicating wether or not the prepayment has been issued.

• Factor (field BPRFCT)

• Receipt (field FCTVCR)

• Site (field FCY)

This code is used to identify the site concerned. It is unique for each site.

• Company (field CPY)

• field AMTCUR1

Amount expressed in the transaction currency. It displays the open item amount in the various time periods set up for the inquiry.

• field AMTLOC1

Amount expressed in the bookkeeping currency. It displays the open item amount in the various time periods set up for the inquiry.

• field AMTCUR2

• field AMTLOC2

• field AMTCUR3

• field AMTLOC3

• field AMTCUR4

• field AMTLOC4

• field AMTCUR5

• field AMTLOC5

• field AMTCUR6

• field AMTLOC6

• field AMTCUR7

• field AMTLOC7

• field AMTCUR8

• field AMTLOC8

• field AMTCUR9

• field AMTLOC9

• field AMTCUR10

• field AMTLOC10

• Transaction currency amount (field AMTCUR)

Amount expressed in the selected transaction currency.

• Local currency amount (field AMTLOC)

• field LIBTOT1

• field AMTTOT1

Amount expressed in currency:

• in company currency if the inquiry is carried out on a company or a homogeneous company group,
• in folder currency if the inquiry is carried out on all the companies or on a heterogeneous company group.

It displays the aggregated balance of the open items in the various time periods set up for the inquiry.

• field PER1

• field POUR1

• field LIBTOT2

• field AMTTOT2

• field PER2

• field POUR2

• field LIBTOT3

• field AMTTOT3

• field PER3

• field POUR3

• field LIBTOT4

• field AMTTOT4

• field PER4

• field POUR4

• field LIBTOT5

• field AMTTOT5

• field PER5

• field POUR5

• field LIBTOT6

• field AMTTOT6

• field PER6

• field POUR6

• field LIBTOT7

• field AMTTOT7

• field PER7

• field POUR7

• field LIBTOTLOC

• field AMTTOTLOC

Amount expressed in currency:

• in company currency if the inquiry is carried out on a company or a homogeneous company group,
• in folder currency if the inquiry is carried out on all the companies or on a heterogeneous company group.

It displays the aggregated balance of the open items in the various time periods set up for the inquiry.

• field POURTOT

• field ACCCUR2

• Description (field LIBTOT)

• Amount (field AMTTOT)

Amount expressed in currency:

• in company currency if the inquiry is carried out on a company or a homogeneous company group,
• in folder currency if the inquiry is carried out on all the companies or on a heterogeneous company group.

It displays the aggregated balance of the open items in the various time periods set up for the inquiry.

• Risk (field TOTRSK)

Global risk = Commercial risk + Financial risk, for the bill-to BP, the company/site combination and all collective accounts included. It is expressed in transaction currency or bookkeeping currency depending on the inquiry setup..

• Authorized credit limit (field OSTAUZ)

Maximum credit amount authorized for this customer. It is used if the customer is declared as controlled in the credit control field. It is expressed in the bookkeeping currency.

• Types (field LEVCTL)

This field recalls the type of control defined for the BP.

• Controlled: The customer can be delivered if their credit level is lower than their authorized credit level.
• Free: The customer can always be delivered.
• Blocked: the customer can no longer be delivered.

According to the chosen parameter, the credit:

• Is checked by folder or accounting company,
• can take the loans and/or the order book.

• Credit control level (field OSTCTL)

• Rate origin WIP ctrl. (field OSTCHGTYP)

This zone recalls the type of credit for this BP.

• Revised: the amounts are converted into current date according to the type of credit defined in the Reveised control type parameter.
• Archived: amounts already converted for the various entries are cumulated.

If the company field is empty, i.e. there is an heterogeneous group of companies, the conversion will be done into folder currency (defined with the CURSHRFLD parameter), must be into the revised currency.
If the Company field concerns a group of homogeneous companies, the conversion will be done into company currency (defined as the revised currency or history currency according to the Credit control origin parameter.

• Accounting balance (field LIBSOL)

Amount that represents the balance of the account flows concerning accounts that could have an impact on the accounting balance. It is expressed in the bookkeeping currency.

• Credit (field OSTTOT)

Global authorized credit, taking into account the accounting balance, the shipments in progress, the shipments not invoiced, the invoicing in progress, and, as an option, the orders in progress, order loans, deliveries on loans and notes payable/receivable.
It is expressed in the bookkeeping currency.

• Credit insurance (field CDTISR)

Amount of the insurance subscribed to specialized organisms (sfac and others) for the cover of the customer risk in case of default. This amount is expressed in the folder currency.

• On order + (field ORDBPIATI)

Amount of the non-delivered (customer) or received (supplier) orders, for the company/site combination, all collective accounts/groups of collective accounts included. It is expressed in the bookkeeping currency.

• field LNDBPIATI

Amount expressed in the bookkeeping currency for loan orders.

• field DLVOST

Amount expressed in the bookkeeping currency of non-validated deliveries.

• Delivered not invoiced + (field NIVDLV)

Amount of the non-invoiced deliveries (Customer) or non-invoiced receipts (Supplier) for the Company/Site combination, the bill-to BP, all collective accounts/groups of collective accounts. It is expressed in transaction currency or bookkeeping currency.

• field LNDDLV

Amount expressed in the bookkeeping currency of loan deliveries.

• Invoices not posted + (field NPTINV)

Amount of the non-validated invoices, for the company/site combination, all collective accounts/groups of collective accounts included. It is expressed in the bookkeeping currency.

• Commercial risk (field OST)

Commercial risk: It concerns the bill-to BP, at company/site level, including all the collective accounts.

• For the customers:
  • + Orders in progress,
  • + In order loan,
  • + The deliveries in progress,
  • + Delivered not invoiced,
  • + Delivered on loan,
  • + Invoiced not posted,
  • = Commercial risk.
• For the suppliers:
  • + Orders in progress,
  • + Received not invoiced,
  • + Invoiced not posted,
  • = Commercial risk.

• Non-matched credit notes - (field CNONIP)

Amount of the unmatched credit memos, expressed in the bookkeeping currency of the Company/site combination.

• field INV

Amount expressed in the bookkeeping currency for invoices.

• field INVNBP

Amount expressed in the bookkeeping currency for invoices that do not have the status "Approval payment".

• Provisional payments + (field PAYNEX)

Amount of the recorded payments who did not go through any posting phase, for the pay-by BP, the company/site combiantion and the collective account/group of collective accounts. It is expressed in the bookkeeping currency.

• Notes P/R 1 + (field NYTBIL1)

Amount of the open items in the portfolio of notes payable/receivable (from 1 to 3) for the company/site and the pay-by BP, all collective accounts included. The notes P/R posting implies that the payment method has been included in the process. It is expressed in the bookkeeping currency.

• Notes P/R 2 + (field NYTBIL2)

• Notes P/R 3 + (field NYTBIL3)

• Financial risk (field BLC)

Financial risk: It concerns the Paying BP, at the company/site level.

• For the customers:
  • - Unmatched credit memos
  • + Open items approved for payment
  • + Open items not approved for payment
  • + Provisional payments
  • + Draft managements 1..3  (taken into account as an option in the financial risk)
  • = Financial risk.
• For the suppliers:
  • - Unmatched credit memos
  • + Invoices
  • + Provisional payments
  • + Draft managements 1..3  (taken into account as an option in the financial risk)
  • = Financial risk.

• field ACCCUR3

• Description (field LIBEL)

• Amount (field AMT)

• Description (field DES)

• Date (field DAT)

• Document no. (field NUM)

The "Customer since", "Last quote, order, shipment, invoices"fields are for the Bill-to/Sold-to customer for the Company/Site combination. The "Last payment, doubtful receipt and reminder" fields are for the paying-customer for the Company/Site combination. They can be justified via right click.

"Highest reminder level":It is the maximum reminder level observed for the Pay-by customer.

"Number of doubtful receipt entries"  (respectively "doubtful receipt entry"): It is the number (respectively, cumulated amount) of returned, unsettled payments entered via the entry of doubtful receipt entries, independently of the question about what is going to happen later to these doubtful receipt entries.

"Average payment time": This is an average, which is derived from the difference in number of days between the invoice accounting date and the payment date.

"Early/late payment": This is an average, which is derived from the difference in number of days between payment date and the due date of the invoice. A case of late payment is not signalled, the inverse case where the customer pays in advance of the due date, the number of days will be preceded by a "-" sign.

Not paid / average lateness : expresses for the late and unpaid invoices, the average number of days late. A case of late payment is not signalled, the inverse case where the customer pays in advance of the due date, the number of days will be preceded by a "-" sign.

For instance:

BP situation with a pivot date of 03/03/2005 :

Average payment time : [(58 days*100)+( 57*200)] / 300 = 57,33 days is the average payment time.

Early/late payment : [(29 days*100)+(28*200)] / 300 = 28,33 days is the average payment lateness with respect to the due date of the invoices.

Not paid / average lateness : [(27 days*300) /300] = 27 days is the average lateness for late and unpaid invoices on the day the inquiry is made. The INV004 is excluded from the calculation because the due date is later than the inquiry date.

The summary of the commercial actions for the sold-to BP can be viewed in the "actions" section:

- First contact date : first commercial action carried out and the type.

- Date of last contact : most recent commercial action carried out and the type.

- Next contact : next commercial action to be carried out and the type.

"Order movement history" and "loan order"represent the sum of the orders received from this partner since they became a customer.

• Amount (field AMT)

• field UNPNBR

"Number of doubtful receipt entries"  (respectively "doubtful receipt entry"): It is the number (respectively, cumulated amount) of returned, unsettled payments entered via the entry of doubtful receipt entries, independently of the question about what is going to happen later to these doubtful receipt entries.

• field UNP

• field MAXFUPLEV

The "Customer since", "Last quote, order, shipment, invoices"fields are for the Bill-to/Sold-to customer for the Company/Site combination. The "Last payment, doubtful receipt and reminder" fields are for the paying-customer for the Company/Site combination. They can be justified via right click.

"Highest reminder level":It is the maximum reminder level observed for the Pay-by customer.

"Number of doubtful receipt entries"  (respectively "doubtful receipt entry"): It is the number (respectively, cumulated amount) of returned, unsettled payments entered via the entry of doubtful receipt entries, independently of the question about what is going to happen later to these doubtful receipt entries.

"Average payment time": This is an average, which is derived from the difference in number of days between the invoice accounting date and the payment date.

"Early/late payment": This is an average, which is derived from the difference in number of days between payment date and the due date of the invoice. A case of late payment is not signalled, the inverse case where the customer pays in advance of the due date, the number of days will be preceded by a "-" sign.

Not paid / average lateness : expresses for the late and unpaid invoices, the average number of days late. A case of late payment is not signalled, the inverse case where the customer pays in advance of the due date, the number of days will be preceded by a "-" sign.

For instance:

BP situation with a pivot date of 03/03/2005 :

Average payment time : [(58 days*100)+( 57*200)] / 300 = 57,33 days is the average payment time.

Early/late payment : [(29 days*100)+(28*200)] / 300 = 28,33 days is the average payment lateness with respect to the due date of the invoices.

Not paid / average lateness : [(27 days*300) /300] = 27 days is the average lateness for late and unpaid invoices on the day the inquiry is made. The INV004 is excluded from the calculation because the due date is later than the inquiry date.

The summary of the commercial actions for the sold-to BP can be viewed in the "actions" section:

- First contact date : first commercial action carried out and the type.

- Date of last contact : most recent commercial action carried out and the type.

- Next contact : next commercial action to be carried out and the type.

"Order movement history" and "loan order"represent the sum of the orders received from this partner since they became a customer.

• Average payment lead time (field LTIPAY)

Average payment time: This is an average, which is derived from the difference in number of days between the invoice accounting date and the payment date.

For instance:

BP situation with a pivot date of 03.03.07 :

[(58 days*100)+( 57*200)] / 300 = 57,33 days is the average payment time.

• Early/Late payment (field LATPAY)

Early/late payment: This is an average, which is derived from the difference in number of days between payment date and the due date of the invoice. A case of late payment is not signalled, the inverse case where the customer pays in advance of the due date, the number of days will be preceded by a "-" sign.

For instance:

BP situation with a pivot date of 03.03.07 :

[(29 days*100)+(28*200)] / 300 = 28,33 days is the average payment lateness with respect to the due date of the invoices.

• Unpaid/Avg. days (field LATPAY2)

Not paid / average lateness: expresses for the late and unpaid invoices, the average number of days late. A case of late payment is not signalled, the inverse case where the customer pays in advance of the due date, the number of days will be preceded by a "-" sign.

For instance:

BP situation with a pivot date of 03.03.07 :

[(27 days*300) /300] = 27 days is the average lateness for late and unpaid invoices on the day the inquiry is made. The INV004 is excluded from the calculation because the due date is later than the inquiry date.

• field CNTFIRDAT

The summary of the commercial actions for the sold-to BP can be viewed in the "actions" section:

• First contact date: first commercial action carried out and the type.
• Date of last contact: most recent commercial action carried out and the type.
• Next contact: next commercial action to be carried out and the type.

• field CNTFIRTYP

• field CNTLASDAT

• field CNTLASTYP

• field CNTNEXDAT

• field CNTNEXTYP

• field ORDBPCATI

"Order movement history" and "loan order"represent the sum of the orders received from this partner since they became a customer.

• field LNDBPCATI

• field ACCCUR4