>

Contract Report for multi-year Events

Comments

3 comments

Date Votes
  • Seth Halvaksz

    Minka Verkaar i don't think Rich will be able to answer a best practice question. I'm tagging Martin Stephens in case he can help, he's the expert on best practices for reporting.

  • Martin Stephens

    I haven’t encountered a scenario where contract reporting needs to span multiple events.  From what I understand, the requirement (enhancement request) is to create a contract at the account level and link it to multiple events, allowing consolidation of orders from multiple events under one contract. 

         “One ‘ring’ to rule them all and in the darkness bind them”..  :-)

    The only workaround I can think of is creating a “Master” event (in addition to the individual events) that aggregates order information across all years and attaching a Master Contract to it.  However, this approach is far from ideal—any changes to order details on related events would also need to be updated on the master event to keep the contract (and potentially payment schedules) accurate.  This approach would keep your individual events intact for fiscal year closing but would result in additional work to manage the contract.  

    Enhancements to Contract Group reporting might help, but this still involves multiple contracts across events. We’d have to assume clauses are built consistently across events, which may not always be true. This is why I believe account-level contracts would be the most effective solution.

    It might be possible to build a Crystal Report that consolidates contracts across multiple events by connecting events through Event Seasons or Contract Groups. However, this would be complex and still subject to the same issue of potential deviations in contract details.

  • Minka Verkaar

    Thanks Martin Stephens for the background. I have enough information to go back to the customer. 

Please sign in to leave a comment.