Auto-detect SaaS spend with Plaid
Connect a bank or corporate card through Plaid and Cubbie proposes registry entries from recurring software charges.
What Plaid detection does
Connect a company bank account or corporate card through Plaid and Cubbie scans transactions for recurring software charges, then proposes subscription registry entries automatically. It is the quickest way to surface SaaS spend that never went through procurement.
Connect your account
1. Open Finance → Plaid in your dashboard.
2. Start the connection and complete the Plaid Link flow — Plaid is the same bank-connection service used by most finance tools.
3. Approve your institution and accounts.
What Cubbie sees, and what it keeps
Access is read-only. Cubbie cannot move money, initiate a payment, or change anything at your bank.
To find the software charges, Cubbie reads the transaction history for the accounts you approve, going back up to two years. Recurring charges can only be spotted against the full history, so a scan looks at the transactions on those accounts rather than a pre-filtered subset. Anything that is not a software subscription is read in passing and never retained.
What gets saved is only the recurring software subscriptions the detector identifies: vendor, amount, cadence, first and last charge, and an inferred renewal date. Everything else is discarded when the scan finishes. Cubbie does not store your raw transactions, your account or routing numbers, or your balances.
Your bank credentials never reach Cubbie at all. You enter them with Plaid, and the token exchange happens server-side so the access token is never exposed to the browser.
Disconnect an account any time from the same page. Disconnecting your last account also deletes the subscriptions that were detected from bank data. Full detail is in Privacy Policy section 5.
Run a sync
After connecting, run a transaction sync from the same page. Cubbie classifies recurring vendor charges and writes detected subscriptions into your registry, where you can confirm, edit, or remove them.
What the classifier looks at:
- Recurring charge patterns from the same vendor
- Known SaaS vendor names
- Charge amounts and billing cadence (monthly or annual)
Review what was found
Detected subscriptions appear in your subscription registry alongside records from CSV imports and identity provider connectors. Treat them as a starting point: confirm the vendor, set an owner, and correct any renewal date that was inferred from billing cadence rather than a contract.
Good to know
- Plaid detection complements identity provider connectors rather than replacing them: Plaid sees what you pay for, while Okta or Google Workspace see what your team actually uses. Together they power seat-drift and rightsizing findings.
- Re-run a sync whenever you want to pick up recent charges — for example after a new card statement closes.