KariTECH
Teams / Programmatic
PROGRAMMATIC RECONCILIATION / ILLUSTRATIVE WORKFLOW

Find the difference before report day.

Turn matched DSP and ad server counts into a clear list of discrepancies, with the calculation basis attached.

Try the discrepancy checker
Two frosted reporting grids align, with one offset lime marker in sharp focus.
PROGRAMMATIC RECONCILIATION / A CONNECTED WAY TO WORK
THE SHIFT

Same team.
A different way to work.

WITHOUT A CONNECTED WORKFLOW

When someone has time.

An analyst pastes two reports into a spreadsheet, matches placements, calculates differences, and builds an escalation list. A mismatch in dates can send the investigation in the wrong direction.

WITH A CUSTOM WORKFLOW

A process that keeps moving.

A connected workflow could collect scheduled reports, apply reviewed placement mappings, compare counts, and carry unresolved exceptions into the next review.

WHAT THIS MAKES PRACTICAL

An investigation history for every recurring discrepancy, so the same issue does not start from scratch each month.

THE WORKFLOW

Here’s how it
could come together.

A repeatable placement-level comparison instead of a last-minute check of totals.

  1. 01

    Align the comparison

    Confirm placement mapping, date range, timezone, filters, metric definitions, and report freshness.

  2. 02

    Compare on an explicit basis

    Use the team’s chosen reference and review threshold, keeping undefined percentages visible.

  3. 03

    Attach the evidence

    Keep both counts, the difference, source records, and prior investigation notes together.

  4. 04

    Route the investigation

    Assign the discrepancy to a person who can check reporting, tags, and setup before escalating.

WHAT GOES IN

Matched placement identifiers, DSP and ad server reports, calculation reference, and an agreed review threshold.

WHAT COMES OUT

A review queue with source counts, calculation basis, investigation context, and accountable owners.

WHAT WE WOULD MEASURE
  • Placements compared on a consistent basis
  • Time needed to prepare an exception list
  • Recurring issues with a documented investigation
PEOPLE KEEP THE FINAL CALL

Built to support
your judgment.

A difference is a reason to investigate, not proof of a tracking failure or billing error. People confirm the comparison and decide what needs escalation.

TRY ONE BUILDING BLOCK

Start with something useful.

Compare pasted counts here. The Delivery Reconciliation Desk concept extends that step into scheduled collection, mappings, and an investigation history.

Try the discrepancy checker
LET’S FIND YOUR FIRST WORKFLOW

What’s slowing
your agency down?

Bring one recurring headache and the tools you use.
That’s enough to start a useful conversation.

Discuss your workflow

Tell us what happens today.
We’ll explore what could work better.