supplier-statement-check
Related Servers
Alternatives to supplier-statement-check
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables users to review a supplied batch of supplier invoices or vendor bills for repeated references, normalized reference variations, and identical amount-and-date candidates, returning grouped evidence and exact review reasons from local history. Supports saved reports, CSV export, and use with MCP clients such as Claude Desktop, Claude Code, and Cursor.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables local, credential-free investigation of reconciliation differences from supplied snapshots, including bounded searches for uncleared entry combinations, digit-transposition clues, statement comparison, and read-only previews of cleared-status changes.MIT
- FlicenseNot gradedqualityDmaintenanceSelf-serve MCPB demo for accounts payable invoice exception review. It performs deterministic matching across invoice, purchase order, goods receipt, vendor master, invoice history, tax code master, and payment rules.-
- FlicenseBqualityBmaintenanceEnables AI assistants to perform financial reconciliation with a deterministic proof engine: intake files, match transactions, verify proofs, resolve exceptions, and sign off on balanced journals under the user's authority.21-
- AlicenseNot gradedqualityCmaintenanceEnables users and AI agents to reconcile CSV bank statements against invoices or bills by matching amounts and references, then sorting each line into matched, likely, review, or unmatched groups with reasons. It exposes read-only tools for matching files and inspecting detected CSV columns and row counts.MIT
- AlicenseAqualityBmaintenanceEnables LLM agents to query and reconcile an accounts-payable ledger through safe read-only SQL, deterministic invoice-to-payment matching, and exception explanations for underpayments, duplicates, currency mismatches, and overdue invoices. Ships with a synthetic ledger, golden-set evals, and a month-end review workflow so quality can be measured in CI.4MIT
TDQS
Scored across 8 tools
The tools are mostly distinct: license tools, the core comparison tool, and report tools have clear separate purposes. The main overlap is between report_get, report_page, and report_export_csv, but the descriptions clarify saved reports, paged evidence, and CSV export well enough to avoid serious confusion.
All tools use snake_case and generally follow a resource-prefix pattern (license_*, report_*, supplier_statement_check). Minor deviation: license_status names a state rather than an action, while other tools use action-oriented suffixes.
Eight tools is well-scoped for a supplier statement checking server with licensing and report handling. Each tool appears to earn its place without excessive surface area.
The set covers license state/activation, the core comparison operation, and report listing, retrieval, paging, deletion, and CSV export. A minor gap is the lack of an explicit save/create-report tool, though report persistence may be implicit in supplier_statement_check.