How Pleo works

Requirement evaluated: Automated vendor onboarding workflow: request → IT security check (for software) → finance approval → vendor master creation in NetSuite

For a $250M technology company needing a structured new-vendor request workflow (intake form, IT security gate for software vendors, sequential finance approval, then automated vendor master creation in NetSuite), Pleo has no documented mechanism. Pleo's 'vendor' features consist of two distinct capabilities, neither of which addresses this requirement: virtual 'vendor cards' that lock a payment card to a specific recurring merchant for subscription management, and a 'vendor tagging' feature that imports and syncs existing vendor records from NetSuite into Pleo for expense-coding purposes. …

Limitations: Pleo is a corporate card and expense management platform; it has no procurement-style vendor onboarding module, no conditional sequential approval workflow for new supplier requests, and no mechanism to create or write vendor master records in NetSuite as the output of an onboarding process. …

Requirement evaluated: Preferred vendor lists by category with contract terms visibility

Your company needs a procurement-grade preferred vendor directory: a catalog organized by spend category (IT, facilities, professional services, marketing, travel) where employees can see which suppliers are approved before they buy, and where negotiated contract terms like rates, payment terms, and renewal dates are surfaced at the point of selection. Pleo does not provide this mechanism. Its closest vendor-management features are (1) 'vendor cards,' which are dedicated virtual cards that can be locked to a specific merchant and assigned spending limits, designed to control recurring subscription payments rather than guide buyers toward approved suppliers across categories; and (2) …

Limitations: Pleo is a spend management and corporate card platform; it has no procurement-oriented preferred vendor catalog, no category-based supplier directory, and no mechanism to surface negotiated contract terms (rates, payment terms, rate cards) at the point of purchase. …

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

For a $250M technology company that needs quantitative scorecards measuring on-time delivery, quality issues, invoice accuracy, and supplier responsiveness, Pleo has no mechanism to deliver this. Pleo is a corporate card and spend management platform: its 'vendor' features consist of virtual vendor cards that track recurring subscription spend per supplier (sortable by spend volume and last-paid date) and a supplier invoice payment flow that routes invoices through an approval process before payment. Neither feature captures goods receipt confirmations, delivery events, quality defect data, or communication SLA tracking that a performance scorecard requires. …

Limitations: Pleo cannot produce on-time delivery rates, quality issue counts, invoice accuracy ratios, or responsiveness metrics for this buyer's 800+ vendor base at any price tier or add-on; the transactional data inputs (goods receipts, delivery acknowledgments, defect logs, supplier SLA records) …

Requirement evaluated: Vendor deduplication: identify and merge the 800+ vendor records into a clean master list

For a $250M technology company needing to consolidate 800+ NetSuite vendor records into a clean master list, Pleo offers no mechanism to address this requirement. Pleo is a spend management and corporate card platform: its 'vendor' concept refers to merchants tagged on card transactions or locked to dedicated virtual cards for subscription control, not to formal supplier master records in an ERP. The closest Pleo comes to vendor-related data management is 'vendor enrichment,' an AI feature that attaches a short description and category to vendors appearing on Vendor Card transactions, and 'Recurring Vendors,' an automatically generated overview of subscription spend. …

Limitations: Pleo has no deduplication engine, no fuzzy or probabilistic matching on vendor name, EIN/tax ID, address, or bank account, and no merge workflow or golden-record creation capability. …

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

For a $250M technology company that needs NetSuite to serve as the single source of truth for budgets, Pleo cannot fulfill this requirement. Pleo's budget feature, documented in its help center, works entirely within Pleo itself: an admin or controller creates a budget inside Pleo using a custom Tag, sets a ceiling manually, and Pleo tracks spend against that internally defined ceiling in real time. There is no documented mechanism for Pleo to read live budget balances, period actuals, or encumbrance data from NetSuite GL or budget records. The NetSuite integration runs in one direction: Pleo exports expense transactions to NetSuite for bookkeeping purposes. …

Limitations: Pleo's budgets are entered and maintained manually inside Pleo, creating a separate ledger that drifts from NetSuite as actuals accumulate outside Pleo's view (POs, vendor invoices, payroll-coded spend). …

Requirement evaluated: Sync scope: chart of accounts, departments, classes, locations, projects, vendor master, items, and custom segments

For a $250M tech company running NetSuite as its ERP, Pleo's NetSuite integration operates primarily as an expense-and-card transaction export platform with a partial inbound sync of coding dimensions. On the inbound side, Pleo pulls chart of accounts (synced once daily) and lets administrators configure 'Tag Groups' mapped to NetSuite's standard dimensions (Class, Location, and Department) or custom/standard transaction body and line fields, which covers some of the buyer's custom segment needs. Pleo is a Built-for-NetSuite verified SuiteApp, so the connector runs inside the NetSuite environment and processes exports every 15 minutes. …

Limitations: Three of the buyer's eight required entity types are not covered: vendor master (no documented pull of the full NetSuite vendor list into Pleo for PO coding or matching), items/catalog (no mention in any NetSuite integration docs), and projects (not explicitly confirmed for the NetSuite connector, only for other integr …

Requirement evaluated: Native, bidirectional integration with Oracle NetSuite (not middleware-only)

For a $250M technology company currently building PO discipline on top of NetSuite, Pleo's NetSuite connection is a certified 'Built for NetSuite' verified SuiteApp delivered by Pleo as a SuiteCloud Developer Network Partner, meaning no third-party middleware broker is required. Pleo is a SuiteCloud Developer Network Partner, with a Built for NetSuite verified SuiteApp integration available to all customers. …

Limitations: Pleo's NetSuite SuiteApp is scoped entirely to spend management and accounting export: it cannot originate purchase orders in NetSuite, does not sync the vendor master, and offers no requisition or approval-to-PO workflow. …

Requirement evaluated: REST API for any integrations not covered by native connectors

For a $250M tech company trying to build custom NetSuite integrations beyond Pleo's native connectors, Pleo does offer a documented REST API at developers.pleo.io with OAuth 2.0 and API key authentication, a sandbox environment, and a webhook subscription system. The API uses OAuth 2.0 (client credentials and authorization code flows), accessible by registering an application in the Pleo Developer Portal, and exposes a REST endpoint at `https://external.pleo.io/v0`. …

Limitations: The buyer's NetSuite integration use case requires API access to procurement lifecycle objects (POs, invoice approvals, requisitions); Pleo's API model is built around card expense and accounting export objects, meaning any custom NetSuite connector built on Pleo's API would cover card spend data export but could not r …

Requirement evaluated: Board-ready spend reports: quarterly spend summary by category with trend lines and vendor concentration metrics

This $250M company needs a quarterly board report covering $90M in total spend with category trend lines and vendor concentration metrics. Pleo does offer an Analytics page in its web app: it provides a detailed overview of company spend, including spend by category such as travel and software. It positions itself as a real-time spend report for future budget planning, visible to admins and bookkeepers across the full company. However, the Analytics page gives only a tabular overview and displays only expenses that have been settled — meaning it covers Pleo card transactions and out-of-pocket reimbursements, not PO-based or invoice-routed spend flowing through NetSuite. …

Limitations: Pleo's analytics scope is limited to card and reimbursement spend settled through Pleo itself; for a buyer whose majority spend flows through NetSuite POs and direct-material purchasing, the Analytics page produces a structurally incomplete picture of vendor concentration and category spend. …

Requirement evaluated: Tail spend analysis: identify high-transaction-count, low-dollar vendors for consolidation

For a $250M technology company trying to identify which of its 800+ active vendors to consolidate, Pleo offers two relevant but limited analytics capabilities. First, the Analytics page in the Pleo web app provides a breakdown of spend by category (e.g., travel, software, office expense) and by team or individual employee, with admins able to see the full company-wide view (Pleo Help Centre: 'How the Analytics page works'). Second, the 'Insights' feature can surface top vendors by total spend value, and the 'Recurring Vendors' module tracks subscription-type vendors sortable by high or low spend (Pleo vendor cards help article). …

Limitations: Pleo has no documented mechanism for Pareto or ABC vendor segmentation, transaction-count-vs-spend-value scatter analysis, or supplier rationalization workflows. The buyer's need to identify which of 800+ vendors to retire cannot be addressed by Pleo's category-level and top-vendor-by-spend analytics alone; a dedicated …

Requirement evaluated: Real-time budget tracking: available budget = annual budget minus actuals minus committed (approved POs not yet invoiced)

For a $250M technology company needing available budget calculated as annual budget minus actuals minus committed (approved POs not yet invoiced), Pleo cannot deliver this formula natively. Pleo's budget control architecture is card-transaction-based: admins set per-card spending limits (hard or soft, per-purchase or monthly), and sub-accounts ('sub-wallets') are deducted when a card transaction is made or an out-of-pocket expense is submitted. There is no purchase requisition or purchase order lifecycle module in Pleo's product; the platform has no mechanism to record an approved PO as a committed obligation and deduct it from a budget balance before an invoice or card transaction exists. …

Limitations: Pleo has no purchase order module, no encumbrance or pre-encumbrance ledger, and no mechanism to treat an approved but uninvoiced PO as a budget-consuming commitment; the three-part formula this buyer requires (budget minus actuals minus open PO commitments) cannot be computed inside Pleo at any pricing tier.

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

This $250M US technology company needs every invoice arriving without a matching PO to be automatically flagged or held before payment. Pleo does have a purchase order module: the system will automatically attempt to match invoices to linked purchase orders, and if there is a mismatch, a warning is surfaced for review and correction. However, this mismatch warning only fires when an invoice is already associated with a PO; there is no documented mechanism that detects or holds invoices submitted with no PO reference whatsoever, which is the core of maverick spend tracking. …

Limitations: The supplier invoice payment module, which houses Pleo's only PO-matching capability, is explicitly unavailable to US customers, making it inaccessible to this buyer entirely. …

Requirement evaluated: SOC 2 Type II certification for the platform

For a US-based technology company evaluating Pleo against a SOC 2 Type II requirement, Pleo's own Trust and Security page is the definitive reference, and SOC 2 Type II does not appear on it. Pleo's documented third-party certifications and audits are: PCI-DSS for payment processing, Google's Cloud Application Security Assessment (CASA) for cloud security, HackerOne Bug Bounty Penetration Testing for vulnerability identification, a CAIQ Self-Assessment, and GDPR adherence. Pleo's Data Processing Agreement confirms the vendor 'is regularly audited against PCI standards by independent third party auditors,' but makes no mention of SOC 2 audits. …

Limitations: SOC 2 Type II is entirely absent from Pleo's published security credentials and legal documentation, not available as a paid add-on or upon request per any discoverable source. …

Requirement evaluated: Segregation of duties enforcement: requester ≠ approver ≠ receiver ≠ payment processor

For a $250M technology company replacing an email/Slack approval process and trying to eliminate maverick spend, Pleo's role model (Owner, Admin, Controller, Reviewer, Employee/Cardholder, Bookkeeper) creates a partial separation between the requester and approver legs. Pleo's help documentation explicitly states that 'Reviewers can not review their own expenses' and 'Team and Tag reviewers cannot review their own expenses,' which enforces the requester-not-equal-approver rule for users in the Reviewer supplementary role. …

Limitations: The buyer's requirement demands all four roles to be distinct and enforced as hard system controls; Pleo enforces only the reviewer-cannot-self-review rule, which is nullified for any Admin-role user, and the platform has no goods receipt confirmation step or independently gated payment processor role, meaning three of …

Requirement evaluated: Segregation of duties enforcement: requester ≠ approver ≠ receiver ≠ payment processor

This $250M technology company needs system-enforced separation across four distinct roles in every transaction: the person requesting a purchase cannot approve it, the approver cannot confirm receipt of goods, and the receiver cannot execute payment. Pleo's architecture does not cover this chain. Pleo's documented roles are Employee (cardholder/spender), Admin (broadest access, manages cards, users, and limits), Reviewer (a supplementary add-on role that can approve or reject expenses for assigned teams), Controller, and external Bookkeeper. …

Limitations: Pleo's card-first, expense-review model covers at most one of the four required SOD separations (spender vs. post-spend reviewer) and provides it only after funds have already been committed via card swipe, not before. …

Requirement evaluated: SOC 2 Type II certification for the platform

For a $250M technology company with US offices and Canadian operations requiring audit-ready compliance documentation, Pleo does not appear to hold a SOC 2 Type II certification. Pleo's dedicated Trust and Security page (pleo.io/en/trust-and-security) enumerates its third-party assessments and certifications as: PCI-DSS, Google's Cloud Application Security Assessment (CASA), HackerOne Bug Bounty penetration testing, and a CAIQ Self-Assessment, with GDPR compliance rounding out the framework. Pleo undergoes rigorous third-party assessments and audits covering PCI-DSS, Google's CASA, HackerOne Bug Bounty penetration testing, and a CAIQ Self-Assessment, as well as GDPR adherence. …

Limitations: Pleo's security framework is built around PCI-DSS, GDPR, and CASA; there is no evidence of a SOC 2 Type II report available under NDA or through a trust portal, which means this buyer's CFO and external auditors would have no third-party attestation of sustained control effectiveness over an audit period. …

Requirement evaluated: Link request to existing contract when applicable (e.g., ordering under a blanket PO or master agreement)

For a $250M technology company trying to ensure that purchase requests placed against existing blanket POs or master agreements are properly linked, Pleo offers no mechanism to accomplish this. Pleo is a card-based spend management platform: employees make purchases via physical or virtual company cards within pre-set spending limits, and Pleo captures receipts, categorizes transactions, and syncs expense data to accounting systems. …

Limitations: Pleo's own blog categorizes contract lifecycle management and eProcurement requisition tools as separate product categories from its spend management offering, and independently recommends third-party solutions for those needs. …

Requirement evaluated: Mobile submission capability; our field team needs to submit requests from job sites

For a $250M technology company trying to eliminate 35% maverick spend, Pleo does offer a native iOS and Android mobile app that field employees can use from any location. The app is described by Pleo's own help center as 'the key in making the purchasing experience smooth and effective,' and supports submissions from mobile devices including Apple Pay and Google Pay card transactions, out-of-pocket expense uploads with OCR receipt capture, and spending limit increase requests. However, the mobile submission mechanism is post-purchase: a field employee either swipes a Pleo company card (spending happens first, documentation follows) …

Limitations: Pleo's mobile app covers the post-purchase leg of spend management, not the pre-purchase requisition gate this buyer needs to close maverick spend; field employees on job sites can log what they already spent via card or out-of-pocket reimbursement, but cannot submit a formal spend request that requires approval before …

Requirement evaluated: Self-service request portal where any employee can submit a purchase request without training; must be simpler than email

For a $250M technology company trying to replace ad hoc email purchasing with a structured, no-training employee intake portal, Pleo's self-service model operates through a fundamentally different mechanism. Pleo's employee-facing experience is card-first: employees are issued prepaid Pleo cards with individual spending limits and simply make purchases, with the app capturing receipt data automatically afterward. When an employee needs to spend beyond their limit, they can request a temporary limit increase or a temporary virtual card from within the Pleo mobile app, and a reviewer is notified to approve or deny it. …

Limitations: Pleo has no documented purchase requisition intake portal designed for untrained employees to submit vendor spend requests that flow through approval into PO creation for all spend categories; the PO feature that exists on the Beyond plan requires manual line-item entry by the submitter and is not positioned or designe …

Requirement evaluated: Mobile submission capability; our field team needs to submit requests from job sites

For a $250M technology company whose field team needs to submit purchase requests from job sites before spend is committed, Pleo's mobile footprint is real but misaligned in mechanism. Pleo offers a native iOS and Android app where employees can submit out-of-pocket expenses for reimbursement, request temporary card spending limit increases, and manage card-based purchases — all from the phone. However, the mobile app's documented employee-facing workflows are spend-first and expense-capture-centric: the employee spends (via Pleo card or out-of-pocket) and then submits documentation through the app for review. …

Limitations: Pleo's mobile app is built around card spend management and post-purchase expense capture, not pre-spend purchase requisitions; field employees cannot use it to submit a structured vendor-specific purchase request that routes through an approval workflow and produces a NetSuite PO. …

Requirement evaluated: Guided buying experience: search shows preferred/contracted options first with savings vs. off-contract alternatives

For a $250M technology company trying to steer 450 employees toward preferred suppliers and surface savings against off-contract alternatives, Pleo offers no guided buying catalog. Pleo is architecturally a corporate card and expense management platform: employees receive prepaid cards with individual spending limits, make purchases directly at merchants, and then capture receipts post-transaction. The closest controls Pleo documents are merchant category blocks (which block entire MCC categories per user) and vendor-locked cards (virtual cards locked to a single specific merchant for recurring subscriptions). …

Limitations: Pleo has no catalog, no preferred supplier tagging or search ranking, and no mechanism to show employees the savings foregone when buying off-contract: the entire guided buying layer this buyer requires simply does not exist in Pleo's product. …

Requirement evaluated: Services catalog: pre-defined service offerings from preferred vendors (e.g., standard consulting day rates)

This $250M technology company needs a services catalog where employees select pre-configured service offerings (e.g., a standard consulting day rate from Vendor X at $1,500/day) at the point of requisition, with pricing locked and vendor scope enforced before any spend occurs. Pleo operates entirely differently: its core mechanism is issuing prepaid Mastercards with individual spending limits and merchant-category controls, where spend is captured and categorized after a card transaction takes place. …

Limitations: Pleo has no procurement catalog layer at all: there is no mechanism for an admin to pre-configure a 'standard consulting day rate' item tied to a preferred vendor, nor any guided buying experience that steers employees toward approved service providers with contract-enforced pricing. …

Requirement evaluated: Category-based shopping with visual interface; not just a search box

This $250M technology company needs a visual, pre-purchase catalog that routes employees to approved suppliers by spend category before any money is committed. Pleo has no such mechanism. In Pleo, categories automatically align with your chart of accounts and tax codes so expenses are ready for export and reconciliation: they are a post-transaction coding tool, not a pre-purchase browsing interface. When a Pleo card is used to make a purchase, the system automatically assigns it to a category based on the merchant, meaning the spend event must already have occurred before any category interaction happens. …

Limitations: Pleo's catalog gap is a disqualifying mismatch for this requirement: the buyer explicitly wants a visual category-browsing interface to reduce maverick spend (currently 35% of total spend) by guiding employees to preferred vendors before purchase. …

Requirement evaluated: Service receipt: time-based or milestone-based confirmation for professional services engagements

For this $250M US-headquartered technology company, Pleo's invoice and AP capabilities do not provide the service receipt confirmation step required. Pleo's purchase order module does automatically attempt to match invoices to linked POs and flags mismatches, but the documented matching mechanism stops at a 2-way PO-to-invoice comparison with no third 'delivery confirmed' document in the chain. …

Limitations: Pleo offers no documented mechanism for time-based or milestone-based service receipt confirmation at any price point, and supplier invoice payment — the module that would house any such workflow — is explicitly not available to US customers, making the capability inaccessible to this buyer entirely.

Requirement evaluated: Automatic match-and-pass for invoices within tolerance, reducing AP workload to exceptions-only review

For a $250M technology company moving off manual PO creation in NetSuite, Pleo's AP module offers an automated PO-to-invoice matching step: when an invoice arrives (via email forwarding to a dedicated Pleo inbox or mobile upload with OCR extraction), the system automatically attempts to match it to a linked purchase order and flags any mismatch with a warning for a reviewer to correct. Pleo's invoices page also states that it 'auto-suggests the right PO match, flags discrepancies instantly.' However, Pleo's documented mechanism stops at two-way matching (PO vs. invoice): no goods receipt or delivery confirmation step is documented, meaning the third leg of a true three-way match is absent. …

Limitations: Pleo's documented PO matching is a warning-on-mismatch model with no evidence of configurable tolerance thresholds for straight-through processing; every invoice still enters the configured review workflow rather than an exceptions-only queue. …

Requirement evaluated: Service receipt: time-based or milestone-based confirmation for professional services engagements

For this $250M technology company, which spends heavily on IT, professional services, and marketing, the ability to formally confirm that services were rendered before releasing payment is a core control. Pleo's PO module (available only on the Beyond plan) allows a reviewer to approve a PO before spend occurs, and then the system automatically attempts to match an inbound supplier invoice to that linked PO, surfacing a warning if there is a mismatch. …

Limitations: Pleo has no documented mechanism for a project owner or budget holder to formally attest that professional services were delivered against a time period or milestone before an invoice is released for payment; the closest available substitute is manually adding a reviewer to the invoice approval step, which is an unstru …

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

For a $250M US technology company trying to replace its email-and-Slack PO process, Pleo offers a basic purchase order module that covers the early stages of the lifecycle but stops well short of the five-stage pipeline the buyer requires. A user creates a PO with at least one line item in the Pleo web app, and reviewers approve it through Pleo's configured review workflow. At least one reviewer must approve the purchase order before it advances. The system will automatically attempt to match invoices to linked purchase orders; if there is a mismatch, a warning surfaces so staff can review and correct it. …

Limitations: Pleo's PO feature is documented only through the approval and invoice-matching stages; the "acknowledged," "received," and "closed" stages in the buyer's required lifecycle have no corresponding mechanism in Pleo's help documentation. …

Requirement evaluated: PO change order workflow: amendments require re-approval if they exceed original amount by more than 10% or $5,000

Your $250M technology company needs PO amendments that exceed 10% or $5,000 above the original amount to automatically re-enter an approval workflow before being committed. Pleo does offer a Purchase Order feature, but it is limited to initial PO creation and approval: a user adds line items and currency details, at least one reviewer must approve the PO, and the system then attempts to match incoming invoices to the linked PO, surfacing a warning if there is a mismatch. …

Limitations: Pleo's PO module (available on the Beyond plan) covers initial creation and single-reviewer approval, but stops there: once a PO is approved, there is no system-enforced change order process that would hold an amendment pending re-approval if it exceeds 10% or $5,000. …

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

This $250M technology company needs approval chains that fire differently based on combinations of dollar amount, department, spend category, vendor identity, and GL code; a compound routing matrix. Pleo's approval model offers three layered review types configured in Settings: team reviews (with a per-team dollar threshold above which expenses are flagged), tag-based reviews (routable by department, project, client, or location), and a company-level finance review as a final 'four-eyes' step. …

Limitations: The buyer's requirement for compound routing rules (e.g., 'if IT spend over $10K with a new vendor, route to IT Director AND CFO') is structurally unsupported: tag routing and threshold routing are mutually exclusive in Pleo's current configuration, and there is no GL-code or vendor-identity dimension in the routing en …