TenkeyBridge
← Back to blog

TenkeyBridge Changelog, October 2026: 84 Reports, Cleared Status, Multicurrency, and More Writes

  • tenkeybridge changelog
  • quickbooks desktop api updates
  • quickbooks desktop api new features
Isometric illustration of an open shipping crate with a ledger, gear, coin, bar chart and check mark floating out

Quick answers

What changed in TenkeyBridge in October 2026? Reports went from 48 to 84, cleared status became readable and writable, multicurrency reads and writes landed, several transaction types gained line-level updates and voids, and QBO Projects now map to Desktop jobs.

How many reports does the Desktop API support now? 84, including report filters, budget reports, TransactionListWithSplits, ClassSales, and MissingChecks.

Can I void a Bill or a Journal Entry through the API now? Yes — CreditMemo void matches QBO behavior, and Bill, VendorCredit, Deposit, JournalEntry, and InventoryAdjustment voids are Desktop-only extensions.

Which npm packages are current? @tenkeybridge/client 0.8.1 and @tenkeybridge/mcp 0.8.0.

Where do I check whether a field is supported? The Desktop parity matrix is the source of truth; this post is a summary, not a contract.


A support thread in early October went roughly like this: ExampleCo reconciles a Desktop checking account every month, and their dashboard needed to know which checks had cleared. The data is right there in the company file. There was no way to read it over the API, and no way to mark a transaction cleared after an external reconciliation. That one ticket is a decent summary of October: a lot of "the data exists in Desktop, the REST surface just didn't reach it yet."

Here's what shipped, grouped roughly the way you'd care about it.

Reports: 48 → 84

The single biggest surface change. The report catalog nearly doubled, and the additions are mostly the ones that come up in reconciliation, job costing, and board-pack workflows rather than the headline P&L/Balance Sheet set that was already there.

Report filters. Reports now accept the filter parameters Desktop exposes — date ranges, accounting method, summarize-by columns, and entity/account/class restrictions where the underlying report supports them. Not every report takes every filter; qbXML is uneven about this, and the per-report tables in the docs say which ones apply.

Budget reports. Budget vs. actual and budget overview, which have no QBO-identical shape, so the response follows the same column/row envelope as the rest of the report endpoints rather than inventing a new one.

TransactionListWithSplits. A flat transaction list with the split lines attached. This is the report people kept rebuilding by hand out of individual transaction reads, which is slow and racy against an open company file.

ClassSales. Sales broken out by class, for the many Desktop files that use classes as the de facto department or location dimension.

MissingChecks. Gaps and duplicates in check numbering for a given bank account — a reconciliation staple that has no QBO analog.

If you're deciding which of the 84 to lean on and which to compute yourself, the field guide to the Desktop reports API walks through the response envelope, the column-metadata problem, and the reports that are slow enough to warrant caching.

Cleared status

New endpoints: GET /clearedstatus and POST /clearedstatus. Read the cleared/reconciled flag on a transaction, and set it for transactions that support it.

POST /v3/company/{realmId}/clearedstatus
Content-Type: application/json

{
  "TxnId": "A1B2-1700000000",
  "TxnType": "Check",
  "ClearedStatus": "Cleared"
}

Two honest caveats. First, this is a Desktop-only extension — there is no QBO endpoint with this shape, so it sits outside the compatible surface and your QBO code path won't call it. Second, setting cleared status is not the same as reconciling: Desktop's reconciliation record (statement date, ending balance) is not something the API builds for you. If your product does its own bank matching and wants the flag to reflect that, this is the hook. If you want Desktop to believe a formal reconciliation happened, it won't.

Multicurrency, reads and writes

Company files with multicurrency enabled now round-trip currency on transactions and name-list entities: CurrencyRef and ExchangeRate are readable and writable where Desktop supports them, and home-currency amounts come back alongside transaction-currency amounts.

The behavior that trips people up is the same one that trips them up in the Desktop UI: the exchange rate is pinned per transaction, not per request, and Desktop will recompute home-currency totals from the rate you send. Send a rate that disagrees with the one Desktop has on file for that date and you'll get your rate, not theirs. That's usually what you want for an integration replaying historical data, and occasionally a surprise. The compatibility pages list which entities carry currency and which silently ignore it.

Writes that reach further into the line level

Four related changes, all in the category of "the create worked, the update didn't."

Item group lines on purchase orders. POs can now carry item group lines, which Desktop expands into their component items. You send the group; the expansion belongs to Desktop. Reads return both the group line and the expanded components, so don't double-count when you total a PO.

Line updates on Bill, VendorCredit, Purchase, and BillPayment. Previously these were header-updatable only — change a memo, fine; change a line, and you were deleting and recreating the transaction, which burns the TxnID and breaks anything holding a reference. Line-level updates now go through. Normal Desktop update rules still apply: you need the current EditSequence, and linked transactions constrain what you can change. If you're deciding between sending the whole object and sending a patch, sparse updates vs. full replacement covers the failure modes on Desktop specifically.

Sub-cent line rates. Line rates now preserve more than two decimal places where Desktop stores them, so a $0.0725 unit price stops coming back as $0.07. The rounding rules and where they still bite are in the write-up on sub-cent prices.

Voids, including five Desktop-only ones

CreditMemo void now behaves the way the QBO void operation does: the transaction stays in the file with zeroed amounts and a VOID: memo prefix, rather than disappearing.

Beyond that, five void operations exist that QBO has no equivalent for, because QBO has no equivalent transaction or no void semantics for it:

  • Bill
  • VendorCredit
  • Deposit
  • JournalEntry
  • InventoryAdjustment

These are Desktop-only extensions. They're useful precisely because deleting these transactions in a Desktop file is destructive in ways that are hard to walk back — an audit trail entry exists either way, but a void leaves the document number and the paper trail intact. Void vs. delete on Desktop goes through what each one leaves behind, including the linked-transaction cases where neither is allowed.

QBO Projects map to Desktop jobs

If your integration already creates Project objects against QBO, those requests now work against a Desktop file: a Project becomes a job under the customer, which is the structural equivalent Desktop has always had.

The mapping is close but not identical, and the gaps are the ones you'd expect from a concept that Desktop implements as a nested customer:

  • Desktop jobs inherit from the parent customer in ways QBO projects don't.
  • Job status values map onto Desktop's job status list, which is a fixed set.
  • Nesting depth follows Desktop's customer hierarchy limits, not QBO's.

Check the parity matrix before you assume a field survives the round trip.

Client libraries

  • @tenkeybridge/client 0.8.1 — typed client, updated for the new report names, cleared status, currency fields, and the Desktop-only voids.
  • @tenkeybridge/mcp 0.8.0 — the MCP server, with the expanded report catalog exposed as tools.
npm i @tenkeybridge/client@0.8.1
npm i @tenkeybridge/mcp@0.8.0

Both are still pre-1.0, which means the usual thing: minor versions can move interfaces. Pin them. The MCP server picks up every new read surface automatically, which is a larger blast radius than it sounds like — if you've wired an agent to a company file, re-read how to keep that access checkable before you hand it 84 reports.

A note on what this list is not

Shipping 36 reports does not mean Desktop and QBO now agree about reports. Several of the new ones have no QBO counterpart at all, and several QBO reports still have no Desktop equivalent. Same story for the voids: five of the six additions are extensions, not parity. The compatibility matrix is the thing to read before you plan a sprint around any of this — it's maintained per-entity and per-field, and it is more current than any blog post, including this one.

FAQ

What changed in TenkeyBridge in October 2026?

Reports grew from 48 to 84 with filter support; cleared status became readable and writable; multicurrency reads and writes landed; purchase orders accept item group lines; Bill, VendorCredit, Purchase, and BillPayment gained line-level updates; CreditMemo void plus five Desktop-only voids shipped; QBO Projects now map to Desktop jobs; and line rates preserve sub-cent precision.

Which new entities and reports were added?

No brand-new top-level entities — Project became usable against Desktop by mapping to jobs, and clearedstatus is a new endpoint rather than an entity. On reports, the notable additions are budget reports, TransactionListWithSplits, ClassSales, and MissingChecks, alongside filter parameters across the catalog.

Which npm versions are current?

@tenkeybridge/client 0.8.1 and @tenkeybridge/mcp 0.8.0.

Do I need to change anything in my existing integration?

No. Everything here is additive — existing endpoints, query syntax, and OAuth2 flows are unchanged. The one thing worth reviewing is sub-cent rates: if you were compensating for two-decimal truncation on line rates, that workaround may now double-correct.

Where do I find the changelog between posts?

The API reference tracks endpoint and field changes as they land, and the compatibility pages are versioned alongside them. These roundups on the blog summarize a month at a time.

What's next?

More write coverage. If you want to try any of this against a company file you don't have to install, the sandbox is the fastest path.