PaperSave, Webiplex Docupeak, and Paramount Workplace are now part of PairSoft

 Statement of Work

Introduction

This statement of work (“SOW”) describes the approach PairSoft and Client will follow to implement PaperSave with invoice processing to support Client’s accounts payable processes. The implementation will be done with a prefabricated workflow template that cannot be modified, and it will be directly integrated with the Client’s Blackbaud RE NXT and FE NXT application using Sky API.

Scope

ServiceDescription
PairSoft application software
  • PaperSave 7 for FE NXT with Sky API
  • PaperSave 7 for RE NXT with Sky API
  • PaperSave Native OCR
  • PaperSave Auto Entry
  • PaperSave Invoice Processing
Configuration of standard workflows and Auto Entry
  • One Invoice Processing workflow template
    (Client selects one of two standard versions)
    • Workflow is unchanged
    • Unlimited reviewers
    • Unlimited approval thresholds and approvers
    • One company
    • Three drop points (scan, email, drag & drop)
  • One workflow with no check deposit
    • Workflow is PairSoft’s gift capture workflow template
    • One workflow drop point to be used for scanning or capturing already scanned or electronic gift documentation
PaperSave Native OCR
  • Out-of-the-box using the standard, unmodified North American invoice template (see supported fields for each workflow in User Guide)
Auto Entry
  • To be used in the workflow described above
  • For profile fields supported out-of-the-box, refer to documentation
SmartForm (if licensed; see ATP)
  • One standard, prefabricated template

Project Overview and Responsibilities

MILESTONE 1: Preparation & LaunchPairsoftClient
Conduct technical planning meeting

  • Review the implementation process and scope of work in detail
  • Review the previously submitted prerequisite documentation
  • Review the PaperSave 7 deployment whitepaper
  • Create the project timeline
  • Provide answers to questions
✓
Installation/provisioning of PaperSave 7 for RE NXT and FE NXT with Sky API Auto Entry and OCR modules✓
Test PaperSave components

  • Native OCR, Auto Entry, and may include SmartForm
✓✓
Client sets up scanner per validation recommendations outlined in Documentation✓
Activate ‘PaperSave 7 by PairSoft’✓
Client will grant environmental access for PairSoft to the ERP environment; Client will also create a supervisory user within the ERP system.✓
MILESTONE 2: Software SetupPairsoftClient
Deploy and test the workflow template✓
Conduct one interactive walk through of template deployment✓✓
MILESTONE 3: Train & TestPairsoftClient
Conduct remote trainings (approximately 4 hours)

  • PaperSave Essentials, PaperSave Native OCR, Workflow end-user, and Administrator
✓
Conduct User Acceptance Testing (UAT)

  • Only test documents should be processed in PaperSave during this phase
  • UAT serves to validate the configuration and enhance the understanding of the Solution
✓
Complete the testing plan and report any defects to PairSoft within 5 business days

  • During the UAT process, it is possible that new PaperSave product defects may be exposed or known product defects encountered. If a workaround is implemented by PairSoft, the defect will not delay the acceptance of the application.
✓
Provide support to UAT users

  • PairSoft will monitor the UAT process to answer questions and resolve issues
  • PairSoft will implement any necessary workarounds
✓
MILESTONE 4: Go-LivePairsoftClient
Remove test items and Go-live✓✓
Provide hypercare support (for up to 2 weeks)

  • The Project team will conduct an introduction to support call
✓
Deliver Project Closure and Support Transition Document

  • The document will provide transition resources and instructions to utilize PairSoft’s PaperSave customer support organization, as well as the PairSoft client portal
✓

Acceptance: If PairSoft does not receive timely written notification within five (5) days of any defects during the UAT, the project shall be deemed accepted. If the application is placed into production and invoices are being processed, the project shall be deemed accepted and will be closed.

Project Governance

Changes

If the parties agree to any changes to this SOW, they shall execute an amendment to this SOW effecting such changes (“SOW Amendment“). No additions or other changes to this SOW shall be effective unless such changes are in writing and signed by both parties in the form of a SOW Amendment.

Out of Scope

Any services and/or activities not listed in the tables above are out of scope and excluded from the Professional Services project.

Assumptions

The client shall provide PairSoft with all information relevant to the services to be performed and shall cooperate and provide PairSoft with all assistance as may be required for PairSoft to perform the services. Client grants PairSoft employees’ access to their data and environment to provide the scoped solutions outlined in the SOW.

Exclusions of PairSoft Responsibility

  • Installation and / or configuration of third-party products including but not limited to Microsoft Office and SharePoint
  • Hardware procurement or licensing
  • Configuration of any hardware components including desktop and multi-function scanners
  • Network configuration or troubleshooting, including permissions for file sharing or access
  • Support for users across multiple domains
  • Development of Client specific documentation such as Client test plans, implementation plans, custom Client training materials, and Client specific system documentation
  • Weekend work or after-hour deployments are excluded from the delivery methodology