Skip to main content

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.

Bulk Re-categorize can update many bank transactions at once. Always run the preview first, review the proposed GL changes, and confirm the accounting period policy before committing.

​
When To Use Bulk Re-categorize

Use Bulk Re-categorize when accounting has tuned categorization rules and wants historical bank activity to follow the updated logic. Good uses include:
  • New categorization rules were created for repeat merchants.
  • MCC defaults were reviewed and mapped to better GL accounts.
  • Suggested rules were accepted after repeated manual overrides.
  • Opening bank-feed imports need an initial pass through the current rule set.
  • Uncategorized bank transactions need cleanup before reconciliation.
Do not use Bulk Re-categorize as a substitute for bank reconciliation. It chooses or updates GL categories. It does not match the bank row to a posted payment, deposit, AP check, or marketplace payout.
Categorization Rules settings page with active rules, suggestions, vendor signals, confidence KPI, and Rules, Suggested Rules, MCC Defaults, Vendor Suggestions, and Audit Trail tabs

​
Open Bulk Re-categorize

  1. Open Accounting.
  2. Choose Bulk Re-categorize.
  3. Select the scope.
  4. Run preview.
  5. Review the proposed changes.
  6. Commit only when the preview is correct.

​
Choose The Scope

The scope controls which transactions Arcus evaluates.
ScopeUse it whenRisk
Only uncategorized transactionsYou want to fill blanks without touching already reviewed rows.Lowest risk. Existing categories stay as they are.
All transactionsYou intentionally want the current rules to re-evaluate existing categories.Higher risk. Prior manual decisions can be overwritten.
Start with uncategorized transactions unless accounting has a clear reason to reprocess everything.

​
Review The Preview

Preview mode shows what would change before anything is committed. Review:
  • Date and description.
  • Amount.
  • Current GL account.
  • Suggested GL account.
  • Confidence score.
  • Source of the suggestion.
Confidence is a review clue, not an approval. A high confidence row can still be wrong when a merchant name is reused for different activity or when the business uses a special GL treatment.

​
Commit The Changes

Commit applies the previewed result to the selected scope. After commit:
  • The bank transaction categories update.
  • The categorization audit trail records how the change was applied.
  • Reconciliation and reporting views use the updated category going forward.
  • The change does not create a bank match by itself.
  • The change does not create or void source documents.
If the preview looks wrong, reset, adjust the rules, test again, then rerun the Bulk Re-categorize preview.

​
Common Scenarios

ScenarioWhat to do
New merchant rule was createdPreview uncategorized rows first, then commit if the merchant and account are correct.
A broad rule caught too muchCancel, lower its priority, add tighter conditions, and test the rule before retrying.
Accounting wants to reclassify a prior monthConfirm period policy first. Do not reclassify closed-period activity without approval.
Preview count is zeroThe selected scope has no eligible rows, or the rules do not match the historical transactions.
Suggested GL account is wrongFix the rule or MCC default before committing. Do not commit and clean it up later.

​
Common Blocks

  • Run Preview is disabled: choose a scope and wait for the page to finish loading.
  • No rows appear: try the uncategorized/all scope intentionally and verify rules are active.
  • Commit is disabled: run preview first and confirm the preview has eligible rows.
  • Confidence is low: review the rule source and prefer a narrower merchant rule.
  • Period is closed: follow the period-close policy before changing historical categories.
  • Reconciliation is still unmatched: categorize first, then use the match workspace to pair bank rows with posted cash activity.

Categorization Rules

Create, test, prioritize, bulk apply, and audit GL auto-categorization rules.

Bank Feed Match Workspace

Match bank transactions to posted cash, AP payments, checks, and marketplace payouts.

Bank Reconciliation

Start and complete bank reconciliations after transactions are categorized and matched.

Chart of Accounts

Maintain the GL accounts used by categorization rules and bank activity.