CSV import
Transaction files from your ledger or bank export are mapped once per client and then re-used every period.
Integrations
Get your data in, without a project plan.
Zerqis reads the exports your team already produces. Direct ledger connections are on the roadmap; nothing below is a connector we claim to ship today.
Available today
What a firm can run a full close on right now.
Idempotent re-runs
Rows are keyed on their source identifiers, so re-importing a corrected file updates records instead of duplicating them.
Rules carried forward
Client-specific categorization rules live in Zerqis, so they apply to every future import without re-teaching.
On the roadmap
Direct connections we are working towards
These are planned, not shipped. If one of them is what stands between your team and a faster close, tell us — roadmap order is driven by the firms we are building with.
- General ledger sync for the major small-business accounting platforms
- Bank feed ingestion so transactions arrive without a manual export
- Document sources for receipts and supporting evidence
- An API for firms that already have their own data pipeline
Building on your own pipeline?
Zerqis is a normal web application over a relational database. If your firm has engineering capacity, an integration is a conversation, not a procurement cycle.
Bring your own extract
If you can produce a consistent transaction file, Zerqis can consume it. Mapping is per client and takes minutes.
Tell us what you need
We would rather build the two connectors our design partners actually use than a directory of fifty that nobody does.
Want a connector we don’t have yet?
Tell us which system your close depends on and we will tell you honestly where it sits on the roadmap.