Advertising spend reconciliation
Reconcile advertising spend against finance and billing exports.
Compare exported advertising-platform spend with card statements, accounting exports or client billing files. Use ReconLoom's existing reconciliation workflows to inspect where the records differ.
Compare exports you already have
Choose CSV, XLS or XLSX exports from an advertising platform and a corresponding financial, accounting or billing source. ReconLoom works with files you export; it does not connect directly to Meta Ads, Google Ads, LinkedIn, bank accounts, cards or accounting systems.
Example: platform spend and a card statement
Use the existing Financial workflow when the two files contain comparable transaction amounts, dates, currencies or references. Confirm the fields, sign conventions and any date or amount tolerances that apply to your exports.
Example: platform spend and client billing
Use Financial or Generic Record depending on the structure of your files. In Generic Record, confirm an identity field and choose the fields to compare, such as client, campaign, date, currency or amount. ReconLoom does not infer that a campaign belongs to a client; you choose and confirm the mappings.
Review possible discrepancies
Depending on the fields and rules you configure, inspect records present on one side, changed values, amount or date tolerance outcomes, invalid rows, duplicate candidates, conflicts and unresolved cases. Currency conversion, tax or fee interpretation and campaign allocation are not inferred automatically. Different currencies require your review; conversion is never implicit.
Review and export locally
Review available source values, differences and row provenance. Financial runs must be finalized before export; Generic Record results follow their supported review and finalization flow. Export a reviewed CSV or XLSX report locally.
Local-first data handling
Reconciliation source files and rows are processed on your device and are not sent to ReconLoom services during reconciliation. Large workloads may use local browser storage. Trial, entitlement and privacy-safe analytics metadata may use network services when those features are used; see the Privacy Notice.