Every charge. Verified with AI.

Pleaxy checks every supplier invoice against your contract rates, purchase orders and cloud usage - and holds what doesn't match before you pay.

Get started Talk to us

Already using Pleaxy? Sign inSee pricing

Invoices · Pleaxy

PLEAXY

US East · Buyer

Dashboard

Approvals

Purchase orders

Invoices

Suppliers

Contracts

Invoices

AllAWSAzureGCP

Invoice	Amount	Match
Amazon Web Services (AWS) INV-7712	$48,120	Matched
Northwind Data INV-7751	$28,410	Discrepancy
Google Cloud INV-7760	$41,365	Matched
Oracle Cloud Infrastructure (OCI) INV-7768	$12,430	Pending

$6,482

Potential overcharge

Northwind Data INV-7751 · billed above the contract rate

SDK & API

TScreate-po.ts

1await pleaxy.purchaseOrders.create({2  supplier: "AWS",3  provider: "aws",4  lineItems: [{5    scopeType: "account",6    ruleType: "amount",7    nteAmount: 50_000,8    validFrom: "2026-09-01",9    validUntil: "2026-09-30",10  }],11});

201 Created· POST /v1/…/purchase-orders

1{2  "id": "PO-8842",3  "supplier": "AWS",4  "amount": 50000,5  "currency": "USD",6  "status": "pending_approval"7}

1const pos = await pleaxy.purchaseOrders.list();2const waiting = pos.filter((po) =>3  po.status === "pending_approval",4);

Sending…· GET /v1/…/purchase-orders

1[2  { "id": "PO-8851", "supplier": "Figma",3    "amount": 14000, "status": "pending_approval" },4  { "id": "PO-8853", "supplier": "Northwind Data",5    "amount": 18000, "status": "pending_approval" }6]

1const result = await pleaxy.invoices.runMatch(2  "INV-7730"3);4if (result.matchStatus === "discrepancy") {5  // Held for one reviewer before approval6}

Sending…· POST /v1/…/invoices/{id}/run-match

1{2  "id": "INV-7730",3  "po": "PO-8836",4  "supplier": "Beacon Metrics",5  "amount": 12400,6  "matchStatus": "discrepancy",7  "discrepancyReason": "amount"8}

1// Preview: paying through Pleaxy isn't live yet2await pleaxy.invoices.getStripePayment(3  "INV-7745"4);5// A person signed in pays it with Stripe

Sending…· GET /v1/…/invoices/{id}/stripe-payment

1{2  "available": true,3  "quote": {4    "amount": 18000,5    "fee": 5,6    "total": 18005,7    "currency": "USD"8  }9}

Examples

Created PO-8842 and routed it to Manager and Finance. The invoice landed Oct 1:

AWS · Invoice INV-7712 · September

Invoiced: $48,120
Metered usage: $47,5401.2% under · within tolerance
Purchase order: $50,000Within budget

Auto-matched · approved · due Oct 31

Two purchase orders are at your stage. Tell me which to approve and I'll confirm before I do.

PO-8851 · Figma: $14,000Waiting 1 day
PO-8853 · Northwind Data: $18,000Waiting 3 days

2 waiting on you

It doesn't match. It's billed well above the purchase order:

Beacon Metrics · Invoice INV-7730

Invoiced: $12,400
Purchase order: $10,00024% over · outside tolerance

Held · flagged for one reviewer

Preview: not live yet

That matches the approved invoice, amount and supplier, so it's ready to pay. Open it and choose Pay with Stripe: you pay by bank transfer and cover Stripe's fee, so Northwind Data receives the full amount.

Northwind Data · Invoice INV-7745

Invoice: $18,000
Bank transfer fee: $5Stripe's fee, covered by you

Ready for you to pay with Stripe

Web app

Purchase orders · Pleaxy

PLEAXY

US East · Buyer

Dashboard

Approvals

Purchase orders

Invoices

Suppliers

Contracts

Purchase orders

Waiting on you	Amount	Waiting
Northwind Data PO-8853	$18,000	3 days
Figma PO-8851	$14,000	1 day

ApproveRejectYou confirm each one

Invoice	Amount	Match
Amazon Web Services (AWS) INV-7712	$48,120	Matched
Beacon Metrics INV-7730	$12,400	Discrepancy
24% over PO-8836Held for review

PO	Amount	Status
Northwind Data PO-8853	$18,000	Pending approval
Figma PO-8851	$14,000	Pending approval
Amazon Web Services (AWS) PO-8842	$50,000	Invoiced
INV-7712· $48,120Reconciled
Beacon Metrics PO-8836 INV-7730 · Discrepancy	$10,000	Invoiced

Works with

Plugs into what you already use. Nothing to migrate.

Cloud billing, read-only
- AWS
- Google Cloud
- Azure
- OCI
Invoices
- PDF
- UBL
- cXML

Pleaxy

Claude
Codex
Any MCP agent

How it works

Every step is an API call your code or agent can make - from connect to settled.

Connect
Northwind, a supplier, joined free. Your cloud billing is linked read-only: Amazon Web Services (AWS), Google Cloud, Microsoft Azure or Oracle Cloud Infrastructure (OCI).
N
Northwind
Joined free
Your billing · read-only
AWS
Google Cloud
Azure
OCI
Invite sent
Invite any supplier - software, services, contractors - and they onboard free. Link read-only billing for Amazon Web Services (AWS), Google Cloud, Microsoft Azure or Oracle Cloud Infrastructure (OCI), and revoke it anytime.
- supplier_connections.create
Order and route
PO-8842, $50,000, raised via the SDK. The manager approved it, then Finance. POs under $10k approve automatically.
PO-8842$50,000
Manager Approved
FinancePending Approved
Auto-approves under $10k
Raised via SDK
Raise POs from code, the SDK, or agent chat. Approval chains decide who signs, anything under your approval threshold auto-approves, and the supplier gets the PO.
- purchase_orders.create
Match
AWS sent INV-7712 for $48,120. Your usage was $47,540, 1.2% under, within tolerance. Matched.
Suppliers invoice from the PO or enter one in Pleaxy, and your team can record cXML, UBL, or PDF invoices too. Each is matched to its PO, cloud invoices to usage too; out-of-tolerance ones go to one reviewer.
- invoices.run_match
Pay and chase
AWS INV-7712, $48,120. Your agent nudged Finance, Finance approved it, and it pays Thursday, a day before it's due Friday.
Approved invoices go to your payment run on your schedule, and your agent nudges whoever's holding one up. Suppliers see where each invoice is and when a payment has been recorded.
- invoices.record_payment

The problems we're here to fix

Complex spend creates expensive mistakes. Pleaxy catches them.

Pleaxy connects what you agreed to, what you used, what you were billed and what you paid - finding discrepancies before payment and keeping buyers and suppliers looking at the same invoice. Each conversation plays as you reach it; send a question yourself to take over.

Paying more than you agreed to
- Buyers
The problem
Contract rates, negotiated discounts, credits and pricing changes don't always make it onto the final invoice. When thousands of line items are involved, small discrepancies can quietly become significant overpayments.
How Pleaxy helps
Pleaxy checks every invoice line against the rate in your contract and the PO it bills - holding anything priced above what you agreed before it's paid, and showing which term it broke.
Pleaxy Assistant
Procurement · Buyer
Buyer: Check Northwind Data's September invoice against our contract.
Assistant:
It doesn't match. INV-8120 bills 1,400 credits at $3.00, but your contract rate is $2.60 - $560 more than you agreed to. It's held before payment.
Buyer: Ask Northwind Data for a corrected invoice.
Assistant:
Sent. INV-8120 stays on hold, and Northwind Data sees the contract rate and the $560 difference behind it.
Assistant: Hi! Here's how I handle this one.
Invoices that don't match actual usage
- Buyers
The problem
Usage-based services make invoices difficult to verify. The invoice may be mathematically correct while the underlying quantities, tiers, rates or commitments are not.
How Pleaxy helps
Connect your cloud billing read-only and Pleaxy compares each cloud invoice with the metered usage behind it - holding the invoice for review when the two don't agree.
Pleaxy Assistant
Procurement · Buyer
Buyer: Does Cirrus Cloud's September invoice match our usage?
Assistant:
No. INV-7790 bills $18,620, but your metered usage for September comes to $14,300 - $4,320 more than you used, so it's held for review.
Buyer: What's behind the extra $4,320?
Assistant:
Nothing in your account's metered usage accounts for it. The invoice stays with the reviewer, alongside the usage figures, until Cirrus Cloud explains or corrects it.
Assistant: Hi! Here's how I handle this one.
Invoices with no PO - or not enough PO
- Buyers
- Suppliers
The problem
An invoice arrives before a PO is created, or the remaining PO balance isn't enough to cover it. The invoice gets blocked, approvals restart and payment is delayed.
How Pleaxy helps
Pleaxy draws down every PO as invoices land against it, so you always know what's left - and your agent can tell you when the next invoice won't fit, while there's still time to raise another PO.
Pleaxy Assistant
Procurement · Buyer
Buyer: Is PO-8842 ready for AWS's October invoice?
Assistant:
Not yet. PO-8842 has $4,200 left, and AWS billed $47,900 for September - an October invoice that size would go over the PO and be held.
Buyer: Raise a PO to cover October.
Assistant:
Raised PO-8903 for $50,000 and routed it to Manager and Finance. Once approved it goes to AWS - weeks before their October invoice, so it lands on a PO that can take it.
Assistant: Hi! Here's how I handle this one.
Rejected invoices suppliers discover too late
- Buyers
- Suppliers
The problem
An invoice is rejected or blocked on the buyer's side, but the supplier may not know there's a problem until payment fails to arrive - adding days or weeks to resolution.
How Pleaxy helps
Pleaxy makes invoice status and rejection reasons visible, so buyers and suppliers can identify the issue, resolve it and resubmit without waiting for another payment cycle.
Pleaxy Assistant
Accounts receivable · Supplier
Assistant: Hi! Here's how I handle this one.

See everything Pleaxy checks

For suppliers

Invited by a customer? Joining is free.

Receive their POs, invoice straight from them, and see where every invoice stands - including why one was rejected - without chasing anyone.

How it works for suppliers

Built agent & SDK first - for buyers and suppliers

If you're on the buyer side - the team purchasing cloud spend - integrate the SDK or point an MCP-compatible agent at Pleaxy to create purchase orders, reconcile invoices against metered usage, and manage approvals without a portal.

If you're on the supplier side - invoicing that spend - connecting costs nothing: receive POs, flip them to invoices, and let approved invoices settle on schedule.

import { Pleaxy } from "@pleaxy/sdk";

const pleaxy = new Pleaxy({
  baseUrl: "https://api.pleaxy.ai",
  apiKey: process.env.PLEAXY_API_KEY,
  workspaceId: process.env.PLEAXY_WORKSPACE_ID,
});

// Called by the buyer's own code or agent - "supplier" is the
// counterparty you're purchasing from.
const po = await pleaxy.purchaseOrders.create({
  supplier: "Amazon Web Services",
  provider: "aws",
  lineItems: [
    {
      scopeType: "sku", scopeId: "AWS-EC2-M5LG",
      name: "EC2 m5.large", ruleType: "quantity",
      unit: "hr", unitPrice: 0.096, qty: 5_000,
      nteAmount: 0, paymentTerms: "Net 30",
      validFrom: "2026-01-01", validUntil: "2026-12-31",
    },
  ],
});

// Once the supplier invoices against the PO:
const invoice = await pleaxy.invoices.runMatch(invoiceId);
// invoice.matchStatus === "matched" once reconciled
// against metered usage.

Get API keys Read the docs

For buyers

Create & approve POs by API, SDK, or agent chat
Auto-match invoices against metered usage
Fixed API pricing - no percentage of spend

For suppliers

Receive POs and flip them to invoices instantly
100% free - no subscription, no licensing
Ask your agent to chase down a pending approval

Skip the code too - talk to your agent

Every Pleaxy action is also exposed over MCP, so any MCP-compatible assistant - Claude, an internal ops bot, whatever your team already runs - can create POs, run invoice matching, and chase approvals with the same permissions as your API key. No new UI to learn, on either side.

Pleaxy Assistant

Procurement · Buyer

Raise a $50,000 AWS PO for September and match the invoice to metered usage when it lands.

Created PO-8842 for $50,000 against AWS - routed to Manager and Finance since it's over your $10,000 auto-approve threshold.

INV-7712 landed Oct 1. AWS invoiced $48,120, metered usage came in at $47,540 - 1.2% under and within tolerance, so it auto-matched and was approved without a review. Scheduled to pay Oct 31.

Pleaxy Assistant

Accounts receivable · Supplier

Which of our invoices are stuck waiting on buyer approval?

Two: INV-S-551 with Globex Inc, pending 6 days, and INV-S-498 with Umbrella Labs, pending 2 days. Want me to nudge Globex?

Yes, send it.

Sent. I'll nudge again in 24h if it's still pending.

Works with Claude and any MCP clientSame auth as the API - scoped API keysRead the MCP setup guide →

Built for how you actually ship

A few lines of code cover what used to be a portal, a form, and an email thread.

Build a line-item PO against a cloud provider's public price list - no portal, no forms.

import { Pleaxy } from "@pleaxy/sdk";

const pleaxy = new Pleaxy({
  baseUrl: "https://api.pleaxy.ai",
  apiKey: process.env.PLEAXY_API_KEY,
  workspaceId: process.env.PLEAXY_WORKSPACE_ID,
});

// Called from the buyer's side - "supplier" is who you're
// purchasing from.
const po = await pleaxy.purchaseOrders.create({
  supplier: "Amazon Web Services",
  provider: "aws",
  lineItems: [
    {
      scopeType: "sku",
      scopeId: "AWS-EC2-M5LG",
      name: "EC2 m5.large",
      ruleType: "quantity",
      unit: "hr",
      unitPrice: 0.096,
      qty: 5_000,
      nteAmount: 0,
      paymentTerms: "Net 30",
      validFrom: "2026-01-01",
      validUntil: "2026-12-31",
    },
  ],
});

// po.status === "awaiting_fulfillment" once approved

Available in your language

Every SDK is generated from the same OpenAPI spec that powers the API Reference, so they stay in lockstep with the API - pick the five we maintain directly, or generate a client for anything else.

TypeScriptOfficial

@pleaxy/sdk

PythonOfficial

pleaxy-python

GoOfficial

pleaxy-go

JavaOfficial

pleaxy-java

RubyOfficial

pleaxy-ruby

View install instructions & quickstarts →

Stop paying for charges nobody checked.

Connect your suppliers and contracts, and let Pleaxy hold what doesn't match before it's paid.

Get started See pricing Talk to us

Every charge. Verified with AI.Every charge. Verified with AI.

Works with

How it works

Connect

Order and route

Match

Pay and chase

The problems we're here to fix

Paying more than you agreed to

Pleaxy Assistant

Invoices that don't match actual usage

Pleaxy Assistant

Invoices with no PO - or not enough PO

Pleaxy Assistant

Rejected invoices suppliers discover too late

Pleaxy Assistant

Invited by a customer? Joining is free.

Built agent & SDK first - for buyers and suppliers

For buyers

For suppliers

Skip the code too - talk to your agent

Pleaxy Assistant

Pleaxy Assistant

Built for how you actually ship

Available in your language

Stop paying for charges nobody checked.

Every charge. Verified with AI.