CheckAdd qbXML example
Writes a check from a bank account.
qbXML
CheckAddRq, version 16.0
<?xml version="1.0" encoding="utf-8"?>
<?qbxml version="16.0"?>
<QBXML>
<QBXMLMsgsRq onError="stopOnError">
<CheckAddRq>
<CheckAdd>
<AccountRef>
<FullName>Checking</FullName>
</AccountRef>
<PayeeEntityRef>
<FullName>City Utilities</FullName>
</PayeeEntityRef>
<RefNumber>2052</RefNumber>
<TxnDate>2026-01-15</TxnDate>
<Memo>January electricity</Memo>
<ExpenseLineAdd>
<AccountRef>
<FullName>Utilities</FullName>
</AccountRef>
<Amount>212.40</Amount>
<Memo>Electricity</Memo>
</ExpenseLineAdd>
</CheckAdd>
</CheckAddRq>
</QBXMLMsgsRq>
</QBXML>
Open in the validator
Check it against the qbXML 16.0 schema, edit it, and run it in your own QuickBooks.
Things to know
- Write amounts with two decimals (40.00, not 40). QuickBooks refuses a whole-number amount with status 3040, though the schema allows it.
- A *Ref that names a record QuickBooks doesn't have answers 3120 when it gives a ListID and 3140 when it gives a FullName.
The same request with QuBe Sync's API
QuBe Sync takes this JSON, writes the qbXML for you and delivers QuickBooks' answer to your webhook as JSON.
POST
/api/v2/connections/{connection_id}/checks
{
"account_ref": {
"full_name": "Checking"
},
"expense_line_add": [
{
"account_ref": {
"full_name": "Utilities"
},
"amount": 212.4,
"memo": "Electricity"
}
],
"memo": "January electricity",
"payee_entity_ref": {
"full_name": "City Utilities"
},
"ref_number": "2052",
"txn_date": "2026-01-15"
}
Every field CheckAdd takes is in Intuit's reference.
More requests
Vendors and purchases