Every amendment a new version of the contract
Contract Modifications brings each add-on order in as a new version of the contract and sends it back through review.
ASC 606 contract modifications one version at a time
New orders from Salesforce caught
When Salesforce brings an add-on order for an approved contract, Finrep flags it on that contract with the opportunity, its close date and its files.
- Add-on orders flagged on the contract.
- Opportunity, date and files shown.
Company A · Platform renewal
Version 1Overview
Revenue treatment
Checklist
You decide how the order is treated
The preparer adds the order as an amendment, treats it as a separate contract or discards it, so a person makes the judgment the standard calls for.
- Add as amendment or separate contract.
- Only on an approved contract.
MSPreparer
A new version the old one kept
An amendment creates a new version of the contract, dated to the order's close date. Facts, obligations and checklist answers carry over, and the modification items on the checklist reopen for review.
- Every version kept and selectable.
- Modification checklist items reopened.
Company A · Platform renewal
Version 2The current version and its decisions stay in history. The new draft needs fresh confirmations.
Re-approved before it counts
The new version returns to the preparer, runs through the five steps again and goes up the approval route, so no modification takes effect without its approvers.
- Analysis re-run on the new version.
- Re-approved by value band.
Review
Version 23 levelsChecklist
Separate prospective or catch-up
Fina classifies each modification as a separate contract, prospective or cumulative catch-up, splits mixed ones, and the schedule is rebuilt with a delta journal entry drafted.
- The three treatments, with mixed cases split.
- A delta entry from the version change.
More in Revenue Recognition Automation
AI Contract Review
Bring contracts in from Salesforce or as PDFs, typed and summarised for ASC 606 review.
Explore →Cited ASC 606 Analysis
Fina works the five steps and the checklist from the contract, each fact cited to the Codification.
Explore →Review & Sign-off
Route each contract to reviewers by TCV or MRR, with section sign-off and a read-only auditor role.
Explore →
FAQs
A contract modification is a change in the scope or price, or both, of a contract that the parties approve (ASC 606-10-25-10), such as an amendment, change order or upsell. Contract Modifications brings each one into Finrep as a new version of the contract.
A modification is a separate contract when it adds distinct goods or services at their standalone selling prices (ASC 606-10-25-12). Otherwise it's prospective if the remaining goods or services are distinct, or a cumulative catch-up if they aren't (ASC 606-10-25-13). In Contract Modifications today, the preparer decides between an amendment and a separate contract.
Contract Modifications picks up add-on orders that Salesforce brings for an approved contract, and shows each one on that contract with its opportunity, close date and files for the preparer to act on.
Contract Modifications keeps it. An amendment creates a new version dated to the order's close date, and every earlier version stays on the contract, so you can open the analysis as it stood before the change.
Yes. In Contract Modifications, the new version returns to the preparer, the five steps run again, and it goes up the approval route for its value band before the change takes effect.
No. Finrep never uses your data to train models. Contracts you use with Contract Modifications 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.


