3.2.7 Tracers

This topic provides the systematic instructions to capture the Tracers details.

Tracers are reminders, sent to various parties involved in a bill indicating that an exception that has occurred while processing the bill. In this screen, capture tracer details for the following exception events:
  • Payment Exception
  • Acceptance Exception
  • Charge Exception
  • Reserve Exception

Reserve Exception – sent by negotiating bank (for bills under LC), if discrepancies are noted, and negotiation is done under reserve (right of recourse). The tracers are for reminding resolution of the discrepancies and get stopped when the respective discrepancy is marked as resolved

The details specified for the product involved in the bill will default to the contract. Change the defaults to suit the requirements of the bill you are processing.

Note:

If the option Reimbursement Claim in the Bills and Collections Product Definition screen, you will not be able to save details in this screen
Specify the User ID and Password, and login to Homepage.

Navigate to Bills and Collections Product Definition screen.

  1. On Bills and Collections Product Definition screen, Click Tracers.
    Tracers screen is displayed.
  2. On the tracers screen, specify the details as required.
    For information on fields, refer to: Table 3-17

    Table 3-17 Tracers - Field Description

    Field Description
    Tracer Generation Indicate whether the exception tracer (for reserve, acceptance, payment and charges) applies to the bill you are processing. Select one of the following options:

    Required -If you specify that a tracer applies to a bill, you should also specify the number of tracers that should be generated, for the exception.

    Not Required - select this option to indicate that the exception tracer is not applicable, to the bill you are processing.

    Till resolved -If you indicate that the tracer should be generated until the exception is resolved, you need not specify the number of tracers that should be sent. This is because the tracer is generated at the frequency that you specify until the exception is resolved.

    Number of Tracers Required If you have indicated that the tracer is applicable, to the bill you are processing, you should also specify the maximum number of tracers that should be generated, for each of the exception events.

    By default, the first tracer for all authorized bills linked to this product will be sent after the number of days that you prescribe, for the product.

    Start Tracer after Days Based on the requirement, exception tracers is generated after the maturity date of the bill. While creating a product, you have also indicated the number of days that should elapse after the bill matures on which the first tracer should be generated.
    Generation Frequency Days Specify the frequency (in days), with which the tracer should be sent to the concerned parties, involved in the bills linked to this product.
    Preferred Tracer Medium For each of the exception tracers that you specify, indicate the preferred medium through which the tracer should be generated to the concerned party.

    For a bill involving the product, change the medium that is defaulted. The medium you specify here is only the preferred medium, for the exception tracer.

    Template ID Specify the template related to MT799 or MT499 message types. The adjoining option list displays all the templates related to MT799 (if it is under LC) or MT499 (if it is not under LC) message types defined in the ‘Swift FFT Template Screen Maintenance’ screen. Choose the appropriate one.

    This field is mandatory if the ‘Tracer Generation’ is indicated as ‘Required’ and ‘Preferred Medium’ as ‘SWIFT’. This Template id is used while generating Charge and Commission Tracer (CHG_COM_TRACER) in MT799/MT499 swift format as part of LQ EOD Batch if the ‘Preferred Medium’ is ‘SWIFT’.

    For further details on Swift FFT Template Screen Maintenance screen, refer the section ‘Maintaining SWIFT FFT Template’ in the Defining Free Format Messages chapter in the ‘Messaging System’ User Manual.