> 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/repair-finance-synchronization.md).

# Repair finance synchronization

Repair a finance synchronization problem while keeping delivery evidence, invoices, payouts, currencies, and external accounting receipts consistent.

Use this guide when a finance connection, invoice, publisher payout, currency conversion, or accounting receipt is delayed, rejected, or different from the Podigee evidence. Finance sync does not change ad delivery. It transfers approved money records to the selected authority.

## Identify the affected record

Open **Monetization > Evidence & Money > Finance**. Identify whether the problem affects:

* finance authority;
* tax, currency, and rounding rules;
* Settlement period;
* buyer invoice;
* publisher statement or payout;
* accounting connection;
* external receipt;
* reconciliation or adjustment.

Record the short record reference, version, seller or buyer, publisher, period, currency, state, last attempt, and visible failure reason.

![The saved One Podigee finance setup shows the active invoice issuer and country rule used by finance workflows.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-7bec62f466c4dcf903dc2350d385dd2e4805b393%2Fdoc-monetization-020-finance-authority-active.jpg?alt=media)

*Confirm the active finance authority before you repair a downstream record.*

## Read the synchronization state

| State                 | Meaning                                             | Safe action                                                    |
| --------------------- | --------------------------------------------------- | -------------------------------------------------------------- |
| **Draft**             | The record is prepared but not approved.            | Complete the finance review first.                             |
| **Ready**             | The record passed local checks and can be sent.     | Start the declared sync operation.                             |
| **Syncing**           | The external system is processing the exact record. | Wait. Do not submit again.                                     |
| **Retryable failure** | A temporary connection or provider issue occurred.  | Repair the dependency and retry the same version once.         |
| **Rejected**          | The external system refused the record.             | Read the provider reason and correct the named input.          |
| **Synchronized**      | A receipt confirms the exact record.                | Keep the receipt and do not resend without an approved reason. |
| **Held**              | A finance or compliance hold prevents transfer.     | Resolve or release the hold with evidence.                     |

## Check the local record before retry

Confirm:

* buyer, publisher, and legal entity;
* Settlement period and original delivery dates;
* invoice or payout state;
* tax treatment and rate evidence;
* source and Settlement currency;
* amount, precision, and rounding;
* beneficiary or invoice recipient;
* active connection and stored credential reference;
* review result for the exact record version.

If any value changed, create the current version through the normal finance workflow. Do not edit an approved or issued record to make the external system accept it.

## Repair the finance connection

If the connection is unavailable:

1. Open **Monetization > Integrations**.
2. Select the finance or accounting connection.
3. Check its authority, endpoint, credential reference, certification, and expiry.
4. Repair or rotate the credential through the secure access workflow.
5. Create a new connection version when the endpoint, mapping, or authority changed.
6. Run the managed connection test.
7. Complete the configured review.
8. Activate the new connection only after the test passes.

Keep the previous connection version and failed receipt. A new connection version must not change the meaning of historical invoices, payouts, or delivery evidence.

## Retry one approved synchronization

When the page offers **Retry synchronization**:

1. Open the failed invoice, payout, or accounting job.
2. Confirm the exact record version and amount.
3. Check whether an external receipt already exists.
4. Repair the named temporary connection problem.
5. Select **Retry synchronization** once.
6. Wait for the final state.
7. Confirm the external receipt and local status.

The operation uses the same idempotency key and exact record digest. If the external system already accepted the request but its response was lost, the retry returns the original receipt instead of creating a second invoice or payout.

## Handle an invoice synchronization failure

For a buyer invoice, check:

* invoice approval is complete;
* invoice number is not already issued;
* legal entity and country match the finance authority;
* tax and currency rules are active for the period;
* delivery lines and totals are locked;
* the accounting system accepts the document profile.

If the invoice was rejected because of a wrong buyer, tax, or currency, open reconciliation or the approved correction workflow. Keep the issued document unchanged and create a credit note or later adjustment when required.

## Handle a payout synchronization failure

For a publisher payout, check:

* the statement is approved;
* the beneficiary version is current;
* the amount and currency match the statement;
* any payout hold has a release record;
* the external payout route is active;
* the payout has no existing paid or submitted receipt.

Do not prepare a second payout because the first receipt is delayed. Inspect the original payout job and external status first.

## Handle currency or rounding differences

Compare the exact tax, currency, exchange-rate, precision, and rounding rule versions. Check the rate source and fixing time used for the Settlement period.

Do not type a new amount into an invoice, payout, or reconciliation form to force a match. Create a controlled correction from the balanced ledger entry and apply the configured review rule.

## Reconcile a receipt mismatch

If Podigee shows **Syncing** or **Retryable failure** but the external system says it received the record:

1. Copy the short local record and job references.
2. Search the external system by idempotency key or request digest.
3. Compare document or payout number, amount, currency, and recipient.
4. Record the external receipt in the finance synchronization case.
5. Mark the local operation complete only after the exact record matches.

If the values do not match, stop and open **Reconciliation**. Do not resend the record until the difference is resolved.

## Confirm the final state

Open the finance job detail and confirm:

* exact record and version;
* source delivery evidence and Settlement period;
* local state;
* external state and receipt;
* amount, currency, and document or payout identifier;
* retry count and timestamps;
* any remaining warning.

![The current One Podigee revenue job detail shows the selected job, its current state, delivery scope, and the evidence result.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-ef87d1b1ad7097633ced378a24cd98551cc57cf8%2Fdoc-monetization-068-job-detail.png?alt=media)

*The job detail ties the synchronization result to the exact finance record.*

## Escalate after one controlled retry

Escalate when the external system and Podigee disagree, when the same exact version fails after the connection is healthy, or when money could be duplicated or lost. Include the short invoice, payout, job, connection, and receipt references, the amount and currency, and the visible failure. Do not include credentials or private banking data.

## Expected result

The selected finance record is synchronized once, or remains safely blocked with a clear reason. Delivery evidence, invoice or payout state, currency, accounting receipt, and reconciliation history continue to refer to the same exact record without duplicate money movement.


---

# 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/repair-finance-synchronization.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.