DocBits- IDP for Infor ERP
HomeAppStatusAPI
🇳🇱 Nederlands
🇳🇱 Nederlands
  • Overzicht en basisprincipes
    • DocBits
      • Belangrijkste Kenmerken van DocBits
    • Architectuur
      • DocBits Infor on Premise Klant
      • Certificeringen
    • Infor Infrastructuur
    • Release-opmerkingen
  • Eindgebruiker en partners
    • Eindgebruikerssectie
      • Dashboard
        • Dashboard Tools
        • Documenten Samenvoegen
        • Documentstatus
        • Documenten Filteren
        • Overzicht van Geüploade Documenten
        • Taakenteller
        • Gevalideerde Geëxtraheerde Velden
        • Documentflow
        • Problemen oplossen
        • Toetsenbord Sneltoetsen
      • Taken
      • Advance Shipment Dashboard
      • Dashboard voor inkooporders
      • Factuurdashboard
      • Shipment Order Dashboard
      • Gebruikersconfiguratie-opties
      • AI Tabel
        • AI Tabel Tags
      • Validatiescherm
        • Vage Gegevens
        • QR-codes
        • Toetsenbord Sneltoetsen
      • Doel en Gebruik
      • Inkooporder Matching
        • Automatische Afstemming van Inkoopordergegevens
        • Leverancier Artikelnummer Map
        • Toetsenbord Sneltoetsen
      • Boekhouding voor Kostfactuur en Indirecte Verkoop
      • Hoe Documenten te Importeren
        • FTP
        • Handmatige Import
        • Webhook
        • E-mail
          • IMAP
          • OAuth Office365
      • Technische Ondersteuning in DocBits
        • Maak een ticket aan
        • Help-pictogrammen
      • Cursus
        • Introductie
        • Dashboard
        • Geverifieerde Documenten
        • AI Table
        • Master PO Matching met DocBits
      • Ons Document Prioriteit Systeem
      • Leverancier Portaal
        • Leverancier Registratie
        • Leverancierstatus
      • Bronnen en ondersteuning
        • Gebruikersondersteuning
    • Partner Sectie
      • Factuurautomatiseringstest met DocBits
  • Administratie en instelling
    • Instellingen
      • Global Settings
        • Bedrijfsinformatie
          • Defining App Color in Company Settings
        • Groups, Users and Permissions
          • Gebruikers
            • Modifying User Details
            • Admin Privileges
          • Suborganisaties
            • How to create a Sub-Organization
          • Groepen en Machtigingen
            • Purpose and Use
            • Adding/Editing Groups
            • Machtigingen activeren
            • Toegangscontrole
            • Troubleshooting
        • Integration
          • API Key
          • API Calls and Examples
          • API Key Management
          • Configuring Single Sign-On (SSO)
            • Infor SSO Configuration
              • V1
              • V2
              • Azure SSO
          • Identity Service Provider Configuration
          • Best practices
          • Troubleshooting Common Issues
        • Documenttypes
          • Purpose and Scope
          • Adding/Editing Document Types
          • Activation
          • Customization Options
          • Best Practice
          • Troubleshooting
          • Layout Manager
            • Purpose and Use
            • Navigeren in de Lay-outbeheerder
            • Configuring Field Properties
            • Using the Template Preview
            • Save and apply changes
            • Best practices
            • Troubleshooting
          • Document Sub Types
          • Creating a new Sub Type
          • Configure subtypes
          • Using Actions
          • Best Practices
          • Tabelkolommen
            • Purpose and Use
            • Adding a new Column
            • Editing and deleting columns
            • Best practices
            • Troubleshooting
          • Velden
            • Purpose and Use
            • Configuring Field Properties
            • Setting Validation and Match Score
            • Velden Toevoegen en Bewerken
            • Best practices
            • Troubleshooting
            • New Fields with Charges
          • Modeltraining
            • Purpose and Use: Model Training
            • Import Data: Model Training
            • Manage training data
            • Testing the model
            • Best practices
            • Troubleshooting
          • Regex
            • Purpose and use
            • Creating a Regex Pattern
            • Editing and Saving Regex Patterns
            • Best practices
            • Troubleshooting
          • Script
          • Script Activation and Management
          • Testing Scripts
          • Purpose and Use
          • Creating and Editing Scripts
          • Best Practices
          • Troubleshooting
          • e-docs
            • Purpose and Use
            • Setting Up EDI Templates
            • Using the XSLT Editor
            • Previewing EDI Messages
            • Best Practices
            • Troubleshooting
            • XRechnung
              • Standard Preview
            • Mapping XRechnung in DocBits
              • TOML Export
            • EDI 810 (Invoice) Mapping
            • EDI 850 (Purchase Order) Mapping
            • EDI 855 (Purchase Order Acknowledgement) Mapping
            • EDI 856 (Advance Shipment Notice) Mapping
            • Peppol BIS Billing 3.0
            • eSLOG 1.6 en 2.0
          • Meer Instellingen
            • Purpose and use
            • Best practices
            • Troubleshooting
            • Behandeling van dubbele documenten
            • Goedkeuringsstempel
            • Supplier Item Number Map - Admin Documentation
            • Aankooporder tolerantie-instellingen / Extra aankooporder tolerantie
            • Aankooporder uitschakelen statussen
            • PO-tabel in Layout Builder
            • Automatische controle op PO-updates
            • Eenheidsprijs PO berekenen
            • Export niet gematchte PO-regels
        • E-mailmelding
          • Configuring Notifications
          • Managing Notifications
          • Best Practice
          • Troubleshooting
        • Custom Filters
        • Dashboard
          • Customizing Filters
      • Documentverwerking
        • Documents Expiry
        • Importeren
          • Test: Multi Email Import and Handling Tests
          • Test: Email Import and Handling Tests
          • Test: FTP Import Connection
          • Test: File Import 1
        • Regelbeheerder
          • TransactionConfig Pro Template
            • Case 1, 2, 3: Quantity and Unit Price Within Tolerance
            • Case 4, 5: Quantity Within Tolerance, Unit Price Outside Tolerance (Approved)
            • Case 15: Charge Line - Charge Per Unit Outside Tolerance (Rejected)
            • Case 14: Header Charge - Charge Per Unit Outside Tolerance (Approved)
            • Case 12, 13: Header Charge - Charge Per Unit Within Tolerance
            • Charge Per Unit Outside Tolerance (Rejected)
            • Case 14: Charge Line - Charge Per Unit Outside Tolerance (Approved)
            • Charge Per Unit Within Tolerance
            • Case 11b: Quantity Outside Tolerance (Positive Rejected), Unit Price Outside Tolerance (Rejected)
            • Case 10b: Quantity Outside Tolerance (Negative Rejected), Unit Price Outside Tolerance (Rejected)
            • Case 8b, 9b: Quantity Outside Tolerance (Approved), Unit Price Outside Tolerance (Approved)
            • Case 11a: Quantity Outside Tolerance (Positive Rejected), Unit Price Within Tolerance
            • Case 10a: Quantity Outside Tolerance (Negative Rejected), Unit Price Within Tolerance
            • Case 7: Quantity Within Tolerance, Unit Price Outside Tolerance (Positive Rejected)
            • Case 6: Quantity Within Tolerance, Unit Price Outside Negative Tolerance (Rejected)
            • Case 8a, 9a: Quantity Outside Tolerance (Approved), Unit Price Within Tolerance
            • Case 15: Header Charge - Charge Per Unit Outside Tolerance (Rejected)
            • Tax Lines
        • Ocr-instellingen
        • Classificatie En Extractie
          • Tabelextractie voor kostenelement
          • Auto extract belastingcode
        • Master Data Lookup
        • Lijst van Waarden
        • Exporteren
        • Module
          • Annotatiemodus
          • Approval Before Export
          • Doc Scan
          • Doc Script
          • IDM ACL Updater
          • Swiss QR Code
          • Auto Export if PO Matched 100%
        • Beslisbomen
      • Loginstellingen
        • Taakbeheer
        • Gegevenssynchronisatie
      • Leverancier Instelling
        • Leverancier Algemene Instellingen
        • E-mail Sjablonen Bewerken
        • Exportconfiguratie voor Leverancierportaal voor M3
      • API-Licenties
      • Cachebeheer
    • Workflow
      • Release
      • When
        • Card description
        • Document Operator for Sub-Organizations
        • Document Type Operation
      • And
        • Assigned User Condition
        • Checkbox Field Condition
        • Checkbox
        • Combined Price of Quantity Difference
        • Compare two fields
        • Compare with Purchase Order
        • Confirmed Delivery Date
        • Docfield is
        • Document Field Comparison
        • Document Field
        • Document Status Condition List
        • Document Type Operation one of
        • In Order Confirmation Purchase Order
        • Single Assigned User Condition
        • Single Document Status Condition
        • Supplier on Invoice
        • Text in field
        • Unit Price Combined with Fields
      • Then
      • Workflow Example: Conditional Export Trigger
      • Workflow Documentation
      • Standard Workflow
        • Above Max Amount
        • Cost Invoice - Export
        • Less than Max Amount
        • Purchase Invoice - 2nd Approval Quantity Export
        • Purchase Invoice - 2nd Approval Quantity
        • Purchase Invoice - 2nd Approval Unit Price Export
        • Purchase Invoice - 2nd Approval Unit Price
      • Material Ordering and Processing Workflow
    • Setup
      • Document Types
        • EDI Data Transformation Process
        • Layout Builder
        • Origin Layouts
        • Regex Manager
      • Document Training
        • Training Header Fields
        • Training Line Fields/Table Training
          • Adding New Columns
          • Advanced Settings
          • Defining Tables and Columns
          • Grouping Function
          • Manual Row Selection
          • Mapping Columns
          • Save and Delete Rules
      • Stream for Cloud Customers
      • Testing
        • PO Matching
        • Auto Accounting
          • LN
          • M3
      • Leveranciersportaal
      • WatchDog Installatie
  • Infor integratie en configuratie
    • Importing Master Data
      • Field Mappings
      • LN
        • Auto Accounting
        • Suppliers and Purchase Orders
        • Tax Codes
      • M3
        • Auto Accounting
        • Suppliers and Purchase Orders
        • How to import all suppliers
        • Tabelextractie voor kostenelement
      • Custom Master Data
    • Exporting in DocBits
      • Export Module
    • Exporting to INFOR
      • Creating a BOD Mapping File
      • Een IDM Mappingbestand maken
      • Creating an ION API Endpoint
      • Creating an ION API File
      • Export to M3 Mapping (API)
      • Exporting to IDM
      • Order Confirmation
      • M3
        • Handling Charges with Infor M3
        • M3 Configuration
      • LN
        • Exporteer Belastingcodes naar LN
        • LN Configuration
      • Page
  • Geavanceerde functies en tools
    • Scripting in DocBits
      • Calculating Total Charges Script for Docbits
      • Calculating Total Charges Script for Docbits
      • Delete lines with empty quantity and amount
      • Formatting Export Certificate Reference Numbers Script for Docbits
      • Functies
      • Generating Extended Invoice Numbers Script for Docbits
      • Generating Extended Invoice Numbers Script for Docbits
      • USD as Default Currency
    • Course
      • A Step-by-Step Guide
      • Connect DocBits with Infor SSO
      • Create your Custom App in Infor OS
      • Infor OS with DocBits API Integration
      • M3 Export
      • Sync Flex Dimensions: Infor to DocBits
    • Postman for DocBits
    • SQL Access
    • Leverancier- en Inkoopordergegevens importeren in DocBits vanuit CSV-bestanden
    • PowerBI
Powered by GitBook
On this page
  • Overview
  • 1. Transformation
  • Purpose
  • How It Works
  • Admin Capabilities
  • Example:
  • 2. Preview
  • Purpose
  • How It Works
  • Admin Capabilities
  • Example:
  • 3. Extraction Paths
  • Purpose
  • How It Works
  • Admin Capabilities
  • Example:

Was this helpful?

Export as PDF
  1. Administratie en instelling
  2. Instellingen
  3. Global Settings
  4. Documenttypes
  5. e-docs

XRechnung

Overview

In the XRechnung administration panel, you will encounter the following key components:

1. Transformation

Purpose

The Transformation process is essential for converting raw data, usually in XML format, into a structured format that meets specific requirements, like generating an invoice. In XRechnung, this is primarily achieved using XSLT (Extensible Stylesheet Language Transformations). XSLT is a language designed for transforming XML documents into other types of documents, like another XML, HTML, or plain text.

How It Works

• XSLT Template: The XSLT file defines how the XML data is processed and what the final output should look like. It applies rules and templates to extract, manipulate, and output the data from the XML document.

• Elements and Attributes: The XSLT file contains specific elements and attributes that control the transformation process. For instance, <xsl:value-of> is used to extract the value of a specific node from the XML document.

Admin Capabilities

• Modifying the XSLT:

• Edit Existing Templates: An admin can modify the existing XSLT templates to change how the input XML data is transformed. For example, if there’s a need to extract additional information from the XML document, an admin could add new rules in the XSLT file.

• Create New Versions: If changes are required, an admin can create a new version of the XSLT template. This ensures that previous versions remain intact for historical reference or rollback if needed.

Example:

Suppose the XSLT template extracts the invoice ID using:

<xsl:value-of select="//INVOICE/INVOICE_ID/text()" />

If a new field, such as a customer reference number, needs to be extracted, an admin might add:

<xsl:value-of select="//INVOICE/CUSTOMER_REFERENCE_NUMBER/text()" />

2. Preview

Purpose

The Preview function allows admins to view the output generated by the XSLT transformation before finalizing it. This step is crucial for ensuring that the transformation rules work correctly and that the output meets the required standards.

How It Works

• Real-Time Validation: The preview feature provides a real-time rendering of how the transformed data will look when applied to an actual document (like an invoice). This helps in catching errors or formatting issues early.

• Adjustments: If the preview shows discrepancies or errors, adjustments can be made directly in the transformation (XSLT) file.

Admin Capabilities

• Customizing the Preview:

• Modify Preview Settings: An admin can adjust which parts of the transformation are previewed. For instance, they might focus on specific sections of the document or test new rules added to the XSLT template.

• Save and Iterate: After making adjustments, the preview can be refreshed to see the changes. This iterative process allows fine-tuning until the desired output is achieved.

Example:

If an admin notices that the date format in the preview is incorrect (e.g., showing YYYY-MM-DD instead of DD-MM-YYYY), they can modify the XSLT to format the date correctly and immediately see the result in the preview.

3. Extraction Paths

Purpose

Extraction Paths define the specific paths within an XML or JSON structure from which data should be extracted. This process is essential for isolating key pieces of information within the document that will be used in the transformation or for other processing tasks.

How It Works

• XPath and JSONPath: Extraction paths use languages like XPath (for XML) or JSONPath (for JSON) to specify the location of the data within the document. These paths are crucial in telling the system exactly where to find and how to extract the required information.

Admin Capabilities

• Defining and Modifying Paths:

• Modify Existing Paths: An admin can modify the extraction paths if the data structure changes or if additional data needs to be extracted. This might involve changing the XPath or JSONPath expressions.

• Add New Paths: For new fields or data points, an admin can define new extraction paths. This would involve specifying the correct path in the XML or JSON document.

Example:

In an XML invoice document, if the path to the invoice ID is defined as:

"invoice_id": "//INVOICE/INVOICE_ID/text()"

And a new field, such as a shipping address, needs to be added, an admin might add:

"shipping_address": "//INVOICE/SHIPPING/ADDRESS/text()"

PreviousTroubleshootingNextStandard Preview

Was this helpful?