1. Service Description

With the change in business cases/scenarios, Customers are required to add/update validation rules for Order Matching. These updates should be backed with a verified and justified business scenario. The matching tolerance updates will adjust validation rules to match the customers desired configuration as specified in the business case.

Through this standard change request only the following validation rules will be adjusted:

• Price Difference - Header Sum Validation with Absolute Tolerance (Exceeding PO Price)
• Price Difference - Header Sum Validation with Percentage Tolerance (Exceeding PO Price)
• Price Difference - Header Sum Validation with Absolute Tolerance (Less Than PO Price)
• Price Difference - Header Sum Validation with Percentage Tolerance (Less Than PO Price)
• Price Difference - Line Sum Validation with Absolute Tolerance (Exceeding PO Price)
• Price Difference - Line Sum Validation with Percentage Tolerance (Exceeding PO Price)
• Price Difference - Line Sum Validation with Absolute Tolerance (Less Than PO Price)
• Price Difference - Line Sum Validation with Percentage Tolerance (Less Than PO Price)
• Price Difference - Unit Price Validation with Absolute Tolerance (Exceeding PO Price)
• Price Difference - Unit Price Validation with Percentage Tolerance (Exceeding PO Price)
• Price Difference - Unit Price Validation with Absolute Tolerance (Less Than PO Price)
• Price Difference - Unit Price Validation with Percentage Tolerance (Less Than PO Price)
• Price Difference - Partial Match Validation with Absolute Tolerance (Exceeding PO Total)
• Price Difference - Partial Match Validation with Percentage Tolerance (Exceeding PO Total)
• Price Difference - Partial Match Validation with Absolute Tolerance (Less Than PO Line Total)
• Price Difference - Partial Match Validation with Percentage Tolerance (Less Than PO Line Total)

Requests for adjustments to matching tolerances should be initiated by the customer with desired changes and justification.

For Basware to commence work on your order, you’ll need to provide all required information along with a valid PO or pre-authorized signature. Basware will endeavor to complete order within 2 weeks of receiving all needed information and accepting your order. This, however, requires that you provide all necessary resources, deliverable and meet the timelines agreed when your order is accepted. You’ll find more information of what you need to provide in this service catalog.

Validation of the request will be performed by a Technical Consultant. Implementation will occur in the test environment for user acceptance testing.  Post UAT approval, the updates will be applied to the production environment as per agreement with the customer.

1.1 Pre-requisites

Your order will be eligible for processing via the Service Catalog provided the request meets all the conditions specified in the checklist below. If the request does not meet all conditions, the order may be returned to you or it will be handled according to the standard Change Request process with a specified work estimate.

Service Catalog Checklist for Matching Tolerance
1	Confirmation that the spend has been authorized (e.g. a Purchase Order)
2	The request does not include changes to the current organization hierarchy.
3	No interface changes will be needed to create the tolerance updates. If any interface changes are necessary, an additional change request will be required.
4	There are no known business or technical restrictions to prevent the project objectives from being met.
5	The requested adjustments clear the validation check of the Technical Consultant. If it fails, then this request will be handled via standard change request process with specific work estimate.
6	All information provided to Basware will be accurate and approved as such by the Customer.
7	Only changes mentioned in this Service Catalog will be fulfilled as per the specified business case.  Additional consulting will require an additional change request.

Only changes mentioned in this Service Catalog will be fulfilled as per the specified business case.  Additional consulting will require an additional change request.

If the request does not meet all conditions, it may be returned to the Customer or it will be handled according to the standard Change Request process with a specified work estimate.

1,2 Deliverables (What you’ll get)

Your order will be completed and closed when the following deliverables are finalized:

• The configurations are updated with requested validation rules on both Test and Production environments.
• You’ve been live with new rules in your production environment for 1 week

In case you cancel an accepted order, or it is indefinitely delayed or by more than 3 months, Basware will close the order and invoice the work on a pro rata basis.

2. Customer Requirements

We’re committed to completing your order as soon as possible and to do this, we need you to observe all the stated requirements, including data and resources, at the stated or agreed timelines. If any requirement is incomplete, ambiguous or delayed, throughout any stage of the order, it will likely impact the delivery schedule and in some cases, result in additional costs. If you’re not ready with all needed information and resources, we recommend you to hold off placing your order until you’re ready.

2.1 When placing the order

When placing the order, we need you (the Customer) to observe the following requirements and provide all necessary information, documents and/or test data.

• A purchase order to confirm that order is authorized to proceed, unless an alternative has been otherwise agreed.
• A business case/scenario from you for which you want to define the new validation rules.

2.2 When your order is accepted

Once your order has been accepted, you’ll be informed of when the new validation rules will be configured to your test environment, the target testing period and deployment date. To facilitate this, you’ll need to ensure the following resources are assigned and available to:

	Key Task/Responsibility	Resource type	When
1	Join planning and order confirmation meeting	Customer, Basware	Order acceptance
2	Co-ordinate responses to Basware queries as they arise (SPOC)	Customer or Basware	Build and testing
3	Deploy necessary changes to customer-controlled interfaces	Basware	Build and testing
4	Review and correct any integration issues	Basware	Build and testing

2.3 When your order is accepted

Once we’ve made the change to your test environments, we’ll confirm to you that it is ready for testing. You’ll need to mobilize your team to validate that the solution and services are acting as expected. As part of this, you’ll need to ensure the following resources are assigned and available to:

	Key Task/Responsibility	Resource type	When
1	Review and correct any validation issues	Basware	User acceptance testing
2	Perform end-to-end user acceptance testing for specified business scenario	Customer	User acceptance testing
3	Report issues with collected evidence	Customer	User acceptance testing

2.4 When your order is ready for production

Once you’ve completed your acceptance testing, we’ll be ready to move your change into production. As part of this, you’ll need to ensure the following resources are assigned and available to:

	Key Task/Responsibility	Resource type	When
1	Formally sign-off user acceptance testing and confirm deployment to production	Customer	Move to production
2	Confirm production deployment date	Customer	Move to production
3	Deploy necessary changes to customer-controlled interfaces	Basware	Move to production
4	Validate successful deployment to production	Customer	Move to production

3. Delivery Process

Adding a new validation rules means making changes to several solutions and services. In some cases, there are customer-specific configurations that also need to be considered when delivering a change. 

3.1 Implementation

Basware deliverables:

• Suggest the best applicable rules complying to the customer requirements
• New rules have been configured and unit tested in all Basware P2P applications

Customer deliverables:

• Approval on the needed validation rules
• Sample files for specified business scenario

3.2 System Testing

Basware deliverables:

• Testing of the configured validation rules as per customer business scenario

Customer activities to be completed:

• Respond to queries related to configuration from Basware

3.3 User Acceptance Testing

Basware deliverables:

• Issues identified during UAT have been resolved, providing they meet the original scope of the order
• Support provided to Customer during the agreed 1-week period

Customer deliverables:

• Signed User Acceptance form, stating that the solution works as expected and is ready for production use
• Confirmed date to move changes to the production environment

3.4 Move to Production

Basware deliverables:

• Migrate changes to production environments
• Provide hypercare support for 1 week

Customer deliverables:

• Confirmation the new validation rules has been configured to production environments successfully

4. Invoicing

Basware will invoice the Customer upon accepting the order, which will occur when the service request is received, verified to meet all the requirements and conditions described and confirmed as having begun processing. Additional costs may apply if the service request is changed after it has been accepted.

5. Assumptions 

• All tasks are to be carried out during normal working hours, i.e. 9am – 5:30pm, Monday to Friday. A consulting day is to be 8 working hours, within the period defined by this assumption. Basware recognizes that the working day may need to be flexible in terms of start and finish times based on project activities and priorities. Therefore, changes in the working day start and finish time will be at the discretion of the Project Manager and consultants concerned. Time in excess of this (more than 8 hours in a day or weekend work) is subject to additional authorization and agreement between Customer and Basware.
• Customer will provide sample data when necessary.
• Customer resources will be required for testing changes and will be available during normal working hours.
• All Customer Test and Production environments are in sync.
• Where applicable, Customer will provide at least 10 invoices for testing the above changes.