Minimum Version Required: 22.01
Pre-Conditions
System: Encompass Mobile.
Permissions: Administrative access to Financial Settings, AR Account Maps, and Company Records.
Configuration: Multiple company records or Mapped Locations exist within the site environment.
Scenario: Invoices are being processed through Load Sheets where "Split Invoicing" or specific AR Account Mapping is active.
Steps
Identify the Invoice Type: Determine if the invoices on the deposit slip are standard or if they utilize the Split Invoice functionality.
Verify AR Account Mapping: Navigate to the AR Account Maps settings. Check if the invoices in question are hitting an AR Account tied to a specific Mapped Location.
Check Load Sheet Route Location: If the invoice is NOT a split invoice, verify the Route.Location associated with the Load Sheet. The system will default to this location ID for grouping.
Analyze the Logic Trigger: Review the data based on the following logic flow:
If Invoice.SplitInvoice is empty: The system groups by the Load Sheet's Route Location.
If Invoice.SplitInvoice is NOT null: The system groups by the Mapped Location ID found in the invoice's ARAccount.ARMap.
Reconcile Company Records: Ensure that the desired "Expected Behavior" (combined totals) aligns with your AR mapping. If multiple company records exist, the system will naturally split the deposits if they map to different locations.
Contact Support: If the grouping logic remains inconsistent with your business requirements after verifying the mappings above, contact Encompass Support. Please provide the following information:
Exact Issue: Discrepancy between actual and expected grouping on Deposit Slips.
Examples: Specific Invoice numbers and Load Sheet IDs involved.
Evidence: Clear screenshots of the Deposit Slip showing the split totals.
System Details: The name of the site environment and the date/time the behavior was first observed.
Configuration Changes: Any recent changes to Company Records, AR Account Maps, or Mapped Locations.
Fields And Definitions
ARAccount.ARMap: The specific mapping configuration that determines which ledger account and location an Accounts Receivable entry is directed to.
Invoice.SplitInvoice: A field indicating whether a single transaction has been divided into multiple invoice records, often triggering specialized routing logic.
Mapped Location: A defined entity in Encompass used to segregate financial data and physical inventory, which directly influences how deposits are categorized.
Route.Location: The primary location associated with a specific delivery route and its corresponding load sheets.
LoadSheet.Location: The physical or logical site where a load sheet is generated and settled.
Best Practices
Consistency in Mapping: To maintain a single combined total on deposit slips, ensure that all relevant AR Accounts point to the same Mapped Location where possible.
Single Company Record: If your business structure allows, utilizing a single company record simplifies deposit grouping by tying all AR accounts to a single entity.