How Precoro works

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

For a $250M technology company moving from ad-hoc Slack/email approvals with 35% maverick spend, Precoro enforces segregation of duties through a combination of distinct role-based permissions and configurable multi-step approval workflows applied to every document type across the procure-to-pay cycle. Precoro's User Roles documentation defines separate, granular roles: a Creator role lets a user generate purchase requisitions or POs but does not grant approval rights; an Approve role lets a designated approver review and act on documents created by others; a separate Receipt role covers goods/service confirmation; and a distinct Pay role enables payment document creation and is typically gr …

Limitations: Precoro's Super User role can approve any document regardless of whether that user is in the approval workflow, which creates a potential override path that administrators should govern carefully. …

Requirement evaluated: Policy compliance reporting: percentage of spend through approved channels, contract compliance rate, approval policy adherence

For a technology company coming from an email/Slack approval environment with 35% maverick spend, Precoro addresses all three dimensions of this requirement through its Spend Management and Analytics suite. For approved-channel spend visibility: <cite index="21-1">the product page documents the ability to monitor actual versus planned spend across departments, projects, and suppliers, and to spot off-policy purchases, duplications, and top spending categories using prebuilt spend and performance dashboards.</cite> For contract compliance: <cite index="29-4,29-5,29-6">procurement reports help businesses ensure purchasing activities align with company policies, dashboards show whether the comp …

Limitations: Precoro's compliance reports are constructed from a custom report builder rather than delivered as a pre-packaged scorecard with a single "% of spend through approved channels" KPI out of the box; the buyer's CFO will need to configure the relevant views using the available data points and filters. …

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

For a $250M technology company replacing ad-hoc Slack/email approvals with structured procurement controls, Precoro provides four genuinely distinct role constructs that can be mapped to each SOD touchpoint: a Creator (requester) role for submitting purchase requisitions, a configurable Approval Workflow for the approver stage, a dedicated Create Receipt role for goods/services confirmation, and a separate Payment role for recording payment. …

Limitations: The material ceiling for this buyer is that SOD is enforced by configuration policy rather than system constraint: an admin can assign the same user as both requester and approver on a document type without a platform-level block, and the Super User role creates a logged-but-unblocked override path that a compliance au …

Requirement evaluated: SOC 2 Type II certification for the platform

For a $250M technology company whose CFO is already scrutinizing spend controls and audit readiness, Precoro holds a current SOC 2 Type II certification at the application level. The certification covers all five AICPA Trust Service Criteria: security, availability, processing integrity, confidentiality, and privacy, and was issued by an external AICPA-accredited auditor rather than through self-attestation. …

Limitations: Precoro does not publicly disclose the specific audit period dates or renewal cadence for its SOC 2 Type II report, so the buyer should request the current report to confirm the coverage period is recent and verify that annual renewal is in progress. …

Requirement evaluated: Blanket PO support for contract-based spending with release tracking against the total commitment

For a $250M technology company managing contract-based vendor relationships across indirect and direct spend categories, Precoro provides a dedicated Blanket PO per Total feature. A buyer creates a blanket PO by setting a fixed total commitment amount and a validity period; <cite index="14-1,14-2">a blanket PO is a long-term agreement between an organization and a supplier involving recurring deliveries and multiple payments, and in Precoro you determine and approve a fixed total amount for the whole order without needing to specify individual items upfront.</cite> As invoices are posted against the blanket PO, <cite index="19-1,19-2">the system requires a fixed total amount to be set upfron …

Limitations: <cite index="19-5,19-6">The blanket PO total commitment amount is not pre-encumbered against departmental budgets; the budget is impacted only after an invoice is created</cite>, so real-time budget consumption lags behind the commitment ceiling by one step in the invoice cycle. …

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

For a $250M tech company currently tracking nothing beyond email-and-Slack approvals, Precoro's Purchase Orders module delivers a named, discrete status for every stage the buyer requires, all visible from the PO management list without opening individual documents. After a PO clears the approval workflow, it carries an 'Approved' status; Precoro then tracks supplier-side acknowledgment through a dedicated sending sub-status on the PO itself: 'Not Sent,' 'Sent,' 'Message Received' (supplier opened the email), and 'Confirmed' (supplier confirmed taking the order into work). …

Limitations: Supplier 'acknowledgment' is captured either via email open/confirmation tracking or through the Supplier Portal; suppliers who neither open the PO email nor use the portal will leave the PO in 'Sent' rather than 'Confirmed,' so the buyer should plan a Supplier Portal onboarding effort alongside rollout to maximize ack …

Requirement evaluated: Automatic PO generation from approved requisitions; no manual PO creation

For a $250M technology company currently creating every PO manually in NetSuite after Slack or email approvals, Precoro eliminates that manual step through a dedicated 'Automatically Create Orders from Requisitions' toggle in Configuration → Basic Settings → Documents Setup → Purchase Requisitions. Once enabled, the system fires PO creation automatically at the moment a PR clears its final approval stage — no human opens a PO form, no buyer clicks a 'create order' button. …

Limitations: The automatic PO generation fires only for line items that have a supplier already specified on the PR: <cite index="1-9,1-10">only items with a specified supplier are added to the automatically created PO, and if a PR contains even one item without a supplier, the PO is only generated after a supplier is selected for …

Requirement evaluated: PO templates for recurring purchases (monthly facilities services, quarterly IT maintenance)

For a $250M technology company whose ops team currently re-enters every recurring PO by hand in NetSuite, Precoro offers a native recurring PO feature that directly eliminates that manual cycle. <cite index="9-5">Users can create a Recurring Purchase Order from scratch or convert one of their existing Purchase Orders.</cite> <cite index="1-2,1-4,1-6">The user opens the PO they want to make recurring, presses the "Make Recurring" button on the right action panel, selects a Validity Period and Repeat Frequency, and assigns budgets for future recurring documents.</cite> <cite index="9-15,9-16">Recurring Orders solve the problem of manually creating and sending repeated documents to suppliers, a …

Limitations: <cite index="9-6,9-7">A PO cannot be made recurring if it has any related documents already entered, meaning POs previously created from requisitions cannot be set to recur</cite>; this buyer's ops team will need to initiate recurring POs as standalone documents rather than converting requisition-linked POs. …

Requirement evaluated: Matched invoices push to NetSuite AP for payment processing (or integrate with our AP automation tool)

For a NetSuite shop like yours that currently manually creates AP records, Precoro's native two-way NetSuite integration handles this requirement directly. <cite index="6-2,6-3,6-4,6-5">Precoro's AI turns supplier invoices of diverse formats into structured documents, matches them to approved POs, and then automatically syncs approved transactions with NetSuite, eliminating duplicate entries.</cite> On the AP push specifically: <cite index="10-12,10-15">invoices land in NetSuite under Transactions → Payables → Enter Bills → List, and once an invoice is created in Precoro, it is sent to NetSuite automatically.</cite> The trigger is approval status: <cite index="2-12">when the document acquire …

Limitations: <cite index="2-13,2-14">Invoice field synchronization operates one-way (Precoro to NetSuite); changes made in NetSuite after the push are not transferred back into Precoro</cite>, so any post-push edits must be managed in NetSuite directly. …

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

For a $250M technology company replacing email-based procurement and needing its NetSuite master data available in Precoro without manual re-entry, Precoro's NetSuite integration covers all eight dimension types the buyer specified. Each dimension has a dedicated import mechanism on the NetSuite Integration page: <cite index="1-27,1-32,1-33">chart of accounts are imported from NetSuite into Precoro via an "Import Chart of Accounts" button, with the user selecting which accounts to pull in.</cite> <cite index="5-3">Classes, Locations, and Departments can each be integrated both as Custom Fields for Items and as Custom Fields for Documents.</cite> <cite index="3-3">Customers and Projects are i …

Limitations: <cite index="1-12,1-13,1-14">All master data sync (chart of accounts, departments, classes, locations, items, projects, vendors) is one-way: changes made in Precoro are not written back to NetSuite; only changes made in NetSuite propagate to Precoro after a data update.</cite> Additionally, <cite index="23-48,23-49,23- …

Requirement evaluated: SSO via Okta (our identity provider)

For a 450-person technology company running Okta as its identity provider, Precoro provides a dedicated, step-by-step Okta SSO setup guide in its help center, confirming Okta is an explicitly named and supported IdP. <cite index="8-1">Precoro can integrate with any identity provider that supports the SAML 2.0 protocol</cite>, and Okta is called out by name with its own configuration article. <cite index="9-1,9-2,9-6,9-7">The admin opens Okta, creates a new SAML App Integration, then maps Precoro's SSO configuration tab fields: Single Sign-On URL to Assertion Consumer Service (ACS), and Audience URI (SP Entity ID) …

Limitations: No SCIM 2.0 automated provisioning or deprovisioning documentation was found in Precoro's help center: the Keycloak guide notes that deleting or disabling a user in the IdP does not remove them from Precoro (they simply cannot log in), meaning IT will still need to manually offboard departing employees in Precoro itsel …

Requirement evaluated: Contract repository: store agreements, track renewal dates, alert stakeholders 90/60/30 days before expiration

For a $250M technology company managing 800+ vendors today with no centralized contract visibility, Precoro's Contract Management module (inside the Supplier Management section) directly addresses this requirement. Users create a contract record, attach the agreement file, and populate an expiration date; the system then lets them configure an Expiration Date Reminder set to 30, 60, 90, 120, 150, or 180 days before expiry, which maps precisely to the buyer's requested 90/60/30-day cadence. …

Limitations: The buyer must manually enter the expiration date and configure the reminder for each contract; there is no documented AI extraction of renewal dates from uploaded agreement text. Notification granularity is fixed to preset intervals (30, 60, 90, 120, 150, 180 days) …

Requirement evaluated: Rate card management: contracted pricing loaded into the system so PO prices auto-validate against the agreement

This $250M tech company needs contracted pricing loaded against specific vendors so that PO line prices are automatically validated against the agreement, not just tracked. Precoro's approach assembles this capability from three intersecting mechanisms rather than a single dedicated rate-card module. First, the internal catalog stores approved items with fixed prices and SKUs; administrators can enable 'Restrict Catalog Items Editing' to lock the Price, Currency, and Unit fields so requesters cannot override contracted rates when adding catalog items to PRs or POs (from Precoro help.precoro.com/how-to-set-up-a-purchase-requisition-module). …

Limitations: Precoro has no native rate-card object that stores contracted per-item prices tied to a supplier agreement and auto-validates PO line prices against those rates at order creation; the catalog price-lock plus tolerance-rate mechanism is a workaround that requires manual catalog maintenance and does not prevent a buyer f …

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

For a $250M technology company trying to eliminate ad-hoc vendor onboarding, Precoro offers a documented Supplier Approval Workflow that covers most of the required chain, but breaks down on the conditional IT security gate. At intake, an admin or procurement user sends a Supplier Registration Form via email to the prospective vendor; <cite index="2-5,2-6">the Supplier Registration feature lets you send personalized emails and forms to receive information on cooperation terms from potential vendors.</cite> Once the vendor submits the form, it enters Precoro's Supplier Approval Workflow: <cite index="1-1,1-2">users open the Approval Workflow under Supplier Approval Workflow, create new steps, …

Limitations: The Supplier Approval Workflow applies a single uniform approval chain to all new vendors; there is no documented conditional branching that would include an IT security review step only for software vendors and skip it for non-software vendors, meaning the buyer would need to either route all vendors through the IT se …

Requirement evaluated: Spend dashboards: real-time spend by vendor, category, department, location, and period

This buyer is moving from a zero-visibility state (35% maverick spend, email-based approvals, manual NetSuite PO entry) to a system that needs to surface spend across vendor, category, department, location, and period in real time. Precoro's Spend Management module delivers exactly this dimension set: <cite index="1-1">the platform lets users explore spending by category, supplier, department, and location to understand financial flow in depth,</cite> and <cite index="4-9">provides real-time spend tracking by department, project, or location so finance teams gain full visibility into where every dollar is going.</cite> The reporting engine is the primary mechanism: <cite index="12-24">users …

Limitations: The dashboard operates on procurement data captured inside Precoro; any spend that continues to flow outside the system (legacy email POs, direct card purchases not submitted as expense reimbursements) will remain invisible until the buyer achieves full adoption. …

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

For a $250M technology company trying to identify 800+ vendors ripe for consolidation, Precoro's Reports module captures supplier name, document totals, dates, and document counts across POs and invoices, all exportable to XLSX. Precoro's own help documentation for spend-by-supplier analysis instructs users to export the item report, copy the data into a Google spreadsheet, and build a pivot table there — this is the documented mechanism for granular supplier segmentation, not a native in-platform view. …

Limitations: Precoro does not offer a native tail spend segmentation tool: the platform captures the underlying transaction data but surfaces it only through per-document-type custom reports that must be exported and pivoted in a spreadsheet to produce the high-count/low-value vendor segmentation this buyer needs. …

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

For a $250M technology company replacing email/Slack approvals and trying to eliminate 35% maverick spend, Precoro operates at the purchase requisition intake stage: employees create PRs by selecting items from a pre-built, admin-controlled catalog loaded with contracted prices, SKUs, and supplier assignments. <cite index="6-25,6-26,6-28,6-29">Precoro lets you organize supplier products into easy-to-use catalogs, create catalogs of approved items with images, prices, and SKUs, and sort or filter items by location, project, or department so teams don't waste time sifting through things they don't buy.</cite> A 'Restrict Catalog Items Editing' setting locks requester modifications to catalog-s …

Limitations: Precoro's catalog eliminates off-contract buying by restricting employees to pre-approved items, but it does not display an on-contract vs. off-contract savings comparison inline at search time: the buyer's specific requirement for search results that show preferred options first with savings vs. …

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

This $250M tech company needs employees across four US offices and a Canadian development center to browse pre-approved spend categories visually, without knowing item names or SKUs upfront. Precoro's internal catalog module allows admins to load approved items with images, prices, and SKUs, and items can be grouped using an 'Item Groups' feature and tagged with categories via a custom drop-down field. …

Limitations: Precoro's catalog navigation is a filter-on-a-list model, not a category-tile or hierarchical browse model: employees must open a document first and then narrow a flat item list by category filter, which is materially different from the 'category-based shopping with visual interface' the buyer specified. …

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

Your field team members at job sites can submit purchase requisitions directly from Precoro's native iOS and Android mobile app, available on both the App Store and Google Play. <cite index="15-4,15-5,15-6">The Precoro mobile app allows users to work effectively even when away from their PC; leading actions explicitly include creating purchase requisitions, purchase orders, and receipts, as well as approving or rejecting documents with a single click.</cite> <cite index="2-2,2-3">The App Store listing confirms field users can "create purchase requests, POs, and receipts from the palm of your hand" and approve or reject documents with a single click.</cite> The mobile app also supports attach …

Limitations: Precoro's own product page notes that <cite index="1-26,1-27">the mobile procurement platform provides key features of the web version but not all web version functionalities are available yet, with active work underway to expand capabilities.</cite> There is no documented offline mode, which could be a friction point …

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

For a 450-person tech company whose employees currently submit ad-hoc purchase requests over Slack and email, Precoro replaces that unstructured flow with a dedicated Purchase Requisition (PR) module designed around a scoped employee experience. <cite index="09641a3c-f2c7-4ecb-859f-2ab9982e4103">Employees are guided step by step through a smart intake form that captures purchase and vendor data right at the request stage.</cite> Admins configure a restricted "Creator" role so requesters see only the PR module: <cite index="16-38,16-39">roles limit which modules and features employees see, so they will only encounter the parts of Precoro they actually use, with no confusing options or complic …

Limitations: Precoro's intake layer is a purpose-built procurement module, not a fully abstracted consumer-app interface: employees open a left-nav menu, click "Create," and select a form type, which requires at minimum a brief orientation to the tool. …

Requirement evaluated: Our specific rules: under $1,000 auto-approved against budget, $1,000-$10K department head, $10K-$50K VP, $50K-$100K VP + Finance, over $100K VP + Finance + CFO

This $250M technology company needs a five-tier dollar-threshold approval chain, including auto-approval under $1,000, single approver at $1K-$10K, escalating to a three-party requirement (VP + Finance + CFO) above $100K. Precoro's Approval Workflow module, configured under Configurations > Approval Workflow, directly supports this structure. Administrators define each approval step and set per-approver dollar thresholds using 'From,' 'From To,' and 'Less or equal' range conditions; for example, a department head approver can be scoped to documents from $1,000 to $10,000, a VP approver from $10,000 to $50,000, and so on, with documents below $1,000 bypassing all steps via the 'Less or equal' …

Limitations: The auto-approval for sub-$1,000 purchases is conditional on the Approval Review feature being configured so that documents falling outside any defined threshold range do not silently bypass the workflow; admins must ensure the 'Less or equal $999' condition is explicitly set and budget validation is active. …

Requirement evaluated: Simple receipt confirmation workflow: designated receiver confirms delivery with quantity, condition, and date

For this $250M technology company replacing an email/Slack approval process, Precoro delivers receipt confirmation through a dedicated Receipts module with its own scoped user role. <cite index="13-32,13-33">A receipt is a document confirming delivery and listing items and their quantities; assigned people can make receipts after inspecting delivered goods.</cite> The workflow is receiver-driven, not AP-driven: <cite index="19-6">only users with Create Receipt Roles can access the 'Purchase Order is waiting for Receipt' notification letter</cite>, meaning an office manager, warehouse staff, or IT asset owner can be designated as a receiver without being given full procurement or invoice acce …

Limitations: Condition/quality status (e.g., accepted, damaged, rejected) and an explicit receiver-entered actual delivery date are not native out-of-the-box fields on the receipt form; the buyer would need to configure custom fields for receipts to capture these, adding a setup step that most buyers can handle but that is not zero …