A/P-A/R accounting >  Inquiries >  Banks  

Display all Hide all

Use function to view the transactions for a given bank. In addition to viewing the payments remitted to the bank, you can consult payment forecasts such as supplier or customer payments, rents, loans, salaries, etc.

Setting up bank account records linked to cash accounts to perform a reconciliation

You can define a bank account record at the company or site level that is linked to a normal cash account or a control cash account plus business partner. To reconcile these records, you need to ensure that bank records defined at the same level do not share any of the following definitions: bank, company, site, account, and business partner. The bank record definitions need to be unique.

In reconciliation functions, journal entry lines that are considered are those posted to the site or company as defined in the bank account record and on the cash account plus business partner, as defined in the bank account record. As a result, when several bank account records are created for the same company or site and with the same bank account (plus business partner), the exact same journal entry lines display when running reconciliation functions.

See Bank accounts - Management for a detailed example.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

The inquiry is performed on a single tab.

Header

Presentation

  • the bank code to be inquired:
    the company to which this bank code belongs is then deduced (Company field) and if this bank is reserved for a single site, the latter is also mentioned (Site field), otherwise, the site code remains blank (in this case, a bank account is inquired for a given company, all sites included).
  • the inquiry start dates and end dates:
    the date range makes it possible to mention on which period the journals must be viewed.
    The end date is compulsory because it also makes it possible to display the actual balance.
    If the start date corresponds to the first day of the fiscal year, the carry forward entry is systematically taken into account.
    If the selected date range straddles two fiscal years, the carry forward entry is substituted with the detail of the carry forward entries.

Close

 

Fields

The following fields are present on this tab :

Selection

Specify the payments to be viewed, by entering:

  • A bank
  • an accounting date range
  • A site (optional).
  • Start date (field DATDEB)

 
  • End date (field DATFIN)

 

Other criteria

 

Specify the payments to be viewed, by entering:

  • A bank
  • an accounting date range
  • A site (optional).
  • Balance (field BLC)

 

 

Close

 

Tab number 1

Presentation

Once the criteria have been entered, the makes it possible to

  • enter, on a given date, the actual balance in the currency in which the bank account is kept.
  • complete the tab with the lines corresponding to the entered criteria
  • display the virtual balance, that is, the actual balance of the bank, to which are added the payments that have not been remitted to the bank.
    The payments that have not been remitted to the bank yet appear in a different color so that they can be easily identified.

Close

 

Fields

The following fields are present on this tab :

Grid Details

  • Payment no. (field NUMPAY)

 
  • Batch code (field PAYLOT)

 

 
  • Control (field BPRSAC)

 

 

 
  • Description (field DES)

 
  • Sign (field SNS)

 

 
  • Amount in currency (field AMTCUR)

 
  • Bank amount (field AMTBAN)

 
  • Status (field STA)

 
  • Accounting date (field ACCDAT)

 
  • Reference (field REF)

 
  • Source date (field ORIDAT)

 
  • Due date (field DUDDAT)

 
  • Bank date (field BANDAT)

 
  • Value date (field VALDAT)

 
  • Date created (field BILDAT)

 

 
  • Bank account number (field BID)

 
  • Drawee reference (field BPRREF)

 
  • Check no. (field CHQNUM)

 
  • Bank card number (field CRDNUM)

 

 
  • Order no. (field NUM)

 
  • Bollato sequence number (field BOLLATO)

 

 
  • Entry date (field ENTDAT)

 
  • Rate date (field RATDAT)

 
  • Original doc (field BPRVCR)

 
  • Doc date (field BPRDATVCR)

 

 
  • Virtual book balance (field AMTBLCVIR)

 

Block number 2

  • Theoretical balance (field TOTBLCVIR)

 

 

Close

 

Action icon

Payments

This zoom is applied to the records generated by the A/P-A/R Accounting module.

Accounting Journal

This zoom, which can be applied to all the records, makes it possible to view the accounting journal.

 

Close

 

Specific Buttons

The provides access to the other criteria of the inquiry that are partly displayed at the top of the inquiry screen. There are selection criteria that are:

  • the bank code, start and end date, company and site code
  • a filter on the transaction type and payment mode
  • a filter is also placed on the status of the payment entries to be taken into account, the following status being possible for a payment: Entered, Accepted, in Draft Management, Slip entered, Slip on file, Paying bank entered, Intermediate deposit, Bank deposit, Draft management devaluation, Unpaid.
  • all payments: shows all payments regardless of their status
  • validated payments: are excluded the payments that were no validated during their first posting phase
  • payments in bank: are excluded payments in status Entered, Accepted, in Draft Management, Slip entered, Slip on file, Paying bak entered and Intermediate posting It this filter is placed, the actual balance is equal to the virtual balance
  • reconciled payments: this only takes into account the payments deposited in bank and that have been reconciled.

There are also presentation criteria (by payment date / accounting date or by Type of transaction) and display criteria (screen code).
When the criteria definition function is used, it is possible to store the modified parameters thanks to this button. . Then, a window allows a code identifying the memorized parameters to be entered. The is used to recall criteria memorized under a given code (the code must then be entered). When entering the account inquiry function, the parameters stored under the STD code are recalled by default if they exist.

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation