Skip to main content
Platform Configuration covers the settings that decide how DualEntry behaves for everyone in your organization: the entity and currency structure your books are kept in, who can do what, how records are shaped and approved, and what gets logged. Most of this is configured once during implementation and revisited when the business changes shape, such as when you add a subsidiary, open a new tax jurisdiction, or restructure a team.

​
Structural settings

These define the shape of your books, and they are the settings with the widest downstream effect.
  • Multi-entity and consolidation: the entity hierarchy, intercompany rules, automatic eliminations, and consolidated reporting.
  • Multi-currency: base and transactional currencies, FX rate feeds, translation rules, and month-end revaluation policy.
  • Fiscal year-ends: a per-company fiscal year-end, how period locking replaces period status, and reporting across companies whose fiscal years differ.
  • Tax Management: US sales and use tax, EU and UK VAT, and GST across international jurisdictions.
Change these early. Entity structure and base currency in particular are assumptions that every posted transaction inherits, so revisiting them after a period is closed means restating rather than reconfiguring.

​
Records, workflow, and access

These settings govern day-to-day behavior: what your records look like, who has to sign off, and who can see them.
  • Organization Settings: the configuration hub for branding, core accounting preferences, customer- and vendor-facing email templates, API keys, and a settings-level audit log.
  • Custom fields: which record types accept them, the field types available, company scoping, API access, and how they behave in reports.
  • Date formats: personal, organization, and company date settings, and which one controls in-app views versus customer-facing documents.
  • Approval workflows: multi-stage approval policies with conditional routing, require-all or require-any steps, and spend thresholds.
  • User roles and permissions: built-in and custom roles, entity scoping, and the full permission matrix for users and teams.
  • Subscription billing: contracts, billing schedules, usage-based pricing, and proration, feeding automated revenue recognition.
  • Budgets and forecasts: dimensional budgets, an actuals offset for rolling views, and variance reporting against actuals.
Roles and approval workflows are worth configuring together. An approval policy can only route to someone whose role lets them act on the record, so a policy built before roles are settled tends to strand requests at a step nobody can clear.

​
Compliance and evidence

Two pages cover what DualEntry records about itself and what it can prove to an auditor. Audit trail and compliance documents how every change to your data is recorded, how retention works, and how that record supplies evidence during SOC 2, SOX, and internal control reviews. Security and compliance covers how customer data is protected and where to find current attestations, subprocessor lists, and security policies on the Trust Center. If you are configuring an organization for the first time, the Get Started section sequences these tasks alongside migration and go-live.
Last modified on September 14, 2026