Closive

Methodology

What the scan checks, and how findings are verified

The scan reconstructs, from your signed contracts, what your billing and revenue records should contain — then compares that expected state against the actual exports, customer by customer. Each check below declares the inputs it needs. Your report states which checks ran, which could not, and what input would unlock them. Nothing is skipped silently.

The checks

01Renewal uplift / escalator applied

Tests that:
Where the contract specifies a price increase at renewal (fixed %, CPI-linked, or scheduled), the post-renewal invoices reflect it.
Requires:
Contracts and amendments; invoice export
Typical finding:
Renewal invoices issued at the pre-uplift price.

02Ramp pricing stepped on schedule

Tests that:
Multi-year or ramped pricing steps up in billing on the contract's schedule.
Requires:
Contracts; invoice export or subscription configuration
Typical finding:
Month-13 billing still at the year-one rate.

03Invoice lines match contracted prices

Tests that:
Each recurring invoice line traces to a contracted price, net of contractually valid discounts.
Requires:
Contracts; invoice line-item export
Typical finding:
A configured price that never matched the signed price.

04Discounts within their contractual term

Tests that:
Time-boxed discounts stop when the contract says they stop.
Requires:
Contracts; invoice or coupon export
Typical finding:
A first-year discount still applied in month 18.

05Minimum commits trued up

Tests that:
Where usage bills against a minimum commitment, shortfalls are trued up per the contract.
Requires:
Contracts; invoice export; usage export
Typical finding:
Metered billing below commit with no true-up invoice.

06Contracted items billed

Tests that:
Every billable item in the signed terms — one-time fees, services, overages — appears on an invoice.
Requires:
Contracts; invoice export
Typical finding:
An implementation fee in the order form absent from all invoices.

07Billing frequency and timing match the contract

Tests that:
Annual-in-advance is billed annually in advance; quarterly is billed quarterly; payment terms match.
Requires:
Contracts; invoice export
Typical finding:
An annual-in-advance contract billed quarterly in arrears.

08Credit notes have a contract basis

Tests that:
Each credit memo traces to a contractual trigger — an SLA credit, termination right, or documented concession.
Requires:
Contracts; credit note export
Typical finding:
A credit memo with no clause or documented approval behind it.

09Auto-renewals executed and billed

Tests that:
Terms that auto-renewed are actually being billed; lapsed terms with continuing service are surfaced.
Requires:
Contracts; invoice export
Typical finding:
Service continuing months past term end with no renewal invoice.

10Billed reconciles to recognized

Tests that:
Recognized revenue traces to an enforceable arrangement and delivery or usage evidence, while billing reconciles through AR, deferred revenue, and contract-asset balances.
Requires:
Invoice export; revenue schedule; AR and deferred revenue balances where available
Typical finding:
Revenue recognized with no enforceable arrangement or delivery evidence behind it.

11Revenue schedule consistent with contract terms

Tests that:
The recognition pattern matches the arrangement: ratable for subscription, as-delivered for services, as-consumed for prepaid usage — and updated after amendments in line with the modification treatment your policy and ASC 606 require. Where you have a rev-rec policy memo, observed treatment is tested against your own policy.
Requires:
Contracts; revenue schedule; rev-rec policy; delivery or usage evidence where relevant
Typical finding:
A schedule never updated after a co-term amendment.

12Usage metering reconciles to rated usage

Tests that:
Metered consumption, priced at contract rates, matches what was rated and invoiced.
Requires:
Contracts; raw usage/metering export; invoice export
Typical finding:
Rated usage below metered usage at contract rates.

How the work is done

Extraction is AI-assisted, verification is human. AI reads the contract package — MSA, order forms, amendments, side letters — and extracts the commercial terms, resolving which document governs when they conflict. A person verifies every extracted term and every finding against the source documents before anything reaches your report. A false positive in front of a controller is a failure; we treat it that way.

The math is deterministic. Once terms are confirmed, expected billing and recognition are calculated, not guessed. Every dollar figure in the report is reproducible from the confirmed terms and your exports.

Entity mapping is proposed, you confirm. Matching the customer in a contract to the customer in Stripe and the row in your revenue schedule is genuinely error-prone work. We propose the mappings; you confirm them before checks run against them.

Judgment areas are flagged, not resolved unilaterally. Standalone selling price allocation, bundled performance obligations, variable-consideration estimates, and unusual termination or acceptance provisions are identified and framed as questions for your revenue accountant or auditor — with the relevant clauses assembled — rather than answered by the scan.

Findings are classified by what they are. Dollar-quantified billing variance, revenue-treatment variance, and control exceptions are reported separately. Missing-document and hygiene issues are listed, but never dressed up as dollar findings.

See the output first

The sample report shows exactly what these checks produce.

View the sample reportRequest a scan