One guided setup for every source — Connect → Discover → Map → Sync. Upload a CSV today, wire the ERP tomorrow; the flow is the same and your mapping is remembered.
The same stepper for every connector — learn it once, and the second source is muscle memory.
Pick the source. Upload the file — or store ERP credentials, encrypted at rest with only a last-4 hint kept for display.
Columns resolve to account, period and amount. Entity and version come from the file — or stay fixed on the connection.
Source accounts map to your chart of accounts once, then they’re remembered. Auto-map by code clears the obvious ones for you.
Rows land in staging first. You see exactly what will be written — unmapped accounts are reported, never silently dropped.
Honest statuses: what’s live, what’s connect-ready, and what’s on the way.
The fully shipped end-to-end path: parsed in the browser, staged before commit, mapping remembered — from GL export to a mapped P&L in four steps.
Set up the connection today — TBA credentials stored AES-256 encrypted, destination pinned. The live SuiteQL pull is next on the roadmap.
Pull recurring exports from an SFTP drop — same staging, mapping and commit flow as every other source.
Let your systems push files to a Zencount inbox on their own schedule.
Fetch a file or API endpoint on demand — for the tools that can already speak HTTP.
German Finanzbuchhaltung — SKR-mapped accounts and journals, built for the DACH close.
P&L and transaction-level detail from QuickBooks Online.
Actuals and tracking categories mapped straight to your Zencount model.
Pipeline and bookings to power a bottoms-up revenue forecast.
Inbound rows land in a tenant-isolated staging area first. Commit is explicit, unmapped accounts are reported before anything hits your numbers, and every mapping rule is inspectable data — not a black box.
A 221-row sample GL export is linked right in the upload panel — run the whole four-step flow before touching real data.
Get started →