Every charge. Verified with AI.

Pleaxy understands your contracts, rates, discounts, credits, POs and usage to determine what you should pay — and flags when what you're charged doesn't match.

Read the docs

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
Microsoft Azure 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

Microsoft Azure INV-7751 · usage exceeds 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": "Snowflake",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": "Datadog",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

Agent: 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

purchase_orders.create
invoices.run_match

Agent: 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 · Snowflake: $18,000Waiting 3 days

2 waiting on you

purchase_orders.list

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

Datadog · Invoice INV-7730

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

Held · flagged for one reviewer

invoices.run_match

Preview: not live yet

Agent: 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 Snowflake receives the full amount.

Snowflake · Invoice INV-7745

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

Ready for you to pay with Stripe

invoices.list

Web app

Purchase orders · Pleaxy

PLEAXY

US East · Buyer

Dashboard

Approvals

Purchase orders

Invoices

Suppliers

Contracts

Purchase orders

Waiting on you	Amount	Waiting
Snowflake 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
Datadog INV-7730	$12,400	Discrepancy
24% over PO-8836Held for review

PO	Amount	Status
Snowflake 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
Datadog PO-8836 INV-7730 · Discrepancy	$10,000	Invoiced

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, preventing avoidable costs and keeping buyers and suppliers aligned. Play each conversation to see the agent at work.

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 verifies every charge against the applicable contract, rate, discount, credit, PO and usage data — flagging discrepancies before payment and showing exactly why a charge doesn't match.
Snowflake · INV-8120
September · checked against contract
$560 over
Billed1,400 credits × $3.00
Contract rate1,400 credits × $2.60
Held before payment
Not the contract rate
Billed above contract rate
Buyer — procurement agent
Buyer: Check Snowflake's September invoice against our contract.
Agent:
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.
invoices.run_match
Buyer: Ask Snowflake for a corrected invoice.
Agent:
Sent. INV-8120 stays on hold, and Snowflake sees the contract rate and the $560 difference behind it.
invoices.resolve_discrepancy
Send the suggested question below to see the agent handle it.
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
Pleaxy compares billed quantities and rates against actual usage and the commercial terms that apply to it — identifying unexpected consumption, incorrect rates and charges that need review.
AWS · INV-7790
September · billed vs metered usage
EC2 · Matches usage OK
S3 · Matches usage OK
Data transfer · 180 TB vs 132 TB used+$4,320
Usage doesn't match the bill
Buyer — procurement agent
Buyer: Does AWS's September invoice match our usage?
Agent:
Mostly. EC2 and S3 match your metered usage. Data transfer on INV-7790 bills 180 TB, but usage shows 132 TB — $4,320 more than it should be, so it's held for review.
invoices.run_match
Buyer: Where do the extra 48 TB come from?
Agent:
Nothing in your account's metered usage accounts for them. The line stays with the reviewer, alongside the usage report, until AWS explains or corrects it.
invoices.list
Send the suggested question below to see the agent handle it.
Contract terms that get lost at billing
- Buyers
The problem
The agreement says one thing. The PO says another. The invoice shows something else. Discounts, credits, minimum commitments, pricing tiers and amendments can live across different documents and systems.
How Pleaxy helps
Pleaxy brings those commercial terms together and determines which ones apply to each charge — creating a clear basis for what should actually be paid.
Brightwater · INV-622
460 hours · terms that apply
MSA$150 per hour
Amendment 210% off hours above 400
PO-7802$70,000 approved
Should be $68,100
Billed $69,000
$900 over
Amendment 2 applies
Buyer — procurement agent
Buyer: Which terms apply to Brightwater's October invoice?
Agent:
Three: the MSA rate of $150 an hour, Amendment 2's 10% discount on hours above 400, and PO-7802. INV-622 bills 460 hours with no discount — it should be $68,100, not $69,000.
invoices.run_match
Buyer: Send Brightwater the breakdown.
Agent:
Sent. Brightwater sees each charge with the term it was checked against, and INV-622 is held until the corrected invoice arrives.
invoices.resolve_discrepancy
Send the suggested question below to see the agent handle it.
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 tracks PO balances against expected and incoming charges, identifying funding gaps before they block an invoice and giving buyers time to create, extend or replenish the PO.
Buyer — procurement agent
Buyer: Is PO-8842 ready for AWS's October invoice?
Agent:
Not yet. PO-8842 has $4,200 left, and October usage is tracking at $47,900 — that invoice would be rejected for exceeding the PO.
purchase_orders.list
Buyer: Raise a PO to cover October.
Agent:
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.
purchase_orders.create
Send the suggested question below to see the agent handle it.
Manual reconciliation that doesn't scale
- Buyers
- Suppliers
The problem
Finance and procurement teams spend hours comparing invoices against POs, contracts, spreadsheets, usage reports and supplier portals — often line by line.
How Pleaxy helps
Pleaxy performs the reconciliation automatically across all available sources. Charges that match move forward; exceptions are surfaced with the supporting evidence a reviewer needs to make a decision.
Kestrel · September
Invoices matched to POs
11 / 12matched
INV-601 · Hosting Matched
INV-602 · Support Matched
INV-604 · 120 h vs 100 h on POFor review
Kestrel sees the same result
Buyer — procurement agent
Buyer: Reconcile Kestrel's September invoices against their POs.
Agent:
11 of 12 match their POs line for line. INV-604 bills 120 hours against a PO for 100, so it's held for review instead of going to approval.
invoices.run_match
Buyer: Kestrel's timesheet backs the 120 hours — move it forward.
Agent:
Done. INV-604 is in the approval chain, and Kestrel sees the same match result and status you do.
invoices.resolve_discrepancy
Send the suggested question below to see the agent handle it.
Late fees and avoidable payment delays
- Buyers
The problem
Invoices get stuck waiting for approvals, PO corrections or discrepancy resolution. By the time the issue is discovered, the due date has passed — potentially triggering late fees or disrupting service.
How Pleaxy helps
Pleaxy tracks every invoice through its lifecycle, identifies what is blocking payment and alerts the right people before the due date — helping resolve exceptions while there's still time to act.
AWS · INV-7712
$48,120 · due Friday
1.5% fee after Fri
Waiting on Finance approval
Finance alerted before the due date
Pays Thursday once approved, a day early
Alerted Finance
Buyer — procurement agent
Buyer: Which invoices could hit a late fee this week?
Agent:
One. AWS INV-7712 for $48,120 is due Friday and still waiting on Finance — a 1.5% late fee applies after that. Want me to alert Finance?
invoices.list
Buyer: Yes — and make sure it's paid on time.
Agent:
Alerted Finance. As soon as they approve, INV-7712 is scheduled to pay Thursday — a day before it's due, so no fee.
invoices.remind
Send the suggested question below to see the agent handle it.
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.
Supplier — AR agent
Supplier: Did any of our invoices get rejected?
Agent:
One. Globex rejected INV-S-551 for $12,300 yesterday: it cites PO-7710, but the PO they approved for this work is PO-7719.
invoices.list
Supplier: Reissue it against PO-7719.
Agent:
Done. I flipped PO-7719 into INV-S-560 for the same $12,300, noted that it replaces INV-S-551, and it's now in Globex's approval queue.
purchase_orders.flip_to_invoice
Send the suggested question below to see the agent handle it.
Credits and discounts that never get applied
- Buyers
The problem
Negotiated credits, rebates and discounts can be buried in contracts, emails or amendments. If they don't appear on an invoice, they can easily go unnoticed.
How Pleaxy helps
Pleaxy tracks the commercial terms you're entitled to and checks whether they were actually applied — flagging missing credits and discounts before money is left on the table.
Salesforce · INV-9031
Q3 · what your renewal entitles you to
8% volume discount Applied
Q3 service credit · $5,000Missing
Held until the corrected invoice applies the credit
$5,000 credit not applied
Buyer — procurement agent
Buyer: Were all of Salesforce's credits applied this quarter?
Agent:
No. The 8% volume discount was applied, but your renewal also includes a $5,000 service credit for Q3, and INV-9031 doesn't apply it. It's held for review.
invoices.run_match
Buyer: Ask Salesforce to apply it.
Agent:
Sent, citing the renewal clause. INV-9031 stays on hold until the corrected invoice arrives with the $5,000 credit.
invoices.resolve_discrepancy
Send the suggested question below to see the agent handle it.
Renewals and pricing changes nobody catches
- Buyers
The problem
Rates change, contracts renew and promotional pricing expires. Without a clear view of the applicable terms, higher charges can be accepted simply because they look legitimate.
How Pleaxy helps
Pleaxy tracks effective dates, amendments and pricing changes so every charge is evaluated against the terms that were actually in force when it occurred.
Datadog · INV-7741
October · billed $11,400
Current term · Until Oct 31$10,000 / mo
Renewal · From Nov 1$11,400 / mo
Current term applies
$1,400 over
Billed before renewal
Buyer — procurement agent
Buyer: Did any supplier bill us a new price in October?
Agent:
Two did. Twilio's promotional rate ended September 30, so its higher rate is correct. Datadog INV-7741 bills its renewal price of $11,400 for October, but the renewal only starts November 1 — $1,400 over.
invoices.run_match
Buyer: Hold the Datadog invoice and let them know.
Agent:
Held. Datadog sees that October falls under the current term at $10,000, with the renewal's effective date alongside it.
invoices.resolve_discrepancy
Send the suggested question below to see the agent handle it.

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

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.

Buyer — procurement agent

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.

purchase_orders.create
invoices.run_match

Supplier — AR agent

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?

invoices.list

Yes, send it.

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

invoices.remind

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 →

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

The problems we're here to fix

Paying more than you agreed to

Buyer — procurement agent

Invoices that don't match actual usage

Buyer — procurement agent

Contract terms that get lost at billing

Buyer — procurement agent

Invoices with no PO — or not enough PO

Buyer — procurement agent

Manual reconciliation that doesn't scale

Buyer — procurement agent

Late fees and avoidable payment delays

Buyer — procurement agent

Rejected invoices suppliers discover too late

Supplier — AR agent

Credits and discounts that never get applied

Buyer — procurement agent

Renewals and pricing changes nobody catches

Buyer — procurement agent

How it works

Connect

Order and route

Match

Pay and chase

Built agent & SDK first — for buyers and suppliers

For buyers

For suppliers

Skip the code too — talk to your agent

Buyer — procurement agent

Supplier — AR agent

Built for how you actually ship

Available in your language

Every charge. Verified with AI.