I model renewals in the CRM by decoupling the contract date from when a real decision would happen. A renewal hits the books for a given month, but if there is an ongoing processor review or fee negotiation going on, payout issue, senior management change of strategy, cash flow pressure-most decision processes can accelerate.
One rule I learned to enforce is that no renewal can be count upon as credible until the decision maker, business need and time horizon have all been confirmed within 30 to 45 days. If any one of those three variables is different, then I downgrade the confidence level and will bucket it into a more conservative forecast for renewal.
That administration may be separate from the person who originally signed up for a solution, or who reviews costs, risk or account stability later in payment processing and merchant services. For example, if a merchant is facing chargebacks or concerns about their reserves, processor holds or cash flow issues, they may delay taking a decision.
The contract end date at which the forecast is based is not the solid prediction of renewal. This is the one that has high buying intent, who owns the decision with confirmation and so on; but does the merchant believe that the service is still grounded in a present-day, business need?