The event types used in the Accounts Receivable area produce posting pairs based on instructions from the Line Type field on the accounting line. In this field, users specify which posting pair is to be created by selecting a Line Type that corresponds to a posting pair. The generic event type processor is actually what is used to create posting lines in this event category. Rules in this event type processor involve the short payment functionality that is specific to Accounts Receivable or logic to infer a default object or default revenue source. To be eligible to use the AR-specific tolerance logic, one has to be doing a document-level reference not a customer account or accounting line reference.
If the referenced document type is RE (Receivable) or CL (Referral to Collection Agency) and the referencing document type is CR (Cash Receipt), update the Collected Amount on the referenced accounting line with the delta amount of the referencing line.
*Then the tolerance tables are evaluated: System Tolerances (STOL), Fund Tolerances (FTOL), and Document Code Tolerances (DTOL). If the amount of the referencing CR is not within tolerances for the RE, then issue the common tolerance error.
*If within underage tolerances, and the 'Allow Final Short Reference on CR’ parameter is set to 'Manual’ on the APPCTRL table, the Reference Type may be manually set on the accounting line of the CR document to Partial or Final and evaluated by the generic tolerance logic; however, if the 'Allow Final Short Reference on CR’ parameter is set to 'Auto’, then the system evaluates the AR-specific tolerance logic, and then sets the reference type to final and updates the Short Payment Tolerance Amount on the RE accounting line with the short amount. Common referencing logic will then see that the RE line is closed.
*If within overage tolerances, under the 'Manual’ or the 'Auto’ setting of the 'Allow Final Short Reference on CR’ parameter, the system evaluates the generic or AR-specific tolerance logic respectively, and then sets the reference type to Final and updates the Over Payment Tolerance Amount on the RE accounting line with the overage amount. Common referencing logic will see that the RE line is closed.
If a posting code used has a default object, that object code and sub object code, if available, will be inferred to the posting line. The Bad Debt Expense Object is one such example.
If a posting code used has a default revenue source, that revenue source code and sub revenue source code, if available, will be inferred to the posting line. The NSF Check Charge Revenue Source is one such example.
If the AR Event Type Processor is called, and all of the following are true:
The referencing document type is RE, CL, CR, or WO
The referenced document type is RE, CL, or ARE
The reference is a non-memo type of reference
The AR_REF_OPT on the Application Parameters table has a parameter value of 3
Then, if the BFY field on the referencing accounting line is NOT blank, the processor will set the BFY on the liquidation posting line(s) to that BFY value. If the BFY value on the referencing accounting line is blank, the processor will set the BFY on the liquidation posting line(s) to the CURR_BFY value of the accounting line.
Note: For CR documents, if the APPCTRL parameter Allow Final Short Reference on CR = Auto, proceed with the AR Event Type Processor logic using the special Short & Over Payment Logic. (This will set the Ref Type and/or issue any tolerance errors. Any user selected Ref Type value will be overwritten during the AR Event Type Processor logic.) For CR documents, if the APPCTRL parameter Allow Final Short Reference on CR = Manual, bypass the AR Event Type Processor logic and call the Generic Event Type Processor logic to perform the tolerance evaluation.