Finance Rejects Marketing Numbers: The Reconciliation Ritual

Why Finance Rejects Marketing Numbers

Finance operates on GL truth - bank deposits, invoices, refunds, chargebacks, payment processor fees. Marketing operates on platform truth - pixel fires, UTM tags, attribution windows. These systems rarely align perfectly, but rejection signals a material gap.

Common rejection triggers: (1) Marketing reports $100K revenue attributed to a campaign; finance sees $87K deposited after processor fees and refunds. (2) Marketing counts a sale on day 1; finance records it on day 3 after payment clears. (3) Marketing attributes a $5K order to email; finance sees it came from a returning customer with no new touchpoint. (4) Marketing reports 500 conversions; finance counts 480 paid invoices plus 20 chargebacks.

The rejection is not an accusation - it's a reconciliation failure. Finance needs marketing's data to close the books. Marketing needs finance's data to validate measurement.

The Reconciliation Ritual: Monthly Procedure

Establish a fixed monthly window (e.g., 48 hours after payment processor settlement). Assign one person from marketing and one from finance as reconciliation owners.

Marketing exports: total revenue reported by channel, total conversions by source, total orders attributed to paid campaigns, refunds/cancellations by source
Finance exports: total revenue deposited to bank account, total refunds/chargebacks processed, total payment processor fees deducted, GL entries for revenue recognition
Compare totals. Acceptable variance: <5% or <$500, whichever is smaller. If variance exceeds threshold, proceed to diagnosis
Diagnosis checklist: (1) Are refunds and chargebacks included in marketing's attributed revenue? (2) Are payment processor fees deducted? (3) Are multi-day payment settlement delays accounted for? (4) Are currency conversions applied consistently? (5) Are duplicate orders or test transactions excluded?
Document the variance source in a shared reconciliation log. If unresolved, escalate to CFO and CMO with root cause hypothesis
Repeat monthly until variance stabilizes below threshold for 3 consecutive months

Attribution Conflicts: The Most Common Rejection

Marketing attribution (last-click, first-click, multi-touch) rarely matches finance's invoice-level truth. A customer may click an ad on day 1, receive an email on day 5, and purchase on day 7. Marketing may credit the email; finance credits the customer record.

Resolution: Define a single source of truth for attribution. Options: (1) Last non-direct click (simplest, most conservative). (2) First-touch for awareness campaigns, last-touch for conversion campaigns (requires campaign tagging discipline). (3) Multi-touch with fixed weights (e.g., 40% first, 20% middle, 40% last - requires agreement on weights).

Once defined, marketing must report attributed revenue using that model. Finance validates the model against invoice records. Variance should shrink to <3% within two months.

Measurement Gaps: Pixels, UTMs, and Tracking Decay

Marketing's numbers are only as good as pixel firing and UTM tag accuracy. Finance sees what actually happened; marketing sees what the pixel recorded.

Common gaps: (1) Pixel fires but order fails to process (false conversion). (2) UTM tag missing or malformed (order attributed to direct). (3) Pixel fires after purchase (conversion counted but no revenue). (4) Pixel fires multiple times per user (duplicate conversions). (5) Third-party cookie deprecation (iOS, Firefox, Safari users untracked).

Audit pixels quarterly: (1) Install pixel on thank-you page and verify it fires for test purchases. (2) Check UTM tag format against documentation. (3) Compare pixel-reported conversions to invoice count for a single day. (4) Review pixel-to-revenue ratio by source (should be consistent month-to-month). (5) Test on iOS and Android separately.

Operational Leakage: Orders Finance Sees But Marketing Doesn't

Finance may report revenue that marketing's attribution system never captured. This is operational leakage - real money that bypassed tracking.

Sources: (1) Direct orders (no UTM, no pixel). (2) Phone orders. (3) B2B deals with custom invoices. (4) Wholesale or partner orders. (5) Refunded orders (finance records them; marketing may not). (6) Orders from users with ad blockers or privacy tools.

Quantify leakage: (Finance total revenue - Marketing attributed revenue) / Finance total revenue. If >10%, investigate. If >20%, tracking infrastructure is broken.

Mitigation: (1) Tag all order sources at the invoice level (not just pixel-based). (2) Implement a fallback tracking method (e.g., server-side pixel, CRM integration). (3) Exclude known untrackable sources from marketing's reported total and flag them separately.

Refunds, Chargebacks, and Net Revenue

Marketing reports gross attributed revenue. Finance reports net revenue after refunds and chargebacks. The gap is material and often overlooked.

Procedure: (1) Marketing exports attributed revenue by source. (2) Finance exports refunds and chargebacks by source (requires payment processor or CRM tagging). (3) Calculate net attributed revenue for each source. (4) Compare to gross. Acceptable variance: <3% per source.

If refund rate is high for a specific source (e.g., >8%), investigate: low-quality traffic, product-market fit issue, or customer expectation mismatch. This is a signal, not a rejection.

Documentation and Escalation

Create a reconciliation log (spreadsheet or simple database). Record: month, total variance, variance %, root cause, action taken, owner, resolution date.

If variance exceeds threshold and root cause is unclear, escalate within 5 business days. Escalation path: (1) Marketing and finance leads meet to diagnose. (2) If unresolved, CFO and CMO review. (3) If still unresolved, audit tracking infrastructure (pixels, UTMs, CRM integrations).

Unresolved rejections compound. A 5% monthly variance becomes 60% annual variance. Establish a norm: all rejections resolved within 30 days or escalated to executive review.

Questions

FAQ

What variance percentage is acceptable?

Less than 5% or less than $500, whichever is smaller. This threshold accounts for rounding, timing differences, and minor tracking gaps. Variance above this requires diagnosis. If variance is consistent (e.g., always 3%), document it and move on. If variance is random or growing, investigate.

Who owns the reconciliation?

Assign one person from marketing (usually analytics or ops) and one from finance (usually accounting or FP&A). They own the monthly ritual, diagnosis, and documentation. Escalation goes to CMO and CFO if unresolved within 5 business days.

Should marketing include refunds in attributed revenue?

No. Marketing reports gross attributed revenue. Finance calculates net revenue after refunds and chargebacks. Compare gross-to-gross and net-to-net separately. If refund rate differs by source, investigate the source quality.

What if the variance is always 7-8%?

Consistent variance is often explainable (e.g., payment processor fees, known untrackable traffic, attribution model difference). Document the cause and establish it as the baseline. Monitor for deviations from baseline. If baseline shifts, investigate.

Want this on your account?

Thirty minutes. Bring the number that keeps you up.

Book a demo