TimeTrackingAdd qbXML example
Records time an employee or vendor worked, optionally billable to a customer.
qbXML
TimeTrackingAddRq, version 16.0
<?xml version="1.0" encoding="utf-8"?>
<?qbxml version="16.0"?>
<QBXML>
<QBXMLMsgsRq onError="stopOnError">
<TimeTrackingAddRq>
<TimeTrackingAdd>
<TxnDate>2026-01-15</TxnDate>
<EntityRef>
<FullName>Jane Doe</FullName>
</EntityRef>
<CustomerRef>
<FullName>Acme Corp</FullName>
</CustomerRef>
<ItemServiceRef>
<FullName>Consulting</FullName>
</ItemServiceRef>
<Duration>PT2H30M</Duration>
<Notes>Site visit</Notes>
<BillableStatus>Billable</BillableStatus>
</TimeTrackingAdd>
</TimeTrackingAddRq>
</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
- Duration is written as an ISO 8601 duration, such as PT1H30M for an hour and a half.
- 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}/time-trackings
{
"billable_status": "Billable",
"customer_ref": {
"full_name": "Acme Corp"
},
"duration": "PT2H30M",
"entity_ref": {
"full_name": "Jane Doe"
},
"item_service_ref": {
"full_name": "Consulting"
},
"notes": "Site visit",
"txn_date": "2026-01-15"
}
Every field TimeTrackingAdd takes is in Intuit's reference.
More requests
Accounting