Your numbers in, without the project.
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.
From CSV to a mapped P&L.
The same stepper for every connector — learn it once and the second source is muscle memory.
01 · Connect
Pick a source. Upload a file — or store ERP credentials, encrypted at rest, with only the last 4 characters shown.
02 · Discover
Columns resolve to account, period and amount. Entity and version come from the file — or stay fixed on the connection.
03 · Map
Source accounts are mapped to your chart of accounts once, then remembered. Auto-mapping by account number handles the obvious cases.
04 · Sync
Rows land in staging first. You see exactly what will be written — unmapped accounts are reported, never silently dropped.
Every source, one setup flow.
Honest statuses: what’s live, what’s connect-ready — and what’s in the works.
CSV / Excel Upload
The fully available end-to-end path: parsed in the browser, staged before commit, mapping remembered — from ledger export to mapped P&L in four steps.
LiveNetSuite
Set up the connection today — TBA credentials stored AES-256-encrypted, target fixed. Live SuiteQL fetch is next on the roadmap.
Connect-readySFTP download
Pull recurring exports from an SFTP directory — same staging, mapping and commit as any other source.
PreviewSFTP receive
Your systems deliver files into a Zencount inbox on their own schedule.
PreviewHTTP fetch (URL / API)
Load a file or API endpoint on demand — for systems that already speak HTTP.
PreviewDATEV
Financial accounting with SKR-mapped accounts and posting journals — built for the close in the DACH region.
Coming soonQuickBooks
P&L and transaction-level detail from QuickBooks Online.
Coming soonXero
Actuals and tracking categories mapped straight into your Zencount model.
Coming soonSalesforce
Pipeline and closed deals as the basis for a bottom-up revenue forecast.
Coming soonYou approve what becomes a number.
Incoming rows land first in a tenant-isolated staging area. The commit is explicit, unmapped accounts are reported before anything touches your numbers — and every mapping rule is inspectable data, not a black box.
Connection credentials encrypted at rest
rows written without your explicit commit
map an account once — reused on every sync
connections, mappings and staging are org-isolated
Try it with the demo file.
A sample general-ledger export with 221 rows is linked right in the upload panel — try the full four-step flow before you touch real data.
Don’t see your system? Talk to us.