Portfolio demonstration with synthetic data

Reconciling recurring revenue

A fictional SaaS finance team needs a monthly recurring revenue (MRR) close it can trace back to individual billing events. This demo shows how the team handles duplicate events, late cancellations, and missing CRM accounts.

My role

I reconciled recurring revenue reporting across two systems and validated that a difference in metric definitions explained a discrepancy. The walkthrough below illustrates a separate month-end close with fictional records.

From billing event to monthly close

CollectRead billing events and a CRM account list.
ValidateKeep one event per ID and check account matches.
RouteHold unmatched events and flag late arrivals for review.
ReportApply eligible movements and show the remaining exposure.

Billing supplies the effective date and MRR change. CRM supplies the account match. This fictional close remains open for three days after month-end. An in-period event received after that cutoff goes to review for a possible prior-period adjustment.

January 2026 close

Try resolving the exceptions Confirm the CRM match for AC-99 Approve the late cancellation as a January adjustment

MRR waterfall · USD · dashed line marks the $2,400 billing snapshot

Show events


Event	Account	Effective	Received	Disposition	MRR change

Close sign-off

Compare the event-based close with a separate synthetic month-end billing snapshot. The billing snapshot stays fixed as you resolve exceptions, so you can see whether each decision moves the close closer to billing.

View billing snapshot balances

Billing account	January ending MRR

Resolution log

These decisions use fictional approvers and reasons. The log records your selections and reversals during this page session.


Event	Decision	Reason	Approver	Time (UTC)

What changes when both exceptions clear

Confirm the CRM match to release $150 in MRR. Approve the late cancellation to apply a $200 reduction. With both resolutions selected, the revised close is $2,400 and the review queue is empty. Clear either selection to replay the close without that resolution.

In a production workflow, record the approver, timestamp, and reason for each decision. Track how long exceptions stay open alongside their count and absolute MRR value.

This example uses one batch of fictional billing events, with all figures in US dollars.