SharePoint
Document management and intranet for operational files
ProPay integrates with SharePoint for storing integration documentation and deployment artifacts, not claims data. SharePoint is document management and intranet software many operators already use to store internal documentation and vendor files. It's a coordination layer around ProPay's integration and exceptions, not a claims channel.
SharePoint is document management and intranet software many operators already use to store internal documentation and vendor files. This isn’t where claim data lives, SharePoint is where your team coordinates around ProPay: storing integration documentation and deployment artifacts.
What ProPay does with SharePoint
During deployment, your Forward Deployed Engineer can store field-mapping documentation, connector specs, and other integration artifacts directly in a SharePoint site your team already uses, rather than a separate document store.
Nothing about claim data, parts sourcing, or payment execution routes through SharePoint. It’s purely operational, the coordination layer around the integration and around exceptions that need a person’s attention, not a channel for claim records themselves.
How the SharePoint connection works
Deployment documentation is stored in a SharePoint location your team designates during onboarding.
This is set up once, early in deployment, alongside the rest of the SharePoint configuration your team already maintains, it isn’t a separate ongoing integration to manage.
What stays in SharePoint
SharePoint continues to run exactly as it does for every other team and project already inside it. ProPay adds one more source of notifications or tracked work, using the structure your team has already built.
Data handling and security
Anything ProPay posts into SharePoint, an escalation, a deployment update, is a notification about activity happening on your company-specific ProPay instance, not a copy of underlying claim or customer data. ProPay is SOC 2 compliant, with both Type I and Type II audits complete.
The claim recommendations behind any escalation posted to SharePoint carry their own confidence level and audit trail inside ProPay, independent of whatever your team tracks in SharePoint.
Setting this up
A dedicated Forward Deployed Engineer sets up the SharePoint connection early in deployment, working with whoever on your team owns that workspace.
Frequently asked questions about ProPay and SharePoint
Does claim data flow into SharePoint?
No. SharePoint is used for operational coordination, escalations, deployment tracking, documentation, not claim, parts, or payment data.
How does ProPay connect to SharePoint?
Deployment documentation is stored in a SharePoint location your team designates during onboarding.
Is SharePoint required to use ProPay?
No. SharePoint is an optional coordination layer some clients use during deployment and ongoing operation; it isn’t required for ProPay’s core claims functionality.
