Recipes Mapping allows admins to automate how Bill Explainer identifies and maps data from the source file using logical rules. Use Recipes when your data varies too much for fixed paths or values, and default methods like Source Path Mapping or Value Mapping aren not sufficient.
Instead of manually assigning variables one by one in the Source Path, Value Mapping steps, or Recipes apply smart, rule-based logic to detect and assign values based on patterns, contexts, and conditions in the data. For Example: Labeling a line item as a discount when the description contains the word “Promo.”
This is especially useful for mapping dynamic or variable content like item names, discounts, surcharges, or section headers where consistent paths may not exist, but identifiable patterns do.
Recipes use Rule-Based Identification to recognize and map data fields automatically by applying a set of user-defined conditions. These rules can be simple or complex and are built using logical constructs such as:
Single term matching - Matches exact words or terms.
Sentence term matching - Detects phrases or combinations of words.
Value-based matching - Matches based on known or expected values (For Example: 10% Discount).
Context-based matching - Considers data position or placement (For Example: item name appearing below a specific section).
Tag and attribute-based matching - Uses the structure of the XML (For Example: tag names or attributes) to guide matching.
Path-based matching - Applies logic to specific data paths extracted from XML files.
Practical Example
Is Description - A boolean variable indicating whether the item is a description. If set to true, the system treats the item as additional information linked to the preceding line item in the bill hierarchy. Here is an example of how to use Recipes to flag descriptive line items.
Select the Source Path - Click on the Source Path field, search for the required path, and select it from the list of available XML paths.
Configure the Value Filter - Click on the Value button to define a filter using the contains parameter.
Search for an existing value.
If the value appears, select it from the list.
If not, click the suggested value to create it.
Finalize the Mapping - After selecting the source path and value, click the Select button to confirm and link the recipe configuration to the variable.
Once configured, the variable is successfully mapped. The system will use this mapping to dynamically populate the bill content during rendering. This enables Bill Explainer to detect and apply the variable each time a new bill is processed, ensuring consistent and accurate content generation.
Benefits
Saves Time: Speeds up configuration by automating repeated or complex mapping scenarios.
Automates Mapping: Reduces the need for manual mapping by using intelligent rule-based logic.
Handles Complexity: Supports advanced logic for mapping data with varied structures or dynamic content.
Improves Accuracy: Matches data with higher precision by applying specific patterns or conditions.
Reduces Errors: Minimizes the chances of incorrect mappings due to human error.