Event Type FAQs

Event Types are codes with specific instructions used in CORE transactions to drive how CORE posts transactions.  Event Types are specific to each transaction and the underlying posting codes. These sets of instructions can greatly impact how the transaction posts. 

You will want to submit a request to the CORE Governance Committee (CGC) for new event types.  The request is to be submitted by Department Controllers, Budget Directors, or Procurement Officials.  CGC New Request Forms can be located 

Event Type Requirements requests are to be directed to the CORE Governance Committee (CGC).  CGC request forms can be located on the CORE Website by selecting the CORE Governance website. 

The Event Type field on the ITA transaction has been locked.  This will ensure that the ITI and ITA always have the same event type.  In the past, some users would edit this field and it would create incorrect accounting postings for the transaction.   If an error is discovered in the Event Type on the ITA, the user will need to discard the ITA and communicate with the ITI department and modify the Event Type to the correct one before copying forward to create the new ITA. 

Transactions with incorrect postings may not have the proper elements needed to perform their intended purpose. When this happens, additional work is required to correct the postings. 

On most transactions, the event type field can be found on the account line.  Other transactions such as Internal Exchange Transaction (IET) can be found on the exchange details line. 

Some system generated transactions do not use an event type or the event type is inferred from the process used to create them.  Invoice (IN) and Receiver (RC) CORE Transactions do not have Event Types. 

If you do not select an Event Type, CORE will assign one, which is generally the most commonly used Event Type for that transaction. This takes place when the transaction is validated. Note: If a default Event Type is not correct and you do not select an alternate, your transaction may post incorrectly. 

If you’re not sure which Event Type to use, you will want to consult with your supervisor or team lead. 

Use these best practices when considering Event Types:

• • • Use the same Event Type for the transaction that does the same thing

    • The same types of transaction should all post the same way.

    • Review posting lines before submission and as part of the transaction approval process.

    • Ensure a thorough review of the transaction for uncommon, unique or highly complex transactions.

    • Making corrections can be a time-consuming task.

You will want to use the REF-014 Report - Event Type Posting Detail to see a list of available event types and associated posting codes, based on the Transaction code you select. 

Within the report, you can enter prompts for Transaction Code, Transaction Type, Debit Posting Code, and/or Credit Posting Code.