Skip to main content
Glama
laf-rge

QuickBooks MCP

by laf-rge

create_bill_payment

Pay one or more bills and optionally apply vendor credits to clear Accounts Payable. Records vendor payments for bank feed matching.

Instructions

Create a bill payment (the QBO 'check' / 'pay bills' flow). Pays one or more existing bills and optionally applies vendor credits, clearing Accounts Payable. Use this to record vendor ACH/EFT debits or checks so the bank feed can match them — especially when a bank charge equals bills minus credit memos. Amounts default to each bill's open balance and each credit's remaining balance. Returns payment details and a link to view in QuickBooks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vendor_nameNoVendor display name (e.g., 'US Foods'). Will be looked up to get ID.
vendor_idNoVendor ID (use if you already know it, otherwise use vendor_name)
payment_accountYesBank account name or number the payment is drawn from (e.g., 'PLAT BUS CHECKING', '5752'). Will be looked up to get ID.
txn_dateYesPayment date in YYYY-MM-DD format (use the bank debit date for bank-feed matching)
memoNoPrivate memo for the payment
doc_numberNoReference number, e.g., check number or EFT reference (optional)
billsYesBills to pay. Each bill must belong to the vendor and have an open balance.
creditsNoVendor credits to apply against the bills (optional). Each credit must belong to the vendor and have remaining balance.
draftNoIf true, validate and show preview without creating (default: true)
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description discloses key behaviors: it pays bills and applies credits, defaults amounts to open/remaining balances, supports a draft mode, and returns payment details and a link. It could mention it reduces bill balances, but overall it is transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences that are dense with information, front-loaded with the purpose and flow. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (9 params, nested objects), the description covers the overall flow, defaults, use case, and return value. It lacks explicit mention of vendor consistency constraints but otherwise is complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds minimal extra meaning beyond the schema, though it contextualizes the draft parameter's purpose. The default amount behavior is already in the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates a bill payment, explains it as the QBO 'check/pay bills' flow, and specifies it pays bills and applies vendor credits to clear AP. This distinguishes it from siblings like create_bill or create_expense.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides concrete guidance: 'Use this to record vendor ACH/EFT debits or checks so the bank feed can match them — especially when a bank charge equals bills minus credit memos.' It implies it's for paying existing bills but doesn't explicitly exclude other scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/laf-rge/quickbooks-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server