Period close, controls, and an audit trail you can hand to auditors.

The five-stage close

Accruals, FX, intercompany, lock, statements.

Accruals auto-reverse on day one. FX revaluation runs against live rates and auto-reverses. Intercompany eliminations post as paired entries. Periods lock at the row level once statements are issued. Trial balance is database-enforced (debits equal credits on every posted JE) so the close focuses on the work that actually requires judgment.

• Accruals: configurable, auto-reverse on day one of the next period.
• FX revaluation: ASC 830 monetary items at the period-end rate.
• Intercompany eliminations: paired entries with shared audit-trail IDs.
• Period locking: row-level lock once statements are issued.

AI Accountant close

Run the close. Review every proposal before it posts.

AI Accountant close mode reviews an entity's books for a period and prepares the work: it flags what is blocking the close and drafts the period-end entries across the subledgers - prepaid and depreciation amortization, revenue recognition, accruals, loan interest and principal, FX revaluation, and the allowance for doubtful accounts. Nothing posts automatically. Every draft lands in the review queue for a human to approve through the same controls - separation of duties, permissions, and period locks - and only then posts via SmartGL.

• One run surfaces blockers and draft entries across the subledgers for an entity and period.
• Proposes, never posts: a human approves every entry before it reaches the ledger.
• Flags trial-balance breaks, unfinished bank and intercompany reconciliations, stale crypto fair value, unposted stock comp and dividends, and unremitted sales tax.
• Variance and flux analysis highlights material month-over-month swings for review.

Dual-Control Mode

Drafter and approver, separated by design.

Dual-Control Mode is available on every plan. The user preparing a journal entry, bill, invoice, or settings change cannot be the same user who posts or applies it. Approval chains are configurable per workflow.

• Drafter and approver enforced as different users.
• Configurable approval chains and routing rules.
• Separation of duties enforced, not optional.
• Per-record audit trail (every change is attributable.

Outlier detection

Anomalies flagged with the reasoning shown.

GL outlier detection runs configurable rules across posted entries: Z-score by account, Benford's law on first-digit distributions, unusual account combinations, round-number patterns, weekend postings, and threshold dodging. Every flagged entry comes with a written explanation you can hand to the reviewer.

• Z-score by GL account over recent periods.
• Benford's law on first-digit distributions.
• Unusual account combinations.
• Round-number, weekend, and threshold-dodging detection.
• Written explanation for every flagged entry.

Audit log

Every action preserved.

The audit log records every user action against every record, capturing who edited what, what the prior value was, when the change was applied, and which IP and session it came from. The log is immutable.

Why Quoining

A close that runs on the ledger, not on a checklist in Excel.

Industry surveys keep finding that the overwhelming majority of closes still run through spreadsheets, which is why they take weeks. Quoining's close lives where the entries are: blockers are computed from the actual state of your books, and controls are enforced by the system rather than promised by a policy document.

• Close readiness is calculated live: uncategorized activity, unreconciled accounts, draft entries, pending approvals.
• Dual-control and separation-of-duties are available on every plan, not an enterprise upsell.
• Period locks are real locks; nothing back-posts into a closed period silently.