> 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/document-processing-and-formats.md).

# Document processing and formats

Configure document format handling in Smart Connect DMS with Birds Document Warehouse.

The DMS (Document Management System) module extends Smart Connect with specialized document format handling and processing. It integrates with **Birds Document Warehouse** to provide document storage, validation, and routing.

## What is document processing?

Document processing in DMS:

* Receives structured documents (UBL, accounting documents, purchase documents)
* Parses and validates format-specific data
* Extracts structured data (invoice numbers, amounts, vendor details, line items)
* Routes documents to Finance & Operations and stores in Document Warehouse
* Provides audit trails and compliance reporting

## Handler types overview

Smart Connect uses handlers to process different document types and manage data routing. Handlers are specialized processors that validate, transform, and integrate document data.

### Handler framework

Smart Connect handlers follow the **Microsoft Dynamics 365 Finance & Operations standard framework** for electronic reporting and data management. This ensures consistency with F\&O's native data processing capabilities and compliance with standard business workflows.

### Core handlers

Core Smart Connect handlers manage fundamental data routing and processing:

* **Queue handlers** – Route messages from connectors to processors; manage payload storage and retrieval
* **Processor handlers** – Apply business logic transformations and field mappings
* **Response handlers** – Log processing results and manage status tracking
* **Error handlers** – Capture and retry failed messages with configurable retry logic

### DMS handlers

The Document Management System extends Core handlers with specialized document processing:

* **UBL handler** – Processes electronic invoices in UBL (Universal Business Language) format
* **Raptor handler** – Processes accounting documents and general ledger entries
* **Tungsten handler** – Processes purchase orders and goods receipt documents

Each DMS handler validates format-specific data and routes documents to Birds Document Warehouse for storage and retrieval.

***

## Supported document formats

### UBL (Universal Business Language)

**Purpose:** Standardized electronic invoice format\
**Use case:** E-invoicing, international invoice exchange, compliance requirements\
**Input:** XML file conforming to UBL 2.0 or 2.3 standard\
**Processing:** Schema validation, data extraction, format conversion\
**Output:** Structured vendor invoice data ready for F\&O posting

**Document Warehouse integration:**

* Validates XML schema compliance
* Stores original XML document for audit trail
* Extracts and structures invoice line items
* Maintains document-to-posting link for traceability

### Raptor (accounting documents)

**Purpose:** General accounting document format\
**Use case:** Manual journal entries, inter-company transactions, accounting reconciliation\
**Input:** XML or JSON formatted accounting document\
**Processing:** GL account validation, cost center mapping, amount validation\
**Output:** General journal entry data ready for posting

**Document Warehouse integration:**

* Validates GL accounts and cost centers against F\&O dimension tables
* Stores linked documents for approval and audit
* Maintains source document trail for reconciliation

### Tungsten (purchase documents)

**Purpose:** Purchase order and goods receipt document format\
**Use case:** Supplier orders, goods receipt matching, procurement workflows\
**Input:** EDI or digital purchase document\
**Processing:** Line item extraction, quantity validation, delivery date parsing\
**Output:** Purchase order and goods receipt data for F\&O

**Document Warehouse integration:**

* Captures and stores procurement documentation
* Matches extracted PO data to F\&O purchase orders
* Flags quantity discrepancies for review
* Stores source documents with transaction metadata

## Configuring document format handling

The DMS configuration is integrated with Smart Connect connectors and processors. While DMS extends the Core functionality, the underlying configuration uses Core Smart Connect forms and tables.

{% hint style="warning" %}
DMS-specific configuration screens and connectors may be accessed through custom DMS extensions or through Core Smart Connect parameters and processor configuration. Verify availability of DMS-specific forms in your Smart Connect installation.
{% endhint %}

### Format configuration through connectors

Document formats are typically handled through specialized DMS connectors:

| Connector Type      | Formats Handled         | Description                     |
| ------------------- | ----------------------- | ------------------------------- |
| UBL Connector       | UBL invoices (2.0, 2.3) | Electronic invoice processing   |
| Exaccount Connector | Accounting documents    | GL entry and journal processing |
| Tungstan Connector  | Purchase documents      | PO and goods receipt processing |

### Using format-specific processors

Each format type has corresponding processor configuration:

| Processor Type        | Formats              | Configuration                           |
| --------------------- | -------------------- | --------------------------------------- |
| UBL Invoice Processor | UBL invoices         | Validation rules, schema settings       |
| Accounting Processor  | Accounting documents | GL/cost center mapping, validation      |
| Purchase Processor    | Purchase documents   | Line item extraction, quantity matching |

## Document validation and quality assurance

### UBL document validation

UBL documents are validated during processing:

* **Schema validation:** Verify XML conforms to UBL 2.0 or 2.3 standard
* **Required fields:** Vendor code, invoice number, amount, line items
* **Data type validation:** Amounts are numeric, dates are valid, quantities are positive
* **GL account validation:** GL accounts and cost centers match F\&O setup

### Exaccount document validation

Accounting documents are validated against F\&O:

* **GL account lookup:** Verify all GL accounts exist in F\&O
* **Cost center validation:** Cost centers must be valid in F\&O dimensions
* **Amount validation:** Totals and line items must balance
* **Narrative validation:** Required narrative fields are populated

### Tungstan document validation

Purchase documents are validated for completeness:

* **PO matching:** Link to existing F\&O purchase orders
* **Line item validation:** Quantities match PO specifications
* **Delivery date validation:** Dates are reasonable and within business rules
* **Quantity variance:** Flag over/under-receipt beyond configured tolerance

## Document Warehouse integration

DMS documents are automatically linked to **Birds Document Warehouse** for:

* **Permanent storage:** Source documents stored with audit trail and metadata
* **Document-to-posting link:** Source document linked to F\&O transaction for traceability
* **Retrieval:** Quick access to source documents for audits and inquiries
* **Compliance:** Document retention policies and audit trail

### Accessing documents in Document Warehouse

Documents processed by DMS are stored in Birds Document Warehouse. To retrieve and review documents:

1. Access Birds Document Warehouse (contact your Document Warehouse administrator)
2. Search by invoice number, vendor, date range, or other metadata
3. View the document details and linked F\&O records
4. Access document history and audit trail

## Performance and best practices

### Optimize document processing

* **Batch processing:** Process multiple documents in batches rather than individually
* **Validation rules:** Configure appropriate validation to catch errors early
* **Document retention:** Archive documents after retention period to manage storage

### Quality assurance

* **Test document samples:** Validate processor behavior with representative documents before production
* **Monitor error logs:** Review processing failures to identify format or validation issues
* **Verify GL account mapping:** Ensure GL accounts and cost centers are correctly configured
* **Audit transactions:** Regularly verify that source documents link correctly to F\&O transactions

### Troubleshooting

| Issue                             | Cause                                               | Solution                                                                                          |
| --------------------------------- | --------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
| Document format not recognized    | Document doesn't match expected format              | Verify document is in correct format (UBL XML, Exaccount JSON, etc.); check format version        |
| Validation error                  | Document data fails validation checks               | Review validation error message; fix document data (GL accounts, cost centers, amounts)           |
| GL account not found              | GL account in document doesn't exist in F\&O        | Verify GL account number is correct; confirm account is active in F\&O                            |
| Document Warehouse not responding | Service unavailable or network issue                | Check Document Warehouse status; verify connectivity; contact DMS administrator                   |
| Document stuck in processing      | Processor not completing or error in transformation | Check processor logs; verify all required fields present in document; review transformation rules |

## Related pages

* [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)
* [Processors and transformations](https://docs.dynalogic.com/birds-smart-connect/readme/processors-and-transformations.md)
* [Predefined scenarios](https://docs.dynalogic.com/birds-smart-connect/readme/predefined-scenarios-and-use-cases.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/document-processing-and-formats.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.
