Transaction Reconciliation for digital advertising teams

Transaction reconciliation for advertising cards

Advertising card reconciliation must explain the difference between wallet funding, card loads, pending verification holds, threshold settlements, reversals and refunds. A single displayed balance is not enough for agencies, finance teams or clients.

Reconciliation model

• Record the platform-wallet deposit and the card-load debit as separate events.
• Link each card authorization to the ad account, campaign owner and billing profile.
• Show pending holds separately from settled media charges.
• Attach reversals and refunds to the original authorization or settlement.
• Export client-level records without mixing unrelated ad accounts.
• Alert when a settlement appears without a known authorization or when a hold remains pending beyond the expected window.

Worked reconciliation case

A campaign card receives a USD 300 load from the platform wallet. The ad platform creates a USD 1 verification authorization, then later settles a USD 248 threshold charge. The ledger keeps the USD 300 card load, USD 1 pending hold, USD 248 settlement and later USD 1 reversal as separate but linked records. Client reporting uses the settled charge, not the pending hold.

Daily review

Each day, finance compares ad-platform invoices with issuer-side card events and platform-wallet movements. Differences are classified as pending hold, delayed settlement, reversal, refund, fee or manual adjustment. Manual corrections require an operator, reason and source evidence.

Failure boundaries

Do not report a reversal as unrelated income, mix platform-wallet deposits with issuer-side card spending, or create a second debit when a webhook is replayed. Do not merge multiple clients into one card ledger when client reporting must remain separate.

Additional FAQ

Which amount should be shown to clients?

Use settled advertising charges and documented refunds. Pending authorizations should be labeled clearly and excluded from final spend until they settle.

How should refunds be matched?

Match refunds to the original settled transaction and ad account reference. A refund changes the card ledger; it should not be treated as a new platform-wallet deposit.

Frequently asked questions

What should be checked before the first transaction?

Confirm the displayed fees, available balance, supported use case, card status and merchant requirements. Start with a controlled amount and retain the resulting ledger entry.

Does a virtual card guarantee merchant acceptance?

No. Acceptance depends on the issuer program, merchant rules, geography, verification requirements and current risk controls.

How should teams evaluate operational quality?

Review fee disclosure, card controls, transaction detail, refund handling, support channels, API idempotency and incident procedures.