three-way-match

three-way-match is a skill for Claude Code, Codex from yourlastnamesoundslikeatypeofpasta/acumatica-mcp-server. It costs 151 tokens per session (1,315 once invoked), scanned A, original, MIT.

A read-only procedure for a three-way match: comparing what a business ordered, received, and was billed for. It checks Acumatica purchase orders, receipts, and vendor bills line by line for price and quantity differences.

In plain words
What is it for?
Use it to validate a vendor bill, verify received quantities and prices against the purchase order, and flag variances for review.
Why use it?
It helps catch billing errors before payment by connecting the three documents and comparing their details.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to validate a vendor bill, verify received quantities and prices against the purchase order, and flag variances for review.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yourlastnamesoundslikeatypeofpasta/acumatica-mcp-server/three-way-match
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add yourlastnamesoundslikeatypeofpasta/acumatica-mcp-server --skill three-way-match
Clone the repo
git clone --depth 1 https://github.com/yourlastnamesoundslikeatypeofpasta/acumatica-mcp-server

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for three-way-match

README.md
[![agentmods](https://agentmods.dev/badge/skills/yourlastnamesoundslikeatypeofpasta/acumatica-mcp-server/three-way-match/github.svg)](https://agentmods.dev/skills/yourlastnamesoundslikeatypeofpasta/acumatica-mcp-server/three-way-match)
Your own site
<a href="https://agentmods.dev/skills/yourlastnamesoundslikeatypeofpasta/acumatica-mcp-server/three-way-match"><img src="https://agentmods.dev/badge/skills/yourlastnamesoundslikeatypeofpasta/acumatica-mcp-server/three-way-match/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for three-way-match

Your own site · 80×15
<a href="https://agentmods.dev/skills/yourlastnamesoundslikeatypeofpasta/acumatica-mcp-server/three-way-match"><img src="https://agentmods.dev/badge/skills/yourlastnamesoundslikeatypeofpasta/acumatica-mcp-server/three-way-match.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 151 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,315 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00151 $0.01315
Opus 5 $0.00076 $0.00658
Sonnet 5 $0.00030 $0.00263
Haiku 4.5 $0.00015 $0.00131

Measured 11d ago against content hash b2be9d53c6c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

three-way-match scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/three-way-match/SKILL.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Acumatica - Three-Way Match (Bill <-> Receipt <-> PO)

Reconcile what was ordered (PO) vs received (receipt) vs billed (bill), line by line, and flag variances before a bill is paid. Read-only - never releases or edits a document.

⚠️ Known tenant behaviour

  • $orderby is silently ignored - sort client-side.
  • Date filters need datetimeoffset'YYYY-MM-DDTHH:MM:SS-04:00' literals.
  • $select/$filter field names must match exactly or you get a hard 500.
  • Decimal comparison filters (e.g. gt 0) may 500 with "Type conversions not supported" - filter client-side instead.
  • Render each document number as a Markdown link from its browser_url.

The linking chain (verified field names)

Each Bill line (Bill -> expand="Details") carries the back-references: POOrderType, POOrderNbr, POLine -> the originating PO line, and POReceiptType, POReceiptNbr, POReceiptLine -> the receipt line. Line amounts: Qty, UnitCost, ExtendedCost, Amount, InventoryID, LineType.

Each PurchaseReceipt line (PurchaseReceipt -> expand="Details") carries: POOrderType, POOrderNbr, POLineNbr (link to PO line), ReceiptQty, OrderedQty, OpenQty, UnitCost, ExtendedCost, InventoryID, POReceiptNbr, POReceiptLineNbr.

Each PurchaseOrder line (PurchaseOrder -> expand="Details") carries: LineNbr, InventoryID, OrderQty, QtyOnReceipts, UnitCost, ExtendedCost, Completed.

Goods lines carry these PO/receipt references. Non-goods bill lines (e.g. accrued warranty, freight, GL-only) have the reference fields empty - those are legitimately "no PO" and should be reported as unmatched-by-design, not as errors.

How to match a single bill

  1. get_record(entity="Bill", id="Bill/<RefNbr>", expand="Details").
  2. For each bill line with a POOrderNbr, pull the PO once: get_record(entity="PurchaseOrder", id="<POOrderType>/<POOrderNbr>", expand="Details") and find the line where LineNbr == bill.POLine.
  3. For each bill line with a POReceiptNbr, pull the receipt: get_record(entity="PurchaseReceipt", id="<POReceiptType>/<POReceiptNbr>", expand="Details") and find the line where its POReceiptLineNbr/LineNbr matches bill.POReceiptLine.
  4. Compare per line (see rules) and classify each as Match, Variance, or Unmatched.

Read the full file on GitHub · 87 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 87 lines · 151 tokens per session scan A b2be9d53c6c6

Subscribe to this mod's changes

three-way-match is a skill published in the GitHub repository yourlastnamesoundslikeatypeofpasta/acumatica-mcp-server (0 stars, last pushed 27d ago), licensed MIT. It adds 151 tokens to every session and 1,315 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.