How to determine Who, What, and When for a Posted Transaction

Modified on Sat, 20 Jul at 10:29 AM

As a Controller or Manager you will face situations when you need to know the identity and timing of a transaction that may have been incorrectly posted. These steps will help you identify the user, and other related information needed to correct the mistake.

Who

To determine who posted a transaction:

  1. Search Posted Purchase Invoice in the search bar
  2. From the Posted document list, select the document you want to identify.
  3. Double click on the document to open it.
  4. Click on the drop down at the top left corner of the page near address bar.
  5. Click on Help and select About This Page.
  6. Click on the Table Fields, and scroll down to User ID field. Here you will see the user identity.
  7. Make sure to close the field and go back to your posted document.

What

To identify what transactions were posted by this document:

  1. When you have selected your document, click on Action, then Navigate, on the ribbon.
  2. A new page will show you all ledgers that are affected. Here you can see the entries that were posted.
  3. To view any of these entries select the row that you want and click on the icon Show Related Entries, this will open the entries that were posted by the document under review.

When

In order to find out when this transaction was created (this can be different from Posting Date):

  1. Double click on the No. of Entries column for the related entry you are researching as shown in the transaction in the last step.
  2. Note the Entry No. field for each ledger entry.
  3. Search for G/L Register in your search field.
  4. In the register, filter your list for the entry number you want to look at.
  5. Under the Creation Date column in the list you the see the date transaction was created. It may be different from the posting date.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article