How to Dispute a Chargeback with TJX (T.J. Maxx, Marshalls, HomeGoods)
TJX mails chargeback backup documentation with the physical check and will not send it ahead of time. A TJX vendor therefore sees the deduction posted in Vendor Self Service before receiving the documentation that justifies it, and the work of a TJX dispute begins against an unexplained number. Vendor Self Service at www.tjxvendors.com is where you find the deduction, but it is a reporting layer with no dispute-filing function. TJX does not publish its dispute route or a dispute window in its public vendor materials, so confirm both with Vendor Relations at 1-508-390-3407 before you file. Read the VSS record precisely: INV, VCB, and PB are invoice types (invoice, chargeback, payback), not reason codes, and the reason a chargeback was taken sits in a separate free-text Chargeback column, for example “Unit Difference”. Paid invoices drop off VSS 30 days after the payment date, so late detection costs you self-service access to the record entirely.
At a glance
- Submission channel
- Not published in TJX's public vendor materials. VSS is reporting-only and has no filing function; confirm the current route with Vendor Relations at 1-508-390-3407
- Where deductions surface
- Vendor Self Service (VSS) at www.tjxvendors.com, current as of the close of business the previous day; the login ID is usually the vendor number
- Case-ID / notice shape
- Invoice Type carries INV (invoice), VCB (chargeback), or PB (payback), which are transaction types rather than reason codes; the reason itself is free text in a separate Chargeback column, for example “Unit Difference”
- Backup documentation
- Mailed with the physical check and not available ahead of time, even once the deduction has posted to VSS
- Record retention in VSS
- Paid invoices drop off 30 days after the payment date; older records require a call to Vendor Relations
- Banners covered
- T.J. Maxx, Marshalls, HomeGoods, and the HomeSense and Sierra banners, selectable as a Chain filter in VSS
Submission channel
TJX does not publish a chargeback dispute route in its public vendor materials, so confirm the current route with Vendor Relations at 1-508-390-3407 before filing. Vendor Self Service is a visibility layer, not a filing one: its four tabs (Selection Criteria, View Invoices, Preferences, Signout) let you find and read a deduction, and nothing in the documented interface submits a dispute. Treat VSS as the place you detect and evidence the charge, and Vendor Relations as the place you confirm where the answer goes. Nothing is auto-submitted; Roy prepares and assembles the packet, and a person reviews and approves it before anything reaches TJX.
Reason-code taxonomy at a glance
TJX does not publish a numbered reason-code table, and the most costly misreading of a TJX deduction is treating the Invoice Type as one. INV, VCB, and PB are invoice types, meaning invoice, chargeback, and payback. They tell you what kind of transaction the row is, not why money was taken. A supplier that reads VCB as a reason code sorts every chargeback it receives into a single bucket and loses the ability to triage at all. The reason lives in a separate Chargeback column and arrives as free text, for example “Unit Difference”, TJX's wording for a quantity discrepancy. Because the reason is a text label rather than a code, TJX deductions must be normalized from language into dispute categories before any evidence can be pulled. The free-text label and the mailed backup together are the authoritative statement of the claim.
The backup arrives with the check, not before it
TJX mails chargeback backup documentation with the physical check and will not send it ahead of time, even after the deduction has posted to VSS. That inverts the usual order of a deduction investigation. You learn the amount first, from the VSS record, and the documentation explaining it arrives later in the mail, which means the point at which you can start working a TJX charge and the point at which you can fully answer it are not the same. Two consequences follow. First, detection has to be routine and calendar-driven rather than triggered by the arrival of paperwork, because here the paperwork is the last thing to arrive rather than the first. Second, the VSS record itself, the invoice type, the free-text chargeback reason, and the check number, is the only evidence of the claim you hold until the envelope lands, so capture it the moment it appears rather than retrieving it later. Build the case from your own shipment and invoice records while you wait, then reconcile the mailed backup against it when it arrives.
Reading a VSS record correctly
A TJX vendor reviews invoice, deduction, and payback activity in Vendor Self Service at www.tjxvendors.com, where the data is current as of the close of business the previous day and the login ID is usually the vendor number, issued at account setup. Read three fields together and in order. The Invoice Type tells you the transaction kind: INV for an invoice, VCB for a chargeback, PB for a payback. The Chargeback column tells you the stated reason, in free text, for example “Unit Difference”. The check number ties the row to the payment whose envelope will carry the backup. Reading the invoice type as the reason collapses three signals into one and produces a deduction log that cannot be triaged, prioritized, or matched to evidence. Log the free-text reason verbatim rather than an internal alias, because that text is the claim TJX will expect you to answer.
Unit difference and quantity claims
“Unit Difference” is TJX's own wording for a quantity discrepancy, and it is the reason text most directly answerable from shipment records. A quantity claim asserts that TJX received fewer units than you billed, so the answer is documentary proof of what left your dock and what was accepted into carrier custody: the carrier-signed bill of lading and its carton count, reconciled against the invoiced quantity and the pack configuration on the order. Because TJX states the reason as free text rather than a code, do not assume every quantity-worded reason is the same claim. Read the exact wording on each row and match the evidence to what that row actually alleges. Where the wording is ambiguous, or where your own records do not cleanly support the billed quantity, the case belongs in human review rather than in a filed dispute.
Date-driven blind spots in VSS search
VSS search is invoice-date driven, so a deduction tied to an invoice outside your selected date range is invisible to you even when it is unpaid. This is a silent under-reporting trap rather than an error you will see, because the interface returns a clean result set that simply omits the activity you did not ask for. Two defaults compound it. Chain is a filter dimension across T.J. Maxx, Marshalls, HomeGoods, and the HomeSense and Sierra banners, so a default view can hide another chain's activity entirely. And factors and holding companies receive a Secondary Vendor dropdown that resets to “all vendors” every time you return to Selection Criteria, a real routing trap for a supplier holding several vendor numbers across TJX entities. The defensive habit is the same in all three cases: widen the invoice-date range deliberately, sweep every chain, and re-set the secondary vendor on every pass rather than trusting a retained selection.
The 30-day retention cliff
Paid invoices drop off VSS 30 days after the payment date, and retrieving an older record means calling Vendor Relations. Late detection therefore costs you self-service access to the record itself, not just time, and turns a lookup you could have run in a browser into a phone call. Combined with a date-driven search that can hide unpaid activity outside your selected range, this makes the cadence of your review the single controllable variable in TJX deduction management. Capture the VSS row, the invoice type, the free-text chargeback reason, and the check number, at the point of detection, and store it in your own system so the record survives its disappearance from VSS.
Terms run from DC receipt
TJX payment terms run from the date goods are received at the TJX distribution center, not from the ship date. That makes the DC receipt date a load-bearing fact in more than one direction: it drives when payment is due, and it is the reference point against which the transit portion of a shipment's history is read. Keep the proof of delivery and the DC receipt date alongside the bill of lading in the case file rather than treating them as freight paperwork, because a reconciliation built on the ship date will not line up with how TJX is calculating.
What TJX does not publish
TJX does not publish a dispute window, a numbered reason-code table, or a per-claim-type evidence matrix in its public vendor materials, and this guide does not fill those gaps with an estimate. A guessed deadline is worse than no deadline, because a supplier relying on it could miss the real one. Confirm the dispute window and the filing route with Vendor Relations at 1-508-390-3407, which covers Marshalls, T.J. Maxx, and HomeGoods, and record the answer you are given against your own account. Note also that the public TJX document titled a vendor compliance manual is a social-compliance and responsible-sourcing document rather than a routing or chargeback guide. It is not the source of a deduction rule and should not be cited as one. Because TJX publishes no per-claim-type evidence matrix, the evidence list below is general dispute practice, the documents that answer each kind of claim, rather than a TJX-published requirement list.
What evidence you need
- Carrier-signed bill of lading and its carton count, against a unit-difference or quantity claim
- The invoice, for billed quantity and price as presented to TJX
- Proof of delivery and the DC receipt date, which is the date TJX payment terms run from
- The ASN, EDI 856, for the shipment record transmitted at ship time
- The VSS record itself: invoice type, the free-text chargeback reason, and the check number
- The chargeback backup documentation that arrives in the mail with the physical check
How Roy disputes TJX
Roy captures the TJX deduction from the VSS record at detection rather than waiting for the mailed backup, and stores the invoice type, the free-text chargeback reason, and the check number before the 30-day retention cliff removes the row. It reads INV, VCB, and PB as invoice types rather than reason codes, and normalizes the free-text reason, for example a unit-difference claim, into a dispute category so the right evidence is pulled: the carrier-signed bill of lading and carton count against a quantity claim, the invoice for billed quantity, the proof of delivery and DC receipt date, and the ASN. It sweeps invoice-date ranges, every chain, and each vendor number rather than trusting a retained selection, so date-driven and secondary-vendor defaults do not hide activity. When the mailed backup arrives, Roy reconciles it against the case already built.
Nothing is auto-submitted. Roy prepares and assembles the dispute packet, and a person reviews and approves it before anything goes to TJX. Ambiguous cases, including reason text that does not resolve cleanly to a category and quantity claims your own records do not support, route to human review rather than to a filing. Because TJX does not publish its dispute route or window, Roy stages the packet for filing through whichever route Vendor Relations confirms for your account rather than assuming one.
Related retailers & next steps
Related off-price retailers where the shortage or quantity claim is answered from the carrier-signed bill of lading: Burlington, Bealls, and Ross Stores. See the Deduction Code Library for how TJX states a chargeback reason as free text rather than a code table.