A document’s signature date, effective date, receipt date and implementation date answer different questions. Check which one triggers the payment term, then test immediately before, on and after that date.
Write a small timeline
Record when the document was signed, when it was received, when the terms apply and when the operational change was made. Use those fields to distinguish a late implementation from a different contractual trigger.
If the terms are retroactive, an earlier service may need later review. Do not erase the earlier calculation or pretend the team knew a document before it received it. Preserve what was known and what was subsequently established.
Test both the date and the scope
Boundary tests should hold the service, product, provider, location and other inputs constant. Otherwise a changed result may be caused by a different reference or exception rather than the date.
A fee schedule has its own version and effective period. Record both. A broad year label or the date a file was downloaded is not enough to establish which services it covers. See how to identify a fee schedule.
Treat gaps and overlaps as questions
An old schedule ending on one date and a new one starting later can leave a gap. Two amendments with overlapping scope can leave a conflict. The safe output is a review question, not a nearest-date guess.
Document the resolution and re-run the relevant checks. For partial changes, keep a test that confirms unaffected terms are still unchanged.
Test three dates around the change
Illustrative example.
| Date in worked example | Rule | Result for $100 reference |
|---|---|---|
| Day before the effective date | Old 100% rule | $100 |
| Effective date | New 108% rule | $108 |
| Day after the effective date | New 108% rule | $108 |
This example assumes that the rule expressly uses the service date. The $100 reference and 108% multiplier illustrate this example. If the system still returns $100 on the effective date, the test identifies a difference to investigate—not its cause.
Date errors to check
- Using signature date as the trigger without reading the term.
- Applying a current schedule to historical services automatically.
- Testing only a date far after the change.
- Overwriting old evidence when a retroactive document arrives.
Build the date record
- List the dates and what each means.
- Confirm the actual trigger for the rule.
- Test the day before, day of and day after.
- Retain old and new results with their source versions.
Keep reading
Sources
Apply the agreement and records relevant to your review. Examples explain the method; they do not determine a payment obligation.
Need a term or calculation explained?
Read an answer or send a general question about the step you are working on.
Calculator values are not attached. Leave out patient and confidential information.