Postver / Deployment guide
Deployment guide
A checklist for
self-hosted procurement.
Before deployment, agree where data lives, which systems can access it, who approves decisions and who operates the installation. Review database, documents, identity, AI, ERP connectivity and recovery together.
1. Map the data destinations
List the database, invoice documents, mailbox, identity provider, AI route and backup storage. Name the environment and country where each is operated, and the owner responsible for it.
In Postver, the data-destination view declares the configured destinations. A new destination requires a second person’s approval before information flows to it. Read the deployment overview.
2. Agree identity and decision rights
Review your identity provider, SSO and SCIM setup, the entities each person can access, and the people responsible for invoice review and approval.
Keep preparation and approval separate for payment runs. Review how rules move through draft, test, review and publication, and who can approve a configuration change. In Postver, nobody approves their own rule change.
3. Review the AI route explicitly
Ask which model receives each request and where that model runs. Check the configured route and data destination rather than assuming that self-hosting automatically makes every connected service local.
Postver supports a private model route on your servers. Each suggestion identifies its model and the destination of the data it used. AI suggestions and approval decisions remain separate.
4. Keep system ownership clear
Agree which system owns purchase orders, bills and payment evidence, and review the access required for each connection. Postver can read Coupa purchase orders while NetSuite remains the ERP for bill posting and payment records.
Test the difference between a successful request and a confirmed financial record. Include an interrupted ERP connection in the walkthrough: an unknown outcome needs reconciliation, rather than an automatic second posting. Review the NetSuite and Coupa workflows with the relevant system owners.
5. Plan operation, recovery and total cost
Assign responsibility for infrastructure operation, access reviews, backups and recovery checks. Agree how your team will check the freshness of recovery points and inspect the audit record.
Budget for your configured infrastructure and services alongside the software quote. Postver offers per-invoice pricing or a flat annual software fee with unlimited invoices; both have no per-seat fees. Compare the pricing models using the same invoice volumes and deployment scope.
Bring IT, security, finance and procurement together before sign-off. Use the checklist to name owners and unresolved questions, then test a representative invoice workflow in the intended environment.
Self-hosted deployment questions
Does self-hosting remove the need to review connected services?
No. Review the destinations and access of the services you configure, including AI, mail, identity, storage and ERP connections.
Where does data residency come from?
Residency follows the installation and configured destinations. Review each destination with your infrastructure and security owners.
What should we bring to a deployment walkthrough?
Bring your entities, ERP and purchasing systems, identity provider, planned storage and AI route, recovery expectations and approval policy.
Review the boundaries before you install
Walk through your data destinations and responsibilities with the Postver team.