The Banking Entry (31.1) function is the single entry point for creating, maintaining, and allocating statements. You can modify existing bank statements, depending on their status. You can also add new lines to an allocated statement.

The system lets you reconcile a banking entry line created in one entity with open items created in another entity. In order to process this intercompany transaction, intercompany accounts must be defined in Domain Create for the domains involved in the transaction. For more information on processing intercompany transactions, see Intercompany and Cross-Company Transactions.

Depending on your organization’s business procedure and your access rights, you can use banking entry in different ways:

This flexibility supports segregation of duties if one individual creates the statement lines from a paper copy, and another person performs the actual linking to accounts, invoices, and payments. You can assign these activities to different roles using Role Permissions Maintain. If you do not have access to the Banking Entry Allocate activity, you cannot use the allocation features in Banking Entry.

For more information on roles and permissions, see QAD Security and Controls User Guide.

You can modify the following fields on Not Allocated or Partly Allocated statements:

You can only delete statements that have a status of Not Allocated.

Banking entries can be saved in draft format when Draft Instances is selected in Change System Settings (36.24.5.1). When you save a record in draft format, none of the system validations are performed. You can then return later to complete the record by choosing the Banking Entry Browse Drafts activity and selecting the record you want to finish from the list. For more information on drafts, see Introduction to QAD Enterprise Applications User Guide.

For more information on Change System Settings, see QAD System Administration User Guide.