Implementing Demographic History

Revenue agencies are required to keep detailed records of all transactions both current and historical.  When demographic changes are required (name changes, address changes etc.) to a taxpayer’s registration information, a record must be kept, which records the data that was updated, who updated the data, and when the data was updated.  This data not only facilitates research of changes to demographic data, but also is an effective tool in preventing and detecting fraud related to taxpayer registration data.

This document will provide guidance for setting up demographic history in ETPM.

  • https://blogs.oracle.com/tax/resource/Demographic_History_Guidelines.pdf
  • Comments:

    Post a Comment:
    • HTML Syntax: NOT allowed
    About

    This blog is for our Oracle Public Sector Revenue Management customers, delivery partners, and even our fellow Oracle professionals, and is dedicated to all things Oracle Tax and Revenue Management. We will focus on support and implementation tips, announcements, and FAQs (frequently asked questions) for all of our Oracle Public Sector Revenue Management products. This include Oracle Public Sector Revenue Management (PSRM), Oracle Tax Analytics, and our Oracle PSRM Self Service and integration products.

    Search

    Categories
    Archives
    « April 2014
    SunMonTueWedThuFriSat
      
    1
    3
    4
    5
    6
    7
    9
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
       
           
    Today