Insights

When Finance Closes on Accrual and Ops Reports on Cash

Two legitimate clocks. One unlabeled number. The meeting is the collision.

Finance books the month on accrual. Ops tracks the week on cash movement and receipts on the dock.

Both clocks are honest. The Power BI tile has one label. The meeting becomes the collision.

Black-and-white tidal flats with two waterlines under an overcast sky

This is timing basis—not “different definitions of margin”

When two reports disagree on what belongs in a measure, you have a definition problem. That story is already told in why Power BI reports show different numbers and in margin definitions that don’t survive a meeting.

This post is the clock.

Accrual asks when the economic event was recognized. Cash asks when money or goods moved. Ops often lives closer to receipts, shipments, and working-capital reality. Finance lives closer to the close. Both need numbers. Neither is wrong for wanting its own basis.

The failure is publishing one revenue, one inventory, or one “actual” without saying which clock is running. Leaders argue about accuracy when they are arguing about time.

A mid-market company does not need a lecture on accounting theory. It needs labels, separate measures where both bases matter, and meeting rules that stop treating them as interchangeable.

Where the clocks collide

Revenue and bookings. Sales celebrates an order. Finance waits for recognition rules. Ops cares when product ships and cash follows. One unlabeled “sales” tile will lose someone’s trust every month.

Inventory and receipts. The plant sees product on the floor. The ledger may still be in transit, unvouchered, or accrued. A working-capital conversation that mixes those views without a timestamp is a fight waiting to start.

Vendor spend and open commitments. Ops manages the dock and the shortage. Finance manages the accrual and the close. Same vendor. Different as-of stories.

Forecast versus actuals. The forecast may be a cash or bookings view. The actuals may be booked accrual. The variance is then a basis mismatch wearing a performance costume.

None of this requires bad data. It requires two legitimate management clocks forced into one word on a page.

The costs of one unlabeled number

  1. The room debates truth instead of action. Twenty minutes go to “which number is right.” Both may be right on their basis. The unlabeled tile made them look like rivals.

  2. Ops stops trusting the finance-owned app. The plant or supply team keeps a cash-and-receipts workbook because the official page feels late or “accounting-only.” Dual systems return. See the grain cousin in ops still runs the plant from spreadsheets—here the split is basis, not only shift detail.

  3. Finance stops trusting ops packs. Close-ready actuals get mixed with operational snapshots in the same executive view. Controllers refuse to sign what they cannot defend. Sign-off becomes a monthly negotiation.

  4. Variance analysis lies. A miss can be timing, not performance. Without basis and as-of on the page, leaders “fix” a problem that will reverse next period—or miss a real one hidden inside a timing bridge.

  5. Working-capital decisions get the wrong clock. Inventory, payables, and receivables actions need operational timing and ledger timing. One blended tile pushes the real work back into side files.

  6. Model debt compounds. Authors hard-code filters to “make it match finance” or “make it match the plant” inside report pages. The semantic model never learns two named measures. Every new page reinvents the compromise.

  7. Refresh timing gets blamed for a basis problem. Overnight refresh can be fine. The fight is still there at noon because accrual and cash were never distinguished. People escalate gateways when they needed labels.

  8. New leaders inherit a trap. A new COO opens “Actuals,” compares to the plant huddle, and concludes the program is broken. The program published a noun without a clock.

How to fix it: name the clocks, then govern the meeting

  1. Inventory where both bases appear. List the decisions that need accrual, cash or receipts, or both. Revenue recognition, inventory on hand, open PO, collections, shipments. Write which clock each decision uses.

  2. Create separate measures with adult names. Accrued revenue. Shipped not billed. Cash collections. Inventory perpetual versus inventory accrued. Do not hide two logics under “Actuals.” Names are the first control.

  3. Put as-of and basis on the page. A small, visible label beats a glossary nobody opens. “Accrual, books as of Tuesday close” and “Operational receipts through 6 a.m.” are management sentences. Put them where the room can see them.

  4. Stop blending clocks in one unlabeled visual. If a chart needs both for a bridge, show a bridge. Do not average them into one line and hope the meeting is kind.

  5. Assign stewards by basis. Finance owns close-aligned measures. Ops owns receipt and movement measures that management has agreed to fund. Shared dimensions—item, plant, customer—stay shared. Basis logic does not get smuggled into a page filter.

  6. Rewrite the agenda to the clock the decision needs. Working-capital huddle runs on operational timing. Monthly financial review runs on accrual. The same company can use both without forcing one tile to pretend it is both.

  7. Build a timing bridge for the collisions you repeat. Where leadership always asks “why don’t these match,” fund a governed bridge: recognition lag, in-transit, open receipts, cut-off. Make the bridge a product, not a monthly hero file.

  8. Refuse unlabeled exports. If someone pastes a number into the pack, it carries basis and as-of or it does not enter the minutes. Leaders enforce the rule. Tools cannot.

  9. Review one collision end to end. Pick revenue or inventory. Separate the measures. Label the pages. Retire the blended twin. Then move to the next fight. Do not relaunch every dashboard with a new color palette.

What good looks like

Finance and ops still care about different rhythms. That is normal.

The model exposes both clocks with names a successor can read. The operating review opens the operational view on purpose. The financial review opens the accrual view on purpose. When someone compares them, they open a bridge, not a blame session.

Trust returns because the company stopped asking one word to do two jobs.

This is not anti-ops and not anti-finance. It is anti-ambiguity. Ambiguity is expensive in every mid-market Monday meeting.

Executive takeaway

Accrual and cash are two legitimate clocks. An unlabeled Power BI number makes them look like a data quality failure.

Name the basis. Separate the measures. Put as-of on the page. Run each meeting on the clock it owns. Build bridges where the clocks must meet.

Need a 30-minute look at where accrual and operational timing collide in your reports? Contact Alluvium. We’ll map one shared KPI, the two clocks underneath it, and the labels the room needs.

Book a 30-minute consult.

Next step

Book a Session

Need a clearer finance or executive reporting stack? Book a Session.

Book a Session