Click to return to BOL home page
Banker Store Read A Reg Vendor Connect Career Connect Learning Connect Bankers Information Network
 

Support for BOL is provided by:

MAIN CONTENT 
Compliance

    Agency Road Maps

    Alphabet Soup

    Compliance Tools

    FACTA/FCRA

    OFAC

Lending

    FACTA/FCRA

    Lending Tools

    SCRA

Marketing

Operations

    Check 21

    Operations Tools

    SAR Resrch Guide

Security

    AML/BSA

    Bank Robbery

    Counterfeits

    ID Fraud/Phishing

    Security Tools

Technology/eBanking

    Info Security


SPECIAL AREAS 
BOL Archives

BOL Blogs

Briefing Archive

Calendar

Court Watch

e-Card Exchange

Examiner's Corner

Executive Briefing

HR Corner

Infovault

Launch Pad

Regulator Roadmaps

Risk Management

Site Map

Site Orientation

Top Stories


~ ~ ~
SERVICES 
CrimeDex

Em@il Education

ID Verification


~ ~ ~
SHOP 

Banker Store

Bankers Info Ntwk
Vendor Connect

CONNECT 

Career Connect

Learning Connect

Vendor Connect

Guru Central

INTERACT 

Ask a Guru
Bankers Threads

Contact Us

Give Us Feedback


TOOLS 

BOL Toolbar

60 Second Solutions

Alphabet Soup

Banker Tools

BOL Forms

FUN 

BOL Recipes

eCard Exchange

LEARN MORE 


About Our Sponsors
About Us






Print Friendly! Email This Article! Discuss NOW!


An Auditor's Viewpoint on Critical Data Changes
by Eileen Shannon, Independent Audit Associates, Inc.

I read BOL Guru John Burnett's response to a question concerning the verification of master file changes (file maintenance). In his response, he commented that a random sampling of the maintenance input from a system report to the source document would be acceptable. While I agree that a 100% review is not practical, we use a different approach.

We suggest to our clients that they identify "critical" data changes (ex. name or address, interest rate, loan delinquency history, advancing due dates on loans, etc.) that may be used for fraudulent purposes. We suggest once the "critical" changes have been defined, 100% of those changes be verified. This verification would include a procedure where the source document is compared to the system report for accuracy and to ensure the change was properly documented and approved.

After these items have been reviewed, the maintenance report should be scanned for "critical" date changes that were made without documentation. Research should be done on these file maintenance changes.

First published on BankersOnline.com 8/25/03



Open the newly required
"UAD" .XML appraisals
Download Free UAD Reader


Privacy Policy    Disclaimer   Recommend This Site !   Contact Us


BankersOnline is a free service made possible by the generous support of our advertisers and sponsors. Advertisers and sponsors are not responsible for site content. Please help us keep BankersOnline FREE to all banking professionals. Support our advertisers and sponsors by clicking through to learn more about their products and services.