Use this guide in your DEV environment to confirm that users, supplier communications, purchase order data, supplier responses, buyer review, and ERP write-back work as expected. Complete every required test with your Leverage implementation team before moving to PROD.
Before you begin
Complete these prerequisites before testing:
PO Lifecycle Questions are complete and your purchase order workflows are documented.
The Integration Build Guide is complete and your ERP integration is configured.
You can create test purchase orders in your ERP.
You can access the Leverage DEV environment.
You have at least one test supplier contact.
Outbound message rules are enabled.
If any prerequisite is incomplete, work with your Leverage implementation team before continuing. Contact implementations@tryleverage.ai.
Phase 1: Prepare users and test data
1. Verify buyer users
Goal: Confirm that every required internal team member can access Leverage.
In Leverage, go to Settings → Users.
Confirm that all required buyer users are listed.
Confirm that each user has registered and can sign in to the DEV environment.
✅ Pass when: Every required team member can access Leverage in DEV.
2. Set up test suppliers
Goal: Test the supplier experience without contacting real suppliers.
Go to Suppliers.
Add a test supplier contact to a supplier record.
Assign the PO Processor role to the contact.
💡 Tip: Use a separate email account or plus addressing, such as yourname+supplier@company.com. Consider creating two or three test supplier contacts when testing multiple scenarios.
✅ Pass when: Your test supplier contacts are ready and have the PO Processor role.
3. Configure outbound message rules
Goal: Make sure automated supplier messages are configured for testing.
Configure the required rules and sending cadence.
Confirm that the rules are active and send to contacts with the PO Processor role.
✅ Pass when: The appropriate outbound rules are active for your test supplier contacts.
Phase 2: Verify PO data and communications
4. Verify purchase order data from your ERP
Goal: Confirm that the READ integration brings accurate purchase order and line data into Leverage.
Create a test purchase order in your ERP using a test supplier.
Include the line items and scenarios you need to validate, then record the PO number and expected values.
Wait for the configured synchronization cycle to complete.
In Leverage, go to Purchase Orders and open the test PO.
Verify the PO number, supplier, line items, quantities, prices, delivery dates, custom fields, and scheduled outbound messages.
⚠️ Stop if data is missing or incorrect: Contact support before continuing. The READ integration must work correctly before you test downstream workflows.
✅ Pass when: The test PO in Leverage matches the source data in your ERP.
5. Verify email delivery
Goal: Confirm that acknowledgement emails reach supplier contacts with the correct information.
Perform the action configured to trigger an outbound message, such as creating a PO or changing its status.
Check the inbox for your test supplier contact.
Confirm that the email contains the correct PO information, working links, a PO PDF, professional formatting, and the correct sender information.
⏱ Timing: Delivery depends on your configured rule cadence. If an expected message does not arrive, check the spam or junk folder and confirm that the rule is active.
💡 Tip: Open supplier links in a separate browser or private window so you do not reuse your buyer session.
✅ Pass when: The supplier receives a complete, accurate email and every link works.
6. Verify the PO PDF
Goal: Confirm that the attached PDF contains all required purchase order information.
Open the email from the previous test.
Download and review the attached PO PDF.
Confirm that it includes your company branding, complete PO header, line descriptions, quantities, unit prices, delivery or expected dates, applicable terms and conditions, required custom fields, and readable formatting.
⚠️ If information is missing: Document the missing content and contact support to request a PDF template adjustment.
✅ Pass when: The PDF is accurate, complete, and easy for the supplier to read.
Phase 3: Verify supplier and buyer workflows
7. Test supplier response actions
Goal: Confirm that suppliers can respond to purchase orders correctly.
Open the supplier response link from the test email in a separate browser or private window.
Acknowledge one test PO as-is and confirm that a success message appears.
Use a new test PO to submit a line-price change with justification notes.
Use another test PO to submit a promise-date change with notes.
Use another test PO to submit a quantity change with justification.
✅ Pass when: Each supplier action submits successfully and displays a confirmation.
8. Test the buyer review process
Goal: Confirm that buyer users can review and resolve supplier changes.
Sign in to Leverage as a buyer user.
Open Needs Review.
Locate the changes submitted during the supplier tests.
For each change, confirm that the original and new values and the supplier notes are clear.
Test both approving and rejecting changes, including rejection comments.
Confirm that the status updates correctly after each action.
✅ Pass when: Buyers can understand, approve, or reject every submitted change and the status updates correctly.
9. Verify write-back to your ERP
Goal: Confirm that supplier acknowledgements and approved changes return to your ERP as configured.
For acknowledgements:
Locate a PO acknowledged during the supplier test.
In your ERP, confirm that the PO status and acknowledgement data were updated.
Verify the configured promise or due date, quantity, and unit cost fields.
For approved changes:
Locate a supplier change approved during buyer review.
In your ERP, confirm that the approved price, date, or quantity is reflected on the PO.
Confirm that applicable history or notes were recorded.
⏱ Timing: Write-back timing depends on your integration configuration and synchronization frequency.
⚠️ Do not move to PROD if write-back fails: Contact support immediately.
✅ Pass when: Acknowledgements and approved changes appear correctly in your ERP.
Phase 4: Test your unique workflows
The tests above cover core functionality. Before go-live, also validate the workflows, business rules, and edge cases identified during your PO lifecycle discussions.
Consider testing:
Multi-level approvals, thresholds, and department-specific routing.
Blanket POs, standing orders, drop-ship arrangements, and consignment inventory.
Special supplier terms, pricing agreements, or communication requirements.
Industry-specific compliance, certifications, or lot tracking.
Cancellations, split shipments, partial deliveries, and emergency changes.
High-volume processing and connections to other business systems.
Define the expected result for each scenario, involve the appropriate buyers and stakeholders, and test the most critical workflows first. Run these tests after the core guide and before using real suppliers in PROD.
Go-live checklist
Before moving to production, confirm that:
All required buyer users can access Leverage.
Test POs appear in Leverage with accurate data.
Supplier emails are delivered reliably.
PO PDFs contain the required information.
Suppliers can acknowledge POs and submit price, date, and quantity changes.
Buyers can approve and reject supplier changes.
Acknowledgements and approved changes write back to your ERP.
Your organization-specific workflows pass testing.
Your team is trained on the new process.
Next steps
Document any issues found during testing.
Complete final configuration adjustments.
Schedule the go-live date with your team.
Prepare supplier communications and any supplier training or town halls.
Confirm the move from DEV to PROD with your Leverage implementation team.
Troubleshooting
The PO is missing or inaccurate: Stop testing and contact support. Do not continue until the READ integration is correct.
The supplier email did not arrive: Check the rule cadence, confirm the rule is active, verify the PO Processor role, and check spam or junk folders.
The PO PDF is incomplete: Document the missing fields or formatting and contact support for a template adjustment.
ERP write-back failed: Do not move to PROD. Contact support immediately.
Need help?
Contact the Leverage Help Desk or email support@tryleverage.ai.