INVARITECHClaims DeskSend one redacted remittanceSend a remittance

Invaritech · Claims Desk

Retailer deductions,checked against the evidence.

You supply Coles, Woolworths, Metcash, ALDI or Costco, and money comes off your remittance under promo, short-delivery, DIFOT, shrinkage or a prior credit. The proof exists. It is just spread across portals, PODs, invoices, promo agreements and old remittances. We rebuild that chain and mark every line supportable, missing proof, worth challenging, or Code risk.

Send one redacted remittanceSee a sample teardown

One remittance in, one page back. No system access. Findings are factual; Code points are context, not legal advice.

A service of Invaritech, who also build the finance automation and compliance automation behind it.

One remittance, examined

This is what comes back.

Every deduction lands in one of a few places: supportable, missing proof, worth challenging, or Code risk. Not every claim is wrong. The ones worth reviewing don’t announce themselves.

Remittance adviceExamined by Invaritech
DeductionRetailer’s reasonAmountVerdict
  • Short-delivery claimINV-4471Qty received under invoiced−$3,120missing proof
  • Promo scan deductionPROMO-W32Scan claim past funding cap−$8,640worth challenging
  • Shrinkage chargeDN-2210In-store loss charged back−$1,450Code risk
  • DIFOT penaltyWK-32Delivery KPI penalty, wk 32−$2,200missing proof
  • Trading-terms rebateTT-Q2Agreed Q2 rebate−$5,900supportable
Flagged for reviewof $21,310 deducted on this remittance
$15,410Illustrative figures
See a sample teardown

Sample · illustrative, one line from a single remittance

Deduction line
Promo scan deduction · PROMO-W32 · −$8,640
Claim type
Promo funding claim
First-pass verdict
Worth challenging
Evidence to pull
Signed promo agreement, funding cap, scan report
Likely gap
The funding cap that limits the claim
Dispute priority
High. $8,640, 12 days left in the window.
Suggested query
“Please confirm the agreed funding cap for PROMO-W32. The scan deduction exceeds the funded amount we hold on file.”
Code risk
A set-off needs written consent, or a supply agreement that allows it and a reasonable amount.

Who this is for

Built for one job. Honest about the rest.

Built for you if

  • You sell into Coles, Woolworths, Metcash, ALDI, or Costco and take deductions you cannot fully explain.
  • Your finance or AR team writes off short-pays because chasing them costs more than they return.
  • Claims arrive across portals, debit notes, and remittances, and the proof lives somewhere else.

Not for you if

  • You sell direct to consumers, not through grocery retailers.
  • You already recover these claims in-house.
  • You want self-serve software today. This starts as a service.

The method

A retailer claim is an assertion. We put every one through two tests.

01

Is it supported by the document trail?

We rebuild the chain: PO, ASN, signed POD, invoice, promo agreement, price list, credit note, and prior remittance. Then we see whether the claim actually ties back to it.

02

Does it carry Code risk?

Some deductions need legal or commercial review before anyone uses them externally. Shrinkage, set-offs, and wastage depend on the Code context, contract wording, and evidence trail.

Not every deduction is wrong. The money sits in the claims that fail one of those tests.

The claim ledger

Claim types worth checking before they age out.

Pull one recent remittance, debit note, or portal claim and run it against the list. Each line ends up in one of these stamps.

  • supportableThe document trail backs the deduction. Accept it and move on.
  • missing proofThe claim may be valid, but the proof that would settle it is absent.
  • worth challengingThe trail contradicts the claim, or the claim exceeds what was agreed.
  • Code riskThe Food and Grocery Code may limit this charge. Worth legal or commercial review.

The same four verdicts the 20-type checklist and the DIFOT checker use on invaritech.ai.

01missing proof

Short-delivery / shortfall

Did fewer units arrive than you billed? A shortfall claim must be made within 30 days of delivery. Late ones are challengeable.

  • Signed POD
  • ASN
  • Invoice
  • Received qty
02worth challenging

Promo funding claim

Does the deduction match the agreed promo amount, cap, window, and store scope? Or has it crept past the deal?

  • Signed promo agreement
  • Funding cap
  • Scan report
03Code risk

Shrinkage charge

If an in-store loss shows on a remittance, flag it as Code risk before accepting or disputing it.

  • Reason code
  • Supply agreement
  • Remittance line
04missing proof

DIFOT / OTIF penalty

Did you actually deliver late or incomplete on the agreed measure? Or is the scorecard wrong?

  • ASN
  • Booked window
  • Dock timestamp
  • POD
05worth challenging

Duplicate / already-credited

Has the same claim already been deducted, set off, or credited on a prior remittance?

  • Prior remittance
  • Debit note
  • Credit note
06Code risk

Wastage charge

Chargeable only if expressly agreed, reasonable, with a stated calculation, and the retailer took steps to reduce the cost.

  • Wastage clause
  • Calculation basis
  • Batch evidence
07supportable

Overpricing / price discrepancy

Did the invoice price differ from the agreed price list on the effective date? Which way?

  • PO
  • Agreed price list
  • Effective date
08worth challenging

Set-off against invoice

Was there written consent, or does the supply agreement allow the set-off and is the amount reasonable?

  • Written consent
  • Supply agreement
  • Claim basis
09missing proof

Post-audit claim

Does a historic claim, often raised one to two years later, match the original agreement and transaction trail?

  • Original PO
  • Price list
  • Promo agreement

How the desk works

From a scattered remittance to a claim you can act on.

The evidence is real. It is just spread across portals, PODs, invoices, promo agreements, email, and your ledger. We reconstruct the chain and hand you the pack to dispute with.

  1. 01

    Capture

    Pull claims from retailer portals, remittance advices, debit notes, and accounting short-pays.

  2. 02

    Classify

    Sort every claim by type and reason code, so like is compared with like.

  3. 03

    Match

    Tie each claim to the PO, ASN, POD, invoice, promo agreement, price list, credit note, and prior remittance.

  4. 04

    Assess

    Mark each line supportable, missing proof, worth challenging, or Code risk.

  5. 05

    Prioritise

    Rank by dollar value and days left in the dispute window, so nothing ages into a write-off.

  6. 06

    Evidence pack

    Assemble claim, proof required, proof found, the gap, and suggested wording. One page per claim.

  7. 07

    Dispute

    Support the challenge through the normal retailer process. You correct an error, not pick a fight.

  8. 08

    Track

    Track retailer responses and surface the recurring claim patterns worth fixing upstream.

Where the Code affects the check

We use the Food and Grocery Code as context.

It commenced on 1 April 2025. The transition period ended on 1 April 2026. That makes old ‘normal’ deductions worth checking again: set-offs, shrinkage, wastage, listing payments, damage, shortfall, and payment.

Set-offsmay need written consent, or a supply agreement that allows the amount.
Shrinkagecan carry Code risk once the retailer has taken possession.
Wastagemay need express agreement, a stated calculation, and cost-mitigation evidence.
Shelf space & listingmay need express written agreement and a reasonable amount.
Damage & shortfallmay be time-limited after delivery.
Paymentdepends on the agreed payment timeframe.

For Coles, Woolworths, Metcash and ALDI claims, we flag Code risk while checking the evidence chain. For Costco and other retailer or distributor claims, we still reconstruct the evidence chain, contract trail, claim reason, and dispute window.

Code references are review flags drawn from ACCC guidance, not legal advice.

What a teardown reconstructs

Six things we rebuild for every claim.

A deduction is a dispute about what happened. We put the record back together so the answer can be checked.

  1. 01

    The claim

    What the retailer deducted, and the reason they gave for it.

  2. 02

    The rule

    Which agreement, price list, or Code clause the claim depends on.

  3. 03

    The proof

    The PO, ASN, POD, invoice, promo agreement, and prior remittance that should support it.

  4. 04

    The gap

    Which document is missing, and what it would need to show.

  5. 05

    The Code point

    Where the Code may make the deduction worth legal or commercial review.

  6. 06

    The clock

    Days left in the dispute window before the claim ages into a write-off.

Pull one recent remittance and see what holds up.

Send one redacted remittance

Who runs this desk

You work with founders, not account managers.

The Claims Desk is run by the same three people who built Invaritech’s EUDR compliance bridge and its finance tooling. If you send a remittance, one of us reads it. Our engineering team works from Asia and our clients are Australian; we say so here rather than leave you to guess.

Aditi Garg

Director & Founder

Built reconciliation and payment control systems used by Goldman Sachs. Delivered operational programs for Uber and BMW. She scopes every engagement and stays close to delivery.

Abhishek Agarwal

Co-founder

Founder of Codeacious Tech. Delivered enterprise systems across finance, retail, and regulated industries, including architecture programs tied to A$80M+ in client outcomes.

Avishek Majumder

Co-founder & CEO

Data engineer and applied scientist. Builds production pipelines and decision-support systems for compliance-heavy environments. Specialises in anomaly detection and predictive systems.

More about the company, its track record and how it works on invaritech.ai/about, with client work at invaritech.ai/work.

The limits

What we don’t do.

Stated up front rather than buried in a disclaimer, because these are the things you would otherwise have to ask about before sending anything.

We don’t guarantee recovery

We tell you which claims have an evidence gap worth raising. Whether the retailer credits it is between you and them.

We don’t give legal advice

Food and Grocery Code points are review flags drawn from ACCC guidance. Take them to your lawyer or category manager, not to court.

We don’t touch your systems

No ERP connection, no portal credentials, no read access to anything. The first teardown runs on one document you send us.

We don’t work on contingency

No percentage of recoveries, no success fee. The first teardown is free, and what follows is priced as work.

We don’t dispute on your behalf

You own the retailer relationship. We hand you the evidence pack and suggested wording; you decide what to send.

We don’t train models on your documents

Your remittance is used to prepare your teardown and nothing else. Ask and we delete it.

Your document

How we handle what you send.

Where it goes

Into a Google Drive folder shared with your email address and ours, and nowhere else. Not a shared inbox, not a public link, not a third-party processing service.

What it is used for

Preparing the teardown you asked for. It is never used to train public models, never sold, and never shared with another supplier or a retailer.

How long we keep it

Until you ask us to delete it, and we delete it on request without asking why. An NDA is available before you send anything.

What to redact first

Hide bank details, account numbers, personal names, phone numbers and signatures. Leave the deduction reason, claim ID, date, retailer, invoice number, amount and dispute deadline readable if you can — those are the fields the teardown works from.

Full policies: privacy and terms on invaritech.ai.

Before you send anything

Read the method first. It’s all public.

Nothing about how this desk works is secret. The claim types, the evidence each one needs, the Code checks and a worked teardown are all published on invaritech.ai. Read them, use the free checker, and send us a remittance only if the method holds up.

Founding suppliers

We’re working with a handful of Australian FMCG finance teams to shape this.

We’re a small startup based in Asia. We’re not pretending otherwise. We want to see how claims and short-pays actually reach your finance team: where the evidence scatters, what you write off, and what a clean evidence pack would be worth.

In return: early access, direct product input, and founding pricing when we launch.

What partners do

  1. 01Walk us through how claims and short-pays reach you today (30 to 45 min)
  2. 02Share one or two redacted remittances so we can see the real shapes
  3. 03Review early evidence-pack teardowns and tell us where they fall short
  4. 04Help decide which claim types we automate first, and which we leave alone

Founding suppliers · early access

Send one redacted remittance. Get a one-page teardown back.

Leave your work email. We reply with a secure upload link for one redacted remittance. You get back a one-page evidence teardown. Each line marked supportable, missing proof, or worth challenging. Anything near its dispute window flagged. No pitch. No demo deck.

What you get back

  • Every deduction line marked: supportable, missing proof, worth challenging, or Code risk.
  • The proof each line marked worth challenging would need to stand.
  • The documents to pull from your own records.
  • Claims ranked by dollar value and days left to dispute.
  • Suggested wording for your internal review and the retailer query.

No recovery guarantee. Not legal advice. No system access for the first teardown. How we handle your document

No commitment · We’ll only reach out if there’s a fit

What happens after you submit
  1. 1Submit your work email.
  2. 2We send a Google Drive upload link, shared only with that email.
  3. 3You upload one redacted remittance.
  4. 4We return a one-page evidence teardown.
  5. 5You decide whether there is enough value to keep going.
Not sure what to redact?

Hide

  • Bank details
  • Account numbers
  • Personal names
  • Phone numbers
  • Signatures
  • Unrelated supplier or customer details

Leave readable if you can

  • Deduction reason
  • Claim ID
  • Date
  • Retailer
  • Invoice number
  • Amount
  • Promo or debit-note reference
  • Dispute deadline

How we handle your document is a full section above — where it goes, what it is used for, how long we keep it, and what to redact first.