Per-event card reconciliation: accounting hygiene for wedding and event planners

Published: 20 October 2026

Category: how-to-guides | cardbuzz

Tags: accounting, reconciliation, event planners, bookkeeping, business credit cards

An event planner running five weddings in a season puts hundreds of card transactions through the business: vendor deposits, decor purchases, crew meals, hotel blocks, fuel, emergency supplies. Come tax time — or the moment a client questions a recharge — those transactions need to answer three questions: which event was this for, was it authorised, and where is the supporting document. Planners who cannot answer quickly pay their CA extra hours, lose disputes they should win, and never really know which events were profitable.

Per-event reconciliation is the discipline of tagging every card transaction to the event it served, matching it to its document, and closing the books per event rather than per month. It is unglamorous work that pays for itself many times over. Here is how to build it.

Why monthly bookkeeping is not enough

Standard bookkeeping works month by month: all of March's transactions, categorised by expense type. That tells you what the business spent, but an event planner needs to know what each event cost. A single month's card statement might contain spends for three different events at different stages — deposits for a December wedding, final settlements for a November one, crew meals for an ongoing corporate event. Monthly categorisation mashes them together, and per-event profitability becomes guesswork.

Per-event accounting flips the primary key: every transaction carries an event tag first, an expense category second. The month-end books still get built, but they are assembled from per-event records rather than replacing them.

The event ledger: your unit of accounting

Treat each event as a mini profit-and-loss account. For every event, maintain a ledger — a spreadsheet or accounting-software project — with:

The event identifier. A short code: client surname plus date, or a running job number. Use it everywhere — on contracts, invoices, file names, and transaction notes.
Contracted revenue. The total fee agreed, plus any agreed recharges and their terms.
Every cost line, each with: date, vendor or merchant, amount, card reference (last four digits plus transaction date is enough to find it on the statement), expense category, and the supporting document.
Client advances received, with dates — so you always know the event's cash position, not just its profit position.

When the event closes, the ledger should reconcile to zero open items: every cost documented, every recharge billed, every advance adjusted. An event with open items is an event that can still surprise you.

Tagging transactions: the practical workflow

The tagging has to happen close to the transaction, or it will not happen at all. Three workable methods:

Statement annotation. Most card issuers and banking apps let you add notes or tags to transactions. Tag each one with the event code the same week it appears. This is the lowest-friction method and works for solo planners.
A shared transaction log. For teams, a simple shared sheet: date, amount, merchant, event code, purpose, receipt photo. The operations coordinator updates it from the daily card review. Slightly more work, much better for multi-crew operations.
Accounting software projects. If you use accounting software, create a project or cost centre per event and assign transactions to it during bank reconciliation. This is the most robust method and the one your CA will prefer — ask which software they work with before choosing.

Pick one method and enforce it universally. Three half-used systems are worse than one fully used one.

Matching documents to transactions

Every card transaction in the ledger needs its supporting document:

Vendor payments: the vendor's invoice (with GST details where applicable) and the contract or work order it relates to.
Deposits: the booking confirmation or advance receipt from the vendor.
Travel and stay: booking confirmations and hotel folios.
Crew and on-site spends: the daily log entries and any receipts.
Refunds and chargebacks: the credit note or refund confirmation, matched against the original transaction.

File documents per event, named with the event code and a sequence number. When the CA asks for "the decorator invoice for the Sharma wedding", you produce it in seconds. When a client disputes a recharge line, you send the invoice and the matching card statement excerpt in one message. This is what professionalism looks like from the client's side.

Handling the tricky transaction types

Refunds. A vendor refund appears on the card statement as a credit, sometimes weeks after the original charge and sometimes in a different billing cycle. Link it to the original transaction in the ledger explicitly — unlinked credits are how money quietly goes missing from event P&Ls.
Chargebacks. If you dispute a vendor payment, the provisional credit and the final resolution both need ledger entries against the same event. Do not treat a chargeback credit as income.
Foreign currency transactions. Record both the foreign amount and the billed rupee amount; the difference includes the markup. For client recharges, decide contractually whether the client bears the billed amount or a reference rate.
Split transactions. One card payment covering two events (a bulk decor purchase, for instance) must be split in the ledger with a clear allocation basis — by estimated usage, by value, documented at the time. Unsplit shared costs distort every event's profitability.
Personal vs business. If a personal expense ever lands on the business card by mistake, tag it clearly as a personal draw and reimburse the business immediately. Do not bury it in an event's costs.

The event-close checklist

Close each event's books within a defined window after the event — two weeks is a good target, before memories fade and the next event consumes everyone:

Pull all card transactions for the event period and confirm each is tagged.
Match every transaction to its supporting document; chase missing invoices now.
Confirm all client recharges are billed with statement-mapped evidence.
Verify vendor final settlements are paid and retentions released or deducted.
Reconcile client advances against the final invoice; refund or bill the difference.
Compute the event's true profit: revenue minus all tagged costs, including allocated shared costs.
Archive the ledger and documents; mark the event closed.

Step 6 is the payoff. Most planners discover their most "prestigious" events were their least profitable, and their bread-and-butter events carried the year. That knowledge reshapes pricing, client selection, and service packaging — it is the most valuable output of the entire discipline.

Working with your CA

A planner with clean per-event ledgers is a CA's favourite client, and it shows in the bill. Bring to each tax-planning meeting:

Per-event P&Ls for the year, not just a trial balance.
The GST invoice file per event, already matched to payments.
A list of receivables and payables per event with ageing.
Notes on any disputed, refunded, or written-off amounts.

Ask your CA specifically about: input tax credit on event expenses, TDS obligations on vendor payments, the treatment of client advances received before the event, and how to handle events spanning financial years. These are the industry's recurring tax questions, and clean records make the answers cheap to implement.

Key takeaways

Account per event, not just per month: tag every card transaction with an event code first, expense category second.
Maintain a ledger per event — revenue, every cost line with card reference, advances — and close it within two weeks of the event.
Match every transaction to its supporting document; file per event with consistent naming.
Handle refunds, chargebacks, foreign-currency, and split transactions explicitly in the ledger — these are where money quietly leaks.
Use the event-close P&L to learn which events are actually profitable, and let that reshape your pricing.
Clean per-event records make your CA faster, your disputes winnable, and your business genuinely understandable.

Per-event card reconciliation: accounting hygiene for wedding and event planners