Fortnox – Gotchas
Fortnox is the leading Swedish SMB cloud accounting and ERP platform — invoicing, supplier-invoice management, bookkeeping, payments, and reporting for small and mid-sized Swedish businesses.
2 gotchas across 2 resources
These are connector-specific behaviors and limitations to be aware of when integrating.
Journals1 gotcha
journalsAllUse code as journal_symbol when creating a journal entry — it is the same series letter (e.g. "A") used there. type is derived from whether the series is manually posted to: manual series report as general, and every other series (invoice series, and any other automated series) reports as other, since Fortnox does not expose a specific sales/purchase/cash/bank category for non-manual series; allow_vat and currency are not exposed and are always absent.
Tracking Categories1 gotcha
trackingCategoriesAllFortnox has multiple analytic dimensions (projects, cost-centers, DimAx1-3). The unified
tracking-categories resource exposes a single dimension (projects) to keep ids unambiguous.
If you need values from another dimension, or values from multiple dimensions in one response, use
?raw=true to retrieve the raw Fortnox payload and inspect the dimension you need. Note that
Fortnox category codes are unique only within a dimension -- e.g. code "100" may exist on both
projects and cost-centers and refer to different things. The unified id is the project number
only; cross-dimension uniqueness is not guaranteed when raw-mode-merging happens client-side.
For multi-dimension awareness in the unified API, see the upcoming analytic-plans /
analytic-categories resources (parallel-resource path; non-breaking to this endpoint).