Product

One system for close, approvals, and floor data.

Six modules, one record. Each does a defined job and hands its output to the next, so nothing is re-keyed and nothing depends on a spreadsheet only one person can edit.

Modules

Pick a module, see its screen.

Every screen is the real layout filled with labeled sample data. Move through the list with the pointer or the arrow keys.

Ledger matching

Bank lines, invoices, and receipts are matched as they arrive. Exceptions keep their context so reviewers decide in seconds.

  • Automatic matching rules with visible mappings
  • Exception queue sorted by impact
  • Every match keeps its source documents
Numbers

The month, measured.

Progress and effort per period, from the reporting module. Each chart is keyboard-readable, and every figure has a table alternative.

Days to close, last 8 periods days · sample data
4 4.8 5.6 6.4 Mar Apr May Jun Jul Aug Sep Oct
View as table
Days to close, last 8 periods as a table
Perioddays
Mar6.2
Apr5.8
May6.4
Jun5.1
Jul4.8
Aug4.4
Sep4.6
Oct4
Team hours per close step hours · sample data
0 3 6 Matching Approvals Journals Recon Reports
View as table
Team hours per close step as a table
Periodhours
Matching3.5
Approvals6
Journals4.2
Recon5.1
Reports2.2
Where close time goes % of hours · sample data
Approvals Matching Rework Reporting Other 100 hours %
View as table
Where close time goes as a table
Period% of hours
Approvals31
Matching28
Rework18
Reporting12
Other11
Capabilities

What ships in every workspace.

Ledger matching

Bank lines, invoices, and receipts are matched as they arrive. Exceptions keep their context so reviewers decide in seconds.

  • Automatic matching rules with visible mappings
  • Exception queue sorted by impact
  • Every match keeps its source documents

Approval flows

Requests route by amount, cost center, and team. Approvers see the full chain, so sign-off never waits in an inbox.

  • Policy-based routing with limits
  • Delegate and reminder scheduling
  • Sign-off recorded with reason codes

Close checklist

The month-end close runs as a shared checklist with owners and dependencies. Progress is visible while it happens, not after.

  • Templates per entity and period
  • Owners, due dates, and blockers
  • Pinned notes on every step

Inventory visibility

Stock counts, variances, and work-in-progress land next to the ledger. Operations and finance argue from the same numbers.

  • Warehouse and batch level detail
  • Variance thresholds that alert
  • Cycle count scheduling

Audit trail

Every change carries who, what, and when. Auditors get read-only access and exportable evidence without a support ticket.

  • Immutable event log
  • Read-only auditor seats
  • Export packs per period

Close reporting

Close status, burn, and variance reports generate as the period progresses. Leadership reads progress instead of asking for it.

  • Report templates with schedules
  • Share links with expiry
  • CSV and PDF exports
Approvals

Rules that read like your policy.

Approval routing is configuration, not code. Admins edit the rules, test them against a sandbox, and roll them out with a version number — and the audit trail shows which version applied to every decision.

  • Amount limits per approver, enforced before the request is sent
  • Cost-center ownership resolved from your chart of accounts
  • Two-person rule on payments above the threshold you set
  • Emergency overrides that expire and are reported on the close pack
Connections

18 connectors, each with scoped credentials.

Read where you allow, write only where you connect two-way. Credentials are revocable and every sync run is logged.