> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/grow-and-monetize/monetization/reconcile-sources-that-do-not-agree.md).

# Reconcile sources that do not agree

Compare two trusted records with fixed metric definitions and a fixed period, then document why they differ and whether a financial correction is needed.

Use reconciliation in the Podigee Audio Video Ad Server when two trusted records show different results for the same business question. The comparison preserves the selected records, metric definitions, and period so you can investigate without rewriting the source evidence.

Use this workflow for differences between Podigee delivery, provider reports, buyer reports, analytics, invoices, ledger entries, integration attempts, or qualified billable results. A reconciliation case explains a difference. It does not silently edit the source record.

## Before you start

Collect the two records that should be compared. They can be report results, report delivery attempts, billable results, recorded events, invoices, ledger entries, prior resolutions, or integration attempts. You need exactly two distinct records.

Confirm which published metric definitions can measure both records. Set the inclusive start and end dates to the period represented by the records. You need report read permission to inspect a case and reconciliation permission to open or resolve one.

## Start a comparison

1. Open **Monetization > Evidence & Money**.
2. Select **View comparisons**.
3. Select **Compare records**.
4. In **Records to compare**, choose exactly two trusted records. Use search to find a report, delivery attempt, invoice, ledger entry, event, or integration attempt.
5. In **Metrics**, choose one or more published metric definitions.
6. Set **Starts on** and **Ends on** for the inclusive comparison period.
7. Read the notice that the selected evidence stays frozen.
8. Select **Start investigation**.

![The current One Podigee Evidence & Money page provides the entry point for View comparisons and the trusted reporting context.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-ab157f76d1c3f5f7be3a2d369de4c2995b42dd3b%2Fdoc-monetization-072-reports-overview.png?alt=media)

*Open View comparisons from Evidence & Money when two trusted records need an explanation.*

The comparison stores the exact source references and metric versions. Later changes to a report, metric definition, or source record cannot silently change what the case compares.

![The current One Podigee comparison view shows the preserved trusted records, the measurement definition, the zero result difference, and the option to close the case without a financial change.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-7e5b211fdb8f38b01b12ef3e0413ae1ba32979fb%2Fdoc-monetization-086-comparison.png?alt=media)

*Read the source rows and metric difference before you decide whether money must move.*

## Read the comparison

Open the case from **Comparison history**. Check these sections in order:

1. **Comparison period**: confirm the start and end dates.
2. **Investigation progress**: read who started the case and what decisions were recorded.
3. **Trusted records**: check each source label, source type, description, and recorded time.
4. **Measurement definitions**: confirm the metric name, unit, and definition revision.
5. **Result difference**: read the difference between record 2 and record 1.

A positive difference means that record 2 is higher. A negative difference means that record 2 is lower. If a record does not expose a value for the selected metric, the page shows that the records cannot be compared for that definition. Do not treat a missing comparison value as zero.

## Decide whether money must move

When the evidence explains the difference and no correction is needed:

1. Select **Resolve without a correction**.
2. Explain what the records show and why no money must move.
3. Select **Resolve without a correction** again to record the outcome.

When a balanced correction is already prepared:

1. Select **Apply an approved correction**.
2. Choose one eligible correction entry.
3. Explain why this exact entry resolves the difference.
4. Complete the review rule shown on the page.
5. Select **Apply correction and resolve**.

Correction amounts and currencies come from the existing balanced ledger entry. You cannot type a new amount into the reconciliation form. This prevents a comparison from creating an unbalanced finance entry.

## Follow the review rule

The page shows the rule that applies to the selected correction:

* **Review is optional** means the organization permits the correction without another reviewer.
* An individual workspace can use the explicit confirmation that the operator reviewed the exact correction.
* An independent review rule requires a reviewer to approve this exact comparison before the correction can be applied.
* If the review rule is unavailable, restore the finance review rule before applying a correction.

Use **Request review** when the page requires another reviewer. Open the review request from the case when you need to check its outcome. Do not assume that approval of another comparison also approves this one.

## Record a dispute outcome

If the difference is a claim from a buyer, publisher, or other party, open **Resolve a dispute**. Choose **Accepted**, **Partially accepted**, **Rejected**, or **Withdrawn**, then write the evidence and reasoning that supports the decision. If the dispute also requires money to move, choose the existing eligible correction entry and complete the applicable review rule.

The decision is appended to the case. The original records, measurements, and earlier financial history remain unchanged.

![The current One Podigee resolved comparison shows the documented explanation, accepted decision, and no financial change.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-dd29e6e13f83b5fc8157707fa0d31207400444d2%2Fdoc-monetization-086-resolved-outcome.png?alt=media)

*A resolved case keeps the explanation and financial effect with the comparison.*

## Troubleshoot reconciliation

| Situation                               | What to check                                                                                                      |
| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Compare records** is not available    | Confirm that you have reconciliation permission.                                                                   |
| Fewer than two records are available    | Add eligible report, delivery, finance, event, or integration evidence, then return to the form.                   |
| The metric is not listed                | Confirm that a published metric definition exists for the comparison.                                              |
| The result says it is not comparable    | The selected records do not both expose a value for that metric. Choose a compatible metric.                       |
| A financial correction is not listed    | Post a balanced eligible correction entry before resolving the case.                                               |
| The correction button is disabled       | Complete the required review or restore the active finance review rule.                                            |
| The records still disagree after review | Check the period, time zone, metric revision, currency, source type, and data freshness before opening a new case. |

## Expected result

You have a frozen comparison that identifies the two trusted records, the fixed metric definitions, the comparison period, the measured differences, and the documented outcome. If money must move, the case points to an existing approved correction and keeps the review and authorization evidence with the decision.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podigee.com/documentation/grow-and-monetize/monetization/reconcile-sources-that-do-not-agree.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.