Blocking Transactions from Appearing on Member Statements
Helpful Resources
Overview
In certain situations it might be necessary to prevent errors and their corrections from being printed on a member's statement. CU*BASE does not delete the transactions from the member's records; the error and the correction simply do not print on the statement. You will still be able to view all posted transactions through any inquiry options.
Never block a transaction or series of transactions where the ending balance before the errors and corrections is different from the ending balance after the errors and corrections. This will cause the statement balances to appear to be incorrect.
The following example shows the actual transaction sequence as it would appear in an inquiry, as well as how the statement would appear if the transactions were blocked:
Inquiry screen showing all transactions:
|
Date |
|
Transaction |
Balance |
|
|
01/12/01 |
+ |
50.00 |
50.00 |
|
|
01/12/01 |
+ |
100.00 |
150.00 |
error |
|
01/12/01 |
+ |
25.00 |
125.00 |
|
|
01/12/01 |
- |
100.00 |
25.00 |
correction |
Statement with error and correction blocked:
|
Date |
|
Transaction |
Balance |
|
01/12/01 |
+ |
50.00 |
50.00 |
|
01/12/01 |
+ |
25.00 |
125.00 |
In this situation, it would be preferable to print the error and correction on the statement, so that the member can see the correct balance. If you are unsure about whether or not the block a transaction, contact a CU*BASE client service representative.
To Suppress Transactions from Member Statements
-
Transaction Reversal - If making an adjustment using the Member Transaction Reversal feature, use the Suppress transaction from statements flag.
-
Member Account Adjustment - If making an account adjustment using Member Account Adjustment, Tool #918 Update Transaction Desc/& IRA/HSA Post Codes can also be used to block a transaction from appearing on a member's statement. It may be necessary to run a “full” version of the member's transaction history to determine the transaction sequence number.