> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arcuserp.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Account Ledger
> Account Ledger shows transaction history for one GL account at a time. Use it to explain a financial report balance, investigate a reconciliation variance, or trace how source workflows affected a specific account.
Account Ledger is read-only review. To change accounting activity, update the source
transaction when possible, or create an approved journal entry when accounting needs a
manual adjustment.
## Open Account Ledger
Open **Accounting > Account Ledger**. Select a GL account, then optionally
choose a date range. Arcus lists journal entry lines for that account and calculates a
running balance based on the account normal balance.
## What To Review
* **Account selector**: choose the exact GL account you are investigating.
* **Date range**: narrow to the period, statement date, or close window being reviewed.
* **Balance**: current balance for the selected account and filter context.
* **Total debits and credits**: totals for the visible ledger activity.
* **Entry number**: journal entry reference that can be reviewed on Journal Entries.
* **Description**: source or manual-entry context.
* **Source**: the workflow that created the accounting line, such as payment, bank, check, bill, order, or manual.
* **Running balance**: balance after each row, useful when reconciling a point in time.
**Use the ledger after reports point you to an account**
If Financial Reports show an unexpected balance, identify the account, open Account
Ledger, set the same date range, then inspect the source activity behind the balance.
## Investigate A Variance
1. Open the report, reconciliation, or close checklist item that showed the issue.
2. Identify the GL account number involved.
3. Open Account Ledger and select that account.
4. Set the date range to the period being reviewed.
5. Look for unexpected source types, backdated entries, large entries, or manual adjustments.
6. Open Journal Entries for the entry number when line-level detail is needed.
7. Open the source workflow when the entry came from an order, bill, payment, bank transaction, inventory event, return, or payout.
**Do not edit around the source record**
If the ledger line came from an operational record, fix the operational record when
possible. Manual entries that bypass the source workflow can make the GL look better
while AR, AP, inventory, tax, or banking stays wrong.
## Bulk Re-categorize Bank Transactions
Bulk Re-categorize is a separate accounting tool for bank transactions. It applies
categorization rules to historical bank activity. Operators choose the scope, run a
preview, review suggested account changes, and commit only after the preview is correct.
* **Only uncategorized transactions**: safer default because it fills gaps without overwriting existing categories.
* **All transactions**: wider scope that can overwrite existing categorization and should be used carefully.
* **Preview**: shows what would change before anything is committed.
* **Confidence**: helps reviewers decide whether the rule match is strong enough.
* **Commit**: applies the selected scope after the preview is reviewed.
**Preview first, every time**
The bulk tool is useful during cleanup, migration, or rule rollout. Always preview first,
and avoid the all-transactions scope unless accounting expects existing categorization to
change.
## Common Blocks
* **No accounts appear**: confirm Chart of Accounts is configured and the user has accounting access.
* **No entries found**: check the date range, account selection, and whether activity has posted.
* **Totals differ from a report**: verify the report and ledger use the same date range and account.
* **Source looks wrong**: open Journal Entries, then follow the source record link when available.
* **Bulk preview looks risky**: stop and adjust categorization rules before committing.
## Related Articles
Understand account structure, account types, and posting behavior.
Create, review, and reverse journal entries.
Compare control accounts to subledgers, review clearing account health, and audit GL integrity check logs.
Run balance sheet, profit and loss, cash flow, and operational reports.
Configure fixed asset categories, lease payment routing, and transaction categorization rules.
Match bank transactions to payments, deposits, payouts, and checks.