Cashbook Statement Analysis of Transaction

Purpose

Creates the individual Cashbook Transactions that make up a Statement Transaction Batch

This dialog is used for:

1. Coding imported Statement Transaction Amounts
2. Manually creating a Statement Transaction Batch
3. Cashbook Journal entries

Access

1. Cashbook | Edit/View Electronic Transactions | 
2. Cashbook | Edit/ View Statement Transactions |  | 
3. Cashbook | Edit/ View Statement Transactions |  | 
4. Cashbook | Enter Deposits
5. Cashbook | Enter Withdrawals

Dialog Details

Details Specific Fields

Field	Explanation
Transaction Type	[F2] to select the Transaction Type required to determine where the transaction will be coded to Once this is selected, ‘Tab’ to open the module field The module label displayed will be restricted to accounts from the module that the Transaction Type belongs to
Module	[F2] or key the Account Code or GL code
Reference	Can be altered Will appear on the account transaction and printed on the Account Statement/Summary
Description	As above
Company	Display only - prepopulated
Amount	Will be prepopulated from the Electronic transaction browse when  is used Any other access point will allow entry of an amount
Tax Code	Will be prepopulated from the Transaction Type selected  May be changed

Direct Credit / Direct Debit transactions to be exported

When the Cashbook Transactions are being added to a Statement Transaction Batch so that a Direct Credit or Direct Debit file can be created, the below fields are also required

Field	Explanation
External Bank Account	The client bank account number should be entered
	If the transaction is for a client account, then pressing the  button will populate the field with the clients’ bank account number (Provided this has been entered on the Clients  record)
Bank Reference	This is the detail that will show on the client bank statement On a bank statement the bank reference is made up of three fields Entering a ‘/’ or ‘-’ between each word or phrase will split the bank reference between the reference, particulars and code fields on a bank statement E.g. Company/Repayment/CL111/ Notes:  For this functionality to work correctly a / or – MUST be entered after the last item Neither of these characters can be used as part of each bank reference field.  Example: use of P/ship will cause the system to recognise a field break meaning the information imported through your banking software will not be as expected.

• Related Articles

• Quick Code Cashbook Transactions

  Purpose This function is used for the coding of a Statement Transaction Amount as a single Cashbook Transaction Timing Whenever required following a bank statement Access Cashbook | Edit/View Electronic Transactions | Process To quick code a ...

• Statement Transaction Batch

  Purpose A Statement Transaction Batch is made up of one or many Cashbook Transactions. Direct Credit and Direct Debit files are Statement Transaction batches made up of specific cashbook transactions generated by a Vault process, or entered manually. ...

• Cashbook Statement Browse

  Purpose To provide a list of all Cashbook Statement Transaction Batches that have been entered to Vault To provide the ability to track where Cashbook Transactions have posted to To process Statement Transaction Batches Access Cashbook | Edit/View ...

• Splitting an Electronic Transaction

  Problem A transaction on the bank statement needs to be coded to more than one account. This assumes the transaction is not a repeating one (in which case the process would be quite different). Examples A single payment of $160.00 is received from a ...

• Cashbook Journals

  Purpose Cashbook Journals are used to move cash between the General Ledger and any accounts module Timing Cashbook Journals may be completed at any time Access The recommended access point is: Cashbook | Manual Reconciliation This allows immediate ...