Billing Reconciliation
A finance-grade reconciliation package for HRS usage, exports, employer program economics, and statement-ready variance review.
The billing-close page should open on the active statement window so finance and operations are reading the same frame.
Operators need the current mismatch count immediately instead of discovering it after drilling through exports.
Reconciliation only feels production-grade when the correction lane is visible from the first screen.
It exists so finance and operators can see whether the numbers line up before invoices or employer-facing statements are finalized.
That makes the report useful as an operating lane, not just a data dump.
That keeps reconciliation tied to the actual sources of movement instead of turning it into a dead-end finance screen.
{
"period": "2026-03",
"usage_billed_usd": 4318.42,
"program_fees_billed_usd": 912.13,
"variance_usd": 14.27,
"status": "needs_review",
"owner": "finance@northstar.example"
}Billing reconciliation should explain what moved, how much it moved, and who is responsible for closing the gap.
The reconciliation detail should show the exact statement window being reconciled.
Operators need mismatch count and severity immediately, not after drilling through export history.
The last clean close tells finance how stale the current discrepancy really is.
Workflow usage remains tied back to the same underlying ledger that powers platform billing.
Organization fee statements stay in the reconciliation picture without collapsing into one opaque total.
If finance needs to amend a mismatch, the correction lane is already visible from the first screen.
Most billing sources are reconciling cleanly across platform usage, exports, and employer programs.
Only two mismatches remain, but they still need operator review before the statement closes.
Finance still has a clean correction lane before month-end lock.
The month-to-date close routine began across usage, exports, and employer program statements.
Two mismatches were traced back to one export lane and one employer statement.
Finance reviews the final reconciliation state before the next invoice snapshot.
Billing reconciliation compares protected lookups, reports, exports, employer-fee programs, and statement lines against the current billing posture.
It exists so finance and operators can see whether the numbers line up before invoices or employer-facing statements are finalized.
A good reconciliation page should show variance, owner, and next action instead of forcing the team into raw ledger exports every time a number moves.
That makes the report useful as an operating lane, not just a data dump.
From here teams should be able to jump into billing, exports, audit history, or the organization-fee lane that generated the variance.
That keeps reconciliation tied to the actual sources of movement instead of turning it into a dead-end finance screen.