30-min call with RobBook a proof-of-concept call
Job 03 · Trade and finance

// Food and beverage · Promotion claims

Promotion claims checked against the deal before you pay them.

A distributor, retailer or broker claims money for a promotion you ran. AI finds the signed agreement and deal sheet behind it, tests the dates, units, rate and cap against your scan or depletion data, and drafts a recommendation. The proof of concept is free and uses copies of 20 to 30 settled claims, with no access to your TPM tool, ERP or any portal.

Book a proof-of-concept call30 minutes with Rob
Settled claims
20 to 30
TPM, ERP or portal access
None
Signed before anything moves
NDA

// The one job

A claim in. A pay, part-pay or hold call out.

Weeks after a promotion ends, the claims start. A retailer bills back for units it scanned, a distributor sends a billback invoice with a detail file, a broker forwards a claim with a deal number on it. Some customers wait for your check or credit memo; others send the backup and take the amount from your next payment. Either way, someone has to work out how much is owed.

For the test, AI goes back over claims your team already settled. Each gets the agreement and deal sheet it matched, the claimed units and rate beside what the data supports, and a drafted call: pay in full, pay part with the gap shown, or hold for missing backup. No money moves. Your reviewer lays each call next to what your analyst actually paid.

Promotion claimFrom a distributor
Claim no.
Customer
Deal no.
Claim period
ItemUnitsRate
Illustration, not a real claim
Checked
against the deal
Claim checkDraft
Agreement
Dates used
Units source
Call
LineClaimedSupported
Illustration, not a real claim check

// What makes it hard

One deal, several calendars, three sources of units

Which dates apply. A promotion rarely has one date range. Buy-in dates, when a customer can buy at the allowance rate, often open before the in-store dates to cover orders placed ahead of the shelf date, while a scan claim counts only units sold inside the scan dates. Retailers add rules of their own: Kroger's published vendor requirements ask for billback periods that begin on a Sunday or Monday and end on a Friday or Saturday. The draft tests each line against the range that fits its claim type and names the range it used.

Where the units come from. A scan claim rests on the retailer's point-of-sale counts; a billback on purchases rests on what the customer bought from you. In beer, wine and spirits, a depletion allowance is a rebate on the distributor's sales to retailers over a set period, and states set the rules: Maryland requires a beer supplier to offer the same allowance and conditions to all of its Maryland wholesalers at once. Those depletion reports often come through VIP, long a source of daily depletion data for beer brands. The draft sets the claimed units beside your figures and shows each gap.

Foodservice deviations. A brand often agrees a contract price with a foodservice operator below its list price. The distributor still buys from you at list, sells at the contract price and bills you the difference. Gordon Food Service's published supplier billing policy, for example, accrues these sales allowances daily, processes them by its fiscal week, emails a summary PDF with a detailed CSV by item and distribution center, and collects by deduction. The draft confirms the operator is on the agreement, the price was in force on the invoice date, and the difference per case is the one you agreed.

Caps, flat fees and proof it ran. Kroger's vendor requirements describe a billback with a limit, which its contract desk turns into a lump sum with the limit entered; a claim past the limit stops there. A flat fee for an ad or a display is owed once the ad ran or the display went up, so the draft looks for the ad page or the store photo first. Kroger also asks that each contract's notes name the brokerage or vendor first, with a cash control number, and the draft carries those references through.

Where your reviewer looks. Your reviewer, the person who knows these claims best, is usually a trade spend analyst or whoever in finance signs off claims today. They look hardest at errors that cost money either way: a per-unit scan rate paid on cases, units counted outside the dates that apply, a claim paid past its cap, and a fair claim held until the customer simply deducts it.

// What you send

Four things from your trade team

Exports are fine
No TPM logins
01

20 to 30 settled claims

A mix of billbacks, scan, depletion and deviation claims and ad or display fees, each with your analyst's decision: paid, part paid, turned down or sent back.

02

The deals behind them

Signed promotion agreements, deal sheets and contract numbers for those claims, wherever they sit: your TPM tool, your broker's files or a shared drive.

03

The units data your team used

Scan or point-of-sale reports, distributor depletion reports, deviation detail files and any proof that an ad or display ran, for the same claim periods.

04

An NDA, and no logins

Nothing is copied to us before the NDA, and we never sign in to a retailer portal, a distributor site or your ERP. Where customer data can't leave, your reviewer helps us mock up stand-ins.

// Before it starts

What the owner signs off before any claim moves

Five things, settled in this order.

Before the proof of conceptOwner agrees
Reviewer
Named by the owner. Often the trade spend analyst or the finance lead who approves claims.
Success criteria
In writing, before day one
Claims
Picked by your reviewer, across customers and claim types
Price
A range for the live job
NDA
Signed before any copy is made

// How the test is judged

Each recommendation against what your analyst paid

Same claims
Claim by claim
Across the same 20 to 30 claimsYour analyst's decisionThe proof of concept
Matched to the right agreement and deal sheetFrom your claimsFrom your claims
Each line tested against the dates that applyFrom your claimsFrom your claims
Claimed units reconciled to scan or depletion dataFrom your claimsFrom your claims
Rate and cap applied as agreedFrom your claimsFrom your claims
Held for missing backup, with what was missingFrom your claimsFrom your claims
Time to check one claimFrom your claimsFrom your claims
Empty until it runs. Not one cell is filled in before your own claims go through it.Your reviewer fills both sides and makes the call.

// After a yes

About 30 days on incoming claims

Once your reviewer says yes, claims that arrive over the next 30 days or so get the same check.

Nothing is paid on the AI's word: someone on your trade or finance team approves every call before a check is cut, a credit memo goes out or a deduction is accepted. The reviewer keeps comparing as the claims come in.

The month covers promotion claims and nothing else.

// What could follow

Other jobs, once claims run

Ranked, not promised
Each priced on its own
  1. 01

    Deductions management

    The amounts customers took without a claim, matched to their backup after a payment comes in short.

    Next
  2. 02

    Claim status replies

    Answers to distributors and brokers asking where a claim stands, drafted from your records for a person to send.

    Then
  3. 03

    Promotion close-out

    Claims paid on each finished promotion set beside what was planned and accrued, for finance to review.

    After that

// One hard limit

The proof of concept never pays, credits or turns down a claim.

It works from copies of claims that are already closed, and its recommendations go into a spreadsheet for your reviewer. No check, credit memo or accepted deduction comes out of it, and no distributor, retailer or broker hears from it. Those steps belong to a live run you agree to, with a person approving every claim.

Priced for this job alone: a range before the proof of concept, a fixed price after it and before you sign.

Three things set the range: monthly claim count, the number of customers and brokers sending claims, and how many sources the units data comes from.

// Questions

Promotion claim questions

We plan promotions in a TPM tool. Where does this fit?
Beside it. The TPM tool holds the plan, the deal terms and the accruals; this job checks each incoming claim against them. For the test, an export of the deals behind the sample is enough.
Can it check a claim when we can't see the retailer's scan data?
It checks the rest: the agreement, the dates, the rate and the cap. Where a claim's units can't be compared with any data you hold, the draft says so and holds the claim for a person rather than accepting the customer's count.
Does it work for depletion allowances in beer, wine and spirits?
Yes, if you send the program terms and the depletion reports for the claim period. State rules on allowances stay with your team; the draft checks each claim against the program as it was written.
What about foodservice deviation billbacks?
Include some. Send the contract prices, the operators on each agreement and the distributor's detail file, and the draft checks every line against the price in force on its invoice date.
Will it turn down claims for us?
No. It recommends paying, paying part or holding, and shows why. While it is being tested, customers hear nothing at all; once it runs live, each decision goes out only after someone on your team approves it.
Rob Eason

Rob Eason, founder

// Book a call with Rob

Bring the claims you settled last quarter.

A half-hour call with Rob covers what your company makes, your part in it, which customers send the most claims and roughly how many land each month. Keep the claims themselves until the NDA is signed.

  • Co-owned a 60-employee financial services firm and sold his share to his partner.
  • Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
  • 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
  • 4.3/5 from 6 Google reviews of Massmarket AI.
  • Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
  • Takes every proof-of-concept call himself.