Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Create credit card charge

create_credit_card_charge
Read-onlyIdempotent

A credit card charge is a general charge incurred when a QuickBooks user makes a purchase using a credit card. Credit card charges for purchases can be tracked as expenses (in expense accounts) or as items.

The credit_card_charge_add wrapper from qbXML is also accepted. Returns the v2 request to send, and the webhook payload QuickBooks' answer arrives in (this operation's response_json: its data shape and the status codes to handle).

Possible errors (error.code / error.type; the call result explains each): 1030 unsupported_request, 3000 invalid_object_id, 3040 invalid_amount, 3070 string_too_long, 3120 object_not_found, 3140 invalid_reference, 3150 missing_element, 3175 in_use, 3176 locked, 3180 cannot_save, 3210 invalid_value, 3220 not_authorized, 3231 request_not_processed, 3250 feature_not_enabled, 3260 insufficient_permission, 3261 personal_data_access_denied, 3262 payroll_subscription_required, 3263 read_only_access, 3264 merchant_services_subscription_required, 3270 missing_posting_account

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account_ref": "<account_ref>"
    },
    "name": "create_credit_card_charge"
  }
}

Input Schema

NameRequiredDescriptionDefault
memoNoAdditional information.
txn_dateNoThe date of the charge. In some cases, if you leave `txn_date` out of an -Add message, QuickBooks will prefill `txn_date` with the date of the last-saved transaction of the same type.
def_macroNo`def_macro` lets you assign a reusable name to a returned `txn_id` or `txn_line_id` so later requests can reference it with `useMacro`. This feature requires SDK 2.0+.
ref_numberNo`ref_number` is a user-managed transaction reference (for example, a check number). It can be edited and is not guaranteed to be globally unique.
request_idNoYour own label for the request, sent to QuickBooks as its qbXML `requestID` and echoed in the raw answer (`response_xml`); optional, since the answer's webhook already carries the request's `id`.
account_refYes`account_ref` points to an account in the company file. If both `full_name` and `list_id` are provided, `full_name` is ignored.
exchange_rateNo`exchange_rate` is the rate from this currency to the company’s home currency at AsOfDate. You can supply a rate when adding transactions, but QuickBooks does not provide rates through the SDK.
external_guidNoAllows for the attachment of a user defined GUID value.
include_qbxmlNoAlso return the qbXML this compiles to, for debugging. Not part of the v2 request.
item_line_addNoAn ItemLine is used to track any portion of a transaction that represents the purchase of an “item.” `item_line_add` and `item_group_line_add` combine: any number of each. QuickBooks receives them in that order: every `item_line_add`, then every `item_group_line_add`.
is_tax_includedNoFor future use with international versions of QuickBooks.
expense_line_addNo
payee_entity_refNo`payee_entity_ref` identifies the payee (customer, vendor, employee, or Other Name). If both `full_name` and `list_id` are provided, `full_name` is ignored.
sales_tax_code_refNo`sales_tax_code_ref` points to the sales-tax code used for an item or customer context. QuickBooks includes default TAX and NON codes, and a code can be deleted only when nothing references it.
include_ret_elementNo
item_group_line_addNoRefers to items that are grouped together in QuickBooks for fast entry. `item_line_add` and `item_group_line_add` combine: any number of each. QuickBooks receives them in that order: every `item_line_add`, then every `item_group_line_add`.

Output Schema

NameRequiredDescriptionDefault
urlYesReplace {connection_id} with the customer's connection.
bodyYesThe JSON body: the arguments you passed.
qbxmlNoThe qbXML it compiles to. Only with include_qbxml.
methodYes
headersYesSend with the request. Resent unchanged when no 201 came back, it answers with the request already queued.
webhookYesJSON Schema of the payload POSTed to webhook_url once QuickBooks answers, with this operation's response_json (data shape and status codes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnly=true, idempotent, non-destructive, closed-world, so the safety bar is lower, and the description does add real context: the accepted qbXML wrapper alias, the fact that the response is a v2 request plus a webhook payload, and a 25-code error taxonomy (e.g. 3140 invalid_reference, 3260 insufficient_permission) that is genuinely actionable. However, the central behavioral question — whether calling this actually commits a charge or merely compiles a request the caller must send — is expressed so obliquely that it borders on ambiguous for a tool named 'create'. Permissions prerequisites and retry semantics are not covered.

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

Conciseness3/5

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

The opening sentence is an encyclopedia definition of the accounting entity rather than a statement of what the tool does, so the description is not front-loaded with purpose. The second paragraph packs three unrelated things (wrapper alias, return contract, error list) into one hard-to-parse sentence, though the error taxonomy does earn its space for debugging.

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

Completeness3/5

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

For a 16-parameter create tool with nested objects and an output schema, the description covers error handling and the request/webhook return contract, which is more than most. It is still incomplete on the essentials: no statement of the actual side effect or authorization prerequisites, and no routing guidance among the many create_* siblings. An output schema exists, so not explaining return values is acceptable.

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 description coverage is 88% across 16 parameters, so the schema does the heavy lifting and a baseline of 3 applies. The description adds no parameter-level meaning at all — nothing about why account_ref is the sole required field, when to use item_line_add versus expense_line_add, or how include_ret_element affects the response. It only references the qbXML wrapper naming, which is not a parameter.

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

Purpose3/5

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

The description defines the entity ("A credit card charge is a general charge incurred when a QuickBooks user makes a purchase using a credit card") but never states the action verb against the resource — it never says it creates a CreditCardCharge in the company file. The create semantics are carried entirely by the tool name. It also offers no differentiation from close siblings such as create_credit_card_credit, create_charge, or create_bill_payment_credit_card, where the charge-vs-credit distinction matters most.

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

Usage Guidelines2/5

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

There is no when-to-use guidance whatsoever: no statement of when to pick this over create_credit_card_credit, create_bill_payment_credit_card, or the update counterpart. The only guidance-adjacent sentence says charges can be tracked as expenses or as items, which describes downstream accounting configuration rather than tool selection. An agent must infer routing from names alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources