DocBits- IDP for Infor ERP
HomeAppStatusAPI
🇺🇸 English
🇺🇸 English
  • Overview and Basics
    • DocBits
      • Key Features of DocBits
    • Architecture
      • DocBits Infor on Premise Customer
      • Certifications
    • Infor Infrastructure
    • Release Notes
      • Testing Availability on Sandbox
    • FAQ
      • General Information
      • Document Processing
        • Table Extraction Troubleshoot
      • Infor LN (LN Integration)
        • Export Error: "Error Exporting Document to LN. Status Code: 500"
          • not found in direct debit
          • Request validation; Attr. 'ReceiptLine', Value " " : the value must be numeric.
      • Infor M3 (M3 Integration)
        • Costing elements are not properly configured. Please ask your admin to configure it.
      • Mandatory PDP/PPF Channels – PEPPOL as Transport Only for France’s 2026 E-Invoicing
  • End User and Partner Section
    • End User Section
      • Dashboard
        • Dashboard Tools
        • Document Merging
        • Document Status
        • Filtering Documents
        • Overview of Uploaded Documents
        • Task Counter
        • Validated Extracted Fields
        • Document Flow
        • Troubleshooting
        • Keyboard Shortcuts
      • Tasks
      • Advance Shipment Dashboard
      • Purchase Order Dashboard
      • Invoice Dashboard
      • Shipment Order Dashboard
      • User Configuration Options
      • AI Table
        • AI Table Tags
      • Validation Screen
        • Automatic Checks on the Validation Screen
        • Fuzzy Data
        • QR Codes
        • Keyboard Shortcuts
      • Purpose and Use
      • Purchase Order Matching Screen
        • Purchase Order Matching Tools
        • Rules and Calculations
        • Automatic Purchase Order Data Matching
        • Supplier Item Number Map
        • Keyboard Shortcuts
      • Accounting for Cost Invoice and Indirect Sales
      • How to Import Documents
        • Manual Import
        • Webhook
      • Technical Support in DocBits
        • Create a ticket
        • Help Icons
      • Course
        • Introduction
        • Dashboard
        • Validated Documents
        • AI Table
        • Master PO Matching with DocBits
      • Our Document Priority System
      • Supplier Portal
        • Supplier Registration
        • Supplier Satuts
      • Ressources and Support
        • User Support
        • Support Portal Status
    • Partner Section
      • Invoice Automation Testing with DocBits
  • Administration and Setup
    • Settings
      • Global Settings
        • Company Information
          • Defining App Color in Company Settings
        • Groups, Users and Permissions
          • Users
            • Modifying User Details
            • Admin Privileges
          • Sub-Organizations
            • How to create a Sub-Organization
          • Groups and Permissions
            • Purpose and Use
            • Adding/Editing Groups
            • Activating Permissions
            • Access Control
            • 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
        • Document Types
          • Purpose and Scope
          • Adding/Editing Document Types
          • Activation
          • Customization Options
          • Best Practice
          • Troubleshooting
          • Layout Manager
            • Purpose and Use
            • Navigating the Layout Manager
            • 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
          • Table Columns
            • Purpose and Use
            • Adding a new Column
            • Editing and deleting columns
            • Best practices
            • Troubleshooting
          • Fields
            • Purpose and Use
            • Adding and Editing Fields
            • Configuring Field Properties
            • Setting Validation and Match Score
            • Best practices
            • Troubleshooting
            • New Fields with Charges
          • Model Training
            • 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
            • Currently Supported E-Invoice Standards
              • Roadmap
            • E-Invoice examples
              • XRechnung 1.2
              • XRechnung 2.0
              • XRechnung 2.1
              • XRechnung 2.2
              • XRechnung 2.3
              • XRechnung 3.0
              • XRechnung Cross Industry Invoice
              • FacturX
            • EDI Settings: Overview & Benefits
              • EDI Structure Descriptor File Guide
                • EDI Structure descriptor
              • EDI Transformation File Guide
              • EDI Preview File Guide
              • EDI Extraction Paths File Guide
              • EDI Videos
              • EDI Mappings
                • EDI 810 (Invoice) Mapping
                • EDI 850 (Purchase Order) Mapping
                • EDI 855 (Purchase Order Acknowledgement) Mapping
                • EDI 856 (Advance Shipment Notice) Mapping
            • XRechnung
              • Standard Preview
              • Mapping XRechnung in DocBits
                • TOML Export
            • Peppol BIS Billing 3.0
              • Transformation file and Mapping
            • Faktura
            • ZUGFeRD 1.0, 2.1 and 2.3
            • eSLOG 1.6 and 2.0
          • More Settings
            • Purpose and use
            • Best practices
            • Troubleshooting
            • Duplicate Detection
            • Approval
              • Approval Stamp
              • Approval History
            • Purchase Order
              • PO Table in Layout Builder
              • Auto check for PO updates
              • Calculate PO unit price
              • Export not matched PO lines
              • Purchase order tolerance settings / Additional purchase order tolerance
              • Purchase order disable statuses
              • Supplier Item Number Map - Admin Documentation
        • Email Notification
          • Configuring Notifications
          • Managing Notifications
          • Best Practice
          • Troubleshooting
        • E-Mail templates
        • Dashboard
          • Customizing Filters
      • Document Processing
        • Documents Expiry
        • Import
          • Test: Multi Email Import and Handling Tests
          • Test: Email Import and Handling Tests
          • Test: FTP Import Connection
          • Test: File Import 1
        • Rule Manager
          • 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 Settings
        • Classification And Extraction
          • Table extraction for costing element
          • Auto extract tax code
        • Master Data Lookup
        • List Of Values
        • Export
        • Module
          • Annotation Mode
          • Approval Before Export
          • Doc Scan
          • Doc Script
          • IDM ACL Updater
          • Inbound Emails
          • Swiss QR Code
          • Auto Export if PO Matched 100%
          • Export Dashboard Data
          • How to Create Database Access for a Specific Organization User
        • Decision Trees
      • Log Settings
        • Task Management
        • Data Synchronization
      • API Licenses
      • Supplier Setting
        • Supplier General Settings
        • Editing Email Templates
        • Supplier Layout
        • Export Configuration for Supplier Portal for M3
        • Supplier Permissions
      • Cache Management
    • Workflow
      • When
        • Card description
        • Document Type Operation
        • Document Type One of
      • And
        • Compare with Purchase Order
          • Combined Price of Quantity Difference
          • Unit Price Combined with Fields
          • Promised Delivery Date on Purchase Order
          • Order Data in Order Confirmation
          • Confirmed Delivery Date
          • Compare Order Confirmation with Purchase order
          • Tax in document field
          • Any / All Quantity
          • Compare Total Charges
          • Out of Tolerance Unit Price
          • Any / All Unit Price is
          • Item Id on Purchase Order
          • Supplier on Invoice
          • Order Type of Purchase Order
        • Document Field
          • Checkbox is checked
          • Field is
          • Text in Field
          • Compare two Fields with Tolerance
          • Compare two Fields
          • If Country in Field
          • Docfield is
          • Compare Field with tolerances
          • If Country in Field is One of
        • Date & Time
          • Date or Time
          • Today
        • Document
          • Document Type Operation one of
          • Document Operator for Sub-Organizations
          • Document Type
        • Logic
          • Continue with a chance
          • Send HTTPS Request
          • Module active
          • Quoted Item Price
          • Decision Table has Returns
        • Status
          • Single Document Status Condition
          • Document Status Condition List
        • Table
          • Any Value of
          • All Value of
          • Compare values in table
          • Compare In
          • Item Receiving Method
          • Items Have Shelf Life
        • Assignee
          • Assigned User Condition
          • Single Assigned User Condition
          • Assigned Group Condition
          • Single Assigned User Condition
      • Then
        • Document Field
          • Set to
          • Set Checkbox to
          • Invert Checkbox
        • Document
          • Approve the Document
          • Reject the Document
        • Status
          • Change Status to
        • Export
          • Export with Export Configuration
          • Start Export
          • Export with alternate Export
        • Task
          • Create a New Task and assign it to the User
          • Create a New Task and assign it to the Recipient
          • Create a New Task and assign it to the group
          • Create a New Task and assign it to the User in Document Field
          • Assign a Task with Title
          • Create a New Task and assign it to Procurement Group
          • Assign to Procurement Group and Create a Task/Notification
          • Assign Document and Create Task/Notification for Group
          • Assign Document and Create Task/Notification for User
          • Assign Document and Create Task/Notification
        • Table
          • Change Entries with
          • Calculate Columns with
          • Calculate in
        • Assignee
          • Assign user from field
          • Assign document to User
          • Assign document to recipient
          • Assign document to the sub organization
          • Assign document to matching sub organization
          • Assign to group
          • Assign document to procurement group
          • Assign document to
          • Assign Sequentially to User
          • Assign Sequentially to Procurement Group
          • Assign Sequentially to Groups
          • Assign Sequentially to User/Group
        • Action
          • Call Api
          • Run Workflow
          • Send HTTPS request to
          • AI Calculation for Cost Increase Surcharges
      • 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
          • Defining Tables and Columns
          • Advanced Settings
          • Grouping Function
          • Manual Row Selection
          • Mapping Columns
          • Improving Table Extraction with Regex
          • Save and Delete Rules
      • Testing
        • PO Matching
        • Auto Accounting
          • LN
          • M3
      • Supplier Portal
      • WatchDog Installation
    • Report Page
  • Infor Integration and Configuration
    • Importing Master Data
      • Field Mappings
      • LN
        • Auto Accounting
        • Suppliers and Purchase Orders
          • Purchase Order - FAQ
          • Verifying the Logistic Company Setting for Goods Receipt Discrepancies
        • Tax Codes
      • M3
        • Auto Accounting
        • Suppliers and Purchase Orders
        • How to import all suppliers
        • Table Extraction for costing Element
      • Custom Master Data
    • Exporting in DocBits
      • Export Module
      • Alternate Export
    • Exporting to INFOR
      • Creating a BOD Mapping File
      • Creating an IDM Mapping File
      • Creating an ION API Endpoint
      • Creating an ION API File
      • Export to M3 Mapping (API)
      • Exporting to IDM
      • Stream for Cloud Customers
      • Order Confirmation
      • Document Export Mapping
      • M3
        • Example Export M3
        • Handling Charges with Infor M3
        • M3 Configuration
      • LN
        • Example Export LN
          • Configuring the Default Tax Country for Export LN
        • Export Tax Codes to LN
        • LN Configuration
  • Advanced functions and 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
      • Functions
      • 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
    • Importing Supplier and Purchase Order Data into DocBits from CSV Files
    • PowerBI
      • SQL Access
        • Custom classification document
        • Field
        • Document table column
        • Email template
        • Ephesoft PO matching
        • Fellow kv table column rule
        • Group cache
        • Preferences
        • Sales order
        • API credentials
        • public.document_log
        • Auto accounting
        • Document status trigger
        • Document type
        • Documents
        • Document type attributes
        • Document Report
        • Electronic document extraction attributes
        • Lookup field configuration
        • Lookup table
        • Batch instance
        • Document extracted data
        • Document Import log
        • Lookup Configuration
        • Sub document type
        • Document Status alert
        • Inbound Emails
        • Chat Log
        • REST API Lookup Configurations
        • FTP Import Configurations
        • Purchase Order line
        • Receive delivery line
        • Document Script activation status
        • Field validation rules
        • Custom_classification_document_label
        • Training data
        • Tfidf preferences
        • Additional charge costing element
        • PO match tolerance
        • Auto test document
        • Custom classification tag
        • Supplier address
        • Organisation document type
        • Sub Organisation Cache
Powered by GitBook
On this page
  • 1. Purpose
  • 2. Overview
  • 3. Download the PEPPOL XML Transformation File.

Was this helpful?

Edit on GitHub
Export as PDF
  1. Administration and Setup
  2. Settings
  3. Global Settings
  4. Document Types
  5. e-docs
  6. Peppol BIS Billing 3.0

Transformation file and Mapping

PreviousPeppol BIS Billing 3.0NextFaktura

Last updated 6 months ago

Was this helpful?

1. Purpose

This file is responsible for extracting data from a PEPPOL BIS Billing 3.0 XML file, processing it, and saving the relevant information in a specified format. It is designed to enable the extraction of key fields to facilitate further processing or integration into DocBits.

2. Overview

  • Source File: The input is a PEPPOL XML file that follows the PEPPOL BIS Billing 3.0 standard.

  • Extraction Process: The file performs a series of steps to read, parse, and extract key elements such as invoice details, supplier information, amounts, and dates.

  • Output: The extracted data is stored in a structured format, in another XML file.

3. Download the PEPPOL XML Transformation File.

  • Example: This file contains the PEPPOL XML transformation logic for extracting and saving data to another XML file.

  • If you encounter issues with your current file or it becomes unusable, download this backup version to restore the transformation functionality.

Here is the Mapping:

AccountingSupplierParty Information Mapping

  • Supplier Electronic Address

    • Source: //AccountingSupplierParty/Party/EndpointID/text()

    • Mapped To: <INVOICE><SUPPLIER><ELECTRONIC_ADDRESS>

    • Can Appear Multiple Times: No.

  • Supplier Electronic Address Scheme ID

    • Source: //AccountingSupplierParty/Party/EndpointID/@schemeID

    • Mapped To: <INVOICE><SUPPLIER><ELECTRONIC_ADDRESS_SCHEME_ID>

    • Can Appear Multiple Times: No.

  • Supplier Identification

    • Source://AccountingSupplierParty/Party/PartyIdentification/ID/text()

    • Mapped To: <INVOICE><SUPPLIER><PARTYIDENTIFICATION><ID>

    • Can Appear Multiple Times: Each <PartyIdentification> element under Supplier will be extracted.

  • Supplier Identification Scheme ID

    • Source://AccountingSupplierParty/Party/PartyIdentification/ID/@schemeID

    • Mapped To: <INVOICE><SUPPLIER><PARTYIDENTIFICATION><ID_SCHEME_ID>

    • Can Appear Multiple Times: Each <PartyIdentification> element will have its corresponding scheme ID.

  • Supplier Name

    • Source: //AccountingSupplierParty/Party/PartyName/Name/text()

    • Mapped To: <INVOICE><SUPPLIER><NAME>

    • Can Appear Multiple Times: No.

  • Supplier Address Line 1

    • Source://AccountingSupplierParty/Party/PostalAddress/StreetName/text()

    • Mapped To: <INVOICE><SUPPLIER><ADDRESS_LINE_1>

    • Can Appear Multiple Times: No.

  • Supplier Address Line 2

    • Source://AccountingSupplierParty/Party/PostalAddress/AdditionalStreetName/text()

    • Mapped To: <INVOICE><SUPPLIER><ADDRESS_LINE_2>

    • Can Appear Multiple Times: No.

  • Supplier Address Line 3

    • Source://AccountingSupplierParty/Party/PostalAddress/AddressLine/Line/text()

    • Mapped To: <InvoINVOICEice><SUPPLIER><ADDRESS_LINE_3>

    • Can Appear Multiple Times: No.

  • Supplier VAT ID

    • Source://AccountingSupplierParty/Party/PartyTaxScheme/CompanyID/text()

    • Mapped To: <INVOICE><SUPPLIER><VAT_ID>

    • Can Appear Multiple Times: No.

  • Supplier Tax Scheme

    • Source://AccountingSupplierParty/Party/PartyTaxScheme/TaxScheme/ID/text()

    • Mapped To: <INVOICE><SUPPLIER><TAX_SCHEME>

    • Can Appear Multiple Times: No.

  • Supplier Legal Name

    • Source://AccountingSupplierParty/Party/PartyLegalEntity/RegistrationName/text()

    • Mapped To: <INVOICE><SUPPLIER><LEGAL_NAME>

    • Can Appear Multiple Times: No.

  • Supplier Legal ID

    • Source://AccountingSupplierParty/Party/PartyLegalEntity/CompanyID/text()

    • Mapped To: <INVOICE><SUPPLIER><LEGAL_ID>

    • Can Appear Multiple Times: No.

  • Supplier Legal ID Scheme ID

    • Source://AccountingSupplierParty/Party/PartyLegalEntity/CompanyID/@schemeID

    • Mapped To: <INVOICE><SUPPLIER><LEGAL_ID_SCHEME_ID>

    • Can Appear Multiple Times: No.

  • Supplier Legal Form

    • Source://AccountingSupplierParty/Party/PartyLegalEntity/CompanyLegalForm/text()

    • Mapped To: <INVOICE><SUPPLIER><LEGAL_FORM>

    • Can Appear Multiple Times: No.

  • Supplier Post Code

    • Source://AccountingSupplierParty/Party/PostalAddress/PostalZone/text()

    • Mapped To: <INVOICE><SUPPLIER><POST_CODE>

    • Can Appear Multiple Times: No.

  • Supplier City

    • Source://AccountingSupplierParty/Party/PostalAddress/CityName/text()

    • Mapped To: <INVOICE><SUPPLIER><CITY>

    • Can Appear Multiple Times: No.

  • Supplier Country Subentity

    • Source: //AccountingSupplierParty/Party/PostalAddress/CountrySubentity/text()

    • Mapped To: <INVOICE><SUPPLIER><COUNTRY_SUBENTITY>

    • Can Appear Multiple Times: No.

  • Supplier Country Code

    • Source: //AccountingSupplierParty/Party/PostalAddress/Country/IdentificationCode/text()

    • Mapped To: <INVOICE><SUPPLIER><COUNTRY_CODE>

    • Can Appear Multiple Times: No.

  • Supplier Contact Name

    • Source: //AccountingSupplierParty/Party/Contact/Name/text()

    • Mapped To: <INVOICE><SUPPLIER><CONTACT><NAME>

    • Can Appear Multiple Times: No.

  • Supplier Contact Telephone

    • Source: //AccountingSupplierParty/Party/Contact/Telephone/text()

    • Mapped To: <INVOICE><SUPPLIER><CONTACT><TELEPHONE>

    • Can Appear Multiple Times: No.

  • Supplier Contact Email

    • Source: //AccountingSupplierParty/Party/Contact/ElectronicMail/text()

    • Mapped To: <INVOICE><SUPPLIER><CONTACT><EMAIL>

    • Can Appear Multiple Times: No.

AccountingCustomerParty Information Mapping

  • Buyer Electronic Address

    • Source: //AccountingCustomerParty/Party/EndpointID/text()

    • Mapped To: <INVOICE><BUYER><ELECTRONIC_ADDRESS>

    • Can Appear Multiple Times: No.

  • Buyer Electronic Address Scheme ID

    • Source: //AccountingCustomerParty/Party/EndpointID/@schemeID

    • Mapped To: <INVOICE><BUYER><ELECTRONIC_ADDRESS_SCHEME_ID>

    • Can Appear Multiple Times: No.

  • Buyer Identification

    • Source: //AccountingCustomerParty/Party/PartyIdentification/ID/text()

    • Mapped To: <INVOICE><BUYER><PARTYIDENTIFICATION><ID>

    • Can Appear Multiple Times: Each <PartyIdentification> element under Buyer will be extracted.

  • Buyer Identification Scheme ID

    • Source://AccountingCustomerParty/Party/PartyIdentification/ID/@schemeID

    • Mapped To: <INVOICE><BUYER><PARTYIDENTIFICATION><ID_SCHEME_ID>

    • Can Appear Multiple Times: Each <PartyIdentification> element will have its corresponding scheme ID.

  • Buyer Name

    • Source: //AccountingCustomerParty/Party/PartyName/Name/text()

    • Mapped To: <INVOICE><BUYER><NAME>

    • Can Appear Multiple Times: No.

  • Buyer Address Line 1

    • Source://AccountingCustomerParty/Party/PostalAddress/StreetName/text()

    • Mapped To: <INVOICE><BUYER><ADDRESS_LINE_1>

    • Can Appear Multiple Times: No.

  • Buyer Address Line 2

    • Source://AccountingCustomerParty/Party/PostalAddress/AdditionalStreetName/text()

    • Mapped To: <INVOICE><BUYER><ADDRESS_LINE_2>

    • Can Appear Multiple Times: No.

  • Buyer Address Line 3

    • Source://AccountingCustomerParty/Party/PostalAddress/AddressLine/Line/text()

    • Mapped To: <INVOICE><BUYER><ADDRESS_LINE_3>

    • Can Appear Multiple Times: No.

  • Buyer VAT ID

    • Source://AccountingCustomerParty/Party/PartyTaxScheme/CompanyID/text()

    • Mapped To: <INVOICE><BUYER><VAT_ID>

    • Can Appear Multiple Times: No.

  • Buyer Tax Scheme

    • Source://AccountingCustomerParty/Party/PartyTaxScheme/TaxScheme/ID/text()

    • Mapped To: <INVOICE><BUYER><TAX_SCHEME>

    • Can Appear Multiple Times: No.

  • Buyer Legal Name

    • Source://AccountingCustomerParty/Party/PartyLegalEntity/RegistrationName/text()

    • Mapped To: <INVOICE><BUYER><LEGAL_NAME>

    • Can Appear Multiple Times: No.

  • Buyer Legal ID

    • Source://AccountingCustomerParty/Party/PartyLegalEntity/CompanyID/text()

    • Mapped To: <INVOICE><BUYER><LEGAL_ID>

    • Can Appear Multiple Times: No.

  • Buyer Legal ID Scheme ID

    • Source://AccountingCustomerParty/Party/PartyLegalEntity/CompanyID/@schemeID

    • Mapped To: <INVOICE><BUYER><LEGAL_ID_SCHEME_ID>

    • Can Appear Multiple Times: No.

  • Buyer Legal Form

    • Source://AccountingCustomerParty/Party/PartyLegalEntity/CompanyLegalForm/text()

    • Mapped To: <INVOICE><BUYER><LEGAL_FORM>

    • Can Appear Multiple Times: No.

  • Buyer Post Code

    • Source://AccountingCustomerParty/Party/PostalAddress/PostalZone/text()

    • Mapped To: <INVOICE><BUYER><POST_CODE>

    • Can Appear Multiple Times: No.

  • Buyer City

    • Source://AccountingCustomerParty/Party/PostalAddress/CityName/text()

    • Mapped To: <INVOICE><BUYER><CITY>

    • Can Appear Multiple Times: No.

  • Buyer Country Subentity

    • Source://AccountingCustomerParty/Party/PostalAddress/CountrySubentity/text()

    • Mapped To: <INVOICE><BUYER><COUNTRY_SUBENTITY>

    • Can Appear Multiple Times: No.

  • Buyer Country Code

    • Source://AccountingCustomerParty/Party/PostalAddress/Country/IdentificationCode/text()

    • Mapped To: <INVOICE><BUYER><COUNTRY_CODE>

    • Can Appear Multiple Times: No.

  • Buyer Contact Name

    • Source: //AccountingCustomerParty/Party/Contact/Name/text()

    • Mapped To: <INVOICE><BUYER><CONTACT><NAME>

    • Can Appear Multiple Times: No.

  • Buyer Contact Telephone

    • Source: //AccountingCustomerParty/Party/Contact/Telephone/text()

    • Mapped To: <INVOICE><BUYER><CONTACT><TELEPHONE>

    • Can Appear Multiple Times: No.

  • Buyer Contact Email

    • Source: //AccountingCustomerParty/Party/Contact/ElectronicMail/text()

    • Mapped To: <INVOICE><BUYER><CONTACT><EMAIL>

    • Can Appear Multiple Times: No.

PayeeParty Information Mapping

  1. Payee Identification

    • Source: //PayeeParty/PartyIdentification/ID/text()

    • Mapped To: <INVOICE><PAYEE><PARTYIDENTIFICATION><ID>

    • Can Appear Multiple Times: Each <PartyIdentification> element under PayeeParty will be extracted.

  2. Payee Identification Scheme ID

    • Source: //PayeeParty/PartyIdentification/ID/@schemeID

    • Mapped To: <INVOICE><PAYEE><PARTYIDENTIFICATION><ID_SCHEME_ID>

    • Can Appear Multiple Times: Each <PartyIdentification> element will have its corresponding scheme ID.

  3. Payee Name

    • Source: //PayeeParty/PartyName/Name/text()

    • Mapped To: <INVOICE><PAYEE><NAME>

    • Can Appear Multiple Times: No.

  4. Payee Legal ID

    • Source: //PayeeParty/PartyLegalEntity/CompanyID/text()

    • Mapped To: <INVOICE><PAYEE><LEGAL_ID>

    • Can Appear Multiple Times: No.

  5. Payee Legal ID Scheme ID

    • Source: //PayeeParty/PartyLegalEntity/CompanyID/@schemeID

    • Mapped To: <INVOICE><PAYEE><LEGAL_ID_SCHEME_ID>

    • Can Appear Multiple Times: No.

TaxRepresentativeParty Information Mapping

  • Tax Representative Party Name

    • Source: //TaxRepresentativeParty/PartyName/Name/text()

    • Mapped To: <INVOICE><TAX_REPRESENTATIVE_PARTY><NAME>

    • Can Appear Multiple Times: No.

  • Tax Representative Address Line 1

    • Source: //TaxRepresentativeParty/PostalAddress/StreetName/text()

    • Mapped To: <INVOICE><TAX_REPRESENTATIVE_PARTY><ADDRESS_LINE_1>

    • Can Appear Multiple Times: No.

  • Tax Representative Address Line 2

    • Source://TaxRepresentativeParty/PostalAddress/AdditionalStreetName/text()

    • Mapped To: <INVOICE><TAX_REPRESENTATIVE_PARTY><ADDRESS_LINE_2>

    • Can Appear Multiple Times: No.

  • Tax Representative Address Line 3

    • Source://TaxRepresentativeParty/PostalAddress/AddressLine/Line/text()

    • Mapped To: <INVOICE><TAX_REPRESENTATIVE_PARTY><ADDRESS_LINE_3>

    • Can Appear Multiple Times: No.

  • Tax Representative VAT ID

    • Source: //TaxRepresentativeParty/PartyTaxScheme/CompanyID/text()

    • Mapped To: <INVOICE><TAX_REPRESENTATIVE_PARTY><VAT_ID>

    • Can Appear Multiple Times: No.

  • Tax Representative Tax Scheme

    • Source://TaxRepresentativeParty/PartyTaxScheme/TaxScheme/ID/text()

    • Mapped To: <INVOICE><TAX_REPRESENTATIVE_PARTY><TAX_SCHEME>

    • Can Appear Multiple Times: No.

  • Tax Representative City

    • Source: //TaxRepresentativeParty/PostalAddress/CityName/text()

    • Mapped To: <INVOICE><TAX_REPRESENTATIVE_PARTY><CITY>

    • Can Appear Multiple Times: No.

  • Tax Representative Post Code

    • Source: //TaxRepresentativeParty/PostalAddress/PostalZone/text()

    • Mapped To: <INVOICE><TAX_REPRESENTATIVE_PARTY><POST_CODE>

    • Can Appear Multiple Times: No.

  • Tax Representative Country Subentity

    • Source://TaxRepresentativeParty/PostalAddress/CountrySubentity/text()

    • Mapped To: <INVOICE><TAX_REPRESENTATIVE_PARTY><COUNTRY_SUBENTITY>

    • Can Appear Multiple Times: No.

  • Tax Representative Country Code

    • Source://TaxRepresentativeParty/PostalAddress/Country/IdentificationCode/text()

    • Mapped To: <INVOICE><TAX_REPRESENTATIVE_PARTY><COUNTRY_CODE>

    • Can Appear Multiple Times: No.

General Invoice Information

  1. Invoice Type

    • Source: "Invoice"

    • Mapped To: <INVOICE><INVOICE_TYPE>

    • Can Appear Multiple Times: No.

  2. Invoice Sub Type

    • Source: "Purchase Invoice"

    • Mapped To: <INVOICE><INVOICE_SUB_TYPE>

    • Can Appear Multiple Times: No.

  3. Invoice ID

    • Source: //ID/text()

    • Mapped To: <INVOICE><INVOICE_ID>

    • Can Appear Multiple Times: No.

  4. Invoice Type Code

    • Source: //InvoiceTypeCode/text()

    • Mapped To: <INVOICE><INVOICE_TYPE_CODE>

    • Can Appear Multiple Times: No.

  5. Invoice Date

    • Source: normalize-space(//IssueDate/text())

    • Mapped To: <INVOICE><INVOICE_DATE>

    • Can Appear Multiple Times: No.

    • Processing: Uses the DateTimeString template for formatting.

  6. Due Date

    • Source: normalize-space(//DueDate/text())

    • Mapped To: <INVOICE><DUE_DATE>

    • Can Appear Multiple Times: No.

    • Processing: Uses the DateTimeString template for formatting.

  7. Tax Point Date

    • Source: normalize-space(//TaxPointDate/text())

    • Mapped To: <INVOICE><TAX_POINT_DATE>

    • Can Appear Multiple Times: No.

    • Processing: Uses the DateTimeString template for formatting.

  8. Invoice Note

    • Source: //Note/text()

    • Mapped To: <INVOICE><INVOICE_NOTE>

    • Can Appear Multiple Times: No.

  9. Document Currency Code

    • Source: //DocumentCurrencyCode/text()

    • Mapped To: <INVOICE><DOCUMENT_CURRENCY_CODE>

    • Can Appear Multiple Times: No.

  10. Tax Currency Code

    • Source: //TaxCurrencyCode/text()

    • Mapped To: <INVOICE><TAX_CURRENCY_CODE>

    • Can Appear Multiple Times: No.

  11. Accounting Cost

    • Source: //AccountingCost/text()

    • Mapped To: <INVOICE><ACCOUNTING_COST>

    • Can Appear Multiple Times: No.

  12. Invoice Period Start Date

    • Source: normalize-space(//InvoicePeriod/StartDate/text())

    • Mapped To: <INVOICE><INVOCICE_PERIOD><START_DATE>

    • Can Appear Multiple Times: No.

    • Processing: Uses the DateTimeString template for formatting.

  13. Invoice Period End Date

    • Source: normalize-space(//InvoicePeriod/EndDate/text())

    • Mapped To: <INVOICE><INVOCICE_PERIOD><END_DATE>

    • Can Appear Multiple Times: No.

    • Processing: Uses the DateTimeString template for formatting.

  14. Invoice Period Description Code

    • Source: //InvoicePeriod/DescriptionCode/text()

    • Mapped To: <INVOICE><INVOCICE_PERIOD><DESCRIPTION_CODE>

    • Can Appear Multiple Times: No.

  15. Purchase Order Reference

    • Source: //OrderReference/ID/text()

    • Mapped To: <INVOICE><PURCHASE_ORDER>

    • Can Appear Multiple Times: No.

  16. Sales Order Reference

    • Source: //OrderReference/SalesOrderID/text()

    • Mapped To: <INVOICE><SALES_ORDER>

    • Can Appear Multiple Times: No.

Document References and Additional Document Details Mapping
  1. Buyer Reference

    • Source: //BuyerReference/text()

    • Mapped To: <INVOICE><BUYER_REFERENCE>

    • Can Appear Multiple Times: No.

  1. Billing Reference

    • Source: //BillingReference

    • Mapped To: <INVOICE><BILLING_REFERENCE>

    • Can Appear Multiple Times: Yes. Each <BillingReference> element in the source data will generate a <BILLING_REFERENCE> element.

    For each Billing Reference:

    • PRECEDING_INVOICE_NUMBER

      • Source: InvoiceDocumentReference/ID/text()

      • Mapped To: <INVOICE><BILLING_REFERENCE><PRECEDING_INVOCIE_NUMBER>

      • Can Appear Multiple Times: No.

    • PRECEDING_INVOICE_ISSUE_DATE

      • Source: InvoiceDocumentReference/IssueDate/text()

      • Mapped To: <INVOICE><BILLING_REFERENCE><PRECEDING_INVOICE_ISSUE_DATE>

      • Can Appear Multiple Times: No.

  1. Despatch Document Reference

    • Source: //DespatchDocumentReference/ID/text()

    • Mapped To: <INVOICE><DESPATCH_DOCUMENT_REFERENCE>

    • Can Appear Multiple Times: No.

  1. Receipt Document Reference

    • Source: //ReceiptDocumentReference/ID/text()

    • Mapped To: <INVOICE><RECEIPT_DOCUMENT_REFERENCE>

    • Can Appear Multiple Times: No.

  1. Originator Document Reference

    1. Source: //OriginatorDocumentReference/ID/text()

    2. Mapped To: <INVOICE><ORIGINATOR_DOCUMENT_REFERENCE>

    3. Can Appear Multiple Times: No.

Contract Document Reference

  • Source: //ContractDocumentReference/ID/text()

  • Mapped To: <INVOICE><CONTRACT_DOCUMENT_REFERENCE>

  • Can Appear Multiple Times: No.

Project Reference

  • Source: //ProjectReference/ID/text()

  • Mapped To: <INVOICE><PROJECT_REFERENCE>

  • Can Appear Multiple Times: No.

Additional Document Reference

  • Source: //AdditionalDocumentReference

  • Mapped To: <INVOICE><ADDITIONAL_DOCUMENT_REFERENCE>

  • Can Appear Multiple Times: Yes. Each <AdditionalDocumentReference> element in the source data will generate an <ADDITIONAL_DOCUMENT_REFERENCE> element.

For each Additional Document Reference:

  • ID

    • Source: ID/text()

    • Mapped To: <INVOICE><ADDITIONAL_DOCUMENT_REFERENCE><ID>

    • Can Appear Multiple Times: No.

  • SCHEME_ID

    • Source: ID/@schemeID

    • Mapped To: <INVOICE><ADDITIONAL_DOCUMENT_REFERENCE><SCHEME_ID>

    • Can Appear Multiple Times: No.

  • DOCUMENT_TYPE_CODE

    • Source: DocumentTypeCode/text()

    • Mapped To: <INVOICE><ADDITIONAL_DOCUMENT_REFERENCE><DOCUMENT_TYPE_CODE>

    • Can Appear Multiple Times: No.

  • DOCUMENT_DESCRIPTION

    • Source: DocumentDescription/text()

    • Mapped To: <INVOICE><ADDITIONAL_DOCUMENT_REFERENCE><DOCUMENT_DESCRIPTION>

    • Can Appear Multiple Times: No.

Attachment Information (for each Additional Document Reference):

  • EMBEDDED_DOCUMENT_BINARY_OBJECT

    • Source: Attachment/EmbeddedDocumentBinaryObject/text()

    • Mapped To: <INVOICE><ADDITIONAL_DOCUMENT_REFERENCE><ATTACHMENT><EMBEDDED_DOCUMENT_BINARY_OBJECT>

    • Can Appear Multiple Times: No.

  • MIME_CODE

    • Source: Attachment/EmbeddedDocumentBinaryObject/@mimeCode

    • Mapped To: <INVOICE><ADDITIONAL_DOCUMENT_REFERENCE><ATTACHMENT><MIME_CODE>

    • Can Appear Multiple Times: No.

  • FILENAME

    • Source: Attachment/EmbeddedDocumentBinaryObject/@filename

    • Mapped To: <INVOICE><ADDITIONAL_DOCUMENT_REFERENCE><ATTACHMENT><FILENAME>

    • Can Appear Multiple Times: No.

  • EXTERNAL_REFERENCE_URL

    • Source: Attachment/ExternalReference/URI/text()

    • Mapped To: <INVOICE><ADDITIONAL_DOCUMENT_REFERENCE><ATTACHMENT><EXTERNAL_REFERENCE_URL>

    • Can Appear Multiple Times: No.

39KB
Transformation.xslt