Common Mismatched Key Errors
Four Record Keys
Each key is listed in the left column, followed by its location within each product. All four keys must be present and match the Forwarder Placement Record 1001.
| Key to Match | vExchange Analytics | Collection-Master | Q-LawE | YGC |
| cred_fileno | Creditor Fileno |
MASTER.FORW_FILENO
Placement screen in the “File” field next to the Forwarder Number. |
debt.custfile Workcase > enter ourfile > debt.custfile field identified in this screen. |
FORW_FILE |
| sender_int_file | Sender Fileno |
MASTER.FORW_REFNO Placement screen in the “Ref” field next to the “File” field that is next to the Forwarder Number. |
debt.ncustfile Workcase > enter ourfile > debt.ncustfile field identified in this screen. |
FILENO |
| forwarder_id | Sender Id |
MASFORW.EDI_ACCT_NO Inside the Forwarder file [1-2-1-1] EDI Setup screen that is the Account # for the Forwarder. |
cust.edicltcode and cust.yougotclm Workcase > Clients > client list > select client > Misc Info tab to view the fields identified in this screen. |
FORW_ID |
| agent_id | Receiver Id | Pulls from YouveGotClaims ID# in [1-S-4-8] |
cust.edifirmcod Workcase > Clients > client list > select client > Misc Info tab to view the field identified in this screen. |
FIRM_ID |
Common Mismatched Key Errors
| Type of Mismatch | Example | Result of Mismatch |
| Wrong Forwarder ID | Receiver enters the wrong Forwarder ID. |
Claim cannot be matched to an existing claim from the intended Forwarder. The Forwarder will not receive the data in their daily delivery files since the 4 keys do not match what the Forwarder has established on vExchange. |
| Wrong Forwarder Sub ID |
Forwarder uses multiple Sub-Forwarder IDs to place a single claim with a Receiver. Receiver uses the Forwarder ID without appending the correct, matching Sub ID, such as: • TEST.123 vs TEST.987 |
A different Sub Forwarder ID will initiate a new claim rather than send it to the correct claim of the Forwarder. The Forwarder will not receive the data in their daily delivery files since the 4 keys do not match what the Forwarder has established on vExchange. |
| Blank Fields | Creditor Fileno is entered but Sender Fileno is blank or vice versa. |
If a field is left blank, it will establish a new claim in vExchange rather than matching the existing claim. The Forwarder will not receive the data in their daily delivery files since the 4 keys do not match what the Forwarder has established on vExchange. |
| Format Variations |
Account mismatches can occur if the firm exports and manually updates the data with typos. Or the data was auto-formatted by Excel or other software. Examples: • Letter I is re-entered as the number 1. • Letter O is re-entered as the number 0. • Excel got rid of the leading zeros in a Creditor FileNo. • Firm appended “et al” to the Creditor FileNo. • Truncated data (1234-5678-9012-3456 vs 1234-5678-90). • Masked data (1234-5678-xxxx or ****-5678-9012, etc.). Note: You can prevent auto-formatting by Excel. Read How to Prevent Microsoft Excel Automatic Data Conversion for more information. |
All variations from an exact match will create a new claim. The Forwarder will not receive the data in their daily delivery files since the 4 keys do not match what the Forwarder has established on vExchange. |
| Claim Recalled | The Forwarder placed a claim with a Receiver, recalled it, and placed it with a different Receiver. | If we have a recall code on the former account with another agent id, then the account was recalled from the firm. The firm should review their Notes under the account in Analytics for a recall claim vX Status Code. |