Expense recording trends: a card month-end routine

Capturing a cost is close to solved. A photograph of a receipt becomes a transaction, a card feed arrives the same day, and a supplier's invoice can be read and posted without anyone typing an amount. The bottleneck has shifted from entry to policy.

Card spend is where that shift bites first. The transaction lands the same day, the document trails it, and approval comes last. A month-end routine built for that order catches what a routine built around receipts misses.

What to take away

Cards arrive instantly and documents do not, so evidence is now the lagging half rather than the leading half.
Approval has moved after the money, so a written card policy is the control that is left.
Chase missing documents by value, not by count, and attach them at the moment of entry.
Coding rules and recurring charges need their own review, because a card keeps repeating whatever it was set up to do.

Cards reverse the order of events

The transaction now arrives before the document, sometimes weeks before. Company cards from providers like Ramp, Brex, and American Express, and virtual cards issued through Visa or Mastercard networks, have largely replaced the pattern where someone spent their own money and claimed it back.

Card spend reverses sequence

Then
Receipt triggers entry
Now
Transaction arrives first
Then
Approval before money
Now
Review after card works
Now
Document chased by month end

A receipt photographed in Dext or Hubdoc lands beside a card entry in QuickBooks or Xero, but the document often trails the charge by days. That reverses the old sequence in which the receipt was the trigger. Evidence becomes a chase rather than a by-product.

The measure that matters is the share of card spend that has a supplier document against it by the month end, valued rather than counted. One missing receipt for a large purchase outweighs a dozen missing ones for small items.

Approval after the fact

A card that works is a decision already made, and the review is now a conversation about something that has already happened. That removes a genuine cost to employees, and it moves the control from before the money to after it.

Where expense work moved

Then

Getting transaction in: Typed from document
Deciding the account: Chosen by person
Getting the document: Filed with entry
Approval: Before money moved
Scarce skill: Accurate fast entry

Now

Getting transaction in: Arrives from feed
Deciding the account: Proposed by rule
Getting the document: Chased afterwards
Approval: Frequently after
Scarce skill: Spotting bad items

Every place where a control moved from before the money to after it is a place where something can go wrong silently. The compensating control is a written policy: what the card may be used for, what limits apply, how soon the document must be attached, and what happens to spend outside it. That policy is the part no software supplies.

The policy also matters for evidence. The IRS calls the responsibility to substantiate entries and deductions the burden of proof, and says you must be able to prove certain elements of expenses to deduct them.

The month-end routine for card spend

Run the same six steps every month, in this order, so the card account is closed by evidence and not by habit.

List every card transaction with no supplier document, largest first, and chase those before the small ones.
Attach each document to its entry as it arrives, rather than gathering them later.
Check each transaction against the written policypurpose, limit, and anything outside it.
Review the recurring charges for anything new, renewed or unowned.
Look at the coding rules that posted the month's entries, not only the entries themselves.
Agree the card provider's report for the month to the card account in the ledger, before the period is closed.

Step six is the proof. Agreement with an outside record is the only real test that the month can be relied on, whatever produced the entries.

Recurring charges on the card

Subscriptions are the other structural change. Each one is below the level at which anyone would question it, renews without a decision, and is charged to a card rather than invoiced.

The ledger is usually the only place all of them are visible at once. Each year, produce a list: every recurring charge, its amount, its renewal month, and who would notice if it stopped.

That last column is the useful one. A recurring charge with no name against it is a decision nobody is making anymore.

Two ordinary bookkeeping habits do most of the work here. Keep annual charges spread across the periods they cover rather than landing whole in a renewal month, and resist the pull to create an account per service, which turns a spending question into a coding chore. What justifies a separate line is set out in the chart of accounts guide.

Coding rules repeat their own mistakes

Automated coding is a pattern match against what you did before. Two consequences are specific to costs, and both show up on card statements.

A supplier that changes what it sells keeps being coded the way it used to be. A merchant who supplied stationery for three years starts supplying equipment, and every transaction lands in stationery because that is what the rule learned.

And a correction to an entry does not correct the rule that produced it. The entry moves, the rule keeps running, and the same error arrives next month with a fresh date. Whenever you fix a coding error, check whether a standing rule made it, and review the rules themselves once or twice a year rather than only the entries.

What the routine cannot decide

Some questions stay with a person, and they are where the value now sits. A card feed cannot answer them, however clean the matching.

Whether a payment is a cost at all, or an asset, a deposit, a transfer, a repayment or owner money.
Which period a cost belongs to, when the supply date and the payment date differ.
Whether a purchase that outlasts the year should be charged over its life. In the words of IRS Publication 946, depreciation is an annual income tax deduction that allows you to recover the cost or other basis of certain property over the time you use the property.
How a genuinely shared cost is split between the business and the owner, and on what documented basis.
Whether the business should have bought the thing at all.

The first four are the gates set out in the framework for deciding what an outgoing payment actually is. The fifth is not bookkeeping, and it is the one that most often has no owner.

The check that has not changed

Every one of these shifts makes it easier to produce a set of books that is internally consistent and wrong. More feeds, more automatic matching, more items posted with nobody reading them.

Supplier statements against your payables ledger, the card provider's report against the card account, the lender's schedule against the loan balance: that is still the proof. The rest of the method is in the expense recording guide, and the readings that show whether it is holding up are in the measures of coverage, accuracy and latency.

Common questions

Should we move everyone onto company cards?

It removes a real burden from staff and it moves approval to after the spend. Both are true at once, so make the move alongside a written policy rather than instead of one.

Is automatic coding safe for costs?

For repetitive, low value, unambiguous items with a stable supplier, yes, with a monthly review of what it posted. For anything where the answer depends on what was actually delivered, no.

How do we stop subscription spend growing without noticing?

An annual list with a named owner per line, reviewed once. Almost every business that does this cancels something.

What is the first thing to change if we are behind on all of this?

Get documents attached at the moment of entry rather than chased later. It is the cheapest habit here and it is the one that everything else depends on.