What the Furnisher Log Shows Before a Dispute Clears

When a consumer account enters the credit-reporting system, the entity supplying the data — called a data furnisher or credit furnisher — maintains an internal record that precedes anything visible on a consumer's credit file. That record is the furnisher log: a timestamped sequence of account states, payment events, and status codes that the furnisher transmits to one or more national bureaus on a monthly reporting cycle.

This piece covers the specific window between the moment a dispute is received by the furnisher and the moment the dispute code is resolved and cleared. During that interval the log holds a particular set of entries — some required by regulation, some generated by internal workflow — and those entries do not always match what the bureau's own reinvestigation record shows. Understanding what the log captures in that window, and what it does not, is the subject here.

How the Furnisher Log Builds Before a Dispute Code Clears

Data furnishing begins before any dispute arises. On each monthly reporting cycle, the furnisher transmits a Metro 2–formatted file to the bureaus. That file encodes the account's current balance, payment status, scheduled payment amount, date of first delinquency, and a portfolio code identifying the account type. Each transmission produces a dated snapshot. The accumulation of those snapshots, held internally by the furnisher, constitutes the furnisher log in its baseline state. What a furnisher logs before the dispute code is sent is therefore a series of monthly status records that predate the dispute entirely — records the bureau has already ingested and used to build the tradeline.

When a dispute arrives — routed from a national bureau via the automated consumer dispute verification (ACDV) system, or submitted directly to the furnisher under the FCRA's direct-dispute pathway — the furnisher is required under 15 U.S.C. § 1681s-2(b) to conduct a reasonable investigation and report results back to the bureau. The regulation sets a 30-day window for that investigation (extendable to 45 days in certain circumstances involving a consumer-submitted file). The clock starts when the furnisher receives the dispute notice, not when the bureau first logs the consumer's original complaint.

During that 30-day window, the furnisher log acquires new entries. First, the incoming ACDV itself is logged with a receipt timestamp. Second, the furnisher's compliance or operations team generates an investigation record — typically a case number tied to the account — that sits alongside the existing monthly snapshots. Third, if the furnisher's review leads to a change in the reported data (a balance correction, a status change, a deletion of a field), that change is logged with the date it was made internally, which may differ from the date it is transmitted to the bureau. Fourth, a dispute code — drawn from the Metro 2 compliance condition code set — is appended to the next outgoing transmission to signal that the account is under investigation.

The dispute code does not pause the monthly reporting cycle. The furnisher continues to transmit account status updates on its normal schedule while the investigation is open. This means the log may show, in parallel, an active dispute code and a continued series of balance or payment-status updates. Those two data streams are not merged in the log; they occupy separate fields in the Metro 2 record and are processed independently by the bureau's update system.

Once the furnisher concludes its investigation, it transmits the result via the ACDV response. That response carries a disposition code indicating whether the reported data was verified as accurate, modified, or deleted. The dispute code in the log is cleared — meaning it is no longer appended to outgoing transmissions — but the prior entries that carried the dispute code remain in the furnisher's internal record. The log does not erase the investigation period; it appends an end state to it.

Data Furnisher, Bureau, and Consumer: What Each Holds and What Each Is Paid For

The data furnisher — which may be an original creditor, a debt buyer, or a contingency collection agency — holds the account-level record and the internal log. The furnisher is not paid by the bureau for reporting; it reports because doing so supports its collection activity and, where it is an original creditor, because accurate reporting is a condition of its relationship with the bureau. When acting as a debt buyer, the furnisher acquired the account at a fraction of face value and reports the balance it claims is owed, not the price it paid.

The national bureau holds the compiled tradeline — the version of the furnisher's data that has been ingested, formatted, and stored in the consumer's credit file. The bureau does not hold the furnisher's internal log. It holds only what was transmitted to it. When a dispute arrives at the bureau, the bureau sends an ACDV to the furnisher and waits for the response; it does not independently audit the furnisher's records. The bureau is paid by lenders and other permissible-purpose users who pull credit reports, not by consumers.

The consumer holds the right to dispute under the FCRA and to receive the results of the reinvestigation. The consumer does not have access to the furnisher's internal log and does not see the ACDV exchange. What the consumer receives — either directly or via a free annual report — is the bureau's version of the tradeline after the furnisher's response has been processed. The gap between the furnisher's log and the bureau's tradeline is not visible in the document the consumer can obtain.

A consumer reporting agency that is smaller than a national bureau — a specialty bureau covering medical debt, rental history, or employment screening — operates the same ACDV mechanism but on a separate data pipeline. A furnisher may report the same account to multiple bureaus simultaneously, each generating its own tradeline from the same underlying log entry.

Where the Log Produces Results People Do Not Expect When a Dispute Is Open

The most common misreading of the dispute window is the assumption that placing a dispute code on an account freezes the tradeline's effect on a credit score. It does not. The dispute code (Metro 2 compliance condition code XB) signals that an investigation is pending, and some scoring models exclude accounts carrying that code from the score calculation — but not all scoring models do, and the bureau does not apply any universal suppression. The tradeline remains in the file and continues to age, update, and be reported to permissible-purpose requesters throughout the investigation period.

A second friction point arises from the timing mismatch between the furnisher's internal resolution and the bureau's update cycle. The furnisher may close its investigation and transmit a corrected or verified response on day 28 of the 30-day window. If the bureau's next processing cycle for that furnisher's file does not run until day 35, the tradeline on the consumer's file will not reflect the resolution until after the regulatory deadline has already passed at the furnisher level. The log shows the furnisher acted in time; the bureau's file shows the old data for several additional days. These are two separate records with two separate timestamps, and neither is wrong about what it records.

A third friction point involves what a furnisher's dispute code does not resolve: the code signals an open investigation but does not indicate which specific field is disputed, what evidence the consumer submitted, or what the furnisher's investigator actually reviewed. The ACDV form carries a short description field, but that field is often populated with a standardized category code rather than a narrative. The furnisher's log entry for the investigation may therefore contain no more detail than the ACDV itself provided.

Late-arriving dispute codes create a further complication. When a bureau routes a dispute to the furnisher after a processing delay on the bureau's side, the furnisher's 30-day clock begins at receipt — but the consumer's expectation was set by the date the consumer submitted the dispute to the bureau. The gap between those two dates is not reflected in the tradeline and is not visible to the consumer. The mechanics of what a furnisher logs when a dispute code arrives late show that the furnisher's record is internally consistent even when the overall timeline is longer than the consumer anticipated.

Finally, a dispute that results in a "verified as reported" outcome does not remove the account from the file and does not alter the date of first delinquency, which governs the seven-year credit-reporting period under 15 U.S.C. § 1681c. The limitations period — the separate state-law clock governing whether a creditor can sue to collect — runs on a different trigger and a different length. Conflating the two clocks is the single most common misunderstanding in this subject. The furnisher log records neither clock directly; it records account status and dispute disposition, from which those periods must be inferred.

What the Paper Record Shows at This Stage and What It Does Not

The furnisher's internal log, at the close of a dispute window, shows: the date each monthly Metro 2 transmission was sent; the compliance condition code appended during the investigation period; the date the ACDV was received; the disposition code transmitted in response; and the date the dispute code was cleared from outgoing transmissions. It does not show the consumer's original dispute language, the evidence the consumer attached, or any notes the furnisher's investigator made that were not encoded in the ACDV response fields.

The bureau's tradeline record shows: the current reported status, the date of last activity, the date of first delinquency (if applicable), and — after the investigation closes — the updated or verified data. It does not show the ACDV exchange, the furnisher's internal case notes, or the sequence of monthly snapshots the furnisher transmitted before the dispute arrived. A consumer pulling a full credit disclosure under the FCRA receives the bureau's version of the tradeline; the furnisher's log is not part of that disclosure.

When a file dispute is submitted directly to the furnisher rather than routed through a bureau, the furnisher is required under 12 C.F.R. § 1022.43 (Regulation V) to investigate and correct or delete inaccurate information, and to notify the bureau of any change. The direct-dispute pathway generates a log entry at the furnisher that the bureau does not see until the furnisher transmits a correction. During the interval between the furnisher's investigation and its next transmission, the bureau's file reflects the pre-dispute data. The paper record at the bureau is not wrong; it is simply behind the furnisher's internal state.

What neither record shows is the scoring impact of the tradeline during the dispute window. Credit scores are calculated at the moment a report is pulled and are not stored in either the furnisher's log or the bureau's tradeline file. The score a lender saw on day 10 of the investigation window is not recoverable from either record after the fact.

The furnisher log and the bureau's tradeline are parallel records that share data but are not identical — one is the source, the other is the ingested version, and the gap between them is where most of the confusion about dispute timing and outcome originates.

Note: This explains how a process works. It is not legal advice, it is not specific to any debt, and it is not a substitute for a licensed attorney in your state. Rules and time limits vary by state and change over time — check the cited sources.