Collection Package Work Card Record
The Collection Package automatically identifies delinquent loans, negative balance shares, and overlimit line of credit loans, then queues them according to your credit union’s specifications. The system automatically creates Collection Work Card records for all of these situations. The Collection Work Card record includes the following fields, which are defined below:
FM Last Date
The system updates this field with the current system date whenever you perform file maintenance on this CP Work Card record. This field in the CP Work Card record is not updated when the file maintenance is performed by a batch process.
| Attribute | Value |
|---|---|
| Field Number | 002 |
| Mnemonic | FMLASTDATE |
| Data Type | Date |
| Source | System-calculated |
| Help File | 02502 |
| Default Control | No |
| Default Value | Date Null |
Close Date
Enter a close date for the Work Card record following your credit union’s policies. When Daily Posting runs after this date, the system sets the Active field to (0) Inactive.
| Attribute | Value |
|---|---|
| Field Number | 003 |
| Mnemonic | CLOSEDATE |
| Data Type | Date |
| Source | User-entered |
| Help File | 02503 |
| Default Control | No |
| Default Value | Date Null |
Next Work Date
Enter the next date you expect to work this Work Card record.
| Attribute | Value |
|---|---|
| Field Number | 004 |
| Mnemonic | NEXTWORKDATE |
| Data Type | Date |
| Source | User-entered |
| Help File | 02504 |
| Default Control | No |
| Default Value | Date Null |
Last Work Date
The system updates this field with the current system date whenever a collector creates a collection Note record, records a promise to pay, or generates a collection letter.
| Attribute | Value |
|---|---|
| Field Number | 005 |
| Mnemonic | LASTWORKDATE |
| Data Type | Date |
| Source | System-calculated |
| Help File | 02505 |
| Default Control | No |
| Default Value | Date Null |
Last Work Time
The system updates this field with the current system time whenever a collector creates a collection Note record, records a promise to pay, or generates a collection letter.
| Attribute | Value |
|---|---|
| Field Number | 006 |
| Mnemonic | LASTWORKTIME |
| Data Type | Code to 2359 |
| Source | System-calculated |
| Help File | 02506 |
| Default Control | No |
| Default Value | 0 |
Collector ID 0
Whenever the Daily Posting batch program assigns a CP Work Card record to a collector, the system updates the Collector ID 0 field with the assigned collector’s user number. You can change which collector is assigned to a CP Work Card record through file maintenance of this field. The system validates the field value against the Valid Collector List section in the Collection Work Card parameters.
| Attribute | Value |
|---|---|
| Field Number | 008 |
| Mnemonic | LASTCOLLECTORID |
| Data Type | Code to 9999 |
| Source | User-entered or System-calculated |
| Help File | 02508 |
| Default Control | No |
| Default Value | 0 |
The Collector ID 0 field documents the last collector assigned to a CP Work Card record. You can use the value in this field to maintain the same collector on a specific CP Work Card record when you assign collectors with the custom specfile in the Daily Posting batch program.
Collector ID 1 – Collector ID 9
We replaced the Secondary Collector ID List field with new Collector ID 1 – Collector ID 9 fields. These fields are used when a CP Work Card record is assigned to more than one collector.
| Attribute | Value |
|---|---|
| Field Number | 013:001 - 013:009 |
| Mnemonic | SECCOLLECTORID:1 - SECCOLLECTORID:9 |
| Data Type | Code to 9999 |
| Source | User-defined or System-calculated |
| Help File | 02508 |
| Default Control | No |
| Default Value | 0 |
9999 indicates that no collector has been assigned. If you set the Collector ID 0 field to 9999, the system blanks out the Priority 0 field. An assignment of 9999 cannot be included in the Valid Collector List parameter in the Collection Work Card parameters. If you change the Collector ID 0 field to 9999, the system moves all the following fields up, placing the 9999 value at the end of the list.
Note: The system does not prevent you from assigning the same collector to the same Work Card record more than once. For example, if you assign collector 113 to Collector ID 0 and also to Collector ID 5, the system displays the same Work Card record multiple times in the collection queue: once for each assignment. Additionally, each assignment has its own Priority field setting.
You can perform file maintenance on the Collector ID 0 - Collector ID 9 fields and set the values to 9999 in the following areas:
- Directly on the CP Work Card Record screen in the Account Manager work area
- Using the Assign to… functionality in the collection queue
- Using the Perform FM from PowerOn Output function of the Miscellaneous Processing batch program
Note: You cannot set the Collector ID 0 - Collector ID 9 fields to
9999using the Collection Queue Specification File prompt in the Daily Posting batch program.
Type
This field identifies the kind of Work Card record. Only defined Work Card Types are displayed as options for this field.
| Attribute | Value |
|---|---|
| Field Number | 001 |
| Mnemonic | TYPE |
| Data Type | Code to 99 |
| Source | System-defined & User-entered |
| Help File | 02501 |
| Default Control | No |
| Default Value | 0 |
Data Type Descriptions(0) DQ Loan/Share
Select this option if the Work Card record is for collection of a delinquent loan or share.
(1) NSF Check
Select this option if the Work Card record is for collection of an NSF check.
(2) Third Party CC
Select this option if the Work Card record is for collection of a third-party credit card loan.
(3) Fraud
Select this option if the Work Card record is for collection of a fraud.
4–99
Select a credit union-defined collection type. You can define these types in work card type descriptions of the Collection Work Card Parameters.
Note: If you are using the Card Dispute Handling feature, you can create Collection Work Card records for card disputes in the Daily Posting batch program. If you choose to do this, Daily Posting prompts you for a Collection Work Card Type field value with a default type of 4. You can, of course, change it to any value you choose.
Active
This field identifies the status of the Work Card record.
| Attribute | Value |
|---|---|
| Field Number | 009 |
| Mnemonic | ACTIVE |
| Data Type | Code to 1 |
| Source | User-entered or System-calculated |
| Help File | 02509 |
| Default Control | No |
| Default Value | 0 |
Data Type Descriptions(0) Inactive
Indicates the status of this Work Card record is inactive.
(1) Active
Indicates that the status of this Work Card record is active.
When the Daily Posting batch program creates a Work Card record, it sets this field to (1) Active for Work Card records with a Type field of (0) DQ Loan/Share and if collection conditions no longer exist, which make the Work Card unnecessary, Daily Posting sets the Work Card record to (0) Inactive. For a Work Card record with any other type, this field remains set to (1) Active until a user (or a file maintenance specfile) revises it. Symitar’s standard Collection Package specfiles queue Work Card records only if they have a code of (1) Active and do not have a value in the Close Date field.
If you are using the Card Dispute Handling feature, you can create Collection Work Card records for card disputes in the Daily Posting batch program. If you choose to do this, Daily Posting checks the value of the Tracking Code field in the associated Card Dispute Tracking records. If there are any records with a Tracking Code of Pending, the system sets this field to (1) Active. If there are no pending disputes, the system sets this field to (0) Inactive.
The system closes the Work Card record if the collector enters a Note Code field value of (9) Removal from Collections under the following circumstances:
- The loan becomes current
- The member brings the loan under the credit limit
- The member brings the share to a non-negative balance
Note Purge Date
This field is not currently used.
| Attribute | Value |
|---|---|
| Field Number | 007 |
| Mnemonic | NOTEPURGEDATE |
| Data Type | Date |
| Source | System-calculated |
| Help File | 02507 |
| Default Control | No |
| Default Value | Date Null |
Record Change Date
The system stores the system date in this field when you create, change, or save the Collection Work Card record. There are times when the system updates this field because the record was saved, even though there may not be any actual changes in the record.
| Attribute | Value |
|---|---|
| Field Number | 014 |
| Mnemonic | RECORDCHANGEDATE |
| Data Type | Date |
| Source | System-entered |
| Help File | 02513 |
| Default Control | No |
| Default Value | Date Null |
Note: The system does not change the Record Change Date field value when a calculated field changes.
You cannot perform file maintenance on this field.
Priority 0
This field contains the Priority 0 field value you assigned with the Daily Posting batch program using the custom specfile you entered at the Collection Queue Specification File prompt. You can perform file maintenance on this field.
| Attribute | Value |
|---|---|
| Field Number | 11 |
| Mnemonic | PRIORITY |
| Data Type | 20 Characters |
| Source | User-defined or System-calculated |
| Help File | 02511 |
| Default Control | No |
| Default Value | <Blank> |
Priority 1 – Priority 9
These fields determine the order in which the work cards appear in the collection queue. They contain the priority you assigned with the Daily Posting Batch Program using the custom specfile you entered at the Collection Queue Specification File prompt.
| Attribute | Value |
|---|---|
| Field Number | 012:001 - 012:009 |
| Mnemonic | SECPRIORITY:1 - SECPRIORITY:9 |
| Data Type | 20 Characters |
| Source | User-defined or System-calculated |
| Help File | 02511 |
| Default Control | No |
| Default Value | <Blank> |
If you set a Collector ID 0 – Collector ID 9 field to 9999, the system blanks out the associated Priority 0 - Priority 9 field. If you change the Collector ID 1 – Collector ID 9 fields to 9999, the system moves all the following fields up, placing the 9999 value at the end of the list.
You can perform file maintenance on the Priority 0 – Priority 9 fields in the following areas:
- Directly on the CP Work Card Record screen in the Account Manager work area
- Using SymConnect
Note: As of Symitar Release 2025.00, the SymConnect API is fully decommissioned. All clients and vendors are required to transition to SymXchange.
- Using the Perform FM from PowerOn Output function from the Miscellaneous Processing batch program
Non-Displayed Fields
These fields do not appear in the system and are only accessed by PowerOn specfiles, SymConnect, or SymXchange.
Locator
The system stores a unique number within each member account in this field that can be used as a unique identification of this record.
| Attribute | Value |
|---|---|
| Field Number | 010 |
| Mnemonic | LOCATOR |
| Data Type | Number |
| Source | System-entered |
| Help File | 02510 |
| Default Control | No |
| Default Value | 0 |
The value is a positive number greater than zero and up to about two billion. The system automatically assigns the Locator value when the record is created, and you cannot change it.
The Locator field can be used during PowerOn file maintenance (both on demand and batch) to uniquely identify a record. Using the Locator field is recommended since a record’s ordinal sequence number may change if someone else inserts or deletes a record with a lower ordinal sequence number just before you post your file maintenance.
- Have a how-to question? Seeing a weird error? Get help on our collaborative Discourse page.
- Register for the Developer Office Hours where we answer technical Q&A, in real time, from the audience.