Skip to main content

Troubleshooting Guide: Resolving Company Mismatch Between Deposit and Invoice

Distributor troubleshooting for a company mismatch error between a deposit and invoice in Encompass: compare the Company on both, check edits or imports, and correct the wrong record. v26.01+.

B
Written by Bailey Naas-Thornton

Minimum Version Required: 26.01

Pre-Conditions

  • Permissions: Logged in as an administrator or a user with permissions to view and edit General Ledger (GL) configurations, Invoices, and Deposits.

  • System State: Requires an active internet connection and access to the ERP or financial management system.

  • Required Data: You must have the exact DepositID and InvoiceID referenced in the error message.

Steps

  • Locate the Records: Search your system using the specific DepositID and InvoiceID provided in the error message to open both records in separate tabs.

  • Verify Company Assignments: Check the "Company" field on both the Invoice and the Deposit. Note which organizational entity is assigned to each.

  • Review Manual Edits: Check the audit logs or field history for both records. Look for instances where manual data editing changed one side of the relation without cascading updates.

  • Validate Ledger Context: If the records were created recently, ensure that the wrong target company context was not applied at the time of ledger posting.

  • Inspect Integrations: If the records were created via an automated import, check the integration logs to ensure the integration pipeline did not import invoices and deposits under mismatching organizational entities.

  • Correct the Mismatch: If your user permissions allow, update the incorrect record so that the Company matches the related transaction. Be careful not to create a cross-company data linkage attempt violating data segregation boundaries.

  • Contact Support: If the issue persists, or if you cannot save the records due to missing structural cross-validation rules before saving the entity state, contact support immediately. Please gather and provide the following information for efficient troubleshooting:

    • Exact error messages or codes encountered.

    • Screenshots or video recordings of the issue.

    • Log files (specify import or integration logs if applicable).

    • The exact steps taken by the customer that led to the issue.

    • The date and time the issue was first observed and any recurrence.

    • Any changes made to the system before the issue appeared.

Fields And Definitions

  • Company: The General Ledger's company entity that financial transactions are tied to.

  • Deposit ID: The unique identifier for each deposit record in the system.

  • Invoice ID: The unique identifier for a specific invoice.

  • Data Segregation Boundaries: Strict systemic rules designed to prevent financial data and transactions belonging to one company from bleeding into or linking with another company.

  • Cross-Validation Rules: Background logic checks that ensure all linked data points (like an invoice and its payment deposit) share the required criteria (such as the same Company) before the system allows the record to be saved.

Best Practices

  • Establish Import Guidelines: Regularly review integration mappings to ensure that pipelines explicitly assign matching organizational entities for related records like invoices and deposits.

  • Limit Manual Overrides: Restrict the ability to manually edit the Company field on posted transactions. If manual editing is required, ensure users are trained to update all sides of the transaction to prevent changing one side of the relation without cascading updates.

  • Utilize Default Contexts: Encourage users to log into the specific target company context before initiating ledger postings to avoid applying the wrong company context at the time of entry.

Did this answer your question?