CPA Advisory

Numbers you can stand behind.

I help organizations get revenue recognition right, get audit-ready, and keep their data trustworthy through system changes — bridging accounting judgment with the systems that actually run the numbers.

Background

Ten years inside a high-volume revenue system.

Where the expertise comes from A large organization processing revenue across a high volume of individual transactions — determining exactly when that revenue was earned, and translating that logic into calculation code.
The systems side Worked directly in Databricks: locating the right source tables, tracing where data actually lived, and specifying how each calculation should run.

Most accounting problems don't fail on the theory. They fail in the handoff — the point where a judgment call has to become a query, a table join, a scheduled calculation, and nobody in the room speaks both languages fluently.

That gap is where I've spent my career. At a large organization, my job was to determine when revenue tied to a high volume of individual transactions had actually been earned — and act as the bridge to the engineering side: translating that accounting judgment into technical specs a Databricks developer could build against. I owned the "why"; he owned the "how." I made sure the two never drifted apart.

Day to day, that meant knowing which tables held which data, tracking down source-of-truth fields across a sprawling system, and navigating data backfills or pipeline hiccups without losing the accounting context that made the numbers make sense. I also enjoyed working in the data directly — investigating individual line items when a total looked wrong, rather than taking a report at face value.

I bring that same approach to three connected areas of practice: revenue recognition, audit readiness, and data integrity through systems transitions — because in most organizations, they're really the same problem wearing different hats.

How I can help

Three connected areas of practice.

Each stands on its own, but they tend to show up together — get one wrong and the other two usually follow.

01

Revenue recognition

Determining when revenue is actually earned — whether it's contract-based, subscription, usage-based, or milestone work — and building a methodology that holds up.

Learn more →
02

Audit readiness

Evaluating your controls and documentation ahead of a financial statement audit, and closing the gaps before an auditor finds them.

Learn more →
03

Data integrity & transformation

Keeping your numbers correct while you migrate systems — controlling the transition and validating the pipeline that feeds your reporting.

Learn more →
Get in touch

Schedule a consultation.

Tell me a bit about where things stand, and I'll follow up to set up a time to talk.

Email Victoria@vlohncpa.com
Phone (910) 363-7255
Web vlohncpa.com
Sends directly to Victoria's inbox.