PROCESSIT 7.4 R1
For Oracle Fusion Middleware 11g

XML Tags

©2025 Copyright ReadSoft AG (publ). All rights reserved. The contents of this document are subject to change without notice. ReadSoft is a registered trademark of ReadSoft AB. Other product and company names herein may be the trademarks or registered trademarks of their respective owners.
Questions or comments about this document may be emailed to documentation@readsoft.com.

ReadSoft AB (Head office) | Södra Kyrkogatan 4 | SE-252 23 Helsingborg | Sweden | Phone: +46 42 490 21 00 | Fax: +46 42 490 21 20
ReadSoft AG | Falkstrasse 5 | 60487 Frankfurt | Germany | Phone: +49 69 1539402-0 | Fax: +49 69 1539402-13
info@readsoft.com | www.readsoft.com

XML TagsInvoice Fields and XML tagsInvoice header fieldsInvoice lines and line fieldsScanned Invoice ImportPROCESSIT WebTestXML tag list

XML Tags

Invoice Fields and XML tags

During invoice processing in PROCESSIT, invoice data is structured in xml format, where each value is noted as an attribute in an xml tag field. The available fields are determined by profiles in INVOICES. When data has been verified in the capture part, and is transferred to PROCESSIT, each invoice is transferred as an XML document. Each invoice data field and corresponding value is represented as an xml tag in the xml document for the invoice, and the xml is is received by the initial BPEL process in PROCESSIT.

The xml structure for an invoice XML document consists of:

  • An overall ARCDOC definition, specifying the receiving BPEL process and the doctype.
  • Header field tags. Each one can be used a single time.
  • Lineitem tags, containing line field tags. Each line field tag can be used a single time inside a lineitem. There is no limit to the number of lines.

Please refer to ReadSoft INVOICES documentation for details on INVOICES and invoice profiles setup.

Each xml tag is a mapped to the appropriate attributes in the ERP system. Once the invoice workflow is complete, the invoice data is imported and written in the database.

You can also define custom mapping schemas inside PROCESSIT, if you want to customize the field mapping between PROCESSIT and Oracle E-Business Suite. When you use WebTest and custom mapping, you must define the mapping schema used in a <DOCTYPE> xml tag in the invoice.

Invoice header fields

The invoice header fields determines the invoice header data that PROCESSIT receives. This is where you define for example the organization id, the supplier number, invoice amounts etc. for an invoice.

Each header field tag can be used once for each xml document.

Invoice lines and line fields

Each invoice line consists of a LINEITEM tag to define the line. Inside the line item tag, each available line item field tag and value can be defined once. There is no limit to the number of line items, that can be defines.

Scanned Invoice Import

Scanned invoices are interpreted and verified in ReadSoft INVOICES, and then transferred to PROCESSIT. Each invoice data field can be modified in the INVOICES Verify module. The xml document sent to PROCESSIT corresponds to the interpred values and their modification during verification.

Each interpreted or added value is transferred to PROCESSIT as an xml tag with the associated value.

XML documents are created and transferred automatically, based on the invoice values set via Verify. You do not have to correct or work with the values in the xml document itself.

PROCESSIT WebTest

You can emulate an invoice process by sending an xml invoice to a test system via PROCESSIT WebTest.

XML tag list

This is a list of the available xml tags for invoice data. Please note that the capilization patterns must be followed.

	
<?xml version="1.0" encoding="ISO-8859-1"?>
<ARCDOC xmlns="http://www.readsoft.com/D4/D4_DM_INBOUND_TRANSFORMATION/1" doctype="ProcessIT">
	
	<DOCTYPE>Optional Mapping Schema Name</DOCTYPE>
	<Profile></Profile>
	<ORG_ID>987</ORG_ID>
	<Supplier>MY SUPPLIER</Supplier>
	<VENDOR_SITE_CODE>SUPPLIER SITE</VENDOR_SITE_CODE>
	<Buyer></Buyer>
	<Date>01-02-2013</Date>
	<InvoiceType>DEBIT/CREDIT</InvoiceType>
	<Credit></Credit>
	<InvoiceCredit></InvoiceCredit>
	<InvoiceNumber>ABCXYZ12345</InvoiceNumber>
	<InvoiceDate>01-02-2013</InvoiceDate>
	<InvoiceTotalVatExcludedAmount>12345.67</InvoiceTotalVatExcludedAmount>
	<InvoiceTotalVatRatePercent>10</InvoiceTotalVatRatePercent>
	<InvoiceTotalVATAmount>1234.567</InvoiceTotalVATAmount>
	<DeliveryCost><12.34/DeliveryCost>
	<InvoiceTotalVatIncludedAmount>12345.67</InvoiceTotalVatIncludedAmount>
	<InvoiceCurrency>XYZ</InvoiceCurrency>
	<InvoiceOrderNumber>PO NUMBER</InvoiceOrderNumber>
	<ReceiptNumber></ReceiptNumber>
	<SupplierVATRegistrationNumber>987</SupplierVATRegistrationNumber>
	<DeliveryNote></DeliveryNote>
	<BuyerContactPersonName>TASK RECEIVER</BuyerContactPersonName>
	<Remarks>A COMMENT HERE</Remarks>
	<Urgent>Y/N</Urgent>
	<DeliveryCostPackaging>123.45</DeliveryCostPackaging>
	<PaymentReferenceNumber></PaymentReferenceNumber>
	<GiroType></GiroType>
	<CreditInvoiceNum></CreditInvoiceNum>
	<Hextra1></Hextra1>
	<Hextra2></Hextra2>
	<Hextra3></Hextra3>
	<WithholdingTaxAmount>0</WithholdingTaxAmount>
	<DiscountableAmount>0</DiscountableAmount>
	<AwtGroupName></AwtGroupName>
	<LateScan>Y/N</LateScan>
	<BatchName>BATCH_1</BatchName>
	<ProcessLog></ProcessLog>
	<XXIT_FILENAME></XXIT_FILENAME>
	<XXIT_INVOICES_FILENAME></XXIT_INVOICES_FILENAME>
	<XXIT_GUID></XXIT_GUID>

	<LINEITEM>
		<LIT_RowIdentifier></LIT_RowIdentifier>
		<LIT_OrderNumber>PO NUMBER</LIT_OrderNumber>
		<LIT_ArticleIdentifier>LINE ITEM</LIT_ArticleIdentifier>
		<LIT_DeliveredQuantity>1234</LIT_DeliveredQuantity>
		<LIT_DeliveredQuantityUnitCode></LIT_DeliveredQuantityUnitCode>
		<LIT_UnitPriceAmount>1234.56</LIT_UnitPriceAmount>
		<LIT_VatAmount>12.34</LIT_VatAmount>
		<LIT_VatRate>10</LIT_VatRate>
		<LIT_VatExcludedAmount>1234.56</LIT_VatExcludedAmount>
		<LIT_ArticelName>ITEM NAME</LIT_ArticelName>
		<Lextra1></Lextra1>
		<Lextra2></Lextra2>
		<Lextra3></Lextra3>
		<LIT_AccountId>ACCOUNT</LIT_AccountId>
		<LIT_ShiptToCode>SHIP TO</LIT_ShiptToCode>
	</LINEITEM>

</ARCDOC>