QuickBooks
When a deal closes, Strkr creates a draft invoice in QuickBooks with the right customer, line items, and amount. Finance reviews and sends. Payment status syncs back to the deal record for forecasting.
Everything QuickBooks does inside Strkr.
- Create draft invoices on closed-won
- Two-way sync of payment status
- Map Strkr products to QuickBooks items
- Backdate invoices from historical deals
Native code, not a shim.
OAuth where available
QuickBooks will ship with a native OAuth flow when it lands. No pasted credentials for admins to rotate manually.
KMS-encrypted tokens
Access and refresh tokens are envelope-encrypted at rest using a dedicated customer-managed KMS key. Decryption only happens in Lambda memory during an active API call; plaintext tokens never land in a log.
Shared by the workspace
A workspace admin connects QuickBooks once; every teammate uses the shared connection without re-authenticating.
Disconnect at any time
Admins or users can disconnect QuickBooks from inside Strkr. Stored tokens are deleted and the provider's revocation endpoint is called within 24 hours.
QuickBooks is on the roadmap.
We ship integrations as first-class native code, which takes a little longer than a Zapier shim. If QuickBooks is a dealbreaker for your evaluation, reply to the welcome email after you start a trial and we'll flag it to the roadmap.