Skip to Content
Author's profile photo Former Member

Are you Ready for an Audit?

When the IRS or other tax and regulatory agencies call, are you ready? There was a time in the SAP world that being “audit ready” meant implementing SAP DART before archiving. But for many companies, being audit data ready means having a process in place to enable them to respond at a moment’s notice to requirements and information requests from a dizzying array of tax authorities and regulatory regimes. It is an issue that impacts the bottom line: a multi-national company might expect to pay millions in penalties, simply because of their inability to report in a timely manner.

Being audit data ready isn’t easy under any circumstances – it takes deep expertise with SAP and the technology solutions available. DART was originally developed to address the need for IRS data extracts, but businesses with complex operations working in multiple tax and regulatory environments – and sometimes multiple SAP systems – often need greater flexibility than DART enhancements can handle efficiently. These companies need to have it both ways – a standardized, repeatable process to index tax-related data, and the ability to respond efficiently to ad hoc requests.

The right solution isn’t a single tool – it is the solution that delivers what companies need to capture tax and audit data, efficiently, meet ad hoc requests and maintain high system performance. For many environments, the latest version of DART hits the mark for extracting the tax data needed by auditors. Other companies deal with high data volumes and complex tax environments where new technologies and practices can deliver a higher level of flexibility and speed.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      do you know if SAP delivers 1120, 1099, K-1, etc. as part of interactive PDFs out of the box?

      Author's profile photo Clemens Li
      Clemens Li
      in a couple of projects we have to live with restrictions hard to understand. Forbidden transactions in development and sandbox systems justified by hardly seizable audit reasons.

      Also lots of measures are taken to document every irregular but necessary database change in productive systems - knowing that it's still possible to do any kind of malicious data manipulation without leaving traces or fingerprints in the system.

      So is it enough to rely on the assumption that the auditors will never find out what you did?

      External and internal auditing should and will focus more on process, not just data extraction.