Esker vs Zip

Requirement evaluated: Budget data pulled from NetSuite for real-time budget enforcement

For a $250M technology company moving off spreadsheet-based purchasing and looking to enforce budget discipline, Esker's Procurement module (part of its Source-to-Pay suite) explicitly addresses real-time budget follow-up during the requisition and approval workflow. Esker's own product pages state that its e-procurement software 'steps up to the challenge' of real-time budget tracking, and approval workflows are designed to confirm that 'spend is within the agreed-upon budget' before a request advances. …

Limitations: The key gap for this buyer is source-of-truth clarity: Esker's documentation confirms real-time budget enforcement within its own procurement workflow and a pre-built NetSuite connector, but does not explicitly document that NetSuite budget data is the live, upstream input driving Esker's enforcement. …

Requirement evaluated: Budget data pulled from NetSuite for real-time budget enforcement

For a $250M technology company currently creating POs manually in NetSuite with no upstream budget gate, Zip addresses this at the intake stage, before any commitment is made. When an employee submits a purchase request through Zip's intake portal, the platform checks the requested amount against budget data pulled from NetSuite before routing for approval. Zip's named 'Advanced Budgets' feature is documented as catching overspend before approvals happen, alerting teams before budget exhaustion and providing PO balance alerts prior to commitment. …

Limitations: Public documentation does not specify whether Zip's budget enforcement reads NetSuite's native budget periods and department/class/subsidiary dimensions directly or requires those budgets to be re-entered manually in Zip's own budget module; the buyer should confirm during a demo that NetSuite budget records (not just …

Requirement evaluated: Configurable retention policies aligned with our 7-year record retention requirement

For a $250M technology company requiring 7-year procurement record retention, Esker provides a native cloud document archive that automatically captures and stores invoice images, PO data, and workflow history at the conclusion of each transaction. As documented on Esker's AP solution page, 'once validated, invoice data is transferred into the ERP, while the invoice and workflow history are archived and remain accessible for traceability and compliance.' Esker's SAP integration white paper further confirms that 'invoice data and document image are electronically transferred into the Esker archive or a separate archiving solution,' and that its 'versatile user rights management features...hel …

Limitations: The critical gap for this buyer is that Esker's archiving is documented as automatic and compliance-oriented, but no evidence shows an administrator-configurable retention schedule that enforces a specific 7-year window for POs, invoices, and receiving records. …

Requirement evaluated: Configurable retention policies aligned with our 7-year record retention requirement

For a $250M technology company needing 7-year record retention for audit readiness, Zip's documented capability covers audit trail capture and export, but not configurable retention duration. On the audit trail side, <cite index="18-1,18-2">Zip offers comprehensive audit trails across all objects including requests, vendors, POs, bills, and more, allowing enterprise procurement and financial leaders to maintain full operational visibility.</cite> For retrieval, <cite index="18-15,18-16">an increasingly complex regulatory landscape prompted Zip to enable instantly accessible audit-ready export packages for immediate download and sharing.</cite> Zip's trust documentation confirms <cite index=" …

Limitations: No publicly documented mechanism exists for configuring a 7-year minimum retention schedule at the system, document type, or category level within Zip; the buyer would need to negotiate explicit retention commitments through the DPA/MSA, and must treat NetSuite (or another downstream system) …

Requirement evaluated: Configurable multi-level approval chains by dollar amount, department, category, vendor, and GL code

For a $250M technology company moving from ad-hoc Slack approvals to a structured P2P system, Esker's Purchasing module provides an automated approval workflow engine that routes purchase requisitions based on configurable predefined criteria. Esker's AP datasheet explicitly lists vendors, cost centers, G/L accounts, and approver rules as separately configurable workflow rule inputs, and the procurement product page confirms that 'the correct level of authorization is always applied to each request.' The P2P white paper documents that approvers can budget-check expenditures against cost center and GL account during approval, and the AP datasheet confirms that routing criteria include invoice …

Limitations: Esker documents each approval routing dimension (vendor, GL/cost center, dollar amount, approver rules) as separate configurable inputs, but does not publicly document stacked AND/OR logic across all five buyer-required dimensions simultaneously; a complex rule such as 'department = Marketing AND category = Professiona …

Requirement evaluated: Configurable multi-level approval chains by dollar amount, department, category, vendor, and GL code

For a $250M tech company currently managing approvals via Slack and email with 35% maverick spend, Zip's Intake-to-Procure module acts as a no-code orchestration layer that captures every purchase request through a single intake form and immediately applies a rule-based approval routing engine. <cite index="16-23,16-24">Zip uses a visual, drag-and-drop workflow builder that allows administrators to create conditional approval paths without coding, with routing based on spend amount, department, category, or custom fields.</cite> <cite index="5-2">The engine routes requests to the right cross-functional teams and dynamically selects appropriate approvers using queues and user hierarchies,</ci …

Limitations: While spend amount, department, category, and vendor routing dimensions are explicitly documented, GL code as a standalone routing condition (distinct from a custom field mapping) …

Requirement evaluated: Exception routing when matches fail; price exceptions to procurement, quantity exceptions to receiving manager

For a $250M technology company moving off email-and-Slack approvals, Esker's AP Automation module performs 3-way matching (invoice against PO and goods receipt) and routes failed matches into a configurable exception handling workflow. Esker's published datasheet explicitly states that invoices are automatically sent to the appropriate workflow path 'based on predefined criteria such as invoice total, vendor name or exception type,' and its SAP eBook process diagram names 'price/quantity mismatch' as a distinct exception category within the exception handling stage, with a documented 'block/forward for approval or further processing' branching path. …

Limitations: Esker documents 'price/quantity mismatch' as a single named exception type rather than two separately routable categories, so the buyer's required split (price exceptions to procurement, quantity exceptions to receiving manager) …

Requirement evaluated: Exception routing when matches fail; price exceptions to procurement, quantity exceptions to receiving manager

For this $250M technology company replacing ad-hoc email/Slack approvals, Zip's Procure-to-Pay module handles three-way matching natively through its Invoice Review Agent, which, as described in Zip's May 2026 P2P launch, <cite index="3-4">surfaces duplicates, purchase order tolerance breaches, and contract mismatches before anything reaches an approver, with three-way matching running against contract data already in Zip.</cite> When a match fails, Zip's Exception Automation AI takes over: <cite index="14-5">Zip's Exception Automation AI places problem invoices on hold, routes them to the right person with a specific task, and releases them when it's done.</cite> The Invoice Review Agent al …

Limitations: The buyer's requirement calls for two separately configured routing paths by exception type (price to procurement, quantity to receiving manager); Zip's Exception Automation AI is documented as routing to 'the right person' but no source confirms this distinction is natively configurable at the exception-type level rat …

Requirement evaluated: Supplier performance scorecards: on-time delivery rate, quality issues, invoice accuracy, responsiveness

For a $250M technology company with both indirect and direct spend portfolios, Esker's Supplier Management module (part of its Source-to-Pay suite) provides a centralized performance dashboard where procurement and AP teams can track supplier KPIs in real time. The platform explicitly supports tracking of predefined performance metrics against compliance and operational thresholds, and its AI-powered inquiry management feature specifically enables teams to monitor response times and inquiry trends at the supplier level: the product page states users can 'Track inquiry trends, monitor response times and gain actionable insights to drive continuous improvement.' Invoice accuracy is reinforced …

Limitations: The mechanistic evidence for on-time delivery rate (auto-calculated from PO committed date vs. actual goods receipt date) and quality issue tracking (discrete defect counts from goods receipt inspections) …

Requirement evaluated: Supplier performance scorecards: on-time delivery rate, quality issues, invoice accuracy, responsiveness

For a $250M technology company looking to track on-time delivery, quality issues, invoice accuracy, and responsiveness across its 800+ vendor base, Zip operates primarily at the sourcing and vendor management layer rather than as a continuous post-award scorecard engine. At the sourcing stage, Zip's platform lets procurement teams score and compare supplier RFx responses using structured criteria, weighted sections, and automated normalization, and identifies preferred suppliers while tracking realized savings and sourcing performance in a single dashboard (ziphq.com/products/sourcing). …

Limitations: Zip's own documentation acknowledges it is not a standalone supplier relationship management tool designed to replace specialized SRM or TPRM platforms, and its vendor management page describes data storage and export rather than calculated operational KPI scorecards. …

Requirement evaluated: Maverick spend tracking: flag all invoices that arrive without a matching PO

For a $250M technology company currently processing invoices entirely through email and Slack, Esker AP Automation addresses this requirement at the invoice capture stage: as each invoice arrives (via email, EDI, fax, mail, or supplier portal), Esker's AI engine extracts the invoice data and immediately attempts 2-way or 3-way matching against open purchase orders and goods receipts in your ERP. If no matching PO is found, touchless processing is blocked and the invoice is automatically routed to an exception queue for multi-level review, coding, and approval rather than passing silently to payment. …

Limitations: Esker's flagging mechanism operates on invoices that enter the Esker AP platform; invoices that bypass the platform entirely (e.g., vendors paid directly via wire transfer or credit card outside the system) will not be captured or flagged. …

Requirement evaluated: Maverick spend tracking: flag all invoices that arrive without a matching PO

For a company with 35% maverick spend and no systematic PO enforcement, Zip addresses this requirement through two layers that operate end-to-end. First, at the intake stage, Zip forces every purchase request through a structured workflow that automatically generates a PO before any vendor is engaged: the intake-to-pay product page states that 'Zip ensures all requests go through intake and automatically generates POs, so you can drive PO adoption effortlessly.' Second, at the invoice stage, Zip's AP automation module pulls invoices from the AP inbox, applies AI-driven matching against the corresponding PO record, and explicitly 'prevents exceptions at intake, catches the rest with AI matchi …

Limitations: Zip's exception-catching mechanism operates on invoices that enter Zip's AP inbox or intake workflow; invoices submitted directly into NetSuite by the ops team, bypassing Zip entirely, will not be caught by Zip's matching engine unless the buyer fully routes all AP intake through Zip. …

Requirement evaluated: Automatic routing to the right approver based on category, amount, department, and location

For a $250M technology company moving from ad-hoc Slack/email approvals to structured procurement, Esker's Purchasing module operates at the requisition intake stage: when an employee submits a purchase requisition, Esker's configurable approval workflow engine evaluates the request against the company's buying policy and automatically routes it to the appropriate approver(s) without manual handoff. …

Limitations: Explicit documentation confirming 'location' (physical office or site) as a named, discrete routing condition in purchase requisition workflows was not found; buyers with hard location-based routing requirements (e.g., different approvers for the Canadian development center vs. US offices) …

Requirement evaluated: Automatic routing to the right approver based on category, amount, department, and location

For a $250M technology company currently routing all purchasing through ad-hoc email and Slack approvals, Zip's core product is purpose-built to solve exactly this problem. At the intake stage, employees submit a request through a single intake portal that collects structured metadata: what is being purchased, from which vendor, at what cost, and which budget or department it affects. Zip's no-code workflow engine then evaluates that metadata against configurable routing rules and automatically assigns the correct approvers. …

Limitations: Zip's own published documentation explicitly names spend amount, department, category, and vendor as routing dimensions; location as a standalone first-class routing variable is not explicitly documented in Zip's available help content, so buyers with complex location-specific routing rules (e.g., separate approvers fo …

Requirement evaluated: Approval bottleneck analysis: which approvers are slowest, which invoice types take longest

For a 3-person AP team at a $120M multi-location services company currently blind to approval timing, Esker provides role-specific KPI dashboards that surface process efficiency metrics across the full invoice lifecycle. AP managers get a dedicated dashboard tier covering spend visibility, process efficiency, and payment KPIs, while cost center owners see requests pending approval in real time. The platform tracks average processing time by month and breaks out invoices by type (PO vs. non-PO), giving the AP manager visibility into which invoice categories move slowly. …

Limitations: The documented metrics include average processing time by month and invoice type breakdowns, but Esker's product documentation does not explicitly surface a pre-built 'approver league table' report showing ranked cycle times per named approver; that view would likely require the buyer to configure a custom dashboard us …

Requirement evaluated: Approval bottleneck analysis: which approvers are slowest, which invoice types take longest

For a $120M services company currently routing approvals through email chains with zero visibility into who is holding things up, Zip's Spend Insights module directly addresses this gap. The module tracks each request as it moves through Zip's multi-step approval workflow, logging time spent at every stage and by every approver. Zip's capability page states that the platform 'analyzes your cycle times to identify opportunities for optimizing workflows and moving requesters and approvers through the process faster,' and the Enterprise dashboard surface offers 'real-time visibility into spend volume, approver productivity, and savings.' SLA compliance is a named use case: Zip explicitly positi …

Limitations: Some users reviewing Zip's reporting suite note that the standard dashboards cover core cycle-time and approver-productivity metrics well, but teams requiring highly complex, multidimensional procurement analytics (beyond bottleneck identification) may need to export data to an external BI tool for deeper slicing. …

Requirement evaluated: Mobile approval with full invoice image view; approvers must be able to act from their phone in under 30 seconds

For a 3-person AP team at a $120M services company routing 1,800 invoices per month for approval across 6 office locations, Esker's dedicated mobile app, Esker Anywhere, directly addresses this requirement. Approvers receive instant push notifications of pending invoices, open the app on their Apple or Android device, view the full invoice image as received by the accounting department, review key invoice data and prior approvers' comments, then approve, hold, or return the invoice; all in a single, purpose-built mobile interface available 24/7. …

Limitations: No published data confirms a specific 'under 30 seconds' benchmark; the speed claim depends on network connectivity and how quickly each approver can load and review the invoice image on their device. …

Requirement evaluated: Approval delegation with automatic expiration (e.g., delegate to backup for 5 business days while on PTO)

Your three-person AP team at a $120M multi-location services company needs approvers to be able to set a named backup, define a start and end date for a PTO window, and have approval authority revert automatically when that window closes — without any manual cleanup. Zip's workflow engine is documented as supporting dynamic approver selection using queues and user hierarchies, and the platform is designed to route requests to the right cross-functional teams across complex approval paths. …

Limitations: No citable source — from the fact sheet's primary or supporting tiers, Zip's own documentation site, or its workflow capability pages — confirms that Zip offers auto-expiring delegation with a named backup approver and hard date-range control as opposed to manual reassignment or permanent role transfer. …

Requirement evaluated: Vendor communication log: track every inquiry and response to eliminate the 6 hours/week our team spends on status calls

For a 3-person AP team currently spending 6 hours per week fielding status calls, Esker addresses this through two interlocking mechanisms. First, the Esker Supplier Portal gives vendors self-service, 24/7 access to real-time invoice and payment status at each workflow stage (received, approved, paid) so they can check themselves without contacting AP. Second, a built-in chat tool on the portal lets suppliers and the AP team exchange messages directly on the invoice record; all conversations are retained in a persistent log accessible to both parties at any time. …

Limitations: The communication log and status visibility only capture interactions that flow through the portal; vendors who do not adopt the portal and instead continue to call or email will still generate untracked inquiries, so the volume reduction depends on supplier enrollment rates. …

Requirement evaluated: Centralized vendor master synchronized bidirectionally with Sage Intacct

For your 2-entity Sage Intacct environment, Zip establishes a connection with Intacct at the point where vendor master data must stay consistent across both your procurement layer and your ERP. On the inbound side, once the connector is configured, Zip runs a daily scheduled pull from Sage Intacct that brings Entities, Locations, Segments, and your existing vendor list into Zip, giving requesters the correct vendor data when they initiate purchase requests. On the outbound side, when a Zip user submits a purchase request referencing a net-new vendor and that vendor clears Zip's onboarding and approval workflow, Zip creates the new vendor record in Sage Intacct automatically. …

Limitations: The sync as documented operates on a daily schedule for the Intacct-to-Zip direction and triggers only on new vendor creation for the Zip-to-Intacct direction; updates to existing vendor records in either system (e.g., a banking detail or payment terms change entered in Intacct, or a W-9 collected through Zip's supplie …

Requirement evaluated: Learning capability: accuracy should improve over time on our specific vendor invoice formats

For a 3-person AP team processing 1,800 invoices/month across a mixed PO and non-PO portfolio, Esker's Synergy AI addresses the learning requirement at the invoice capture and pre-processing stage (pre-ERP posting). The platform combines OCR, deep learning, and a supervised correction loop: when an AP user corrects an extracted field or a GL coding suggestion, Esker Synergy registers that correction and uses it to improve future recognition on similar invoices. …

Limitations: Esker's public documentation does not explicitly state whether the correction-driven learning model is scoped per-tenant (improving only on your organization's corrections) …

Requirement evaluated: Automatic ingestion from our shared AP email inbox; no manual downloading or sorting

For a team currently downloading invoices from a shared AP email inbox and manually keying them into Sage Intacct, Zip's AP Automation module addresses this at the very first stage of the pre-processing journey (legitimacy and capture). Zip provides a dedicated AP Inbox Agent that actively monitors incoming vendor mail, extracts invoice attachments, and organizes them into the processing queue without any human download or sort step. …

Limitations: The specific technical integration method for connecting the buyer's existing shared Office 365 or Google Workspace AP mailbox (IMAP, OAuth connector, or forwarding rule) …

Requirement evaluated: Native, pre-built, bidirectional integration with Sage Intacct (not middleware-dependent)

Your company runs two ERP entities in Sage Intacct, so the integration mechanism must connect directly to Sage Intacct's Web Services API and carry vendor master, GL codes, dimensions, and payment status bidirectionally. Esker does offer pre-built, native Sage ERP connectors through its Connectivity Suite, but the connectors documented on Esker's own Sage integration page cover Sage X3, Sage FRP 1000, and Sage 100 only. Sage Intacct is not named on that page, and Esker does not appear in the Sage Intacct Marketplace AP Automation category, where certified Sage Intacct connectors from vendors such as Stampli, Tipalti, and BILL are listed. One published Esker case study (People's Care) …

Limitations: Esker's pre-built Sage connectivity is documented exclusively for Sage X3, Sage FRP 1000, and Sage 100. For a buyer whose books of record live in Sage Intacct, no native connector is evidenced, meaning any Esker-to-Intacct data flow would require a custom API build or third-party middleware, directly contradicting the …

Requirement evaluated: Custom field mapping between the AP platform and Intacct

For a $120M multi-location services company running two Intacct entities, Zip's Sage Intacct integration operates primarily as a procurement intake and vendor management layer rather than a deep AP bill coding connector. The Sage Intacct Marketplace listing for Zip documents a daily pull sync that brings Entities, Locations, Segments, and the existing vendor list from Intacct into Zip — giving the platform the structural Intacct objects it needs to route procurement requests and create new vendor records. …

Limitations: The specific requirement — mapping custom or user-defined Intacct fields (such as UDDs on AP Bills, contract codes, or supplemental vendor tags) between the two platforms — has no documented mechanism in any Zip-authored source; the integration as publicly described stops at standard Entities, Locations, Segments, and …

Requirement evaluated: SOC 2 Type II certification (current, not in-progress)

For a $120M services company requiring a current SOC 2 Type II report before deploying AP automation, the publicly documented picture for Esker is materially incomplete. Esker's primary platform-wide certifications are ISO 27001 (for its Information Security Management System, renewed via A-lign) and SOC 1 Type 2 under SSAE 18 and ISAE 3402, which validate internal control processes for on-demand services. Esker's own security datasheet confirms that SOC 2 Type II examination was completed in 2020, but scoped only to the Collections Management solution, not to the AP automation module. Esker's customer-confidence page (updated March 2026) …

Limitations: The buyer's requirement is a current SOC 2 Type II report, and the most recent public evidence shows Esker's SOC 2 Type II scope is limited to the Collections Management module as of 2020; the AP platform's documented certifications are ISO 27001 and SOC 1 Type 2 (SSAE 18), which do not satisfy a SOC 2 Type II requirem …

Requirement evaluated: SOC 2 Type II certification (current, not in-progress)

As a $120M multi-location services company with sensitive procurement data flowing through Sage Intacct, your security review team will want a completed, operational-controls audit rather than a point-in-time snapshot. Zip's official Trust page confirms that <cite index="10-1,10-2">Zip has undergone a Service Organization Controls audit (SOC 2 Type 2), and prospects can contact their account manager or Zip's Security Resource Center to request the most recent report.</cite> The audit runs on an annual cycle: <cite index="11-3">Zip is annually audited for SOC 2 Type 2 compliance on select trust service principles.</cite> Zip's product pages also list SOC 2 Type 2 alongside SOC 1 Type 2, ISO 2 …

Limitations: The report covers 'select trust service principles' rather than all five AICPA Trust Services Criteria, so your security team should confirm which criteria (Security, Availability, Processing Integrity, Confidentiality, Privacy) are in scope when requesting the report. …

Requirement evaluated: Non-PO invoice routing: automatic GL coding suggestions based on vendor history and invoice description

For your approximately 810 non-PO invoices per month covering utilities, professional services, subscriptions, and insurance, Esker Synergy AI applies AI-based predictive line-item coding at the point of invoice capture. The mechanism is explicitly documented for non-PO invoices: Esker's machine learning and deep learning engine analyzes historical transaction data and recommends GL account, cost center, cost type, and tax code values for each invoice line, surfacing those suggestions in a validation form for AP review or bypassing review entirely when no exception is detected. …

Limitations: Esker's documentation confirms coverage of GL account, cost center, cost type, and tax code dimensions for non-PO coding, but the specific depth of its Sage Intacct connector relative to Intacct's full custom-dimension schema (including any user-defined dimensions your two entities may use) …

Requirement evaluated: Per-vendor duplicate sensitivity configuration for vendors that legitimately reuse invoice numbers (e.g., recurring rent or utility billing)

For a multi-location services company with recurring vendors like landlords and utility providers that legitimately reuse invoice numbers monthly, this requirement asks whether Zip can be configured to suppress or tune duplicate flags at the individual vendor level. Zip's Invoice Review Agent does surface duplicate invoices before they reach an approver: <cite index="10-5">the Invoice Review Agent surfaces duplicates, purchase order tolerance breaches, and contract mismatches before anything reaches an approver, with three-way matching running against contract data already in Zip.</cite> Additionally, <cite index="6-1,6-2">Zip catches duplicates, overages, and contract mismatches before invo …

Limitations: For this buyer's 45% non-PO invoice volume (utilities, subscriptions, recurring rent), vendors that legitimately reissue the same invoice number each billing cycle would generate recurring false-positive duplicate flags with no documented per-vendor suppression or sensitivity tuning mechanism. …

Requirement evaluated: Automatic remittance advice sent to vendors upon payment

For a 3-person AP team at a $120M multi-location services company currently sending remittance advice manually (or not at all), Esker addresses supplier payment visibility primarily through its supplier portal rather than through event-triggered outbound remittance delivery. Esker's AP automation module gives suppliers direct, self-service access to invoice and payment status via an online portal, reducing inbound status inquiry calls to the AP team. Separately, Esker's Synergy AI layer can automatically sort and generate responses to inbound supplier inquiries about payment status, including overdue payment reminders and payment confirmation questions. …

Limitations: The primary documented supplier communication mechanism is portal-based self-service access, which places the discovery burden on each vendor and requires portal adoption; for the 1,800 invoices per month this buyer processes across facilities, subcontractor, subscription, and utility vendors, those vendors must active …

Requirement evaluated: Early payment discount detection: auto-flag invoices with discount terms (2/10 net 30) and alert AP when deadline approaches

For your AP team processing 1,800 invoices per month across 6 locations, early payment discount detection requires three connected steps: extracting discount notation (such as '2/10 net 30') from invoice text, calculating the deadline date, and alerting AP before the window expires. Zip's AI invoice processing does capture payment terms as a data field during document extraction, per Zip's own blog content on AI invoice processing. …

Limitations: No help center article, product page, or technical documentation found for Zip confirms a discount-deadline calculation and AP notification feature; the gap between capturing a 'payment terms' text field and auto-flagging an expiring 2/10 window with a deadline-driven alert is material for a buyer whose team is current …

Requirement evaluated: Automated PO distribution to vendors via email or vendor portal

For a company like yours currently relying on the ops team to manually create and send POs out of NetSuite, Esker's Procure-to-Pay module replaces that manual step with automatic PO distribution. Once a purchase requisition clears its approval workflow, the PO is generated and Esker dispatches it to the supplier automatically: the platform converts the document to the supplier's preferred format and delivers it via email or fax, with delivery rules configured per supplier so no ops-team action is needed after approval. …

Limitations: The most granular documentation of per-supplier delivery-method rules (email vs. fax vs. portal, multi-recipient routing) comes from Esker's older DeliveryWare platform documentation rather than the current SaaS procurement module pages; buyers should confirm during a demo that the current cloud procurement module pres …

Requirement evaluated: PO status tracking: from approved through acknowledged, received, invoiced, and closed

For a $250M technology company replacing ad hoc email and Slack approvals, Zip covers the full PO lifecycle natively within its procure-to-pay platform. Once a purchase request clears the approval workflow, Zip automatically generates a PO and delivers it to the supplier through its Vendor App portal — this is the 'approved through acknowledged' handoff, where the supplier receives the PO directly in Zip's portal rather than via email. …

Limitations: Help-center documentation confirms that the supplier portal delivers POs and enables vendor-side interaction, but does not explicitly document a distinct 'acknowledged' status label that is updated by a supplier confirmation action separate from PO delivery — the acknowledged stage is effectively PO delivery to the Ven …