---
title: "Managed Mapping"
slug: "managed-mapping"
updated: 2025-05-21T11:08:03Z
published: 2025-05-21T11:08:03Z
canonical: "help.csgi.com/managed-mapping"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.csgi.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Managed Mapping

Managed Mapping is a specialized approach used when no direct or derived data path is available an exception-handling mechanism for complex or unmappable data points that standard methods like [Source Path](/cx/docs/source-path-mapping), [Value](/cx/docs/value-mapping), or [Recipe Mapping](/cx/docs/recipes-mapping) can not address. These cases are usually resolved through coordinated backend support from CSG teams, ensuring the necessary transformations are handled reliably.

There may be situations where a variable must be mapped, but:

- No relevant source path exists in the uploaded XML.
- The required value cannot be derived using standard logic or recipes.
- Business logic is too specific to be configured using available UI tools.

In these cases, the Managed Mapping option provides a formal way to flag, track, and hand off complex mapping needs that require custom implementation outside the Bill Explainer interface, ensuring visibility and clear collaboration with backend teams.

![](https://cdn.document360.io/c578bb14-e570-4b6e-93ed-f6c5b8a2d8a1/Images/Documentation/2025-05-13_18-33-57.png?sv=2026-02-06&spr=https&st=2026-10-26T14%3A15%3A50Z&se=2026-10-26T15%3A15%3A50Z&sr=c&sp=r&sig=t5N22WRSlJPVkjv%2Brc%2BDuCr11sJY0fFBWbzaKJlHDFI%3D)

### Status Workflow

Managed Mapping uses two status indicators to help teams manage and monitor progress:

#### In Progress

Select In Progress when:

- The variable mapping requirement has been identified.
- Standard mapping techniques cannot be applied.
- A custom solution or backend code is being developed by the services or implementation team.

This status acts as a trigger for backend teams to begin working on the custom logic needed to support the mapping.

#### Complete

Once the backend work is done:

- The CSG team updates the status to Complete.
- This confirms that custom code is now in place to support the mapping during data transformation.
- The variable is now ready for use, and Bill Explainer can correctly process it using the newly implemented backend logic.

> ![Note](https://cdn.document360.io/c578bb14-e570-4b6e-93ed-f6c5b8a2d8a1/Images/Documentation/Note.png?sv=2026-02-06&spr=https&st=2026-10-26T14%3A15%3A50Z&se=2026-10-26T15%3A15%3A50Z&sr=c&sp=r&sig=t5N22WRSlJPVkjv%2Brc%2BDuCr11sJY0fFBWbzaKJlHDFI%3D)
> 
> To ensure successful test runs, make sure all required variables have a **Completed** mapping status. Testing cannot proceed while any mandatory variables are still marked as Managed Mapping - **In Progress**. Ensure all required mappings are marked as completed before initiating test runs.

### Benefits

- Extends system capabilities by supporting edge cases such as multi-variable conditions or data derived from external systems that go beyond what standard UI-based mappings can handle.
- Enables collaboration between client admins and CSG backend teams for complex needs.
- Provides visibility into the status of In-Progress and Completed custom mappings inside the managed mapping.
- Ensures traceability, helping testers and developers understand which variables rely on custom logic.