What is AccountingKit?+
AccountingKit is an accounting workflow automation platform. It connects your accounting system, normalizes financial data, and runs durable, auditable workflows for operational accounting tasks. Its unified API can also be embedded in software products.
Which accounting platforms can I connect?+
Xero, QuickBooks Online, Sage Intacct, FreshBooks, and Wave are available today, each with hosted OAuth, normalized resources, and verified webhooks where the provider supports them. Every provider answers the same accounting contract, and provider-native actions stay available where a provider does something the portable model cannot express.
Which accounting records can I manage?+
You can work with normalized contacts, invoices, quotes, payments, purchase orders, accounts, tax rates, and branding themes. AccountingKit also exposes invoice PDFs, online URLs, and provider deep links.
What happens when a workflow step fails?+
The run keeps its step state, attempts, and terminal error. You can inspect the failure, correct the underlying issue, and resume from the persisted step instead of rebuilding the run from scratch.
Is AccountingKit only for software companies?+
No. The primary use case is connecting your own accounting system and automating your finance operations. Software teams can also use the unified API to embed the same capabilities for their customers.
Can I use the unified API without a workflow?+
Yes. You can connect an accounting organization and read or write normalized resources directly. Workflows add durable orchestration when a business process spans multiple steps.
Why use AccountingKit instead of calling each provider directly?+
AccountingKit combines hosted OAuth, one normalized model across every provider, idempotent writes, retries, replay, signed webhooks, and audit history. Your team can build the accounting experience instead of rebuilding integration reliability around each workflow.
How does AccountingKit protect accounting data?+
Provider credentials and raw provider payloads are encrypted at rest. API keys are environment-scoped, tenant ownership is enforced in the data layer, and customer webhooks are signed.