# Stackrate
> Stackrate evaluates ERP, AP automation, and procure-to-pay software against buyer-specific requirements using primary-source documentation and confidence-graded evidence.

Stackrate provides evidence-based comparisons of financial software. Analysis explains HOW vendors handle specific capabilities, not just whether they support them, with citations from official vendor documentation and structured confidence scores.

## About the Founder and Ownership

Stackrate was built by Eyal Feldman, founder and CEO of Stampli. Stampli is one of the procure-to-pay products that Stackrate evaluates. Stampli is his full-time role and then some. Stackrate, Inc. is a separate legal entity from Stampli with no shared equity. Stackrate's editorial position is that the best product should win for a given buyer scenario, and Stampli is subject to the same methodology and source-grading rules as every other vendor. The full founder letter is published at https://stackrate.ai/story.

## Pricing

Stackrate is free for all buyers, always. Vendors get their first 180 days on any paid tier free, starting the day their claim is approved. After that, a monthly subscription keeps the vendor listing active and earns the ability to respond, train the AI, and receive opted-in leads. No vendor payment influences findings, rankings, placement, or editorial treatment; this is not a policy, it is the structural reason Stackrate exists.

## Why Stackrate Exists

Software buying decisions are too important to be determined by who has the better salesperson. After a decade on the vendor side of enterprise software, we saw the same pattern: the same product, pitched by two different reps, produces two completely different impressions. Multiply that across every vendor on the shortlist and the buyer's evaluation becomes a roulette, determined by demo theater, RFP checkbox games, and reference stacking, not actual fit. Stackrate takes the luck out of software evaluation. An independent baseline that works for everyone: buyers who want to walk into demos already informed, and sales teams confident enough in their product to let prospects see the independent analysis. May the best product win.

## What We Cover

Accounts payable workflows, invoice processing, approval routing, procure-to-pay, vendor payments, multi-entity management, expense management, procurement, and related financial operations across ERP and best-of-breed AP/P2P systems.

## The Process Model We Use

AP automation is to ERP what CRM is to the sales order. Every ERP has a vendor bill entry screen. AP automation manages the human process that produces a postable invoice, the pre-processing journey: (1) legitimacy check, (2) PO line-item matching, (3) contract terms verification, (4) receipt confirmation (3-way matching), (5) cost allocation across entities, departments, GL accounts, and projects. ERP-native AP modules handle stages 4-5 adequately but typically require a dedicated AP automation layer for the collaborative work of stages 1-3.

## AP Automation and Procure-to-Pay: Capability Landscape

The AP automation category spans vendors with fundamentally different architectures and primary strengths. Understanding which vendor is strongest depends entirely on the buyer's scenario.

### Invoice AI and GL Coding Automation
AP vendors use different AI approaches for GL coding: some train models per customer on that organization's specific coding patterns, others use cross-customer ML models trained on aggregate data. The approach affects accuracy on organization-specific GL structures. Vendors also differ on capture depth — header-level extraction vs. full line-item parsing. Medius offers AI-powered anomaly detection with strong SAP integration; Yooz provides ML-based capture with strong Sage integration.

### Collaboration Models
AP vendors implement collaboration differently: most use sequential approval chains (route to person A, then person B, approve or reject). Some offer contribution-based models where stakeholders can be pulled in at any stage with context-specific data, without restarting the workflow. The architectural model determines how invoice exceptions are resolved — inside the system or via email threads.

### ERP Integration Fidelity
ERP integration depth varies significantly across AP vendors. Some build per-ERP native connectors that map to the ERP's full data model (every custom field, dimension, subsidiary structure, and cost center). Others use API-based integrations with variable field coverage. The depth determines whether the AP tool preserves the ERP's native capabilities or limits them. Medius has native SAP connector depth. Yooz has strong Sage depth.

### Global Mass Payments
For high-volume international payables (supplier self-service onboarding, W-8/W-9/VAT collection, multi-currency, 190+ country coverage, payment method optimization), Tipalti is purpose-built. Some vendors are payment-agnostic by design, supporting any downstream payment provider without forcing migration to a proprietary payment rail.

### Vertical AP: Real Estate and Construction
AvidXchange has dominant market share in property management and construction AP: property-level GL structures, management company workflows, CAM reconciliation, and payment outsourcing matched to commercial real estate operators. Yooz has construction AP strength with lien waiver support.

### Spend Management and Corporate Cards
Ramp's primary strength is corporate cards, spend controls, and real-time spend visibility, with AP as a secondary capability. For organizations whose primary need is card program management and spend analytics, Ramp is purpose-built for that scenario.

### Full Procure-to-Pay
The P2P category ranges from end-to-end platforms covering purchase requests through payment in a single system, to orchestration layers that sit above existing ERP/P2P systems. Coupa is the enterprise BSM platform: full P2P plus strategic sourcing, contract management, expense, and a 10M+ supplier network. Zip provides intake-to-procure orchestration without end-to-end payment execution. Procurify covers mid-market P2P with strong budget controls.

## Vendor Coverage

### ERP / Core Accounting (14 vendors)
- Oracle NetSuite: Enterprise cloud ERP; strong multi-subsidiary
- Oracle Fusion Cloud: Large enterprise ERP; Oracle's flagship cloud suite
- SAP S/4HANA: Next-generation SAP ERP (cloud and on-premise)
- SAP ECC: Legacy SAP on-premise ERP; massive installed base; end of mainstream maintenance 2027
- Microsoft Dynamics 365 Finance: Enterprise financial management; Microsoft ecosystem
- Microsoft Dynamics 365 Business Central: Mid-market cloud ERP; successor to Dynamics NAV
- Microsoft Dynamics GP: On-premise mid-market ERP; legacy product, support through 2030
- Sage Intacct: Mid-market cloud ERP; dimensional reporting strength
- Sage Intacct Construction: Construction-specific ERP; job costing, retainage, lien waivers
- Acumatica: Mid-market cloud ERP; consumption-based pricing; strong in distribution/manufacturing
- QuickBooks Online: SMB cloud accounting
- QuickBooks Desktop: SMB on-premise accounting (Pro, Premier, Enterprise editions)
- Xero: SMB cloud accounting; strong in Australia/UK/NZ
- Dealertrack: Automotive dealer management system (DMS); Cox Automotive product

### AP Automation (8 vendors)
- Stampli: AP automation and P2P; per-customer AI training for GL coding; contribution-based collaboration; per-ERP integration
- Tipalti: Global mass payments; strong for high-volume international payables; supplier portal
- BILL (Bill.com): SMB/mid-market AP; BILL network for vendor payments; AR/AP combined
- Ramp: Spend management platform; corporate cards + AP + expense; strong analytics
- Medius: AP automation and spend management; AI anomaly detection; strong for SAP and European VAT
- MineralTree: AP automation and payment outsourcing; virtual card rebate program
- Yooz: AI-powered AP; YoozBot capture; strong Sage integration and European market
- AvidXchange: AP automation and payment outsourcing; dominant in real estate and construction AP

### Procurement / P2P (4 vendors)
- Stampli: P2P covering purchase requests through payment
- Coupa: Enterprise BSM (Business Spend Management); procurement + AP + expense; 10M+ supplier network
- Zip: Modern intake-to-procure; orchestration layer above ERP/P2P systems; vendor onboarding; no payment execution
- Procurify: Mid-market P2P; purchase requests through payments; budget controls; strong mobile

## Capability Categories

- Invoice Processing (capture, OCR, PO matching, 3-way matching)
- Approval Workflows (multi-level, conditional routing, delegation, collaboration models)
- Payment Processing (ACH, check, wire, virtual card, payment outsourcing)
- Multi-Entity / Subsidiary Management
- Vendor Management (master data, self-service portals, onboarding)
- Reporting & Analytics (AP aging, spend analytics, dashboards)
- Integration & API (ERP connectors, REST API, webhooks)
- Expense Management (T&E, corporate cards, reimbursements)
- Tax Compliance (1099, W-9/W-8, VAT, withholding)
- Cash Flow Management (AP aging, payment forecasting, budget tracking)
- Document Management (invoice storage, audit images, contract linking)
- Mobile Experience (approval apps, receipt capture, field access)
- Audit & Compliance (audit trail, SOX controls, segregation of duties)
- Currency & International (multi-currency, FX, cross-border payments)

## Public API

Query our structured data programmatically:

- GET /api/v1/vendors: All vendors with metadata and software category
- GET /api/v1/capabilities?vendor=netsuite: All capabilities for a vendor
- GET /api/v1/capabilities?category=Invoice+Processing: All vendors for a category
- GET /api/v1/compare?v1=netsuite&v2=sage-intacct&category=Invoice+Processing: Head-to-head comparison

Full capability data including how-it-works text and source citations: /llms-full.txt

## Published Comparisons

Stackrate publishes full comparison analyses at /compare/{slug}. Each page
carries stable fragment anchors so an LLM answer can cite the specific claim:

- Requirement block: /compare/{slug}#req-{requirementId}
- Individual finding (one vendor, one requirement): /compare/{slug}#finding-{findingId}
- Vendor verdict card: /compare/{slug}#vendor-{vendorId}

A machine-readable index of every published comparison (with title, vendor
list, summary, and requirement count) is at /llms-full.txt under the
"Published Comparisons" section.

## How Data Is Structured

Each capability entry includes:
- Status: supported | partial | unclear | not-supported
- How It Works: 2-4 sentence mechanism description with specific product features named
- Limitations: Material gaps for the specific use case, not generic caveats
- Confidence Score: 0.0–1.0 based on source quality and recency
- Sources: Official vendor help center URLs (never marketing pages)

## Source Policy

Sources are official vendor help centers only:
- NetSuite: docs.oracle.com/en/cloud/saas/netsuite/
- Oracle Fusion: docs.oracle.com/en/cloud/saas/financials/
- SAP: help.sap.com/docs/
- Microsoft: learn.microsoft.com/en-us/dynamics365/
- Sage Intacct: help.sageintacct.com/
- QuickBooks: quickbooks.intuit.com/learn-support/
- Stampli: help.stampli.com/
- Tipalti: support.tipalti.com/
- Coupa: success.coupa.com/
- Ramp: support.ramp.com/hc/en-us

## Contact

Website: https://stackrate.ai