The right reviewer for every contract
Review & Sign-off routes each contract from preparer to L2 and L3 reviewers by TCV or MRR, then locks the approved version.
Contract approval by value from preparer to L3
Route by TCV or MRR
Set value bands by TCV or MRR. L1 is the preparer, and each band names the reviewers from L2 up, so every contract gets the level of review its value calls for.
- Bands by TCV or MRR.
- Reviewers named per level.
Approval routing
Add bandSet review levels by TCV and currency.
StandardActive
LargeActive
StrategicActive
Nothing goes to review half-done
A contract can go to review only when steps 1 to 5 are confirmed, the allocation balances, the checklist is confirmed and every section is marked prepared.
- Four checks before submit.
- Balanced allocation required.
Submit for L2 review
The approval route and reviewer pools are frozen for this submission.
Approve request a revision or send it back
Reviewers approve their level, request a revision with a note that stays in history, or return the contract to an earlier level. Final approval locks the version.
- Request revision or return to a level.
- Final approval locks the version.
Request revision
Tell the preparer what to revise. This submission stays in history.
Step 4 uses last year's SSP for onboarding. Please re-run it on policy version 3.
Schedule entries checklist and memo each signed
Each section is marked prepared and then reviewed, and an edit after review shows as changed since review, so nothing slips past a reviewer.
- Prepared, then reviewed.
- Changes since review flagged.
All areas signed off
Approved| Area | Prepared | Reviewed (L3) |
|---|---|---|
| Revenue schedule | ||
| Journal entries | ||
| Checklist | ||
| Technical memo |
Final approval locks this version.
Every review waiting and a seat for your auditor
Reviewers work from an inbox of what needs them or was flagged for them, and auditors get a read-only role that can't be combined with any other.
- Needs your review and Flagged for you.
- Read-only auditor role.
Inbox
Needs your review2Flagged for youMore in Revenue Recognition Automation
Cited ASC 606 Analysis
Fina works the five steps and the checklist from the contract, each fact cited to the Codification.
Explore →Revenue Schedules & Suggested JEs
Monthly revenue by obligation and draft journal entries, signed off and exported to CSV.
Explore →Internal Controls
Check every contract against 41 revenue controls, with exceptions, attestations and kept reports.
Explore →
FAQs
Review & Sign-off routes each contract by its value. You set bands by TCV or MRR, L1 is the preparer, and each band names the reviewers at L2 and above. One reviewer approves at each required level.
In Review & Sign-off, a contract can be submitted only when steps 1 to 5 are confirmed, the allocation balances, the checklist is confirmed and every section is marked prepared.
A reviewer in Review & Sign-off approves their level, requests a revision with a note that stays in the contract's history, or returns the contract to an earlier level. Final approval locks that version.
Review & Sign-off covers the schedule, the journal entries, the checklist and the technical memo. Each is marked prepared and then reviewed, and an edit after review is flagged as changed since review.
Yes. Review & Sign-off includes an auditor role that is read-only and can't be combined with any other role, so your auditor can review contracts without being able to change them.
No. Finrep never uses your data to train models. Contracts you use with Review & Sign-off are processed only to serve your requests, encrypted with AES-256 at rest and TLS 1.3 in transit, and Finrep holds SOC 2 Type II and ISO 27001 certifications.


