Suppliers working with Target often discover Target Unpaid Invoices during internal audits, long after the delivery has been made and the goods accepted. The frustrating part is that the invoice looked fine on your end. You shipped. You billed. Nothing came back. And yet, the payment never arrived.
This isn't random.
Target's AP system is highly structured, and when invoices stall, there's almost always a specific, traceable reason. Understanding those reasons is the first step to recovering what you're owed.
Target's AP vendor training identifies four core reasons why invoices go unpaid. Everything else is a variation of these.
1. Target never received your invoice.
This is the one suppliers least expect.
If your EDI transmission fails, Target's system has no record of the invoice, and no payment process begins.
Target's documentation is clear: it's the vendor's responsibility to monitor EDI transmissions and review any EDI 864 error messages, since some are fatal and will block invoices from reaching Target entirely.
If the invoice doesn't appear in the Target AP Dashboard via Specific Document Search, that's your signal, it's an EDI problem, not a payment delay. You'll need to check your EDI logs or contact EDI.Helpdesk@target.com.
If EDI can't be resolved, Target does offer Invoicio, a manual invoice submission fallback, though it comes with a $75 per-invoice fee.
2. The invoice isn't due yet, because ROG hasn't happened.
Many suppliers track payment timelines from their ship date. Target doesn't work that way. Payment terms begin on the Receipt of Goods (ROG) date, the moment Target's DC or FDC checks in and scans your shipment.
Here's where drop loads create a real problem.
With a live load, the DC scans the shipment when the carrier arrives.
With a drop load, the carrier leaves the freight at the dock and the ROG date isn't recorded until Target's replenishment process scans it in, which can be days or weeks later.
Your invoice might look overdue from your records, but Target's payment clock hasn't even started. This is one of the most common sources of unnecessary escalations and, left unaddressed, a quiet contributor to revenue leakage in CPG.
Also worth knowing: float days apply on top of the due date. Target processes EFT payments at least twice a week, on Tuesdays and Thursdays, and can apply up to ten float days at their discretion.
So even when a due date passes, payment may still be within Target's normal processing window.
3. The invoice is on hold because of a debit balance or account hold.
If your vendor account has a debit balance, Target will withhold payment until invoices due outweigh the balance owed. This can silently block otherwise valid invoices.
Similarly, if your account is in Invoice Hold or Vendor Hold, payments stop regardless of invoice status.
You can check account balance through the Total Open Payables Report in POL. For holds, the resolution path depends on the type: general holds go through Target.VendorRequest@target.com, while invoice or vendor holds without a debit balance are handled through Target.Collections@target.com.
4. No matching receipt on file.
Target's payment system requires a three-way match: purchase order, invoice, and receipt.
If an invoice shows as unprocessed and past due by five or more days, Target's training document indicates this typically means Target has no record of receiving the product on that PO, location, and department combination.
In this case, you'll need to submit a dispute through Synergy with valid Proof of Shipment (for collecting shipments) or Proof of Delivery (for prepaid). For Direct-to-Store vendors, the store sticker serves as your POD, keep it for every delivery.
Understanding how proof of delivery works in dispute resolution can make or break these cases.
Log into Target Partners Online and go to the AP Reporting Dashboard. Use the Specific Document Search tool, it provides document status regardless of where the invoice sits in the system.
The statuses you'll see:
Paid: payment has been issued
Open: invoice is released and will pay per terms
Unprocessed, not past due: still within terms, no action needed
Unprocessed, past due: This is the one that requires action
Only invoices showing as unprocessed and past due should be escalated. Escalating open invoices or invoices within ROG terms wastes time and creates unnecessary back-and-forth.
If you're unsure how to interpret what you're seeing, Target's deduction prefix guide can help you decode the details.
Once you've confirmed the invoice is genuinely unprocessed and past due, submit a dispute through Synergy. Target's process is straightforward but specific:
Research the invoice in POL first, then open a dispute in Synergy with one claim per invoice. Required documents include the invoice copy, packing slip, proof of shipment or delivery, and the store sticker for DSD vendors.
After submission, give Target a minimum of 30 days to respond. Watch your dashboard for cases returned with an "awaiting vendor info" status, those need prompt attention or the case stalls.
For more on what causes disputes to get denied before they even get reviewed, the Target vendor dispute guide covers the five most common denial reasons and how to avoid them.
Most of these issues are avoidable with consistent process controls. Submit one invoice per shipment, per PO, per department, per location. Validate EDI transmissions daily. Track ROG dates, not ship dates.
Keep delivery documentation for every order, especially store stickers for DSD shipments. And check invoice status in POL regularly rather than waiting for a quarterly reconciliation to surface a problem.
When volume is high, manual tracking breaks down. Teams handling hundreds of invoices across multiple retailers often find that invoice automation tools are the only practical way to maintain visibility at scale.
iNymbus works specifically in this space, automating the research, documentation, and dispute submission process so suppliers can recover payments faster without scaling their AR team headcount. If unpaid invoices are a recurring problem, it's worth looking at whether the process itself is built to catch them early.