> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-smart-connect/setup-and-configuration/data-handlers.md).

# Data handlers

Complete reference of all data handlers available in Smart Connect processors.

Data handlers are transformation processors that define how data flows from Smart Connect queues into Dynamics 365 Finance & Operations. Each data handler is selected in a processor definition and determines the integration framework and format used for data import, validation, and posting.

Data handlers follow the **Microsoft Dynamics 365 Finance & Operations standard framework** for electronic reporting and data management.

**Configuration location:** **Smart Connect > Definitions > Processors** > **Data handler** field

## Input data handlers

Input data handlers transform incoming data from connectors into F\&O format.

### NANHandlerInDmf - Data Management Framework Import

**Purpose:** Import data using the Data Management Framework (DMF)

**Functionality:**

* Leverages F\&O Data Management Framework for bulk imports
* Supports data entity mappings
* Enables DMF-based validation and staging
* Handles DMF import sequences and error handling

**Use case:** Bulk data imports; large-scale data migrations; DMF entity-based processing; staged data imports

**F\&O Framework:** Data Management Framework (DMF)

***

### NANHandlerInDmfJsonToXml - JSON to XML Conversion for DMF

**Purpose:** Convert JSON formatted data to XML for DMF processing

**Functionality:**

* Parses JSON input data structures
* Converts to XML format required by DMF
* Validates JSON schema and structure
* Enables JSON-based APIs to use DMF framework

**Use case:** External systems sending JSON data for DMF import; API-to-DMF integration

**Input format:** JSON

**Output format:** XML (for DMF processing)

***

### NANHandlerInDmfNoHeader - Data Management Framework Without Header

**Purpose:** Import DMF data without header row processing

**Functionality:**

* Processes DMF imports without requiring header rows
* Handles headerless data files or streams
* Enables direct data import without structural metadata

**Use case:** Headerless data feeds; continuous data streams; systems that don't provide headers

**F\&O Framework:** Data Management Framework (DMF)

***

### NANHandlerInER - Electronic Reporting Import

**Purpose:** Import and process data using Electronic Reporting (ER) framework

**Functionality:**

* Integrates with F\&O Electronic Reporting module
* Processes data formatted according to ER configurations
* Supports XML and JSON data formats
* Applies ER-based transformations and validations
* Posts data through ER import routines

**Use case:** Importing data that requires Electronic Reporting module integration; external data feeds formatted for ER processing

**F\&O Framework:** Electronic Reporting (ER)

***

### NANHandlerInSalesXmlJson - Sales Order XML/JSON Import

**Purpose:** Import sales order data from XML or JSON formats

**Functionality:**

* Parses sales order data from XML or JSON sources
* Maps source format to sales order structure
* Validates order lines, quantities, and pricing
* Creates or updates sales orders in F\&O
* Handles customer and product lookups

**Use case:** EDI-based sales order imports; JSON APIs delivering sales orders; external sales system integration

**Input formats:** XML, JSON

**Output:** Sales orders (SalesTable)

**F\&O Framework:** Standard Sales Order processing

***

### NANHandlerInTungstan - Tungstan/Purchase Order Import

**Purpose:** Import purchase order and related supply chain documents

**Functionality:**

* Extracts PO header and line details
* Validates quantities and unit prices
* Matches to existing F\&O purchase orders
* Handles delivery documentation and scheduling
* Creates or updates purchase order data

**Use case:** EDI-based purchase order imports; supplier order management; goods receipt processing

**Input format:** Tungstan EDI format

**Output:** Purchase orders (PurchTable), Goods receipts

**F\&O Framework:** Standard Purchase Order processing

***

### NANHandlerInMySupplyDistributor - MySupply Distributor Integration

**Purpose:** Integrate with MySupply distributor platform for order processing

**Functionality:**

* Processes data from MySupply EDI/API sources
* Handles distributor-specific data mappings
* Validates supplier and product data
* Creates purchase orders or goods receipts
* Manages distributor synchronization

**Use case:** Distributor integration; MySupply EDI feeds; supplier order management

**F\&O Framework:** Standard Purchase Order processing

***

### NANHandlerInDMSUbl - UBL Invoice Data Handler

**Purpose:** Process electronic invoices in UBL format with Document Warehouse integration

**Functionality:**

* Validates UBL XML schema (2.0, 2.3)
* Extracts invoice header and line items
* Performs vendor lookup and validation
* Stores original document in Birds Document Warehouse
* Creates vendor invoice in F\&O with document link

**Input:** UBL XML invoice documents (2.0, 2.3)

**Output:** Vendor invoices (VendInvoiceTable) with Document Warehouse reference

**F\&O Framework:** Accounts Payable with Document Warehouse integration

***

### NANHandlerInDMSUbl\_RO - UBL Invoice with Regulatory Output

**Purpose:** Process UBL invoices with regulatory compliance requirements

**Functionality:**

* Validates UBL XML schema compliance
* Extracts invoice header and line details
* Processes regulatory compliance requirements
* Creates vendor invoices in F\&O
* Maintains audit trail for compliance

**Use case:** E-invoicing compliance; UBL-based electronic invoices; cross-border invoice processing; regulatory reporting

**Input:** UBL XML invoices (2.0, 2.3)

**Output:** Vendor invoices with regulatory metadata

**F\&O Framework:** Accounts Payable with regulatory extensions

***

### NANHandlerInDMSUblV2 - UBL Invoice Handler V2

**Purpose:** Updated UBL invoice handler with enhanced functionality

**Functionality:**

* Enhanced UBL schema validation
* Improved vendor matching and validation
* Extended Document Warehouse integration
* Additional compliance features

**Input:** UBL XML invoices

**Output:** Vendor invoices with enhanced Document Warehouse linking

**F\&O Framework:** Accounts Payable

***

### NANHandlerInDMSTungsten - Purchase Document Data Handler for DMS

**Purpose:** Process purchase orders and goods receipts in Smart Connect DMS

**Functionality:**

* Extracts PO header and line details
* Validates quantities and unit prices
* Matches to existing F\&O purchase orders
* Identifies discrepancies and flags exceptions
* Stores procurement documentation in Document Warehouse
* Creates goods receipt notes when configured

**Input:** Purchase documents (EDI, XML, JSON)

**Output:** Purchase confirmations and goods receipt notes with document references

**F\&O Framework:** Standard Purchase Order processing with Document Warehouse

***

### NANHandlerInDMSMySupply - MySupply Integration in DMS

**Purpose:** Integrate MySupply distributor data with Document Warehouse storage

**Functionality:**

* Processes MySupply distributor order and master data
* Validates supplier and product information
* Stores documentation in Document Warehouse
* Creates or updates purchase orders and master records

**Input:** MySupply EDI/API data

**Output:** Purchase orders and master data records with document references

**F\&O Framework:** Standard Purchase Order and Master Data processing

***

## Output handlers

Output handlers export or route processed data from processors to external systems, files, or queues. They are configured in queue output settings.

### NANHandlerOutAPI - API Output Handler

**Purpose:** Send transformed data to external HTTP/HTTPS APIs

**Functionality:**

* Formats data for REST/SOAP API endpoints
* Handles authentication (Basic auth, OAuth, custom headers)
* Manages API request/response processing
* Implements retry logic for failed API calls
* Supports JSON and XML output formats
* Logs API responses and errors

**Use case:** Publishing data to cloud services; webhooks; external system integration; real-time data synchronization

**Output format:** JSON, XML

**F\&O Framework:** Standard outbound API integration

***

### NANHandlerOutDmf - Data Management Framework Export

**Purpose:** Export data via the Data Management Framework (DMF)

**Functionality:**

* Exports data through F\&O DMF data entities
* Supports DMF export jobs and staging
* Handles entity-to-file transformation
* Manages export sequencing and error handling

**Use case:** Bulk data exports; F\&O data entity exports; DMF-based integrations

**F\&O Framework:** Data Management Framework (DMF)

***

### NANHandlerOutDmfXmlToJson - XML to JSON Conversion for DMF Export

**Purpose:** Convert DMF-exported XML data to JSON format

**Functionality:**

* Transforms XML output to JSON structure
* Handles schema conversion and data mapping
* Validates JSON output structure
* Enables JSON consumption of DMF exports

**Use case:** APIs expecting JSON; external systems requiring JSON format; data transformation pipelines

**Input format:** XML (from DMF)

**Output format:** JSON

***

### NANHandlerOutER - Electronic Reporting Output

**Purpose:** Generate and export data using Electronic Reporting (ER)

**Functionality:**

* Generates reports using ER format configurations
* Creates document outputs (PDF, Excel, XML, etc.)
* Applies ER business logic and formatting
* Handles ER-based document generation

**Use case:** Document generation; regulatory reporting; formatted output creation

**Output formats:** PDF, Excel, XML, and other ER-supported formats

**F\&O Framework:** Electronic Reporting (ER)

***

### NANHandlerOutGenerateER - Generate Electronic Report

**Purpose:** Create Electronic Reports from F\&O data

**Functionality:**

* Generates ER-based reports
* Applies report formatting and layouts
* Supports parameterized report generation
* Handles report distribution

**Use case:** Report generation; formatted document creation; compliance reporting

**F\&O Framework:** Electronic Reporting (ER)

***

### NANHandlerOutGenerateER\_BusinessDocumentSubmission - Generate ER for Business Document Submission

**Purpose:** Generate Electronic Reports for business document submission to authorities

**Functionality:**

* Creates authority-compliant business documents
* Applies regulatory format requirements
* Manages document submission workflows
* Generates audit trails for submissions

**Use case:** Authority submissions; regulatory compliance; formal business document generation

**Output format:** Authority-specified formats (XML, etc.)

**F\&O Framework:** Electronic Reporting with regulatory extensions

***

### NANHandlerOutEdi - EDI Export Handler (Base)

**Purpose:** Export data in EDI (Electronic Data Interchange) format

**Functionality:**

* Transforms data to EDI message format
* Handles EDI segment structure and validation
* Manages EDI transmission protocols
* Supports standard EDI message types

**Use case:** EDI-based B2B integration; supplier communication; standard EDI compliance

**Output format:** EDI (X12, EDIFACT)

**F\&O Framework:** Standard EDI processing

***

### NANHandlerOutEdiAgcoFendt - EDI Export for AGCO Fendt

**Purpose:** Export data in AGCO Fendt-specific EDI format

**Functionality:**

* Formats data according to AGCO Fendt EDI specifications
* Handles AGCO Fendt message validation
* Manages AGCO Fendt-specific transmissions

**Use case:** AGCO Fendt supplier integration; equipment manufacturer orders

**Output format:** AGCO Fendt EDI format

***

### NANHandlerOutEdiBaywa - EDI Export for Baywa

**Purpose:** Export data in Baywa-specific EDI format

**Functionality:**

* Formats data according to Baywa EDI specifications
* Handles Baywa message validation
* Manages Baywa-specific EDI transmissions

**Use case:** Baywa agricultural supply integration; order processing for Baywa

**Output format:** Baywa EDI format

***

### NANHandlerOutEdiDeWulf - EDI Export for De Wulf

**Purpose:** Export data in De Wulf-specific EDI format

**Functionality:**

* Formats data according to De Wulf EDI specifications
* Handles De Wulf message validation
* Manages De Wulf-specific EDI transmissions

**Use case:** De Wulf agricultural equipment integration; supplier orders

**Output format:** De Wulf EDI format

***

### NANHandlerOutEdiKrone - EDI Export for Krone

**Purpose:** Export data in Krone-specific EDI format

**Functionality:**

* Formats data according to Krone EDI specifications
* Handles Krone message validation
* Manages Krone-specific EDI transmissions

**Use case:** Krone agricultural equipment integration; equipment ordering

**Output format:** Krone EDI format

***

### NANHandlerOutLog - Logging Output Handler

**Purpose:** Log processed data for debugging and audit trails

**Functionality:**

* Records data at each processing stage
* Formats log entries for readability
* Manages log file creation and retention
* Enables troubleshooting and audit tracking

**Use case:** Debugging; audit trails; testing; data flow verification

**Output format:** Log files, system logs

***

### NANHandlerOutSalesInvoice - Sales Invoice Export

**Purpose:** Export sales invoice data from F\&O

**Functionality:**

* Extracts sales invoice details from F\&O
* Formats invoice data for external systems
* Handles invoice line items and totals
* Manages invoice transmission

**Use case:** Invoice distribution; customer communication; external accounting systems

**Output:** Sales invoice data

**F\&O Framework:** Standard Sales Invoice processing

***

### NANHandlerOutSalesInvoiceXml - Sales Invoice XML Export

**Purpose:** Export sales invoices in XML format

**Functionality:**

* Converts sales invoice data to XML structure
* Validates XML schema compliance
* Handles XML formatting for external systems
* Enables XML-based invoice processing

**Use case:** XML-based invoice systems; EDI invoice transmission; structured data export

**Output format:** XML

**F\&O Framework:** Standard Sales Invoice processing

***

### NANHandlerOutSalesOrders - Sales Orders Export

**Purpose:** Export sales order data from F\&O

**Functionality:**

* Extracts sales order details
* Formats order data for external systems
* Handles order lines and scheduling
* Manages order transmission to customers/partners

**Use case:** Customer order communication; order management systems; supply chain systems

**Output:** Sales order data

**F\&O Framework:** Standard Sales Order processing

***

### NANHandlerOutEventQueue - Event Queue Handler

**Purpose:** Queue events for asynchronous processing

**Functionality:**

* Creates events from processor output
* Routes events to internal queues
* Enables event-driven processing
* Manages event sequencing and delivery

**Use case:** Asynchronous processing workflows; event-driven architecture; decoupled systems

**Output:** Internal event queues

***

### NANHandlerOutPaymentFile - Payment File Generation

**Purpose:** Generate payment files for financial institutions

**Functionality:**

* Formats payment data to bank/financial institution standards
* Creates payment files (SEPA, ACH, etc.)
* Validates payment file structure
* Handles payment transmission

**Use case:** Vendor payments; salary processing; interbank transfers; payment automation

**Output formats:** SEPA XML, ACH, proprietary bank formats

**F\&O Framework:** Accounts Payable with payment integration

***

### NANHandlerOutPD - Physical Dimension Output

**Purpose:** Export physical dimension data

**Functionality:**

* Extracts dimension data from F\&O
* Formats dimension information for external systems
* Handles dimension hierarchies

**Use case:** Reporting dimension data; analytics; external BI system integration

**Output:** Dimension data

***

### NANHandlerOutDR - Document Routing Output

**Purpose:** Route documents to Document Routing destinations

**Functionality:**

* Directs processed documents to configured destinations
* Manages document delivery workflows
* Handles archival and retrieval

**Use case:** Document management; workflow routing; document distribution

**F\&O Framework:** Document Routing framework

***

### NANHandlerOutAS2 - AS2 Protocol Handler

**Purpose:** Send data using AS2 (Applicability Statement 2) protocol

**Functionality:**

* Implements AS2 secure transmission protocol
* Manages digital signing and encryption
* Handles MDN (Message Disposition Notification)
* Ensures reliable message delivery

**Use case:** Secure B2B communication; AS2-based EDI; partner integrations requiring AS2

**Output format:** AS2-formatted messages

**F\&O Framework:** Secure EDI protocol

***

### NANHandlerOutDMSUbl - UBL Invoice Export with Document Warehouse

**Purpose:** Export UBL-formatted invoices with Document Warehouse storage

**Functionality:**

* Converts invoice data to UBL XML format
* Validates UBL schema compliance
* Stores invoice copy in Document Warehouse
* Manages invoice transmission

**Use case:** E-invoice distribution; UBL-compliant invoicing; cross-border invoice transmission

**Output format:** UBL XML (2.0, 2.3)

**F\&O Framework:** Accounts Receivable with Document Warehouse

***

### NANHandlerOutDMSProjectInvoice - Project Invoice Export with Document Warehouse

**Purpose:** Export project-based invoices with Document Warehouse storage

**Functionality:**

* Extracts project invoice details
* Formats invoices for external customers
* Stores invoice documents in Document Warehouse
* Links invoices to project records

**Use case:** Project billing; professional services invoicing; project accounting

**Output:** Project invoices with Document Warehouse references

**F\&O Framework:** Project Accounting with Document Warehouse

***

### NANHandlerOutMySupplyDownloadConfirmation - MySupply Confirmation Download

**Purpose:** Download and process confirmations from MySupply platform

**Functionality:**

* Retrieves confirmations from MySupply
* Parses confirmation data
* Updates F\&O with confirmation status
* Manages confirmation workflow

**Use case:** MySupply order confirmations; distributor acknowledgment processing

**Input:** MySupply confirmations

**Output:** F\&O confirmation records

***

### NANHandlerOutTungstenVendors - Vendor Data Export to Tungsten

**Purpose:** Export vendor master data to Tungsten platform

**Functionality:**

* Extracts vendor information from F\&O
* Formats vendor data for Tungsten
* Handles vendor attribute mapping
* Manages vendor synchronization

**Use case:** Vendor data synchronization; Tungsten vendor management; master data distribution

**Output:** Tungsten vendor records

***

### NANHandlerOutTungstenVendorBanks - Vendor Bank Data Export to Tungsten

**Purpose:** Export vendor bank account data to Tungsten platform

**Functionality:**

* Extracts vendor bank details from F\&O
* Formats bank information for Tungsten
* Validates bank account data
* Manages bank data synchronization

**Use case:** Vendor bank account sync; payment routing information; master data management

**Output:** Tungsten vendor bank records

***

***

## Data handler selection guidelines

When configuring a processor, choose the data handler based on:

| Factor                        | Consideration                                                            |
| ----------------------------- | ------------------------------------------------------------------------ |
| **Data source**               | Which external system is sending data? (API, EDI, file, etc.)            |
| **Data format**               | What is the data format? (XML, JSON, ER format, etc.)                    |
| **Target entity**             | Where should data be posted in F\&O? (Sales orders, invoices, POs, etc.) |
| **F\&O module**               | Which F\&O module handles this data? (AP, AR, Inventory, GL, etc.)       |
| **Compliance**                | Are regulatory or audit requirements needed?                             |
| **Document storage**          | Is document warehousing required? (Use DMS handlers)                     |
| **Transformation complexity** | Does the handler support required transformations?                       |

***

## Handler availability summary

**Input handlers (Core framework - 7):**

* NANHandlerInDmf
* NANHandlerInDmfJsonToXml
* NANHandlerInDmfNoHeader
* NANHandlerInER
* NANHandlerInSalesXmlJson
* NANHandlerInTungstan
* NANHandlerInMySupplyDistributor

**Input handlers (DMS - 5):**

* NANHandlerInDMSUbl
* NANHandlerInDMSUbl\_RO
* NANHandlerInDMSUblV2
* NANHandlerInDMSTungsten
* NANHandlerInDMSMySupply

**Output handlers (25):**

*Export & API:*

* NANHandlerOutAPI – HTTP/HTTPS APIs
* NANHandlerOutDmf – DMF export
* NANHandlerOutDmfXmlToJson – XML to JSON conversion
* NANHandlerOutER – Electronic Reporting
* NANHandlerOutGenerateER – Generate ER
* NANHandlerOutGenerateER\_BusinessDocumentSubmission – ER for business submission

*EDI & Transmission:*

* NANHandlerOutEdi – Base EDI
* NANHandlerOutEdiAgcoFendt – AGCO Fendt EDI
* NANHandlerOutEdiBaywa – Baywa EDI
* NANHandlerOutEdiDeWulf – De Wulf EDI
* NANHandlerOutEdiKrone – Krone EDI
* NANHandlerOutAS2 – AS2 protocol

*Sales & Invoicing:*

* NANHandlerOutSalesInvoice – Sales invoice export
* NANHandlerOutSalesInvoiceXml – Sales invoice XML
* NANHandlerOutSalesOrders – Sales orders export
* NANHandlerOutDMSUbl – UBL invoice with Document Warehouse
* NANHandlerOutDMSProjectInvoice – Project invoice with Document Warehouse

*Financial:*

* NANHandlerOutPaymentFile – Payment file generation

*Data & Routing:*

* NANHandlerOutLog – Logging
* NANHandlerOutEventQueue – Event queue
* NANHandlerOutPD – Physical Dimension
* NANHandlerOutDR – Document Routing

*Integration:*

* NANHandlerOutMySupplyDownloadConfirmation – MySupply confirmations
* NANHandlerOutTungstenVendors – Tungsten vendors
* NANHandlerOutTungstenVendorBanks – Tungsten vendor banks

***

## Related pages

* [Processors and transformations](https://docs.dynalogic.com/birds-smart-connect/readme/processors-and-transformations.md)
* [Connectors and connectivity](https://docs.dynalogic.com/birds-smart-connect/setup-and-configuration/connectors-and-connectivity.md)
* [Queues and message handling](https://docs.dynalogic.com/birds-smart-connect/setup-and-configuration/queues-and-message-handling.md)
* [Document processing and formats](https://docs.dynalogic.com/birds-smart-connect/setup-and-configuration/document-processing-and-formats.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dynalogic.com/birds-smart-connect/setup-and-configuration/data-handlers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
