Claims pending reason codes

Each claim pending reason code is designated a two character code which begins with an A, B or a 0.

  • The ‘A’ codes are assigned to the header information of the order.
  • The ‘B’ codes are assigned to the detail lines of the order.
  • The ‘0’ codes are user defined.

The Claims pending system is used for validation against company policy. Certain pending rules are checked when entering a claim, like Outside Returns Policy. Claims that are held as pending can be reviewed by pending code.

The Pending rejections program provides a facility to automatically reject claims based on pending rules via field Auto reject. A pending reason for this purpose must be entered in the Pending Department Definition and flagged as 1-auto reject. Pending checks print R/A’s before rejecting them automatically.

Specific item groups can be set up to bypass the pending check. A control file holds the group codes and a flag to indicate whether or not that group is to be excluded from the pending check. It is not necessary to load all groups, only those to be excluded.

The pending function is available to users that are authorised to review pended claims only. Departments and users within these departments are defined to have the authority to review some or all pended claims, by pending reason code.

Claims that pend can be directed to the appropriate users for approval, based on the division of the Description. If orders have Descriptions from more than one division, the division of the first Description on the order is used.

Departments and users within these departments are defined to the system by Division. The pending review checks these definitions and allows users access to the appropriate claims in the correct divisions.

View Global reasons no to pend
Reasons  Description 
Exceptions by type of claim

The parameters for not pending based on the Type of order/Claim are set in TMSDS/PEND-EXO.  Type of order is classified by the use of the following.

Document type (DT) with valid codes in TMSDS/TR-DT

Document sub-type (DST) with valid codes in TMSDS/TR-DST

Picking method (PCKM) with valid codes in TMSDS/TR-PCKM

Source of transaction (SRCT) with valid codes in TMSDS/TR-SRCT

Type of sale (TOS) with valid codes in TMSDS/TR-TOS

Payment terms code (PYTC) with valid codes in TMSDS/CM-PAYT

In PEND-EXO, the pending reason code is listed and for each of these reason codes, the types of order/claim codes that are not to pend for that reason are listed. 

Do not pend after a return 

The Claims pending check program can bypass the pending claim check depending on the setting in TMSAR/PEND-DSC the following settings.

  • 1 = always checks the pending rule
  •  2 = bypass where zero quantity
  • 3 = bypass if return quantity.

 

View System defined - claims pending reason codes

Claims Pending Reason Codes are established in control file TMSAR/PEND-DSC.

 Pending reason codes Description 
AB=Header amount not equal to detail amount (header)  The sum of the line values does not equal the header value of the claim. 
AC=No claim reference (header)  No claim number – the parameters are set in control file TMSAR/CE-CLNO. If the flag is set to 1=Yes another parameter can be set to check for duplicate claim number as a Warning only or Error. Error setting does not allow duplicate claim number to be entered. 
AD=Authorised qty not equal to returned qty (digital item)  If the access codes returned is not equal to the authorised quantity then the claim will pend. 
AE=Authorised qty not equal to returned qty (stock item)  If the authorised quantity is not equal to the returned quantity then the claim will pend. 
AK= Claim amount not equal to original claim amount (header)  Original amount is not equal to the line total. Zero is ignored as that is a deliberate exclusion from Credit Checking. To automatically adjust the claim amounts, the parameters are established in TMSAR/CL-OADJ. The upper and lower limit must be defined as well as an Adjustment item. This item must be set up in the Item masterfile as a non-stock item. Major Accounts can be set up to automatically balance using a combination of TMSAR/PEND-ADJ and TMSAR/CL-OADJ.
AN=Next month document (header)  Stock is recorded immediately but the debtors and sales are reflected in the next month or sales analysis is not affected. This uses the invoice period on the Distribution Transaction header file. 
 AR=Manual review required (header) The parameters are established on TMSAR/PEND-DST. It holds those document sub-types (valid according to the TMSDS/TR-DST) that are always to pend for manual review. These document sub-types have a pending reason of R=Review manually. 
AU=No authorisation number for return (header)  No authorization number is used when RA numbers are entered manually. Claim Reference Number equal to RGA number for manual docket number. If allocate different numbers depending on type of returns, numeric in both fields. If it needs to be input, pend if left empty. Parameters are established in TMSAR/CL-RGA and TMSAR/RA-SGEN.
AV=Above maximum value allowed (header)  Parameters are established in TMSAR/PEND-VAL. This control file defines the over maximum claim value in whole for pending. 
AX=Customer stopped/expired (header)  Parameters are established in TMSAR/CL-ALCLC. This control file contains a Y/N flag which determines whether entry of claims against a closed customer is allowed. Y = allow entry of claims against a closed customer. N = do not allow entry of claims against a closed customer. 
AZ=Authorisation expired (header) There is a window for validity time frame. Parameters are established on TMSAR/CL-CUTD. This control file calculates the default expiry date on entered claims: today’s date + the number of days on this control file = expiry date. This can be overridden on each claim. This calculated expiry date is used in pending review and purge routines.
BA=Return not allocated to original document (detail) Line on claim not allocated to an invoice. No debtor’s allocation – parameters set in TMSAR/CL-AALOC (N). No invoice could be found either manual or auto allocation. The system can be set up to auto allocate and pick up a price (oldest first). If a claim is auto allocated it could be raised against that specific invoice. The parameters are set in TMSAR/CL-PRCR. This pending reason also applies to digital products.
BB=IC claim but no valid IC invoice found If there is no valid inter-company invoice found for an inter-company claim then the claim will pend with this pending code. The pended inter-company credit claim can be approved on claim pending review if the ‘allow approval’ flag against this pending code is flagged as ‘Y’ on TMSAR/PEND-DSC
BD=Discount override (detail) Discount override on line or discount field on header. This pending reason also applies to digital products.
BF=Return of firm sale (detail) The customer or item or whole order has been flagged as a firm sale. i.e. non returnable sales and goods have been sent back. This pending reason also applies to digital products.
BI=Unauthorised return/mismatch return reason The return is not authorised and the return reason code does not match.
BO=Outside returns policy (detail) The parameters are established in TMSAR/CL-ALLOC and TMSAR/CL-CTL and the Database. These are system defined periods that are used with the minimum and maximum number of months that are set up in TMSAR/CL-CTL. There are some cases where the claim carries a customer number that differs from the billing number on the original invoice. It enables you to determine how this claim is to be allocated. For example: a book store registers a claim under its own account number, but the relating invoice is charged to the book store’s head office account (it’s billing number). Allow allocation to a billing number Y/N auto allocation. This code defines which method of allocating claims to existing invoices is applicable. This pending reason also applies to digital products.
BP=Price override (detail) Price override on a line. This pending reason also applies to digital products.
BQ=Quantity exceeds predefined limit The parameters are established on TMSAR/PEND-QTY. This control file holds a quantity limit, which is used when entering a claim. Claims pend if the quantity that has been claimed is greater than or equal to this limit. This control file also contains a flag that determines whether or not you want the system to check this quantity limit on all types of claims or only those with a physical return.
BT=Total returns exceed threshold (header)

A threshold could be that only a percentage of gross sales can be returned or that there is a time frame allowing returns. These are established in the Customer database maintenance file for Returns policy group and is also applicable to digital products. Parameters are established in the following control files.

  • TMSAR/CE-RTNP
  • TMSAR/RTN-UTHR
  • TMSAR/CL-CTL
BY=Product stopped/expired (detail) Parameters are established in TMSAR/CE-VALIS. The Claim Control and Stock Receiving systems use this control file. It contains two Y/N flags which determine whether claims can be recorded for a suspended (status S) and/or closed (status C) item. The first flag determines whether or not claims can be entered for suspended items. If the flag is set to Y = Claims can be entered for suspended items, N = Claims cannot be entered for suspended items. An error message is displayed requiring you to remove the item. The second flag determines whether or not can be entered for closed items. If the flag is set to Y = Claims can be entered for closed items, N = Claims cannot be entered for closed items. An error message is displayed requiring you to remove the item

 

View User defined - claims pending reason codes

Codes 00-09 are usually used for user defined pending reason codes. The checking of these conditions is sequenced by TMSAR/SEQ-PDOC. The user defined reason applicability could be based on the following.

  • Document type – TMSDS/TR-DT
  • Document sub-type – TM SDS/TR-DST
  • Picking method – TMSDS/TR-PCKM
  • Return reason – TMSDS/TR-RSN
  • Type of sale – TMSDS/TR-TOS
  • Customer number – DSM005 Customer masterfile