Remizen + Zip Integration
Bring request and approval context to employee-expense reviews for a fuller view of company spend.
This describes a possible workflow, not an active or official connection.
Connect Remizen with Zip
Zip is used for purchasing and supplier processes. Consider intake and approval context when assessing new spend. Any connection would need to be designed, validated, and made available before teams could use it.
Expense management with Zip
For organizations that use Zip, a potential workflow could focus on comparing purchase approvals with the resulting spend. The right approach depends on the records available, your internal policies, and how your team reviews spending today.
How it works
- Scope a proposed Zip use case with the people who review spending: Could retain requestor and business-purpose context.
- Plan how to could distinguish intake approvals from expense approvals using the relevant supplier records, purchase orders, invoice references, and approvals, and decide who would own each handoff.
- Before implementation, validate the proposed process to could organize expense exceptions for finance follow-up against your approval policies.
Workflows
- Could retain requestor and business-purpose context
- Could distinguish intake approvals from expense approvals
- Could organize expense exceptions for finance follow-up
Data and workflow considerations
- Review supplier records, purchase orders, invoice references, and approvals before defining a Zip workflow.
- Determine whether Zip data needed for comparing purchase approvals with the resulting spend may be shared, and how long it should be retained.
- Test exceptions and manual review paths before relying on any proposed connection.