Receivable Transaction Type

The Receivable (RE) transaction is used to bill or record money owed as the result of:

  • Goods or services already provided

  • Goods or services anticipated to be provided (for example, rent)

  • Overpayments to a vendor

  • Anticipated or earned revenue from external funding sources (for example, federal grants, taxes)

The RE results in the generation of an Invoice or Statement to bill customers. Accounting entries made by this transaction vary, depending upon the event type coded. Use the Receivable (RE) transaction to:

  • Bill for earned revenue (REI and RES transaction)

  • Bill for unearned revenue

  • Bill for a deposit

  • Bill for a vendor for a refund

In addition to supporting the Receivable transaction itself, Advantage Financial allows you to:

  • Make inquiries on the status of existing receivables already in the system

  • View or print reports related to receivables processing

For detailed information on each of the tabs that exist on RE, refer to the following topics:

Receivable Delivered Transaction CodesReceivable Delivered Transaction Codes

The RE Transaction Type has the following Transaction Codes (listed alphabetically by Transaction Name).

Transaction Name

Transaction Code

Intended Use

Advantage Permitting Receivable

PERE

The PERE transaction cannot be created online. The PERE transaction is created automatically in Advantage Financial when the Advantage Permitting application has sent data to Advantage Financial that requires a Receivable to be created.

Cost Accounting Receivable

CARE

This transaction allows you to record cost accounting related receivables. The CARE transaction allows you to capture funding source information because this type of receivable is typically posted against a particular funding source. It results in the generation of an Invoice or Statement to bill customers.

Receivable

 RE

This transaction is for entering a transaction to record money owed as a result of goods or services provided, overpayment to a vendor, or anticipated receipt of unearned revenue. It results in the generation of an Invoice or Statement to bill customers. Accounting entries made by this page vary, depending upon the event type coded.

Receivable for Inventory

REI

This transaction allows you to record money owed as a result of goods issued from inventory. It results in the generation of an Invoice or Statement to bill customers. The Inventory Receivable Generation chain creates Receivable for Inventory (REI) transactions. Each REI transaction references the Stock Issue Confirmation for External Customers (CIE) transaction that issued the inventory. REI transactions only update the External Stock Return Issue Cross Reference table on cancellation of the transaction. On cancellations of REI transactions modified by the submission of a Stock Return for External Customers (SNE) transaction, the Invoice ID on the External Stock Return Issue Cross Reference table is cleared.

The REI transaction supports the Billed Earned Revenue event type.

Surplus Award Receivable

RES

This transaction allows users to record money owed as a result of surplus auction award of goods or services. It results in the generation of an Invoice or Statement to bill customers. The RES transaction can reference an Auction Requisition (RQA) but is otherwise similar to the RE. The RES transaction supports the Billed Earned Revenue event type.

Unbilled Receivable

UB

The purpose of the Unbilled (UB) Transaction Code is to create a way to book a receivable in the event a cash advance was received prior to the creation of the Receivable. In this case, the UB transaction may be used to reference the Advance (created on a CRA transaction). In addition, the UB transaction may be used to allow a Receivable transaction to reference another Receivable.

This type of reference is limited to instances where the Cash Receipt does not already contain a transaction reference with a Reference Type of Partial or Final (memo references are allowed). When the reference transaction field is entered on the Receivable, the reference type is automatically set to Memo (no accounting action), unless the referenced transaction is an ARE, RQ, CIE, or a RE with a Transaction Sub-Type of UB (Transaction Sub-Type for Unbilled Receivable), or CR with a Transaction Sub-Type of ADV (Transaction Sub-Type for Advance). If an ARE, RQ, CIE, RE with a Transaction Sub-Type of UB (Unbilled) is referenced on the RE then the reference type is automatically defaulted to Partial or Final depending on the reference information on the accounting line and the System Tolerance, Transaction Tolerance and Fund Tolerance table setup. If a CR with a Transaction Sub-Type of ADV (Advance) is referenced on the Receivable then the reference type automatically defaults to Partial or Final depending on the reference information on the accounting line (tolerance will not be used in this scenario).

TasksTasks

For instructions on how to create a RE, refer to the "Create a Receivable" topic.

Related Topic(s):

  • For a description of the delivered event types allowed for the RE transaction type, please refer to "Accounts Receivable Accounting Model" under the Accounting Model Delivered Configuration topic in the CGI Advantage - Financial Administration User Guide.