 |
|
Transaction Sampling: How to Read the Summary by Counts Report
|
|
| |
Summary: Learn how to read the transaction sampling management report summarized by counts.
The Summary by Counts report provides a count of transaction sampling errors by problem type. This report is divided into three sections: |
| Report section |
What it shows |
 |
Transaction View |
The most recent status of sampled transactions
- Population and sampled count figures will not change.
- Reviewed and Not Reviewed counts will change based on departmental review and correction.
- All samples are initially listed as Not Reviewed.
- Once reviewed, errors marked as Not OK must be categorized with a problem code.
- This view only shows transactions with problem codes currently marked and not corrected.
- Your goal is to reduce the Not Reviewed count to zero.
|
|
Transactions Status Code View of Samples |
A historical view of transactions identified with problem codes
- A transaction may have more than one problem code.
- This view reflects the original problem code even after a transaction with a problem code is corrected.
- Pay attention to the variance rate; it shows where you need to focus your attention.
|
|
Aging Information |
Counts of Not Reviewed Transactions and Status Codes
- Information is aged as of current date, not monthly.
|
|
|
Questions? If you have technical questions about the Ledger Review tool, contact Mojgan Amini, (858) 534-1023. For policy questions, contact Debbie Rico, (858) 822-2797. |
|
|
