In the case where the remittance statement doesn't match the integrator's expected value, the integrator should follow the diagram below to determine the pieces of information to provide to Google and resolution flow.
Remittance Disputes
All rights reserved. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-10-16 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-10-16 UTC."],[[["\u003cp\u003eThis guide outlines the steps integrators should take when the remittance statement value doesn't match their expected value.\u003c/p\u003e\n"],["\u003cp\u003eIntegrators will use the provided flowchart to determine the necessary information to share with Google for issue resolution.\u003c/p\u003e\n"],["\u003cp\u003eThe flowchart guides integrators through the process of identifying discrepancies and facilitates a smooth resolution with Google.\u003c/p\u003e\n"]]],["When a remittance statement discrepancy occurs, the integrator must consult a provided diagram to identify necessary information for Google and the proper resolution process. This involves determining what data to provide and understanding the subsequent steps for reconciliation. The core action is using the diagram to navigate the discrepancy resolution, ensuring the correct information is shared with Google to solve the issue.\n"],null,[]]