What happens when you write, and how fast can you go? QuickBooks replaces the whole entity unless you ask it not to. Xero caps you by the day. NetSuite governs by concurrency and may reject a write for reasons that are not in your payload at all.
Xero
POST /Invoices with Idempotency-Key
Arrays of up to 50 objects per request
QBO
POST /invoice?requestid=…, POST /batch
Up to 30 operations per batch; requestid for idempotency
NetSuite
PATCH /record/v1/{type}/{id}
Scripts and workflows fire on write
Read across a row. Where a cell is absent, the concept has nowhere to live in that system — which is a design constraint, not a gap to paper over.
A difference stated without a response is trivia. Each of these carries the handling.
POST an Invoice with only the fields you meant to change and every line on it disappears. The call succeeds. The invoice is now empty and the customer's balance has moved.
Do — Read the current record, mutate it, write the whole thing back with the current SyncToken — or use sparse updates and accept their narrower semantics. A SyncToken mismatch is a real user-visible outcome, not a retryable error: someone else changed the record.
A user event script, a workflow condition, a mandatory custom field or a subsidiary restriction can reject a payload that is structurally perfect. The error text often names an internal field id and nothing else.
Do — Surface the raw NetSuite error to the operator, not a rewritten message. Keep the payload alongside it so support can reproduce. Never retry a rejection automatically.
Xero's daily cap (5,000 per organisation, 1,000 on Starter) makes backfill a multi-day job. NetSuite's concurrency governance means parallelism is capped hard and two workers each politely using three connections will trip a five-connection limit. QBO's 500-a-minute rate is the most forgiving of the three per minute — but its reads are now counted per month against a partner-tier allowance.
Do — One token-bucket limiter per source and tenant, shared across every worker, with retries flowing through it. Retry 429 and 5xx with exponential backoff and jitter; never retry a 400.
A timeout on a write leaves you unsure whether the document exists. Xero honours an Idempotency-Key header, and QBO a requestid query parameter — unique per company, up to 50 characters (36 in a batch) — that returns the original response instead of writing twice. Both only work if you send them. NetSuite's REST record service has neither, so a blind retry may create a duplicate invoice with a new number, which someone will eventually pay.
Do — Send the Xero key and the QBO requestid on every write, generated once per user action and reused on retry. For NetSuite, write a client-generated reference into a field it stores (tranid, externalid, a custom field) before the call, and search on it after any ambiguous failure instead of retrying blind.
Stacked rather than tabbed — a reader comparing two shapes should not have to hold one of them in memory.
QBO — the read-mutate-write cycle, in full
// 1. Read. You need the SyncToken and every line you intend to keep.
const { Invoice } = await get(`/invoice/${id}`);
// 2. Mutate the whole object.
const next = { ...Invoice, DueDate: "2026-11-07" };
// 3. Write it all back. Omitting Line here would empty the invoice.
await post("/invoice", next); // SyncToken travels inside `next`
// The alternative, with narrower semantics:
await post("/invoice", { Id: id, SyncToken: Invoice.SyncToken, sparse: true,
DueDate: "2026-11-07" });Xero — idempotent write, per-object errors
POST /api.xro/2.0/Invoices?summarizeErrors=false
Xero-Tenant-Id: 0c1f…
Idempotency-Key: inv-batch-2026-09-07-001
{ "Invoices": [ /* up to 50 objects */ ] }
// With summarizeErrors=false, each object comes back with its own
// ValidationErrors. One bad invoice does not reject the batch.The payoff. Every difference above that reaches the surface, and what the component does about it.
The normalised object above is what the components read. These are the surfaces it feeds, the words for the concepts in it, and the document that explains the accounting.
Compared acrossXero docsQuickBooks Online docsNetSuite docsVerify quantitative claims