The system must provide leads (reports) that identify potential tax noncompliance. The system must collect and analyze publicly available data to aid in finding tax noncompliance. The system must provide links to sources in its reports. The system must be capable of identifying the tax payer themselves (instead of just a business name). The system must convert data from sources into actionable items Treasury agents can act upon. (I,e, each lead or actionable item should include data source summary. Jane Smith- suspected short term rental income not reported as indicated by XYZ. Review schedule C filings for XYZ business- reported revenue inconsistent with online storefront activity. Recommended audit of ABC company or individual- detected frequent high value transactions via xyz platforms without corresponding tax documents.) The system must include public ecommerce websites in its efforts to gather tax noncompliance data. The system must include public social media platforms in its efforts to gather tax noncompliance data. The system must include records from public government websites in its efforts to gather tax noncompliance data. The system must be able to scan all public websites without human intervention. (i.e. The system will not require a human to configure it to scan sites it has not scanned previously.) The system must be capable of processing real time data to ensure the latest data is being used in reporting. The system’s leads must include data that allows Treasury to validate they are comparing leads to the correct taxpayer data in State of Michigan systems. (i,e, full legal name or business name, SSN/FEIN, DOB, last known address, etc.) The system must be capable of performing its intended functions without access to State of Michigan confidential data. (i.e. The system will not have access to State of Michigan data, that is not publicly available.) The system must provide estimate revenues, organized by tax year, for taxpayers it provides leads on. The system must provide a list of activities the reported taxpayer performs. The system must indicate whether the reported taxpayer is currently up to date on its licenses. The system must indicate where the reported taxpayers are operating. The system must include a list of employees for businesses that are being reported on. The system must include any relevant dates when reporting on a taxpayer. (i.e. Reports on taxpayers business must include dates including, but not limited to, date of inception, date of bankruptcy, date of closure, etc.) The system must provide leads based on the industry the taxpayer is in. The system must be capable of identifying detailed blockchain information as proof of tax noncompliance related to crypto currency. The system must be capable of identifying detailed cryptocurrency wallet information. When reporting on cryptocurrency, the system will provide both the transaction amount in cryptocurrency, and the transaction amount in U.S. Dollars. (U.S. Dollars must be reported at the exchange rate that was in use at the time the conversion took place.) The system must be capable of investigating and identifying the taxpayer behind online avatars which are used to obfuscate the identity of the taxpayer. The system must have an easy-to-use web interface to aid in training new hires. The system must support multiple roles, including but not limited to: Admin users (can perform user modification roles (add/delete/modify users)) Security Users (can access audit logs to ensure proper usage of the system) Read/Write Users (limited/no access to change settings/roles) The system must include a suite of Admin Reports, which include but are not limited to: Access Report (includes username, date of last use, assigned roles) Privileged Access Report (includes configuration changes that have been made, any logs that were deleted) Change to Access Report (lists any role changes in the selected timeframe) Browsing (lists pages/reports in the system users have viewed (to aid in enforcing IRS browsing regulations)) The system must include a configurable logon banner, so that the State of Michigan can insert proper usage guidance in the banner to warn users of regulations regarding the data they are about to access. The system must be able to integrate with the State’s Single Sign On solution, using either a SAML or OIDC integration type. State Data is and will remain the sole and exclusive property of the State and all right, title, and interest in the same is reserved by the State. State Data does not include Contractor Data.
