What it means
A customer adds services, changes a delivery date or agrees to a price reduction, and if sales, delivery and finance hold different contract versions, billing and revenue can diverge. Revenue contract change log completeness checks whether material modifications are recorded with enough evidence to update operational and accounting records.
ICAEW discusses accounting for modifications under IFRS 15 and Deloitte explains contract modifications under US revenue guidance, which show why approved scope and price matter, but the completeness measure itself is a management control. Identify the contract with a stable contract and customer identifier so amendments cannot be attached to the wrong account, and define a change broadly enough to cover scope, price, timing, acceptance, payment and termination rights.
A signed amendment, customer-approved change order or another enforceable agreement can create a new version, while an internal proposal remains pending, and work that begins before paperwork is complete should be logged as a risk without pretending the proposed amount is already agreed. Record both the signing date and the effective date, since they can differ and both matter for billing and performance.
Preserve old terms so a reviewer can explain changes rather than seeing only the latest PDF, and record the approval by identifying the authorised parties and evidence, because a sales note saying "customer is fine" may not satisfy the contract's amendment process. Link the new fixed amount, unit rates, discounts or variable consideration, flagging any unpriced change, and link the scope so delivery teams know which work was added, removed or changed.
Check currency, tax and customer deposits too, because cross-border services may introduce new local treatment and a modified term may change how advances are applied or deferred. Update billing, since invoice schedules, purchase-order references and credit notes may need revision, and update revenue analysis, because contract modifications can be separate contracts or affect remaining obligations under applicable standards and need qualified accounting review.
An approved amendment without a billing update is operationally incomplete even if the log row exists, and added work can change cost-to-complete and margin, so project forecasts should be updated after approval. Check termination changes as well, since a revised exit right can change risk and remaining consideration, and material cases should go to specialists.
Define completeness as every qualifying modification in the source population having a log row with required fields and linked evidence, and sample from outside the log because testing only logged entries cannot find omitted changes. Compare signed documents, CRM notes and project records, count a duplicate version stored in two folders once, and do not collapse different changes into one.
Use a clear status, such as proposed, approved, effective, implemented and superseded, and assign owners so legal or commercial teams capture the agreement, delivery confirms scope and finance confirms accounting and billing updates. Report a rate carefully, since a simple percentage of complete logs needs a reliable total population, including changes discovered outside the system, and preserve an audit trail of who entered and reviewed each change, when and why.
Keep contract prices and customer information confidential and shared only with authorised teams. For an owner, log completeness is the assurance that a changed customer promise reaches sales, delivery, billing and finance together, and a beautiful log that misses signed changes is not complete.
In practice
Real-world examples.
Example
A signed service upgrade is logged with price, start date and revised billing schedule. The sales, delivery and finance teams all see the same version. The first invoice at the new rate is checked against the log entry.
Example
A project team performs added work while the amendment remains unsigned, so the log marks it pending. The entry shows the proposed value but does not treat it as agreed consideration. The commercial team is asked to obtain the signature before more work proceeds.
Example
An audit samples signed amendments outside the log and finds one omitted entry. The amendment was filed in a shared folder but never reached the contract team. Finance adds the entry and checks whether billing was affected.
Formula
Calculation
Illustrative completeness rate = independently identified qualifying contract changes with all required log fields and downstream links / all independently identified qualifying changes x 100
Worked example. An auditor independently identifies 50 signed qualifying amendments from legal files, CRM notes and project records.
- 48 have a log row with all required fields and links to billing, so the completeness rate = 48 / 50 x 100 = 96%.
- The two exceptions are one amendment missing from the log and one logged amendment with no billing link; both are identified and assigned for correction.
- A test of the log alone would have covered only its 49 rows, of which 48 are complete, and would have shown 48 / 49 x 100 = about 98%, which hides the omitted amendment.Case study
Seen in the real world.
This entirely fictional example follows Harbor Analytics. Sales agreed to a customer upgrade, but the billing schedule stayed at the old rate. A cross-check of signed amendments against the change log found the missing entry. Finance corrected the invoice process and separately assessed the amendment's accounting treatment.
The case does not determine IFRS or US GAAP revenue recognition for a real contract. The upgrade added $2,000 a month, and the old rate had been billed for three months, so $6,000 of billing was missing. The team added a monthly check that compares signed amendments with the log and the billing schedule, so a similar gap would be found within one billing cycle.
Watch out
Common mistakes.
- Testing only logged amendments and calling the population complete.
- Treating an informal proposal as an approved enforceable price change.
- Saving a signed document without updating billing and delivery records.
Questions
People also ask.
What sources should be compared?
Signed documents, approved changes, CRM and project records, plus the log itself.
Does every change alter revenue recognition?
Not necessarily. Apply the relevant standard and contract-specific analysis.
What if scope is agreed but price is not?
Keep the item visible as unresolved and avoid inventing approved consideration.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%