Network Portal extends your ERP’s customer and invoice data into a secure, self-service experience for your customers. It does not replace your ERP or create independent records. Instead, it reflects and acts on the data that already exists in your ERP and is synced through Paystand.
At a Glance
At a high level, the data flow works like this:
→ ERP customer and invoice data
→ Synced through Paystand
→ Displayed in Network Portal
→ Payment processed through Checkout
→ Payment status synced back to ERP
Customer Records and Payer Visibility
Network Portal uses the email address defined in your ERP to determine which customer records a payer can access.
What This Means
- Access is tied to the email address defined on ERP customer records.
- If the same email is present on multiple customer records, that user can access all eligible records associated with that email.
- Invoices are grouped and displayed based on the customer records linked to that email address.
This allows a single user to access invoices across multiple related customer records without needing separate accounts for each one.
How Access Is Determined
Access to Network Portal is driven by ERP contact data.
| Access Rule | What It Means |
|---|---|
| Email match required | The user’s email must match the primary contact email on at least one ERP customer record. |
| ERP setup controls access | If the email is not configured correctly in the ERP, the user will not be able to activate access. |
| Visibility is email-based | Once access is granted, users can see invoices tied to all eligible ERP customer records associated with that email. |
Invoice and Transaction Visibility
Network Portal displays invoice and transaction data that is synced through Paystand.
Key Principles
- Users can view invoices associated with all ERP customer records linked to their email address.
- Invoice status updates such as paid or cancelled originate from ERP data and payment events.
- Transactions processed outside of Paystand are not displayed in the Portal.
- Visibility still depends on ERP structure, sync status, and connected subsidiaries.
Considerations
Network Portal is structurally dependent on how customer records, subsidiaries, and contacts are configured in your ERP. Incorrect or inconsistent ERP data will result in incorrect or limited visibility in the Portal.
Important
Before making structural changes to customer records, subsidiaries, or contact assignments, consult your Implementation team or Customer Success Manager to avoid unintended access or visibility issues.
Treat Network Portal as a customer-facing reflection of your ERP structure. Clean ERP contact setup leads to clean Portal visibility. Messy ERP setup does the opposite.