Working Smarter with the Crestwood Concurrent Module in Acumatica

Working Smarter with the Crestwood Concurrent Module in Acumatica

If your organization uses SAP Concur for expenses or AP automation, you’ve likely dealt with the challenge of getting clean, usable data into Acumatica. The Crestwood Concurrent Module is a connector built by Crestwood Associates that automates this entire process. It pulls data from Concur into Acumatica, applies mapping rules, and ensures transactions land in the correct place with minimal manual cleanup.

This article is designed for finance teams, accounting managers, AP leaders, and Acumatica administrators who want clearer visibility into how data is transformed, when you can use the out-of-the-box mapping tools, and when custom extensions might be the right next step.

What the Concurrent Module Does Out of the Box

The module includes several powerful transformation tools that help standardize and clean data as it moves from Concur into Acumatica. These features give teams more control, consistency, and accuracy before a transaction ever reaches an Acumatica screen.

Cross-Reference Mapping

When Concurrent pulls data into Acumatica’s holding area, the Cross Reference Mapping screen lets you transform values on the way in. Common mapping elements include:

  • Branch
  • Vendor
  • Account
  • Subaccount
  • Project
  • Task
  • Payment Method

Key options include:

  • Use XRef Map: Pulls the value from your mapping table.
  • Only Allow Mapped Values: Ensures data doesn’t import unless the value exists in your map.
  • Mapping Grid: Provides a simple Value → Mapped Value structure.

If something imports incorrectly, simply delete the holding record, adjust the mapping, and reimport.

Transformation Tools

To clean up or format incoming data, you can:

  • Strip characters from the left or right
  • Remove a specific string
  • Prepend or append text to an imported value

These tools are ideal for quick formatting fixes without development work.

When You Need More Than the Standard Options

Some organizations require logic that goes beyond standard mappings and transformations. Common examples include:

  • Creating a subaccount or vendor value using multiple fields
  • Pulling a value based on a lookup inside Acumatica
  • Building data relationships or rules that Concurrent doesn’t provide

In these cases, Acumatica’s customization framework allows you to extend the Concurrent Module for more sophisticated automation.

How Custom Extensions Work

Each holding area screen in the module such as Bill Maintenance, Expense Maintenance, or Payment Maintenance includes an overridable method called LineAboutToBeInserted. This method runs after Acumatica finishes its standard import logic but before it saves the final transaction line.

By overriding the method, your team can:

  • Enforce custom validation rules
  • Build conditional mapping logic
  • Combine or restructure fields
  • Trigger logging for exceptions or missing data

Here is a simplified example that ensures a Subaccount value meets a required length and logs an error if not:

public delegate CWCCExpenseLines LineAboutToBeInsertedDelegate(CWCCExpenseLines line);
[PXOverride]
public CWCCExpenseLines LineAboutToBeInserted(CWCCExpenseLines line, LineAboutToBeInsertedDelegate baseMethod)
{
    if (!String.IsNullOrEmpty(line.SubAccount) && (line.SubAccount.Length >= 5))
    {
        line.SubAccount = line.SubAccount.Substring(0,5);
    }
    else
    {
        CWCCLogEntry.AddLog(“EXT-LineAboutToBeInserted”, “Sub could not be parsed – Sub set to ‘XXXXX'” , CWCCMessages.INFOLOGERROR, CWCCSynchObject.Expense);
        line.SubAccount = “XXXXX”;
    }

    return line;
}

This level of customization allows organizations to enforce data standards that align with internal processes, reporting needs, and auditing requirements.

Who Benefits Most From These Capabilities

This blog is particularly valuable for:

  • Controllers, Accounting Managers, and AP Supervisors who need reliable, accurate imports
  • IT or ERP Administrators maintaining Acumatica customizations
  • Organizations with complex chart-of-account structures or multi-entity environments
  • Teams scaling Concur usage and looking to reduce manual cleanup
  • Companies wanting faster closes and cleaner reporting

If your team needs to integrate Concur with  Acumatica the Concurrent Module helps reduce errors, eliminate manual rework, and ensure your data flows into Acumatica correctly from the start.

Ready to Improve Your Concur-to-Acumatica Process?

Crestwood has helped hundreds of companies improve and automate their financial processes. If you want to:

  • Evaluate whether your mapping and transformation setup is optimized
  • Explore custom extensions for advanced automation
  • Get support implementing or upgrading the Concurrent Module

Our Acumatica experts are here to help.

Talk with Crestwood about optimizing your Concur integration.

Written by: Crestwood Products

Related Articles