These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Vendor Payment Portal
- Data model
The tables behind Vendor Payment Portal
Vendor Payment Portal ships with 19 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 19
- Features
- 6
- Change it
- Add fields and tables in Proto
How the model is organised
Supplier access
Buyer entities, Vendors, Users and portal memberships. Define the authenticated person, supplier and buyer relationship for each request.
Invoice submissions
Invoice submissions, submission lines and integration receipts. Retain the submitted document, its lines and the actual buyer handoff response.
Payment visibility
Invoice status snapshots, payment snapshots, payment allocations and remittance documents. Keep invoice balances, payment outcomes and allocations with their source observation and protected remittance.
Early payment offers
Discount offers and discount acceptances. Separate the supplier’s decision from the buyer’s reservation and observed settlement.
Payment profiles
Payee profiles and payment detail requests. Preserve the current verified destination while a proposed change passes independent verification and AP application.
Supplier support
Support cases, case messages, document attachments and notification deliveries. Keep the owner, reader visibility and delivery evidence with the supplier’s question.
Every table, by feature
- Supplier access4
- Invoice submission4
- Invoice and payment status5
- Early payment offers5
- Payment detail changes4
- Supplier support and reporting6
- Users
Authenticated internal or supplier principals; display names never grant authority.
- Vendors
Approved supplier identity imported from the authorised payable system.
Linked to Buyer entities - Buyer entities
The payable-owning legal entity behind every portal relationship.
- Portal memberships
Explicit user, vendor and buyer access grant with expiry and revocation.
Linked to Users, Vendors, Buyer entities
- Invoice submissions
Supplier-submitted document awaiting the actual AP acceptance and approval outcome.
Linked to Vendors, Buyer entities, Users - Submission lines
Supplier line evidence; portal validates arithmetic without granting AP approval.
Linked to Invoice submissions - Document attachments
Document ownership and malware/access gate independent of shared storage URLs.
Linked to Vendors, Buyer entities, Invoice submissions, Support cases - Integration receipts
Verified and deduplicated source response for AP invoices, payments and instruction outcomes.
Linked to Buyer entities
- Invoice status snapshots
Verified observed payable status and balance from the owning AP system.
Linked to Vendors, Buyer entities - Payment snapshots
Observed payment instruction and settlement information from authorised buyer sources.
Linked to Vendors, Buyer entities - Payment allocations
Observed source allocation connecting a payment to the invoice it pays.
Linked to Payment snapshots - Remittance documents
Buyer-provided remittance artifact with protected vendor access.
Linked to Payment snapshots, Vendors - Integration receipts
Verified and deduplicated source response for AP invoices, payments and instruction outcomes.
Linked to Buyer entities
- Discount offers
Buyer-approved early-payment offer bound to a current invoice balance and expiry.
Linked to Vendors, Buyer entities, Users - Discount acceptances
Supplier decision and acknowledged buyer reservation; acceptance alone does not settle money.
Linked to Discount offers, Vendors, Users - Invoice status snapshots
Verified observed payable status and balance from the owning AP system.
Linked to Vendors, Buyer entities - Payment snapshots
Observed payment instruction and settlement information from authorised buyer sources.
Linked to Vendors, Buyer entities - Payment allocations
Observed source allocation connecting a payment to the invoice it pays.
Linked to Payment snapshots
- Payee profiles
AP-owned verified payment destination references; portal exposes only masked values.
Linked to Vendors, Buyer entities - Payment detail requests
Supplier request to change payment details, subject to independent identity verification and AP application.
Linked to Vendors, Buyer entities, Payee profiles, Users - Portal memberships
Explicit user, vendor and buyer access grant with expiry and revocation.
Linked to Users, Vendors, Buyer entities - Integration receipts
Verified and deduplicated source response for AP invoices, payments and instruction outcomes.
Linked to Buyer entities
- Support cases
Vendor-scoped invoice and payment questions with assigned buyer ownership.
Linked to Vendors, Buyer entities, Users - Case messages
Retained conversation with explicit internal-note versus vendor-visible access.
Linked to Support cases, Users - Document attachments
Document ownership and malware/access gate independent of shared storage URLs.
Linked to Vendors, Buyer entities, Invoice submissions, Support cases - Notification deliveries
Scoped notice identity and observed provider delivery outcome.
Linked to Vendors, Users - Invoice status snapshots
Verified observed payable status and balance from the owning AP system.
Linked to Vendors, Buyer entities - Payment snapshots
Observed payment instruction and settlement information from authorised buyer sources.
Linked to Vendors, Buyer entities
Keys and references
Every context resolves the same buyer and vendor. Keep source invoice/payment identities, source revisions, provider event keys and content digests. Exactly one context owns an uploaded attachment. Snapshot history remains retained while is current identifies the latest reconciled result.
Migration order
- Reconcile buyer entities and approved supplier identities with AP.
- Verify internal principals and supplier memberships.
- Import current invoice/payment observations without sending new instructions.
- Reconcile protected remittance and active payee profiles.
- Enable reviewed offers, requests and support after access and integration tests.
Set up Vendor Payment Portal your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.