Sage Intacct — dimensional crypto accounting
Sage Intacct's dimensions (Department, Location, Project, Class) are first-class, and Wag3s posts crypto JEs that respect them.
Sage Intacct is one of the leading mid-market US ERPs and a common alternative to NetSuite. Its dimensional model — every transaction tagged across Department, Location, Project, Class, Customer, Vendor — gives finance teams strong reporting flexibility. Wag3s posts crypto JEs with the right dimension tags so the GL stays sliceable. Multi-entity support handles the consolidation workflow for groups with multiple subsidiaries.
What the Sage Intacct integration does
Daily JE sync with full dimensions
Department, Location, Project, Class tags applied per JE line.
Multi-entity consolidation
Each Sage Intacct entity maps to a Wag3s entity; consolidation works without manual reclass.
Audit-trail integration
Sage Intacct's audit log captures every Wag3s post; the on-chain hash is on the JE line.
The connection in 4 steps
Connect Sage Intacct via Web Services credentials
Create a Web Services user in Sage Intacct with a restricted role — journal entry post and GL read only. Wag3s authenticates using the company ID, user ID, and password via the Sage Intacct XML API.
Map Wag3s entities to Sage Intacct entities
Each Wag3s entity (operating company, foundation, DAO treasury) is mapped to its Sage Intacct entity. Multi-entity setups post JEs against the correct entity and consolidate at the top level.
Configure dimensions per wallet
Assign dimension defaults per wallet — Department, Location, Project, Class — in the Wag3s dimension mapping table. Wag3s applies these tags to every JE line, keeping Sage Intacct's dimensional reports sliceable.
Daily JEs post with full dimension detail
Each day's classified crypto activity posts as a Sage Intacct journal entry with GL account, amount, currency, dimensions, and on-chain transaction hash on every line.
Common configurations
The company holds USDC and ETH in a Safe multi-sig treasury alongside traditional cash in Mercury. Sage Intacct is the GL. Wag3s posts daily crypto JEs with the correct Department and Project dimensions, so the crypto treasury integrates with the existing dimensional P&L reporting without manual reclassification.
The foundation uses Sage Intacct with multi-entity enabled — one entity for foundation operations, one for the DAO treasury. Wag3s posts per-entity JEs and reconciles intercompany grant transfers, giving the finance team a clean consolidated view at month-end.
Sage Intacct integration questions
How are dimensions configured?
Per-wallet dimension defaults can be set in Wag3s (e.g. wallet X is always Department 100, Project DAO Treasury). Override per-transaction via classification rules.
Are Sage Intacct dimensions (Project, Department, Location, Class) supported in the COA mapping?
Yes. All standard Sage Intacct dimensions — Department, Location, Project, Class, Customer, Vendor — are available in the Wag3s dimension mapping table. Defaults can be set per wallet (e.g. a treasury wallet is always tagged to Department 100, Project DAO Treasury) and overridden per transaction category via classification rules. Every journal entry line posted to Sage Intacct carries the configured dimension tags, keeping your dimensional reports fully sliceable.
Does the Wag3s integration respect Sage Intacct SOX controls?
Yes. Wag3s connects via a dedicated Web Services user with a restricted role — journal entry post and GL read only, with no ability to modify chart of accounts or user permissions. Journal entries are posted in draft state and require validation by an authorized Sage Intacct user before they affect the GL, preserving the segregation-of-duties control. The on-chain transaction hash is included on every JE line as an immutable audit reference.
Other connectors that pair with this one.
Connect Sage Intacct in minutes
Free during Alpha. No credit card. Native sync, audit trail, no spreadsheets.