Skip to main content
These pages are accounting controls. They are meant to reveal mismatches so the team can fix the source transaction or posting issue before reports and period close are trusted.

​
Open GL Reconciliation

Open Finance > Close & Reconcile > GL Reconciliation. You can also search for GL Reconciliation in the command palette, or follow the link from Period Close, the Finance dashboard or a subledger drift card. You need permission to view accounting. Click Run Reconciliation to refresh balances. Use Export Summary when accounting needs a CSV of the current control-account status. What is GL Reconciliation? explains the three figures on each card. If the data cannot load, the page says Failed to load reconciliation data. Please try again.

​
What The Cards Mean

  • GL Balance: posted journal entry activity for the control account.
  • Subledger Balance: operational detail that should support the GL balance, such as open customer balances, vendor bills, inventory value, or tax activity.
  • Variance: GL Balance minus Subledger Balance. A clean control should be zero or within rounding tolerance.
  • Balanced: the control account and subledger agree.
  • Variance: the control account and subledger do not agree and need review.
Click a card row to expand it and see the individual documents behind the variance: orders and invoices for receivables, bills for payables, products by location for inventory, and invoice tax for tax payable. Rows highlighted in red have a mismatch between what was posted to the GL and the subledger balance. If the detail cannot load, it says Failed to load detail. Please try again.

​
The Receivables Difference, Broken Down

For receivables, the expanded card breaks the difference between the receivables detail and its control account into named components, then shows any difference that remains. Available customer credits appear as context under Not part of this difference; they are not counted in it. The same difference appears as a warning, not a blocker, on the Period Close checklist.
Do not force a variance away with a blind journal entry A variance usually means a source record, posting rule, mapping, or historical import needs review. Post a manual entry only after accounting understands why the subledger and GL disagree.

​
Review GL Balance Integrity

GL Balance Integrity checks whether posted journal entries balance debits and credits. If an unbalanced entry appears, stop close work and investigate before relying on reports or reconciliation totals.
  • Clean: all checked entries have equal debits and credits.
  • Unbalanced: one or more entries need accounting and technical review.
  • Entries checked: the count of journal entries included in the check.
  • Debits and credits: the total debit and credit values included in the run.
  • Delta: the difference between debits and credits.

​
Review Clearing Account Health

Clearing Account Health shows balances that should eventually drain out, such as Stripe clearing, check clearing, or external marketplace clearing. Current clearing balances can be normal. Old balances need review.
  • Review old Stripe, marketplace, check, and payment clearing balances before close.
  • Trace stale rows back to payouts, bank deposits, check clearing, or payment records.
  • Use Account Ledger to inspect the individual entries inside a clearing account.
Pair this with Period Close Run GL Reconciliation and review GL Integrity before closing a period. Period Close is much cleaner when control accounts and integrity checks are already understood.

​
Open GL Integrity

GL Integrity has no entry in the navigation. Open it by adding /accounting/gl-integrity to your Arcus address. The log shows the most recent integrity checks. Filter by run type or result when you need to confirm whether drift happened in a nightly job, manual review, or period-close workflow.

​
Integrity Run Types

  • Nightly: scheduled check that watches for drift after daily activity.
  • Manual: user-triggered check during investigation or review.
  • Period close: close-related check used before a period is approved.

​
When A Variance Appears

  1. Open the variance card in GL Reconciliation.
  2. Export the summary if accounting wants an offline review copy.
  3. Open Account Ledger for the control account.
  4. Compare the ledger activity to the source records in AR, AP, inventory, tax, payouts, or bank reconciliation.
  5. Fix the source record or posting configuration when possible.
  6. Post an approved accounting adjustment only when the source cannot be corrected directly.
  7. Run reconciliation again and confirm the variance cleared.

​
Common Blocks

  • No control accounts found: set up receivables, payables, inventory and tax payable accounts in Chart of Accounts, then run the reconciliation again.
  • Inventory variance: review inventory value, receipts, adjustments, and fulfillment postings.
  • AR variance: review customer invoices, payments, credits, and manual journal entries to AR accounts.
  • AP variance: review vendor bills, payments, credits, checks, and GRNI activity.
  • Tax variance: review invoice tax totals, tax payable postings, and tax connector settings.
  • Clean integrity but control variance: entries may balance overall while the wrong control account was used.

Chart of Accounts

Understand account structure, account types, and posting behavior.

Journal Entries

Create, review, and reverse journal entries.

Account Ledger

Review transaction history, source activity, debits, credits, and running balance for one GL account.

Bank Reconciliation

Match bank transactions to payments, deposits, payouts, and checks.

Financial Reports

Run balance sheet, profit and loss, cash flow, and operational reports.

Period Close

Close, approve, reopen, and audit accounting periods with pre-close checklist controls.