CGetChargeback

Target Deduction Code A036: Cost Difference Deductions

Target Code A036 is a deduction taken when your invoice cost doesn't match the cost Target has on file. Learn causes, cost-sync fixes, and disputes.

Executive Summary & Quick Answer

Executive summary: A036 is the invoice-difference code with no warehouse in the story. Nothing was damaged, nothing was short — the price disagreed. The cost billed on your 810 doesn't match the cost Target has on file, and Target deducts the difference. It's the purest data deduction in the family, which makes it the most preventable: costs don't change in transit, they change in systems, on dates, by agreement. Every A036 traces to a moment when two systems held two different numbers for the same item — usually a cost change that went live on one side before the other, or a promotion applied to the wrong invoice.

Quick answer: Target Deduction Code A036 is a deduction for a cost discrepancy: the cost billed on your invoice does not match the cost Target has on file, and Target deducts the per-unit difference across the quantity. Prevention is data hygiene — confirm every cost change is effective on both sides before invoicing.


Deep Dive: What Triggers A036

Every item you sell Target has a cost of record in Target's system. Your 810 invoice bills a cost too. When they disagree, Target doesn't call to negotiate — it deducts the difference as A036, per-unit, across the billed quantity.

Where the cost lives in the EDI flow:

Document Cost it carries Failure mode
850 (PO) The cost Target expects to pay, from its item file Your ERP ignores it and prices from its own master
810 (Invoice) The cost you bill Built from a cost that changed — or never matched

The 850 is the tell most suppliers waste. Target sends its expected cost on the PO, line by line. If your order-entry process compares that against your own price master at PO receipt, you know about the disagreement weeks before invoicing — while it's a conversation. If the first comparison happens inside Target's payables matching, it's a deduction.

The classic sequence looks like this:

Cost change agreed ──► your ERP updates (day 1) ──► Target's item file updates (day 30?)
                                   │
                     invoices billed in the gap ──► every one draws A036

Neither side is "wrong" in isolation. The two systems were right on different dates — and the invoices billed inside the gap paid for it.


Business & Financial Impact

  • Deduction = per-unit cost difference × billed quantity. Small per-unit gaps scale brutally on high-velocity items.
  • It repeats until the data is fixed. Like any systemic mismatch, one unsynced cost change deducts on every invoice it touches, not once.
  • Margin distortion, not just cash loss. Finance sees a lower realized price and can't tell negotiated cost from deduction noise without code-level tracking.
  • Comparatively cheap to prevent. No packaging engineering, no dock procedures — this one is fixed at a desk, with a validation step and a calendar.

Root Causes (Ranked)

  1. Invoice cost higher than Target's agreed cost — the direct trigger: your 810 bills above the cost of record.
  2. A cost change not synced before invoicing — the timing gap. The new cost went live in one system while invoices were still billing from the old (or vice versa).
  3. The wrong cost tier or promotion applied — a promotional or tiered cost applied to an invoice it shouldn't touch, or missing from one it should.
  4. Nobody validates the 810 against the 850 — the enabling condition. The PO carried Target's expected cost; no one compared before billing.

Step-by-Step Prevention Workflow

COST CHANGE ──► CONFIRM EFFECTIVE ──► HOLD INVOICING ──► VALIDATE 810 ──► BILL
  (agreed,          BOTH SIDES           IN THE GAP        vs 850 COST
   dated)          (yours + Target's)                      (every line)
  1. Treat cost changes as two-system events. A change isn't done when your ERP updates — it's done when you've confirmed Target's side shows the same cost with the same effective date.
  2. Sync item cost with Target before billing. The record's first prevention step. New item, new cost, new promotion: confirmed on both sides before the first 810 goes out.
  3. Validate every invoice line against the PO cost. The 850 told you what Target expects to pay. An 810 line that disagrees should stop for review, not ship to payables.
  4. Gate promotional costs by date and scope. Promo and tier pricing applied by rule — item, window, PO — not by hand.
  5. Track A036 by item monthly. A repeating item is an unsynced cost sitting in one of the two systems. Find it, align it, and the deductions stop.

The Dispute Path

Target's compliance documentation and violation details live in Partners Online; disputes run through Synergy there.

  1. Pull the deduction detail — invoice, item, billed cost, and the cost Target applied.
  2. Assemble the cost agreement: the negotiated cost, its effective date, and any promotion terms covering the invoice date.
  3. If your billed cost matches the agreement and the effective date, file in Synergy with that documentation.
  4. If the billed cost was genuinely stale, don't dispute — fix the price master and the sync process; the next invoice is the real remedy.

A036 in the Invoice-Difference Family

Code The gap is caused by Manual or auto
A036 Cost billed ≠ cost on file Manual
A038 A different item received than invoiced Manual
A176 Any difference the system detects itself Auto

A036 is the price member of the family: quantities and items can match perfectly and the deduction still lands, because the disagreement is in the money column.

Related: Code A038 · Code A176


Supplier Checklist

  • Every cost change confirmed effective on both sides before invoicing resumes
  • 810 cost validated line-by-line against the 850 cost before transmission
  • Promotional/tier costs applied by dated rule, not manual edit
  • Cost agreements and effective dates archived, retrievable by item
  • Weekly: new A036s matched to cost agreements — dispute in Synergy or fix the master
  • Monthly: A036 by item — any repeat item gets a two-system cost audit

FAQs

What is Target deduction code A036? A deduction for an invoice-vs-receipt difference caused by a cost discrepancy — the cost billed on your invoice doesn't match the cost Target has on file. Target deducts the difference.

How much is an A036 deduction? The per-unit cost difference multiplied across the billed quantity. There's no flat fee — a few cents of mismatch on a high-volume item adds up fast.

How do I dispute an A036 deduction? Through Synergy in Partners Online, with the cost agreement, its effective date, and any promotion terms showing your billed cost was correct for that invoice date.

Why do A036 deductions keep repeating on the same item? Because the underlying cost mismatch is still there. Until both systems carry the same cost with the same effective date, every invoice for that item bills into the same gap.

How is A036 different from A038? A036 means the right item was billed at the wrong cost. A038 means a different item arrived than the one invoiced — an identity problem rather than a price problem.


Is your next shipment at risk for Target?

Run one shipment's PO, ASN, invoice, and delivery data through the free scanner and see the chargeback risks before the truck leaves — no signup, nothing uploaded.

Scan a shipment free →

Get ahead of the next chargeback

Join the early-access list for automated pre-shipment audits that flag compliance errors across every shipment — before they become deductions.

GetChargeback is not affiliated with Target.This guide is compiled from industry sources for general information and is not legal, financial, or compliance advice. Verify current requirements in the retailer's official vendor portal before acting. Last reviewed 2026-07-10.