Sync-and-store vs pass-through: choosing per object
Storing data makes reads fast; passing through keeps it out of your systems. Why the right answer differs for invoices, ledgers and catalogs.
4 min read
BLOG
Notes on integrations, finance and product data.
Engineering notes and platform deep dives from the team building the Unify Graph: QuickBooks, NetSuite, write-back, sync models and agents.
Latest posts.
Fundamentals Platforms NetSuite integrations: subsidiaries, custom fields and SuiteTalk
The NetSuite patterns that decide whether your mid-market deal closes: multi-entity, custom records, approvals and concurrency governance limits.
5 min read
AI agents MCP for finance data: giving agents tools, not keys
What an MCP server should expose for accounting and commerce data, and the guardrails AI agents need before they touch money-adjacent records.
4 min read
Finance Writing to the ledger without breaking the books
Idempotency, validation, closed periods and approvals. A practical checklist for invoice, bill and journal entry write-back to accounting systems.
5 min read
Product data Why product data belongs next to the ledger
Margin by SKU, stock value, ad spend per order: the questions that cross finance and catalog data, and the case for keeping both on one data model.
4 min read
Finance Codat alternatives for fintech and SaaS teams
Codat is refocusing on banks. Realistic options for teams that still need accounting and commerce data, and how to migrate without breaking customers.
4 min read
Platforms The QuickBooks Online API, explained for builders
OAuth, rate limits, webhooks, sandbox companies and the objects that trip teams up. Read this before your first QuickBooks Online API call.
4 min read
Fundamentals What a unified API is, and when you need one
One schema for many platforms sounds simple. What a unified API buys you, what it costs, and three signals your product needs one now.
5 min read