Event types in this area not only include those commonly defined to Accounts Receivable (A/R), but also ones from Accounts Payable. While the event type ID values below do not flow in numerical order, the presentation of event types is in a sequence that they will likely occur. The following depicts the basic order that receivables might take. The 'Accrue No Bill' step is an optional one that is normally only done with revenue and not other receivables such as vendor refunds, deposits, and balance sheet billings. The 'Send For Collection' is a step that is only done for earned receivables and for vendor refunds.
The Event Type Defaults (ETDFLT) page controls the entry of event types on A/R transactions referencing other A/R transactions while also providing a means of defaulting the correct event type on a referencing transaction based on information on the referenced transaction.
REV Event Category includes the following event types that will be used to record revenues. This Revenue Event Category uses the Generic Event Type Processor logic.
AR06: Accrue Earned Revenue When a customer has been provided goods or services that meet the accounting requirements for earned revenue, yet cannot be billed at the present time, this is the appropriate event type to use to record the receivable and revenue.
Posting Pair A: Principal
Dr R009: Earned Receivable (A)
Cr R010: Earned Revenue
Prior Event Types: Referenced accounting activity for this event type is not likely in any form but a memo reference.
Subsequent Event Types: A receivable of this type will be recorded until such time the customer can be billed or collection is made without a bill. If collected, it will be with AR02: Collect Earned Revenue. If transferred to a receivable that allows for billing, AR06 will be referenced by AR01: Bill Earned Revenue.
AR01: Bill Earned Revenue When a customer has been provided goods or services that meet the accounting requirements for earned revenue, this is the appropriate event type to use to record the receivable and revenue.
Posting Pair A: Principal
Dr R001: Billed Earned Receivable (A)
Cr R002: External Billed Earned Revenue
Posting Pair B: Interest
Dr R001: Billed Earned Receivable (A)
Cr R002: External Billed Earned Revenue
Posting Pair C: Late Fee
Dr R001: Billed Earned Receivable (A)
Cr R002: External Billed Earned Revenue
Posting Pair D: Admin Fee
Dr R001: Billed Earned Receivable (A)
Cr R002: External Billed Earned Revenue
Posting Pair E: NSF Fee
Dr R001: Billed Earned Receivable (A)
Cr R005: Billed NSF Revenue
Posting Pair F: Other Fee
Dr R001: Billed Earned Receivable (A)
Cr R002: External Billed Earned Revenue
Posting Pair H: Tax
Dr R001: Billed Earned Receivable (A)
Cr R011: Billed Accounts Receivable Tax (L)
Prior Event Types: Referenced accounting activity for this event type is optional with the only event type referenced being AR06: Accrue Earned Revenue. When terms have not been met to start billing the customer, revenue often has to be recorded for financial purposes, which is the purpose of AR06.
Subsequent Event Types: A receivable of this type will have one of four outcomes:
Collection with AR02: Collect Earned Revenue will occur with a Cash Receipt transaction.
After several attempts at collection have failed, the receivable can be sent to an external party for collection. Event type AR05: Refer Earned Receivable to Collection Agency on a Referral to Collection Agency transaction would record such an event unless the receivable was sold to the external party.
When all attempts at collection have failed and the receivable is considered uncollectible. At this point AR03: Write Off Earned Revenue - Direct Method or AR04: Write Off Earned Revenue would be used on a Write-Off transaction.
If the receivable was recorded as an intercept request, then either IN10 or IN11 event types for intercepting earned revenue would be used on an Internal Exchange Transaction to close all or a portion of the receivable.
AR05: Refer Earned Receivable to Collection Agency When a customer account has had a receivable past due for a significant period of time, the receivable is often turned over to a collection agency for collection. This event type provides the ability to record such a receivable under a different balance sheet account in addition to the different asset posting code.
Posting Pair A: Principal
Dr R004: Billed Earned Receivable Sent for Collection (A)
Cr R002: External Billed Earned Revenue
Posting Pair B: Interest
Dr R004: Billed Earned Receivable Sent for Collection (A)
Cr R002: External Billed Earned Revenue
Posting Pair C: Late Fee
Dr R004: Billed Earned Receivable Sent for Collection (A)
Cr R002: External Billed Earned Revenue
Posting Pair D: Admin Fee
Dr R004: Billed Earned Receivable Sent for Collection (A)
Cr R002: External Billed Earned Revenue
Posting Pair E: NSF Fee
Dr R004: Billed Earned Receivable Sent for Collection (A)
Cr R005: Billed NSF Revenue
Posting Pair F: Other Fee
Dr R004: Billed Earned Receivable Sent for Collection (A)
Cr R002: External Billed Earned Revenue
Prior Event Types: Referenced accounting activity for this event type is required with the only event type referenced being AR01: Bill Earned Revenue.
Subsequent Event Types: A receivable of this type will have one of three outcomes:
Collection with AR02: Collect Earned Revenue will occur with a Cash Receipt transaction.
When all attempts at collection have failed the receivable is considered uncollectible. At this point AR03: Write Off Earned Revenue - Direct Method or AR04: Write Off Earned Revenue would be used on a Write-Off transaction.
If the receivable was recorded as an intercept request, then either IN10 or IN11 event types for intercepting earned revenue would be used on an Internal Exchange Transaction to close all or a portion of the receivable.
AR02: Collect Earned Revenue The collection of revenue can be for a customer account or without one.
Posting Pair A: Principal
Dr A001: Cash (A)
Cr R003: External Collected Earned Revenue
Posting Pair B: Interest
Dr A001: Cash (A)
Cr R003: External Collected Earned Revenue
Posting Pair C: Late Fee
Dr A001: Cash (A)
Cr R003: External Collected Earned Revenue
Posting Pair D: Admin Fee
Dr A001: Cash (A)
Cr R003: External Collected Earned Revenue
Posting Pair E: NSF Fee
Dr A001: Cash (A)
Cr R006: Collected NSF Revenue
Posting Pair F: Other Fee
Dr A001: Cash (A)
Cr R003: External Collected Earned Revenue
Posting Pair H: Tax
Dr A001: Cash (A)
Cr R012: Collected Accounts Receivable Tax (L)
Prior Event Types: Referenced accounting activity for this event type is optional and can be to AR01: Bill Earned Revenue or AR05: Refer Earned Receivable to Collection Agency.
Subsequent Event Types: While there is no event type that will reference and liquidate this type of revenue, there is one that can memo reference it. AP10: Authorize Earned Revenue Refund would be used to request a payment out of revenue to the vendor/customer. (Please refer to the Accounts Payable topic under Accounting Model Delivered Configuration.)
AR03: Write Off Earned Revenue - Direct Method When a customer account has had a receivable past due for a significant period of time and it is determined that the receivable will never be collected, the receivable is written off. This event type provides the ability to record such a write off. It is called the Direct Method because the Allowance For Doubtful Accounts account is not updated. When an amount of receivables is established at the beginning of the year as uncollectible based on prior collection history and then reduced throughout the year is known as the allowance method. The direct method records only a Bad Debt Expense that will reduce equity balances at year end to offset revenues written off.
The reason External Billed Earned Revenue is being rebooked during the write off is because the liquidating reference to the open receivable removed not only the receivable asset but also the revenue.
Posting Pair A: Principal
Dr R007: Bad Debt Expense
Cr R002: External Billed Earned Revenue
Posting Pair B: Interest
Dr R007: Bad Debt Expense
Cr R002: External Billed Earned Revenue
Posting Pair C: Late Fee
Dr R007: Bad Debt Expense
Cr R002: External Billed Earned Revenue
Posting Pair D: Admin Fee
Dr R007: Bad Debt Expense
Cr R002: External Billed Earned Revenue
Posting Pair E: NSF Fee
Dr R007: Bad Debt Expense
Cr R005: Billed NSF Revenue
Posting Pair F: Other Fee
Dr R007: Bad Debt Expense
Cr R002: External Billed Earned Revenue
Prior Event Types: Referenced accounting activity for this event type is required with the only event type referenced being AR01: Bill Earned Revenue.
Subsequent Event Types: There are no subsequent event types.
AR04: Write Off Earned Revenue - Allowance Method When a customer account has had a receivable past due for a significant period of time and it is determined that the receivable will never be collected, the receivable is written off. This event type provides the ability to record such a write off. It is called the Allowance Method because it reduces the Allowance For Doubtful Accounts account established at the beginning of the year as uncollectible based on prior collection history. A Bad Debt Expense account was established when the Allowance was established, that will reduce equity balances at year-end to offset revenues written off.
The reason External Billed Earned Revenue is being rebooked during the write off is because the liquidating reference to the open receivable removed not only the receivable asset but also the revenue.
Posting Pair A: Principal
Dr R008: Allowance for Bad Debt (CA)
Cr R002: External Billed Earned Revenue
Posting Pair B: Interest
Dr R008: Allowance for Bad Debt (CA)
Cr R002: External Billed Earned Revenue
Posting Pair C: Late Fee
Dr R008: Allowance for Bad Debt (CA)
Cr R002: External Billed Earned Revenue
Posting Pair D: Admin Fee
Dr R008: Allowance for Bad Debt (CA)
Cr R002: External Billed Earned Revenue
Posting Pair E: NSF Fee
Dr R008: Allowance for Bad Debt (CA)
Cr R005: Billed NSF Revenue
Posting Pair F: Other Fee
Dr R008: Allowance for Bad Debt (CA)
Cr R002: External Billed Earned Revenue
Prior Event Types: Referenced accounting activity for this event type is required with the only event type referenced being AR01: Bill Earned Revenue. One event type that would have occurred prior to the AR04 write off would be GA04: Establish Allowance for Bad Debt. That event type would have occurred on a journal voucher to establish the Allowance and Bad Debt Expense at the beginning of the year. AR04 will not liquidate that accounting. It will wash a portion of the Allowance established.
Subsequent Event Types: There are no subsequent event types.
AR10: Bill Unearned Revenue When a customer has been provided goods or services that do not meet the accounting requirements for earned revenue, this is the appropriate event type to use to record the receivable and revenue. Unearned revenue is a liability account that may or may not be tracked at the revenue budget level depending on posting code setup.
The event type does not make use of all of the REV event category posting pairs as they do not apply to a receivable that is not yet earned.
The reclassification feature available through Future Transaction Triggering allows for the automatic conversion of a billed unearned revenue to billed earned revenue as of a specified Reclassification Date.
Posting Pair A: Principal
Dr R100: Billed Unearned Receivable (A)
Cr R101: Billed Unearned Revenue (L)
Prior Event Types: Referenced accounting activity for this event type is not likely in any form but a memo reference.
Subsequent Event Types: A receivable of this type has one of four outcomes:
Collection with AR11: Collect Unearned Revenue with a Cash Receipt transaction.
After all attempts at collection have failed the receivable is written off with AR12: Write Off Unearned Revenue on a Write-Off transaction.
Reclassification will occur manually or with Future Transaction Triggering of AR10 to the AR01 event type.
If the receivable was recorded as an intercept request, then either IN12 or IN13 event types for intercepting earned revenue would be used on an Internal Exchange Transaction to close all or a portion of the receivable.
AR11: Collect Unearned Revenue When a customer has been provided goods or services that do not meet the accounting requirements for earned revenue, this is the appropriate event type to use to record the collection of revenue in that situation. Unearned revenue is a liability account that may or may not be tracked at the revenue budget level depending on posting code setup.
The event type does not make use of all of the REV event category posting pairs as they do not apply to a receivable that is not yet earned.
The reclassification feature available through Future Transaction Triggering allows for the automatic conversion of a billed unearned revenue to billed earned revenue as of a specified Reclassification Date.
Posting Pair A: Principal
Dr A001: Cash (A)
Cr R102: Collected Unearned Revenue (L)
Prior Event Types: Referenced accounting activity for this event type is optional and can be to AR10: Bill Unearned Revenue.
Subsequent Event Types: There will be no subsequent referencing of this event type. There may be a reclassification that occurs manually or with Future Transaction Triggering to transfer the amount recorded under AR11 with AR02.
AR12: Write Off Unearned Revenue When a customer account has had a receivable past due for a significant period of time and it is determined that the receivable will never be collected, the receivable is then written off. This event type provides the ability to record such a write off. There is not the choice of write off methods with unearned revenue as there is with earned revenue. A user could cancel the receivable, modify it to zero-dollars, or use this event type.
The option also exists to remove the posting codes from the event type and let the write off just remove the receivable and unearned revenue while not recording any new accounting entries. The accounting entries provided below ease reporting with memo accounts that will not be rolled forward or closed to any equity accounts at year-end.
Posting Pair A: Principal
Dr R103: Unearned Receivable Write Off (A)
Cr R104: Unearned Revenue Write Off (AO)
Prior Event Types: Referenced accounting activity for this event type is required with the only event type referenced being AR10: Bill Unearned Revenue.
Subsequent Event Types: There are no subsequent event types.
AR13: Collect Pre Payment When a customer pays in advance for goods or services, this is the appropriate event type to use to record the collection of revenue in that situation. The difference between this event type and AR11 is in the Customer Account updates. AR11 updates as Unearned Revenue Collection and AR13 updates as a Reserved Credit Balance Collection.
The event type does not make use of all of the REV event category posting pairs as they do not apply to a pre payment.
Posting Pair A: Principal
Dr A001: Cash (A)
Cr R105: Unearned Revenue for Pre Payment (L)
Prior Event Types: Referenced accounting activity for this event type is not likely in any form but a memo reference.
Subsequent Event Types: There will be no subsequent referencing of this event type. There will either be a modification down or a cancellation of the pre payment in the future when that reserved credit balance is applied, or a memo reference to return the pre payment to the customer with AP07: Authorize Pre Payment Refund. (Please refer to the Accounts Payable topic under Accounting Model Delivered Configuration.)
AR50: Bill To Asset Account When a customer has to be billed where the receivable asset is to be recorded along with a reduction to another asset account, this event type is to be used. There is no default balance sheet account for the asset account being reduced, thus one has to be manually entered.
Updates to the Customer Account Information page are not tracked for this type of receivable.
Posting Pair A: Principal
Dr R001: Billed Earned Receivable (A)
Cr A016: Generic Asset (A)
Posting Pair H: Tax
Dr R001: Billed Earned Receivable (A)
Cr R011: Billed Accounts Receivable Tax (L)
Prior Event Types: Referenced accounting activity for this event type is not likely in any form but a memo reference.
Subsequent Event Types: A receivable of this type has one of two outcomes:
Collection with AR51: Collect To Asset Account on a Cash Receipt.
After all attempts at collection have failed the receivable is either cancelled or modified down to what has been closed.
AR51: Collect To Asset Account When a customer pays and the receipt of cash is to be recorded along with a reduction to another asset account, this event type is to be used. There is no default balance sheet account for the asset account being reduced, thus one has to be manually entered.
Updates to the Customer Account Information page are not tracked for this type of receivable.
Posting Pair A: Principal
Dr A001: Cash (A)
Cr A016: Generic Asset (A)
Posting Pair H: Tax
Dr A001: Cash (A)
Cr R012: Collected Accounts Receivable Tax (L)
Prior Event Types: Referenced accounting activity for this event type is optional and can be to AR50: Bill To Asset Account.
Subsequent Event Types: There are no subsequent event types that will reference this one. If the funds are to be returned, event type AP18: Asset Payout Authorization could be used. (Please refer to the Accounts Payable topic under Accounting Model Delivered Configuration.)
AR52: Bill To Liability Account When a customer has to be billed where the receivable asset is to be recorded along with an increase to a liability account, this event type is to be used. There is no default balance sheet account for the liability account being reduced, thus one has to be manually entered.
Updates to the Customer Account Information page are not tracked for this type of receivable.
Posting Pair A: Principal
Dr R001: Billed Earned Receivable (A)
Cr A015: Generic Liability (L)
Posting Pair H: Tax
Dr R001: Billed Earned Receivable (A)
Cr R011: Billed Accounts Receivable Tax (L)
Prior Event Types: Referenced accounting activity for this event type is not likely in any form but a memo reference.
Subsequent Event Types: A receivable of this type has one of two outcomes:
Collection with AR53: Collect To Liability Account on a Cash Receipt.
After all attempts at collection have failed the receivable is either cancelled or modified down to what has been closed.
AR53: Collect To Liability Account When a customer pays and the receipt of cash is to be recorded along with an increase to a liability account, this event type is to be used. There is no default balance sheet account for the liability account being reduced, thus one has to be manually entered.
Updates to the Customer Account Information page are not tracked for this type of receivable.
Posting Pair A: Principal
Dr A001: Cash (A)
Cr A015: Generic Liability (L)
Posting Pair H: Tax
Dr A001: Cash (A)
Cr R012: Collected Accounts Receivable Tax (L)
Prior Event Types: Referenced accounting activity for this event type is optional and can be to AR52: Bill To Liability Account.
Subsequent Event Types: There are no subsequent event types that will reference this one. If the funds are to be returned, event type AP17: Liability Payout Authorization could be used. (Please refer to the Accounts Payable topic under Accounting Model Delivered Configuration.)
AR54: Bill To Equity Account When a customer has to be billed where the receivable asset is to be recorded along with an increase to an equity account, this event type is to be used. There is no default balance sheet account for the equity account being reduced, thus one has to be manually entered.
Updates to the Customer Account Information page are not tracked for this type of receivable.
Posting Pair A: Principal
Dr R001: Billed Earned Receivable (A)
Cr A014: Generic Equity (E)
Posting Pair H: Tax
Dr R001: Billed Earned Receivable (A)
Cr R011: Billed Accounts Receivable Tax (L)
Prior Event Types: Referenced accounting activity for this event type is not likely in any form but a memo reference.
Subsequent Event Types: A receivable of this type has one of two outcomes:
Collection with AR55: Collect To Equity Account on a Cash Receipt transaction.
After all attempts at collection have failed, the receivable is either cancelled or modified down to what has been closed.
AR55: Collect To Equity Account When a customer pays and the receipt of cash is to be recorded along with an increase to an equity account, this event type is to be used. There is no default balance sheet account for the liability account being reduced, thus one has to be manually entered.
Updates to the Customer Account Information page are not tracked for this type of receivable.
Posting Pair A: Principal
Dr A001: Cash (A)
Cr A014: Generic Equity (E)
Posting Pair H: Tax
Dr A001: Cash (A)
Cr R012: Collected Accounts Receivable Tax (L)
Prior Event Types: Referenced accounting activity for this event type is optional and can be to AR54: Bill To Equity Account.
Subsequent Event Types: There are no subsequent event types that will reference this one. If the funds are to be returned, event type AP16: Equity Payout Authorization could be used. (Please refer to the Accounts Payable topic under Accounting Model Delivered Configuration.)
AR56: Collect Return of Grant Advance When a grantee or sub-grantee returns all or a portion of a grant advanced paid to them, that return is recorded with this event type to bring both accounts to zero originally used in the advance.
Posting Pair A: Principal
Dr C011: Cash w/Grantee Of (A)
Cr C009: Cash w/Grantee (A)
Prior Event Types: Referenced accounting activity for this event type is required to be a memo reference to the award advance.
Subsequent Event Types: There are no subsequent event types that will reference this one.
TR20: Bill for Return of Unused Travel Advance Used with the Receivable (RE) transaction to bill the return of an unused travel advance if a trip was cancelled or the entire advanced amount was not used for a trip.
Posting Pair A: Principal
Dr R001: Billed Earned Receivable (A)
Cr T001: Travel Advance (A)
Prior Event Types: A memo reference is required here to the TRADV transaction that created the unused advance.
Subsequent Event Types: A receivable of this type has one of three outcomes:
Collection with TR21: Collect Return of Unused Travel Advance on a Cash Receipt transaction.
After either all attempts at collection have failed, the advance is taxed to the employee as part of payroll, or the advance has been reported as 1099 Miscellaneous income to the employee, the receivable is written off with TR22: Expense Uncollected Travel Advance on a Write-Off transaction.
Referral to a collection agency with TR23: Refer Travel Advance Return to Collection Agency on a Referral to Collection Agency transaction.
TR21: Collect Return of Unused Travel Advance Used with the Cash Receipt (CR) transaction to collect the return of an unused travel advance.
Posting Pair A: Principal
Dr A001: Cash (A)
Cr T001: Travel Advance (A)
Prior Event Types: There is very likely a reference to an RE transaction with the TR20 event type that billed for the return of the advance.
Subsequent Event Types: There are no subsequent event types that will reference this one.
LN34: Bill Loan Principal Repayment - This event type is used with the Receiver (RE) transaction to setup the receivable to from the borrower (customer account) for the amount of principal due.
Posting Pair A: Principal
Dr A312: External Loan Receivable – Current (A)
Cr R002: External Billed Earned Revenue (NR)
Posting Pair B: Interest
Dr A312: External Loan Receivable – Current (A)
Cr R002: External Billed Earned Revenue (NR)
Posting Pair C: Late Fee
Dr A312: External Loan Receivable – Current (A)
Cr R002: External Billed Earned Revenue (NR)
Posting Pair D: Admin Fee
Dr A312: External Loan Receivable – Current (A)
Cr R002: External Billed Earned Revenue (NR)
Posting Pair E: NSF Fee
Dr A312: External Loan Receivable – Current (A)
Cr R002: External Billed Earned Revenue (NR)
Posting Pair F: Other Fee
Dr A312: External Loan Receivable – Current (A)
Cr R002: External Billed Earned Revenue (NR)
Posting Pair G: Additional
Dr A314: Reserve for External Loan Receivable (CA)
Cr A312: External Loan Receivable – Current (A)
Prior Event Types: Referenced accounting activity for this event type is not possible.
Subsequent Event Types: A receivable of this type will have one of four outcomes:
Collection with AR02: Collect Earned Revenue will occur with a Cash Receipt transaction.
After several attempts at collection have failed, the receivable can be sent to an external party for collection. Event type AR05: Refer Earned Receivable to Collection Agency on a Referral to Collection Agency transaction would record such an event unless the receivable was sold to the external party.
When all attempts at collection have failed and the receivable is considered uncollectible. At this point AR03: Write Off Earned Revenue - Direct Method or AR04: Write Off Earned Revenue would be used on a Write Off transaction.
If the receivable was recorded as an intercept request, then either IN10 or IN11 event types for intercepting earned revenue would be used on an Internal Exchange Transaction to close all or a portion of the receivable.
LS15: Bill Capital Lease Principal Payment - This event type is used with the Receivable (RE) transaction to bill the lessee (customer account) for the amount of principal due on a lease.
Posting Pair A: Principal
Dr R001: Billed Earned Receivable (A)
Cr R002: External Billed Earned Revenue (NR)
Posting Pair B: Interest
Dr R001: Billed Earned Receivable (A)
Cr R002: External Billed Earned Revenue (NR)
Posting Pair C: Late Fee
Dr R001: Billed Earned Receivable (A)
Cr R002: External Billed Earned Revenue (NR)
Posting Pair D: Admin Fee
Dr R001: Billed Earned Receivable (A)
Cr R002: External Billed Earned Revenue (NR)
Posting Pair E: NSF Fee
Dr R001: Billed Earned Receivable (A)
Cr R002: External Billed Earned Revenue (NR)
Posting Pair F: Other Fee
Dr R001: Billed Earned Receivable (A)
Cr R002: External Billed Earned Revenue (NR)
Posting Pair G: Additional
Dr A362: Deferred Lease Principal Revenue (L)
Cr A360: Capital Lease Receivable - Current (A)
Prior Event Types: Referenced accounting activity for this event type is not possible.
Subsequent Event Types: A receivable of this type will have one of four outcomes:
Collection with AR02: Collect Earned Revenue will occur with a Cash Receipt transaction.
After several attempts at collection have failed, the receivable can be sent to an external party for collection. Event type AR05: Refer Earned Receivable to Collection Agency on a Referral to Collection Agency transaction would record such an event unless the receivable was sold to the external party.
When all attempts at collection have failed and the receivable is considered uncollectible. At this point AR03: Write Off Earned Revenue - Direct Method or AR04: Write Off Earned Revenue would be used on a Write Off transaction.
If the receivable was recorded as an intercept request, then either IN10 or IN11 event types for intercepting earned revenue would be used on an Internal Exchange Transaction to close all or a portion of the receivable.
LS16: Bill Capital Lease Interest Payment - This event type is used with the Receivable (RE) transaction to bill the lessee (customer account) for the amount of interest due on a lease when the Include Interest in Initial Accounting indication for a lease debt type (as defined on DEBTTYPE) is set to true. When that indication is false, an event type similar to AR01 should be used because the amount of interest is not to be recorded as a receivable or deferred revenue.
Posting Pair A: Principal
Dr R001: Billed Earned Receivable (A)
Cr R002: External Billed Earned Revenue (NR)
Posting Pair B: Interest
Dr R001: Billed Earned Receivable (A)
Cr R002: External Billed Earned Revenue (NR)
Posting Pair C: Late Fee
Dr R001: Billed Earned Receivable (A)
Cr R002: External Billed Earned Revenue (NR)
Posting Pair D: Admin Fee
Dr R001: Billed Earned Receivable (A)
Cr R002: External Billed Earned Revenue (NR)
Posting Pair E: NSF Fee
Dr R001: Billed Earned Receivable (A)
Cr R002: External Billed Earned Revenue (NR)
Posting Pair F: Other Fee
Dr R001: Billed Earned Receivable (A)
Cr R002: External Billed Earned Revenue (NR)
Posting Pair G: Additional
Dr A363: Deferred Lease Interest Revenue (L)
Cr A360: Capital Lease Receivable - Current (A)
Prior Event Types: Referenced accounting activity for this event type is not possible.
Subsequent Event Types: A receivable of this type will have one of four outcomes:
Collection with AR02: Collect Earned Revenue will occur with a Cash Receipt transaction.
After several attempts at collection have failed, the receivable can be sent to an external party for collection. Event type AR05: Refer Earned Receivable to Collection Agency on a Referral to Collection Agency transaction would record such an event unless the receivable was sold to the external party.
When all attempts at collection have failed and the receivable is considered uncollectible. At this point AR03: Write Off Earned Revenue - Direct Method or AR04: Write Off Earned Revenue would be used on a Write Off transaction.
If the receivable was recorded as an intercept request, then either IN10 or IN11 event types for intercepting earned revenue would be used on an Internal Exchange Transaction to close all or a portion of the receivable.
DEP Event Category includes the following event types that will be used to record deposits. This Revenue Event Category uses the Generic Event Type Processor logic.
AR20: Bill Deposit When a customer has to be billed for a deposit for security or other reasons, this event type is used to record the asset for the receivable and the liability for the deposit. Using this event type instead of AR52: Bill to Liability Account, allows for the amount of the deposit liabilities to be tracked on the Customer Account Information inquiry pages.
Posting Pair A: Principal
Dr R200: Billed Deposit Receivable (A)
Cr R201: Billed Deposit (L)
Prior Event Types: Referenced accounting activity for this event type is not likely in any form but a memo reference.
Subsequent Event Types: A receivable of this type has one of three outcomes:
Collection with AR21: Collect Deposit with a Cash Receipt transaction.
After all attempts at collection have failed and the receivable is written of with AR22: Write Off Deposit on a Write-Off transaction.
If the receivable was recorded as an intercept request, then either IN14 or IN15 event types for intercepting earned revenue would be used on an Internal Exchange Transaction to close all or a portion of the receivable.
AR21: Collect Deposit When a customer pays a deposit for security or other reasons, this event type is used to record the cash and the liability for the deposit. Using this event type instead of AR53: Collect to Liability Account, allows for the amount of the deposit liabilities to be tracked on the Customer Account Information inquiry pages.
Posting Pair A: Principal
Dr A001: Cash (A)
Cr R202: Collected Deposit (L)
Prior Event Types: Referenced accounting activity for this event type is optional and can be to AR20: Bill Deposit.
Subsequent Event Types: There will be no subsequent referencing of this event type. There may be a memo reference to return the deposit to the customer with AP06: Authorize Deposit Refund (detailed later in this Accounts Receivable tab).
AR22: Write Off Deposit When a customer account has had a deposit receivable past due for a significant period of time and it is determined that the receivable will never be collected, the receivable is then written off. This event type provides the ability to record such a write off. There is not the choice of write off methods with deposit revenue as with earned revenue. A user could cancel the receivable, modify it to zero-dollars, or use this event type.
The option also exists to remove the posting codes from the event type and let the write off just remove the receivable and deposit liability while not recording any new accounting entries. The accounting entries provided below ease reporting with memo accounts that will not be rolled forward or closed to any equity accounts at year-end.
Posting Pair A: Principal
Dr R203: Deposit Receivable Write Off (A)
Cr R204: Deposit Write Off (CA)
Prior Event Types: Referenced accounting activity for this event type is required with the only event type referenced being AR20: Bill Deposit.
Subsequent Event Types: There are no subsequent event types.
REF Event Category includes the following event types that will be used to record vendor refunds. This Refund Event Category uses the Generic Event Type Processor logic.
Use of the event types in this category is done in lieu of entering a credit memo with an Accounts Payable event type. The application of a credit memo requires another request for payment or multiple requests to equal or exceed the credit memo to occur before settling with the vendor. With the following event types, the vendor will then be invoiced or sent a statement requesting repayment. These event types also are eligible for being entered in the Intercept Request page to offset any future requests for payment to the vendor that occur before the receivable is collected. For intercepts, there is not the same requirement that there be an equal or greater amount of requests for payment for the intercept to be applied. Rather intercepts can be applied partially until the receivable is closed.
AR30: Bill Vendor Refund - Budgetary The first of two different vendor refund receivable methods, based on budgetary needs, is AR30. With this event type budget updates are made to decrease the amount of Accrued Expenditures at the time of billing, so budget authority is restored at the time of billing instead of collection as with the second method.
Posting Pair A: Principal
Dr R300: Billed Vendor Refund Receivable (A)
Cr D011: External Accrued Expenditure / Expense
Prior Event Types: Referenced accounting activity for this event type is not likely in any form but a memo reference to possibly the request for payment or disbursement that was incorrect.
Subsequent Event Types: A receivable of this type will have one of four outcomes:
Collection with AR32: Collect Vendor Refund will occur with a Cash Receipt transaction.
After several attempts at collection have failed, the receivable can be sent to an external party for collection. Event type AR34: Refer Vendor Refund to Collection Agency Budgetary on a Referral to Collection Agency transaction would record such an event unless the receivable was sold to the external party.
When all attempts at collection have failed and the receivable is considered uncollectible. At this point AR33: Write Off Vendor Refund would be used on a Write-Off transaction.
If the receivable was recorded as an intercept request, then either IN16 or IN17 event types for intercepting earned revenue would be used on an Internal Exchange Transaction to close all or a portion of the receivable.
AR31: Bill Vendor Refund Non Budgetary The second of two different vendor refund receivable methods, based on budgetary needs, is AR31. With this event type budget updates are not made to decrease the amount of Accrued Expenditures at the time of billing, so budget authority will only be restored at the time of collection with this second method.
Posting Pair A: Principal
Dr R300: Billed Vendor Refund Receivable (A)
Cr R301: Expenditure Refund Holding Account (CA)
Prior Event Types: Referenced accounting activity for this event type is not likely in any form but a memo reference to possibly the request for payment or disbursement that was incorrect.
Subsequent Event Types: A receivable of this type will have one of four outcomes:
Collection with AR32: Collect Vendor Refund will occur with a Cash Receipt transaction.
After several attempts at collection have failed, the receivable can be sent to an external party for collection. Event type AR35: Refer Vendor Refund to Collection Agency Non Budgetary on a Referral to Collection Agency transaction would record such an event unless the receivable was sold to the external party.
When all attempts at collection have failed and the receivable is considered uncollectible. At this point AR33: Write Off Vendor Refund would be used on a Write-Off transaction.
If the receivable was recorded as an intercept request, then either IN16 or IN17 event types for intercepting earned revenue would be used on an Internal Exchange Transaction to close all or a portion of the receivable.
AR34: Refer Vendor Refund to Collection Agency Budgetary When a customer account, that is also a vendor, has had a receivable past due for a significant period of time, the receivable is often turned over to a collection agency for collection. This event type provides the ability to record such a receivable under a different balance sheet account in addition to the different asset posting code while keeping the reduction in Accrued Expenditures for budgetary purposes.
Posting Pair A: Principal
Dr R304: Billed Vendor Refund Sent for Collection (A)
Cr D011: External Accrued Expenditure / Expense
Prior Event Types: Referenced accounting activity for this event type is required with the only event type referenced being AR30: Bill Vendor Refund - Budgetary.
Subsequent Event Types: A receivable of this type will have one of three outcomes:
Collection with AR32: Collect Vendor Refund will occur with a Cash Receipt transaction.
When all attempts at collection have failed and the receivable is considered uncollectible. At this point AR33: Write Off Vendor Refund would be used on a Write-Off transaction.
If the receivable was recorded as an intercept request, then either IN16 or IN17 event types for intercepting earned revenue would be used on an Internal Exchange Transaction to close all or a portion of the receivable.
AR35: Refer Vendor Refund to Collection Agency Non Budgetary When a customer account, that is also a vendor, has had a receivable past due for a significant period of time, the receivable is often turned over to a collection agency for collection. This event type provides the ability to record such a receivable under a different balance sheet account in addition to the different asset posting code while not reducing Accrued Expenditures.
Posting Pair A: Principal
Dr R304: Billed Vendor Refund Sent for Collection (A)
Cr R301: Expenditure Refund Holding Account (CA)
Prior Event Types: Referenced accounting activity for this event type is required with the only event type referenced being AR31: Bill Vendor Refund Non Budgetary.
Subsequent Event Types: A receivable of this type will have one of three outcomes:
Collection with AR32: Collect Vendor Refund will occur with a Cash Receipt transaction.
When all attempts at collection have failed and the receivable is considered uncollectible. At this point AR33: Write Off Vendor Refund would be used on a Write-Off transaction.
If the receivable was recorded as an intercept request, then either IN16 or IN17 event types for intercepting earned revenue would be used on an Internal Exchange Transaction to close all or a portion of the receivable.
AR32: Collect Vendor Refund A single event type exists for collecting a vendor refund Cash Expenditures is credited at this point, increasing budget availability.
Posting Pair A: Principal
Dr A001: Cash (A)
Cr D014: External Cash Expenditure/Expense
Prior Event Types: Referenced accounting activity for this event type is optional and can be to AR30: Bill Vendor Refund Budgetary, AR31: Bill Vendor Refund Non Budgetary, AR34: Refer Vendor Refund to Collection Agency Budgetary, or AR35: Refer Vendor Refund to Collection Agency Non Budgetary.
Subsequent Event Types: While there is no event type that will reference and liquidate this type of revenue, there is one that can memo reference it. AP01: Authorize Normal Payment would be used to return money the vendor if too much was refunded. (Please refer to the Accounts Payable topic under Accounting Model Delivered Configuration.)
AR33: Write Off Vendor Refund When a customer account, that is also a vendor, has had a receivable past due for a significant period of time and it is determined that the receivable will never be collected, the receivable is then written off. This event type provides the ability to record such a write off. There is not the choice of write off methods with unearned revenue as there is with earned revenue. A user could cancel the receivable, modify it to zero-dollars, or use this event type.
The option also exists to remove the posting codes from the event type and let the write off just remove the receivable and unearned revenue while not recording any new accounting entries. The accounting entries provided below ease reporting with memo accounts that will not be rolled forward or closed to any equity accounts at year-end.
Posting Pair A: Principal
Dr R305: Vendor Refund Receivable Write Off (A)
Cr R306: Vendor Refund Write Off (AO)
Prior Event Types: Referenced accounting activity for this event type is required with the only two event types referenced being AR30 and AR31 for Bill Vendor Refund Budgetary and Non Budgetary respectively.
Subsequent Event Types: There are no subsequent event types.
TR22: Expense Uncollected Travel Advance Used on a Write-off (WO) transaction when an unused travel advance was closed by HRM or by 1099 as taxable income to the traveler.
Posting Pair A: Vendor Refund
Dr D014: External Cash Expenditure / Expense (N)
Cr T001: Travel Advance (A)
Prior Event Types: Referenced accounting activity for this event type is required with the only event type referenced being TR20: Bill for Return of Unused Travel Advance.
Subsequent Event Types: There are no subsequent event types.
TR23: Refer Travel Advance Return to Collection Agency Used on a CL transaction to refer an outstanding travel advance to a collection agency.
Posting Pair A: Vendor Refund
Dr R304: Vendor Refund to Collection Agency (A)
Cr T001: Travel Advance (A)
Prior Event Types: Referenced accounting activity for this event type is required with the only event type referenced being TR20: Bill for Return of Unused Travel Advance.
Subsequent Event Types: There are no subsequent event types.
OVP Event Category includes the following event types that will be used to record overpayments made by a customer. This Overpayment Event Category uses the Generic Event Type Processor logic.
Use of the event types in this category is done automatically when the Auto Apply action is used on a Cash Receipt transaction and a reference is made at the customer account, not transaction or transaction line level. If not enough open receivables are found for a customer account to equal the Line Amount on the Cash Receipt vendor line, an accounting line will be generated with one of these two event types, depending on whether or not the Reserve Cr Balance indication is true, to book the overpayment. Either event type can also be entered to manually record an overpayment.
AR40: Collect Unreserved Overpayment When an overpayment occurs that should be recorded as 'unreserved', this event type is used. When an unreserved credit balance exists, the Auto Netting batch job in A/R can use that credit balance to satisfy an outstanding receivable.
Posting Pair A: Disbursement
Dr A001: Cash (A)
Cr R401: Unreserved Overpayment (L)
Prior Event Types: Referenced accounting activity for this event type is not a likely occurrence.
Subsequent Event Types: Referencing accounting activity for this event type is not a likely occurrence.
AR41: Collect Reserved Overpayment When an overpayment occurs that should be recorded as 'reserved', this event type is used. When a reserved credit balance exists, the Auto Netting batch job in A/R cannot use that credit balance to satisfy an outstanding receivable. A manual effort is required to reduce the credit balance and apply it as necessary.
Posting Pair A: Disbursement
Dr A001: Cash (A)
Cr R400: Reserved Overpayment (L)
Prior Event Types: Referenced accounting activity for this event type is not a likely occurrence.
Subsequent Event Types: Referencing accounting activity for this event type is not a likely occurrence.
SFTR Event Category includes the following event type, which is used when receiving customer payments through lock-box operation. The Cash Receipt Generation batch program reads input from the external collection agency and creates special Cash Receipt (CR) transactions known as Cash Transfers. The underlying accounting event increases cash/collected revenue in a specific account and decreases cash/collected earned revenue in a special Treasury or Clearing account as a net zero transaction.
AR99: CER Transfer from Sweep Used on the Decrease Accounting Line to decrease cash/collected revenue. As the record of cash to the treasury/clearing account was not to a customer account, the decrease of cash and revenue from that account should not update a customer account. The positive line on the cash transfer will make that update.
Posting Pair A: Principal
Dr A001: Cash (A)
Cr R003: External CER
Posting Pair B: Interest
Dr A001: Cash (A)
Cr R003: External CER
Posting Pair C: Late Fee
Dr A001: Cash (A)
Cr R003: External CER
Posting Pair D: Admin Fee
Dr A001: Cash (A)
Cr R003: External CER
Posting Pair E: NSF Fee
Dr A001: Cash (A)
Cr R006: Collect NSF Rev
Posting Pair F: Other Fee
Dr A001: Cash (A)
Cr R003: External CER
Prior Event Types: Referenced accounting activity for this event type should be setup as prohibited.
Subsequent Event Types: Referencing accounting activity for this event type is not a likely occurrence.