Services

Credit Card Reconciliation for Commercial Real Estate: Property Coding and Reimbursable Tracking

September 2026  ·  CleanCRE

A corporate card sitting on a property or a portfolio isn't just another account to reconcile. Every charge has to land against the right property, the right entity, and often the right tenant or vendor, and a fair number of those charges need to make their way back to someone else entirely, an owner who should be reimbursed, a tenant whose expense got fronted on the card. Here's what actually goes into doing it correctly.

Every Charge Needs A Home Before It Gets A Category

A generic business would just categorize a credit card charge as an expense and move on. Property accounting adds a step first: which property, which entity, and sometimes which lease or work order the charge actually belongs to. A card used across a whole portfolio without that discipline turns into a pile of transactions nobody can trace back to where the money actually went, and untangling that after the fact takes far longer than coding it correctly the first time.

Reimbursable Charges Have To Be Flagged, Not Just Recorded

Some charges on a corporate card aren't really the property's expense at all, they're costs that should get billed back to a tenant, or reimbursed by an owner, or reclassified once someone figures out who actually should have paid. If reimbursable charges get coded the same as any other expense, they quietly become the property's cost permanently instead of getting collected back. This is exactly the kind of thing a Reimbursable Expenses workflow exists to catch, flagging a charge at the point of entry so it shows up on a dashboard instead of disappearing into the general ledger.

The Liability Account Has To Match The Statement, Every Month

The mechanics underneath all of this are standard: every charge increases a credit card liability account, every payment reduces it, and the account balance should equal the actual statement balance at any given point. When it doesn't, that mismatch is the first sign something got missed, a charge that never got recorded, a payment applied to the wrong account, a duplicate entry. Reconciling the liability account against the actual statement every month is what catches this before it compounds.

Multiple Cards Across A Portfolio Need Consistent Treatment

A portfolio with several properties or entities often means several cards, sometimes several cards per entity. Treating each one with a different process, different categories, different review cadence, makes portfolio-level reporting unreliable even when each individual card's books look fine on their own. The categorization logic and the reimbursable-flagging process need to be the same across every card, not something that varies by whoever happens to be managing it that month.

What Good Actually Looks Like

Frequently Asked Questions

Why does it matter which property a charge gets coded to?

Because property-level financials only mean something if the expenses feeding them are accurate. A charge coded to the wrong property distorts that property's numbers and understates another's, and portfolio-wide, those small misallocations add up.

What happens if a reimbursable charge isn't flagged?

It just sits as a normal expense on the property's books, and the money that should have come back from a tenant or an owner never gets collected because nobody's tracking that it was ever owed in the first place.

How often should the credit card liability account actually be reconciled?

Every month, without exception. It's one of the faster reconciliations to skip when things get busy, and also one of the easiest places for a small error to sit unnoticed for months.

Does it matter if different properties use different cards from different issuers?

Not for the categorization and reconciliation process itself, that should stay consistent regardless of which card or issuer is involved. What matters is applying the same discipline everywhere rather than letting the process drift card to card.