What Stackpack stores from your accounting system
Last updated: September 22, 2026
This applies to every accounting integration that Stackpack supports.
Stackpack does not store your transactions. During each sync, Stackpack reads transaction lines from your accounting system, aggregates them, and discards them. No bill, payment, expense, journal line, memo, or line amount is written to Stackpack's database. Once a sync completes, the only transaction-derived data Stackpack holds is the monthly summary described below.
Per vendor: monthly spend
For each vendor, Stackpack keeps one record per calendar month with spend, containing exactly:
Field | Meaning |
|---|---|
Year and month | The calendar month the spend falls in |
Amount | Total billed or paid spend for that vendor in that month, net of credits and refunds |
Transaction count | Number of transaction lines that contributed to Amount |
Accrual amount | Total journal-entry (accrual) spend for that vendor in that month, where the integration provides it |
When the department switch is enabled for your account, Stackpack also keeps the same four fields per vendor per department per month, keyed by the department (or class) name.
Months older than the retention window (the current calendar year plus the two prior years, with one extra year during January through March) are deleted on each sync.
Per vendor: labels derived from transactions
Alongside the monthly summary, each vendor record holds:
The vendor's ID and name in your accounting system.
The GL accounts, and where enabled the classes, departments, and locations, that the vendor's transactions posted to, each with a count of contributing lines. Names and IDs only, no amounts.
The earliest month with spend in the retention window and the most recent month with spend.
Per connection
Each integration profile stores what is needed to sync again: the credential your accounting system issued (an OAuth refresh token or API key), the company, realm, organisation, or tenant identifier it is scoped to, the time of the last sync, the list of GL accounts seen during sync (names and IDs), and any excluded GL account list your Stackpack administrator configured. For the CSV integration, the uploaded file itself is stored so it can be re-read and downloaded.
Nothing else from your accounting system is retained. Disconnecting a profile deletes its stored credentials and stops syncing. Vendors and their monthly spend are kept for continuity, and are overwritten by the next sync once an accounting integration is connected again.