Skip to main content

Solutions

Law firms

Tax, audit & accounting firms

Corporations

Governments

Products

Legal

Trade & supply

Tax, audit & accounting

Corporate tax

Risk & fraud

Books

Recommended products

Questions? We are here to help.
Contact us

Purchase

Buy solutions

Buy books

Contact sales

Questions? We are here to help.

Resources

Insights

Events

Product training

Product communities

Developers

Get started with SAP integration

Audit database report

The purpose of this report is to ensure that all transactions posted to the SAP G/L with a tax implication are also posted to the Determination audit database. It is recommended to run this report frequently, at least during the period close process to ensure the two systems are synchronized. Once documents have been identified they can be reprocessed to Determination for inclusion in audit if not already sent successfully. You can both run the report and manually update records using the execute button for update, or you have the option to update records via a scheduled background job using the Audit Status Reprocess program which is discussed below.
note
Reminder that depending on the transaction you are posting for your month end close process you may have later transaction that you miss getting to the audit database. It is best to run the report one more time after all journal entries and batches have been posted for the month so that you pick up any late entries as part of the closing adjustments
note
Documents that show on the report as status N are likely parked documents that are not posted yet to the G/L and status "F" documents have failed to go to audit for some other technical error reason. You will have to manually correct these documents to get them to a status of S with another update run.
Accessing the Audit Database Report
From the ONESOURCE Indirect Tax User Menu select
Reports
>
Audit Database Transactions Update
 or use transaction
/N/IDT/AUDIT_DATABASE
.
Selection Option
Description
Billing Document
The Sales Invoice (SD) document number. Can’t be combined with Document Number and Fiscal Year.
Document Number
The G/L accounting document number (MM-LIV and FI). Can’t be combined with Billing Document.
Company Code
Company code of the transaction.
Fiscal Year
The fiscal year the document was posted in. Relevant for MM-LIV and FI documents only.
Audit DB message status
Filter to select either:
F – Failed transactions that didn’t post successfully to Determination audit U – Untried transactions that never have been sent to Determination.
N – Not posted to the G/L will not go to audit until G/L entry is posted. S – Transactions that have been successfully sent and audited in Determination
Z – Zero value transaction that will not post to audit
Date Created
The date the entry was added to this table.
Sample of a report for
FAILED
 transactions:
From the report one can reprocess one transaction at a time, select all untried and/or failed messages, and then resubmit in bulk to Determination by using the audit update process within this report. If a transaction fails again it stays in the report, if it succeeds in auditing to Determination the status is changed to success.
note
It is recommended to schedule this report to run prior to period closing for F and U status and then reprocess them before closing the period.
To run the report and update the audit database you would run transaction code /IDT/AUDIT_DATABASE from the report menu first selecting any “U” status document. Note the button on the report menu for selecting untried documents. See example below:
After getting the list of untried documents that you need to post to audit then hit the
EXECUTE
 button to run the update of the
UNTRIED
 entries.
Run the report again for the same document numbers and verify that they have now changed from
UNTRIED
 status to a status of “
SUCCESS
”. If the documents in question have not changed to a successful status, then they may be in “
FAIL
” status which will require you to investigate errors on the document. Another possible status would be that they were changed to status of “N” as not posted to the G/L. If this occurs, then you will need to go back to the billing process and attempt to post the document to accounting using transaction code VF02. If the document posts to accounting, then retry the audit update transaction again.
Prior to month end close you will want to check to make sure that all documents have posted to accounting and that the audit report shows them in “
SUCCESS
” status.

This article applies to:

  • Product: ONESOURCE Indirect Tax
  • Sub-Product: SAP