How Yuzu Flags a Duplicate
Before adjudication, Yuzu compares the claim against the member's other approved claims on the same service date. A match is graded in two levels:
Exact: Every service line on the new claim matches a line on a prior approved claim on procedure code, service dates, repricing status, billed amount, and modifiers
Possible: Some lines match, or the providers on the two claims overlap, but the match is not exact. Common case: two claims for the same date and provider where one line's billed amount differs
An exact claim-level match denies the claim. An exact line-level match denies only the duplicated line. A possible match holds the claim for review instead of denying outright, so a human can have the final decision. Denied duplicates produce a remark code of 18 (“Exact duplicate claim/service”) on the adjudication that is visible on the EOP and EOB.
Two things worth knowing about what the check compares:
First, it only looks at approved prior claims, so a claim denied earlier does not make a resubmission a duplicate
Second, providers are matched on NPI or billing TIN, so the same service billed under a different provider identifier can slip past the check
Original vs. Corrected vs. Void Claims
Every claim carries a claim frequency code (CLM05-3 on the 837) that says what kind of submission it is:
1 (original): a new claim
7 (replacement/corrected): replaces a previously submitted claim. This is how a provider fixes billed data, not by sending a second original. A corrected claim sent as a new original is the most common cause of a false duplicate flag
8 (void): cancels a previously submitted claim entirely
Each submission becomes a new iteration in the claim's history (visible on the “History” tab) rather than overwriting previous data. The claim page shows the merged picture across iterations and the history view shows each version as received. Within a single file, originals are processed before voids and adjustments so they apply in the right order.
There are times when Yuzu chooses to ingest “Replacement” claims as originals in our system, but these are rare circumstances that do not happen automatically when we believe that there was an integration error or limitation. Yuzu would still manually look for “duplicate” original claims even if we ingested a particular claim this way.
Timely Filing
The timely filing limit comes from the plan's SPD. In Yuzu, the late-claim check works off a configured limit measured from the last date of service (the current system default is 180 days). A claim that arrives past the limit is denied for timely filing with the remark code TIMELY2 (“Claim received beyond the 180-day filing limit.”). The purpose of the timely filing limit is to make sure that the financial obligations of the plan are known within a definite period of time, allowing for alignment of claim payment with stoploss policies’ contract terms.
The date that counts is when the claim was first received, visible as the earliest entry under Transmissions on the claim record. For claims with no transmissions, like manual uploads or portal-created claims, the claim's created date is used instead.
Yuzu’s system does recognize a few common cases where timely-filing guardrails should be waived:
A group policy can carry a toggle that disables the timely filing denial. This is commonly-used for groups where network integration issues have been widespread or where the group has elected run-in and it is taking providers additional time to re-submit old claims originally sent to a different TPA.
A claim with a COB flag releases the denial automatically, because a claim delayed by a primary payer should not penalize the member.
Proof of Timely Filing
When a provider disputes a late denial, Yuzu will generally overturn an initial denial if the provider furnishes evidence of:
A clearinghouse or network acceptance report showing the claim was accepted before the filing deadline. What matters is when the receiving party accepted the claim, not when the provider initially submitted it
A prior payer's denial or remittance showing the claim was pending with another carrier during the window
A provider's internal billing records or screenshots showing a submission date are weaker proof, since they don't necessarily confirm when the claim was received by the appropriate payer or network.
For network-submitted claims, compare the network's acceptance date against the earliest Transmission date in Yuzu to identify where the delay occurred.
Timely Filing and Appeals
One of the most complicated elements of timely filing is that per industry standards, the clock “resets” every time a claim is processed. This means that a claim may be originally received 179 days after the date of service, denied, then appealed 179 days later and the appeal would still be considered by the plan. This can expose potential stoploss gaps for employers because the total amount of time a claim is in the appeal process could cause it to be paid outside of industry-standard “12/18” contract terms and thus excluded from even “safe” stoploss contracts. This does not happen frequently, and good TPAs like Yuzu will communicate pro-actively on large claims with carriers to see if appeals can be honored even if payment happens outside of contract terms.