Match Local Services Ads charges and credits Get the source data and prepare the review Documentation-checked component path; proposed workflow, not tested WHAT WAS CHECKED Public official documentation and supplied candidate artifacts only. No product login, account exports, client data, installation, credential access, external writes, advertising spend, template imports or live tests. Proposed prompts do not prove a feature supports every requested field. Missing required source data blocks execution. BEFORE YOU START - Existing authorized access to the correct source account and records; no new login, credentials, installation or permission grant is included. - Responsible lawyer/operations reviewer approves scope, definitions and any later action. - AI optional; use only approved minimized data and retain originals separately. DATA ACQUISITION LIMITS - No universal legacy LSA lead-level CSV or migrated-field schema verified. Monthly statements may contain aggregate adjustments only. STOP IF - Missing actual charge/credit references, region eligibility, source billing documents or current migrated UI coverage. KEEP THE ANALYSIS COPY SEPARATE Keep untouched original exports/screenshots and the identifying source map in restricted firm storage. Build a separate minimized analysis file; do not hide raw client data on another tab. Include the complete Scope/coverage note in the AI-visible workbook or prompt. Use aliases and administrative metadata only. Unknown is not zero, false, completed or absent. INPUT FORMAT LIMIT All capitalized analysis tables and alias fields are editorial contracts. Native exports retain real vendor headers; mapping is explicit. No blank starter template is evidence of available data. NATIVE REVIEW INPUTS version: 1 status: Requires distinct native-input templates or an explicit reviewed mapping; existing kit is not drop-in compatible compatibleWithoutMapping: False existingKitFilesInspected: - file: lsa-charges.csv firstLine: lead_id,charge_id,charged_at,amount,currency - file: lsa-credits.csv firstLine: credit_id,lead_id,posted_at,amount,status - file: lsa-reconciliation.csv firstLine: lead_id,original_charge,posted_credits,pending_amount,unmatched_rows,staff_outcome,evidence_refs,review_question - file: outcomes.csv firstLine: lead_id,staff_outcome - file: scope.txt firstLine: G24: scope.txt requiredNativeInputs: - name: ChargeCredits kind: editorial_table proposedDistinctTemplate: native-chargecredits-template.csv columns: - event_alias - lead_alias - entry_type - occurred_at - amount - currency - google_state - staff_outcome - evidence_refs acquisitionRequirement: Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts. - name: Billing kind: editorial_table proposedDistinctTemplate: native-billing-template.csv columns: - period - cost - adjustments - tax - payments - source_ref acquisitionRequirement: Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts. - name: Scope kind: approved_text_section proposedDistinctTemplate: native-scope-template.txt requiredContent: Full approved scope, source account aliases, date filters, date basis/timezone, as-of capture time, definitions, source-to-alias map provenance, matching rules, inspected/excluded records, permission/privacy limits, missing-data reasons, coverage and responsible reviewer. Include recipe-specific policies, versions and tests. Scope must be inside the AI workbook or pasted packet, not merely a separate unprovided file. templateFilesCreatedByThisTask: False requiredGate: Kit owner must add the named inputs or document field-level mapping before replacing an existing kit prompt. Preserve the old kit contract; never rename headers without acquiring missing evidence. OPEN THE INPUT MAPPING GUIDE NATIVE-INPUT-MAPPING.txt Use the distinct native input scaffolds listed below. Complete them from the acquired, reviewed evidence and include every required scope section in the AI-visible packet. Existing synthetic examples exercise the original review prompt only. They are not acquired evidence or a test of this native chain. ChargeCredits: native-chargecredits-template.csv Billing: native-billing-template.csv Scope: native-scope-template.txt STEP 1: Gate the billing review by product and region Tool: Local Services Ads / Google Ads Open: LSA current inbox/migration notice; Lead inbox > menu > Reports and Billing Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included. AI role: not_an_ai_step Read legacy/migrated state, country/category and dates. Legacy Reports supplies charged leads/spend/credits; manually capture displayed values and lead charge/credit states. Migrated lead-level field/export paths must be verified in the actual account first. Expected output: Product/region scope and original lead/report captures. Use it next: Retain actual lead references where visible; do not invent an exported lead ID. Check: Automated-credit eligibility varies; current docs exclude EMEA, healthcare and tax specialists. Unwanted is not automatically refundable. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source documentation: https://support.google.com/google-ads/answer/17213585?hl=en https://support.google.com/localservices/answer/6226265?hl=en https://support.google.com/localservices/answer/7435485?hl=en https://support.google.com/localservices/answer/15100654?hl=en STEP 2: Download the real billing documents Tool: Google Ads billing Open: Billing > Documents > relevant available invoices/statements > Download selected; postpay/prepay: Tax and statutory documents where available Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included. AI role: not_an_ai_step Download actual available billing PDFs for the relevant months and preserve originals. Match the paying account and currency. If no document exists yet or the billing mode/country differs, record the actual availability instead of inventing a statement. Expected output: Original invoice/statement PDFs and visible charge/adjustment totals. Use it next: Staff transcribes checked amounts and posting periods into Billing; keep payment identifiers and tax details local. Check: Original lead charges may remain on invoices after a later credit. A billing payment is not the same as campaign cost, and an aggregate statement may not have lead-level IDs. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source documentation: https://support.google.com/google-ads/answer/1723045?hl=en https://support.google.com/localservices/answer/15100654?hl=en STEP 3: Make the checked, minimized handoff Tool: Excel / source-record reviewer Open: Restricted original workbook > separate analysis workbook > Scope worksheet Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included. AI role: not_an_ai_step Make a ChargeCredits table only from observed lead and credit references, using checked aliases. Preserve original charge date and later credit-posted date separately. Reconcile aggregate invoice totals separately when lead-level linkage is unavailable. Keep staff outcome observations distinct from Google charge state. Keep untouched original exports/screenshots and the identifying source map in restricted firm storage. Build a separate minimized analysis file; do not hide raw client data on another tab. Include the complete Scope/coverage note in the AI-visible workbook or prompt. Use aliases and administrative metadata only. Unknown is not zero, false, completed or absent. Build ChargeCredits with exactly one row per observed charge or credit event, an evidence-backed event alias and entry_type=charge or credit. Do not repeat an original charge on every credit row. Retain original event references privately and document sign conventions in Scope; missing record-level evidence blocks per-lead reconciliation. Expected output: ChargeCredits(event_alias,lead_alias,entry_type,occurred_at,amount,currency,google_state,staff_outcome,evidence_refs); Billing(period,cost,adjustments,tax,payments,source_ref); Scope(eligibility,coverage,migration) Use it next: Format each approved range as a named table. Carry source-row references and coverage into the analysis workbook. Check: Every field has an observed source or an explicit missing reason; staff assignments are marked editorial, not native. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source documentation: https://support.microsoft.com/en-us/excel/merge-queries-power-query https://support.google.com/localservices/answer/15100654?hl=en STEP 4: Ask AI to inspect the checked inputs Tool: Excel Copilot, optional Open: Analysis workbook > Copilot icon at lower right > Chat only Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included. AI role: downstream_application_ai Open the minimized workbook containing the named tables and Scope. Paste the exact prompt; if unavailable, perform the same rule checks manually. PASTE THIS PROMPT Use ChargeCredits, Billing and Scope. Join only checked lead references, retain charges and later credits as separate entries, and list pending/In review and unmatched amounts. Reconcile costs, credits, taxes and payments using their actual sign conventions without treating them as interchangeable. If invoice rows lack lead identifiers, show aggregate-only reconciliation and block per-lead matching. Staff outcomes are observations, not proof of credit eligibility. Do not promise refunds, fabricate IDs, submit feedback/disputes or change budgets. Expected output: Read-only reconciliation with pending credits, unmatched amounts and explicit granularity limitations. Use it next: Copy checked results into a new Review sheet, retaining source references and unresolved blockers. Check: Check arithmetic and date cutoffs; unknown credit is not zero or denied. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source documentation: https://support.microsoft.com/en-us/excel/copilot/get-started-with-copilot-in-excel STEP 5: Human review and final action Tool: Responsible firm reviewer Open: Internal Review worksheet / review document Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included. AI role: not_an_ai_step Finance/marketing reviewer checks the source documents and eligibility. Save the reconciliation; any factual lead feedback is individually reviewed and separately approved. Expected output: Reviewed charge-credit register and unresolved items. Use it next: If approved later, legacy Leads > selected lead > Rate this lead is the documented feedback route, not a guaranteed manual refund claim. Check: No feedback/dispute submitted; credit timing/eligibility is never guaranteed. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source documentation: https://support.google.com/localservices/answer/15100654?hl=en https://support.google.com/google-ads/answer/1723045?hl=en ACCOUNT AND SOURCE CHECKS STILL NEEDED - The live account, entitlement, exact headers, records and field coverage have not been observed. USING THE FILES IN THIS KIT Use the exact files or source text named in the steps above. Native exports keep their own headers. The kit tables are editorial review worksheets; they are not a claim that a product exports those fields. Some routes use reviewed text directly or require additional original files. Never rename an unreviewed raw export to make it appear mapped. Keep expected-result files separate from inputs. The source account, actual data, prompts and end-to-end workflow were not tested. Any final communication, filing, permission change, payment or publication needs its own authorized human action. This guide performs none.