Routty XML formats
This document contains the description of all xml formats used by Routty to exchange any kind of information. By default, the data can be transmitted directly to the REST API of Routty or to an SFTP location to be picked up.
Lexicon
Lexicon | |
Abbreviation | Explanation |
AP | Accounts Payable |
PO | Purchase Order |
GR | Goods Receipt |
VAT | Value Added Tax |
Encoding
Routty supports Unicode encodings, in particular utf-8, utf-16 and utf-32.
The preferred and default encoding is utf-8
Import in Routty
Analytical coding data (Master data)
Description
Analytical master data can be uploaded to allow the user to use this data to form booking proposals. These values are used for validation and enable the user to select these values in Routty. There are 8 dimensions that a client can use to allow to upload specific analytical master data the following fields can be handed over
Example
<?xml version="1.0" encoding="utf-8"?>
<AccountingMasterDataList>
<AccountingMasterData type="string">
<Value>string</Value>
<Description>string</Description>
<CorporateGroupID>string</CorporateGroupID>
<Field1>string</Field1>
<Field2>string</Field2>
<Field3>string</Field3>
<Field4>string</Field4>
<Field5>string</Field5>
<Field6>string</Field6>
<Field7>string</Field7>
<Field8>string</Field8>
<Field9>string</Field9>
<Field10>string</Field10>
</AccountingMasterData>
</AccountingMasterDataList>
Fields
Field | Description | Datatype | Required | Possible value |
type | Type of the master data delivered to Routty | Nvarchar(64) | Yes | CostCenter GlAccount Dimension1 Dimension2 Dimension3 Dimension4 Dimension5 Dimension6 Dimension7 Dimension8 VatCode WdWorkflow MatchingExceptionType Currency PaymentTerms CommodityCode Queue Requester Country |
Value | Value of the type | Varchar(50) | No | Alphabetic values and/or Numerical characters |
Description | Description of the type | Nvarchar(255) | No | Alphabetic values and/or Numerical characters |
CorporateGroupID | Corporate group ID indication | Nvarchar(100) | No | Numerical characters |
Field[1-10] | Free text field | Nvarchar(255) | No | Alphabetic values and/or Numerical characters |
Purchase order data
Description
Purchase order data is persisted in Routty to be used in the AP business flows. These orders can for example be used to be paired and matched with an invoice.
Example
<?xml version="1.0" encoding="utf-8"?>
<PurchaseOrderMasterDataList>
<PurchaseOrderMasterData>
<PurchaseOrderHeader>
<DocumentReference>string</DocumentReference>
<ExtraReference>string</ExtraReference>
<DocumentDate>2019-12-31T22:22:22</DocumentDate>
<DocumentType>string</DocumentType>
<DocumentSubType>string</DocumentSubType>
<Currency>string</Currency>
<TotalNetAmount>3.4</TotalNetAmount>
<TotalVatAmount>3.4</TotalVatAmount>
<TotalGrossAmount>3.4</TotalGrossAmount>
<TotalDiscountAmount>3.4</TotalDiscountAmount>
<PoNumber>string</PoNumber>
<HeaderText1>string</HeaderText1>
<HeaderText2>string</HeaderText2>
<StartDate>2019-12-31T22:22:22</StartDate>
<EndDate>2019-12-31T22:22:22</EndDate>
<DocumentRawId>1000</DocumentRawId>
<DocumentStatus>string</DocumentStatus>
<RequesterId>1000</RequesterId>
<SupplierName>string</SupplierName>
<SupplierNumber>string</SupplierNumber>
<SupplierRegistrationNumber>string</SupplierRegistrationNumber>
<SupplierIban>string</SupplierIban>
<BuyerName>string</BuyerName>
<BuyerNumber>string</BuyerNumber>
</PurchaseOrderHeader>
<PurchaseOrderLines>
<PurchaseOrderLine>
<RowId>string</RowId>
<ExtraReference>string</ExtraReference>
<ArticleCodeSupplier>string</ArticleCodeSupplier>
<ArticleCodeBuyer>string</ArticleCodeBuyer>
<ArticleDescription>string</ArticleDescription>
<EanCode>string</EanCode>
<Quantity>3.4</Quantity>
<UnitCode>string</UnitCode>
<Price>3.4</Price>
<DiscountAmount>3.4</DiscountAmount>
<DiscountRate>string</DiscountRate>
<LineAmount>3.4</LineAmount>
<Status>string</Status>
<GlAccount>string</GlAccount>
<Journal>string</Journal>
<CostCenter>string</CostCenter>
<VatCode>string</VatCode>
<Dimension1>string</Dimension1>
<Dimension2>string</Dimension2>
<Dimension3>string</Dimension3>
<Dimension4>string</Dimension4>
<Dimension5>string</Dimension5>
<Dimension6>string</Dimension6>
<Dimension7>string</Dimension7>
<Dimension8>string</Dimension8>
<MatchOption>string</MatchOption>
</PurchaseOrderLine>
</PurchaseOrderLines>
</PurchaseOrderMasterData>
</PurchaseOrderMasterDataList>
Fields
Purchase order header
Field | Description | Datatype | Required | Possible value |
DocumentReference | The reference of the order, often referred to as PO number | Nvarchar(50) | Yes | Numerical characters |
ExtraReference | Additional Reference | Nvarchar(50) | No | Numerical characters |
DocumentDate | Data of the PO | Datetime | Yes | Numerical characters |
DocumentType | PO Type | Nvarchar(64) | Yes | Alphabetic values and/or Numerical characters |
DocumentSubType | Document subtype | Nvarchar(64) | No | Alphabetic values and/or Numerical characters |
Currency | Currency of document | Nvarchar(64) | No | Alphabetic values |
TotalNetAmount | Total netto amount on purchase order | decimal(18,2) | Yes | Numerical characters |
TotalVatAmount | Total VAT amount on purchase order | decimal(18,2) | Yes | Numerical characters |
TotalGrossAmount | Total amount with VAT on purchase order | decimal(18,2) | Yes | Numerical characters |
TotalDiscountAmount | Total discount amount on purchase order | decimal(18,2) | Yes | Numerical characters |
SupplierNumber | The ID of the supplier | Nvarchar(50) | Yes | Numerical characters |
SupplierName | The name of the buyer | Nvarchar(255) | No | Alphabetic values |
SupplierRegistrationNumber | The VAT number of the supplier | Nvarchar(50) | No | Alphabetic values and/or Numerical characters |
SupplierIban | The IBAN number of the supplier | Varchar(50) | No | Alphabetic values and/or Numerical characters |
BuyerNumber | The ID of the buyer | Varchar(50) | Yes | Numerical characters |
BuyerName | The name of the buyer | Nvarchar(255) | No | Alphabetic values |
HeaderText1 | Header free text field 1 | Nvarchar(255) | No | Alphabetic values and/or numerical characters |
HeaderText2 | Header free text field 2 | Nvarchar(255) | No | Alphabetic values and/or numerical characters |
StartDate | Start date of the purchase order | Datetime | No | Numerical characters |
EndDate | End date of the purchase order | Datetime | No | Numerical characters |
DocumentStatus | Status of the PO (Open or Closed) | Nvarchar(64) | No | Alphabetic values and/or numerical characters |
RequesterId | The person that created the PO | Nvarchar(255) | No | Alphabetic values and/or numerical characters |
Purchase order lines
The following data can be handed over for the purchase order lines of the purchase order:
Field | Description | Datatype | Required | Possible value |
RowID | Line item ID | Nvarchar(64) | Yes | Numerical characters |
ExtraReference | The reference of the order, often referred to as PO number | Nvarchar(128) | Yes | Numerical characters |
ArticleCodeBuyer | Article code buyer | Nvarchar(128) | No | Numerical characters |
ArticleCodeSupplier | Article code of supplier | Nvarchar(128) | No | Numerical characters |
ArticleDescription | Description of article | Nvarchar(512) | No | Alphabetic values and/or Numerical characters |
EANCode | EAN code of article | Nvarchar(128) | No | Numerical characters |
Quantity | Amount of articles | decimal(18,2) | No | Numerical characters |
UnitCode | Measurement unit | Nvarchar(64) | No | Numerical characters |
Price | Unit price of the article | Decimal(18,2) | No | Numerical characters |
DiscountAmount | Discounted amount | Decimal(18,2) | No | Numerical characters |
DiscountRate | Discount rate | Nvarchar(64) | No | Numerical characters |
LineAmount | Amount of line item | Decimal (18,2) | No | Numerical characters |
Status | Status of line item | Nvarchar(64) | No | Alphabetic values and/or Numerical characters |
GLAccount | Gl account on line item | Nvarchar(50) | No | Numerical characters |
Journal | Journal on line item | Nvarchar(50) | No | Numerical characters |
CostCenter | Cost center on line item | Nvarchar(50) | No | Numerical characters |
VatCode | Vat code on line item | Nvarchar(50) | No | Alphabetic values and/or Numerical characters |
Dimension[1-8] | To be specified | Nvarchar(255) | No | Alphabetic values and/or Numerical characters |
Goods receipt data
Description
Through the API all the goods receipt data can be handed over.
Example
<?xml version="1.0" encoding="utf-8"?>
<GoodsReceiptMasterDataList>
<GoodsReceiptMasterData>
<GoodsReceiptHeader>
<DocumentReference>string</DocumentReference>
<ExtraReference>string</ExtraReference>
<DocumentDate>2019-12-31T22:22:22</DocumentDate>
<DocumentType>string</DocumentType>
<DocumentSubType>string</DocumentSubType>
<PoNumber>string</PoNumber>
<HeaderText1>string</HeaderText1>
<HeaderText2>string</HeaderText2>
<DocumentStatus>string</DocumentStatus>
<SupplierNumber>string</SupplierNumber>
<SupplierName>string</SupplierName>
<SupplierRegistrationNumber>string</SupplierRegistrationNumber>
<SupplierIban>string</SupplierIban>
<BuyerNumber>string</BuyerNumber>
<BuyerName>string</BuyerName>
</GoodsReceiptHeader>
<GoodsReceiptLines>
<GoodsReceiptLine>
<RowId>string</RowId>
<ExtraReference>string</ExtraReference>
<ArticleCodeSupplier>string</ArticleCodeSupplier>
<ArticleCodeBuyer>string</ArticleCodeBuyer>
<ArticleDescription>string</ArticleDescription>
<EanCode>string</EanCode>
<Quantity>3,4</Quantity>
<UnitCode>string</UnitCode>
<UnitPrice>3,4</UnitPrice>
<LineAmount>3,4</LineAmount>
<Status>string</Status>
</GoodsReceiptLine>
</GoodsReceiptLines>
</GoodsReceiptMasterData>
</GoodsReceiptMasterDataList>
Fields
Header
Field | Description | Datatype | Required | Possible value |
DocumentReference | Internal reference | Nvarchar(50) | Yes | Numerical characters |
ExtraReference | Additional reference | Nvarchar(50) | No | Numerical characters |
DocumentDate | Date of the PO | Datetime | Yes | Numerical characters |
DocumentType | Indication of goods receipt | Nvarchar(64) | No | Alphabetic values and/or numerical characters |
DocumentSubType | Subtype of the document | Nvarchar(64) | No | Alphabetic values and/or numerical characters |
PoNumber | The linked PO number | Nvarchar(128) | No | Alphabetic values |
SupplierNumber | The ID of the supplier | Nvarchar(50) | Yes | Numerical characters |
SupplierName | The name of the supplier | Nvarchar(255) | No | Alphabetic values |
SupplierRegistrationNumber | The VAT number of the supplier | Nvarchar(50) | No | Alphabetic values and/or Numerical characters |
SupplierIban | The IBAN number of the supplier | Varchar(50) | No | Alphabetic values and/or Numerical characters |
BuyerNumber | The ID of the buyer | Varchar(50) | Yes | Numerical characters |
BuyerName | The name of the buyer | Nvarchar(255) | No | Alphabetic values |
HeaderText1 | Header free text field | Nvarchar (255) | No | Numerical characters |
HeaderText2 | Header free text field | Nvarchar (255) | No | Numerical characters |
DocumentStatus | Status of the PO (Open or Closed) | Nvarchar(64) | No | Alphabetic values and/or numerical characters |
Lines
Field | Description | Datatype | Required | Possible value |
RowID | Line number | Nvarchar(64) | Yes | Numerical characters |
ExtraReference | The linked PO number | Nvarchar(128) | No | Numerical characters |
ArticleCodeBuyer | Article code of buyer | Nvarchar(128) | No | Numerical characters |
ArticleCodeSupplier | Article code of supplier | Nvarchar(128) | No | Numerical characters |
ArticleDescription | Article code description | Nvarchar (512) | No | Alphabetic values and/or numerical characters |
EANCode | EAN code of article | Nvarchar (128) | No | Alphabetic values and/or numerical characters |
Quantity | The quantity of the article | Decimal (18,2) | No | Numerical characters |
UnitCode | The unit of measure of the line | Nvarchar (64) | No | Alphabetic values and/or numerical characters |
UnitPrice | The price of the article | Decimal (18,2) | No | Numerical characters |
LineAmount | Total amount of the line | Decimal (18,2) | No | Numerical characters |
Status | Status of line item | Nvarchar(64) | No | Alphabetic values and/or Numerical characters |
Articles
Description
Articles are a specific type of data used in business flows specialized in handling orders, they can also be used in certain AP flows.
Example
<?xml version="1.0" encoding="UTF-8"?>
<ArticleList>
<Article>
<CorporateGroupID>string</Art_CorporateGroupID>
<Number>string</Art_Number>
<Description>string</Description>
<Type>string</Type>
<GTIN>string</GTIN>
<UnitOfMeasurement>string</ UnitOfMeasurement>
<UnitPrice>decimal</UnitPrice>
</Article>
<Article>
<CorporateGroupID>string</ CorporateGroupID>
<Number>string</Number>
<Description>string</Description>
<Type>string</Type>
<GTIN>string</GTIN>
<UnitOfMeasurement>string</UnitOfMeasurement>
<UnitPrice>decimal</UnitPrice>
</Article>
</ArticleList>
Fields
Field | Description | Datatype | Required | Possible value |
CorporateGroupID | Corporate group ID indication | nvarchar(100) | No | Numerical characters |
Number | Article number | Nvarchar(32) | Yes | Alphabetic values and/or numerical characters |
Description | The description of an article | Nvarchar(255) | No | Alphabetic values and/or numerical characters |
Type | Type of article | Nvarchar(255) | No | Alphabetic values and/or numerical characters |
GTIN | Standard codes, global codes | Nvarchar(14) | No | Alphabetic values and/or numerical characters |
UnitOfMeasurement | What format the article is measured in. | Nvarchar(50) | No | Alphabetic values and/or numerical characters |
UnitPrice | Price of one unit | Decimal(18,4) | No | Numerical characters |
Parties
Description
The parties xml is used to upload any kind of party to routty, this includes both legal entities of your own company and suppliers you might deal with.
Example
<?xml version="1.0" encoding="utf-8"?>
<PartyList>
<Party>
<Metadata>
<Number>string</Number>
<SiteCode>string</SiteCode>
<CorporateGroupID>string</CorporateGroupID>
<IsMasterdata>false</IsMasterdata>
<Name1>string</Name1>
<Name2>string</Name2>
<Address1>string</Address1>
<Address2>string</Address2>
<PoBox>string</PoBox>
<PostalCode>string</PostalCode>
<City>string</City>
<State>string</State>
<Location>string</Location>
<CountryCode>string</CountryCode>
<Telephone>string</Telephone>
<EmailAddress>string</EmailAddress>
<PaymentTerms>string</PaymentTerms>
<PaymentMethod>string</PaymentMethod>
<Dimension1>string</Dimension1>
<Dimension2>string</Dimension2>
<Dimension3>string</Dimension3>
<Dimension4>string</Dimension4>
<Dimension5>string</Dimension5>
<Dimension6>string</Dimension6>
<Dimension7>string</Dimension7>
<Dimension8>string</Dimension8>
<PartyRegistrationNumbers>
<PartyRegistrationNumber>
<Number>string</Number>
<Scheme>string</Scheme>
</PartyRegistrationNumber>
</PartyRegistrationNumbers>
<PartyBankAccounts>
<PartyBankAccount>
<BankNumber>string</BankNumber>
<AccountNumber>string</AccountNumber>
<IBAN>string</IBAN>
<BIC>string</BIC>
<Currency>string</Currency>
<Dimension1>string</Dimension1>
<Dimension2>string</Dimension2>
<Dimension3>string</Dimension3>
<Dimension4>string</Dimension4>
</PartyBankAccount>
</PartyBankAccounts>
</Metadata>
<Type>
<Name>string</Name>
</Type>
<Active>false</Active>
</Party>
</PartyList>
Fields
Metadata
Field | Description | Datatype | Required | Possible value |
Number | The internal number/ID for the party | nvarchar(100) | Yes | Alphabetic values and/or numerical characters |
SiteCode | The code for the site, establishment, or outlet of the party | nvarchar(100) | No | Alphabetic values and/or numerical characters |
CorporateGroupID | Corporate group ID indication | nvarchar(100) | No | Alphabetic values and/or numerical characters |
Name1 | The primary name | nvarchar(400) | Yes | Alphabetic values and/or numerical characters |
Name2 | The secondary name | nvarchar(400) | No | Alphabetic values and/or numerical characters |
Address1 | The first address line of the party site | nvarchar(400) | No | Alphabetic values and/or numerical characters |
Address2 | The second address line of the party | nvarchar(400) | No | Alphabetic values and/or numerical characters |
POBox | The PO box of the party | nvarchar(50) | No | Alphabetic values and/or numerical characters |
PostalCode | The postal/ZIP code of the supplier | nvarchar(12) | No | Alphabetic values and/or numerical characters |
City | The city of the party | nvarchar(100) | No | Alphabetic values and/or numerical characters |
State | The state of the party | nvarchar(100) | No | Alphabetic values and/or numerical characters |
Location | Subdivision of a country, region, city, ... such as a county, province, or state | nvarchar(100) | No | Alphabetic values and/or numerical characters |
CountryCode | The country code of the party | nvarchar(3) | No | Alphabetic values and/or numerical characters |
Telephone | The telephone number of the party | nvarchar(31) | No | Alphabetic values and/or numerical characters |
EmailAddress | The email address of the party | nvarchar(100) | No | Alphabetic values and/or numerical characters |
PaymentTerms | An identifier for the default payment terms associated with this party | nvarchar(100) | No | Alphabetic values and/or numerical characters |
PaymentMethod | An identifier for the expected means of payment | nvarchar(100) | No | Alphabetic values and/or numerical characters |
Dimension[1-8] | To be specified | nvarchar(400) | No | Alphabetic values and/or numerical characters |
Type
Field | Description | Datatype | Required | Possible value |
Name | Name of the party type | nvarchar(20) | Yes | Company, Partner, ShipTo |
Party
Field | Description | Datatype | Required | Possible value |
Active | Active should be True if the party can be used in the business process, False if it should be blocked from use in the business process. | bit | No | True or False |
Export from Routty
Purchase invoice data
Description
The following chapter gives insight in the standard output fields that are used in the export from Routty.
Example
<?xml version="1.0" encoding="utf-8"?>
<PurchaseInvoiceList>
<PurchaseInvoice>
<PurchaseInvoiceHeader>
<DocumentReference>string</DocumentReference>
<ExtraReference>string</ExtraReference>
<DocumentDate>2019-12-31T22:22:22</DocumentDate>
<DueDate>2019-12-31T22:22:22</DueDate>
<PaymentReference>string</PaymentReference>
<DocumentType>string</DocumentType>
<DocumentSubType>string</DocumentSubType>
<Currency>string</Currency>
<CurrencyRate>3.4</CurrencyRate>
<TotalNetAmount>3.4</TotalNetAmount>
<TotalVatAmount>3.4</TotalVatAmount>
<TotalGrossAmount>3.4</TotalGrossAmount>
<TotalDiscountAmount>3.4</TotalDiscountAmount>
<PoNumber>string</PoNumber>
<DnNumber>string</DnNumber>
<NetAmount1>3.4</NetAmount1>
<NetAmount2>3.4</NetAmount2>
<NetAmount3>3.4</NetAmount3>
<NetAmount4>3.4</NetAmount4>
<NetAmount5>3.4</NetAmount5>
<VatAmount1>3.4</VatAmount1>
<VatAmount2>3.4</VatAmount2>
<VatAmount3>3.4</VatAmount3>
<VatAmount4>3.4</VatAmount4>
<VatAmount5>3.4</VatAmount5>
<VatRate1>string</VatRate1>
<VatRate2>string</VatRate2>
<VatRate3>string</VatRate3>
<VatRate4>string</VatRate4>
<VatRate5>string</VatRate5>
<HeaderCost1>3.4</HeaderCost1>
<HeaderCost2>3.4</HeaderCost2>
<HeaderCost3>3.4</HeaderCost3>
<HeaderCost4>3.4</HeaderCost4>
<HeaderCost5>3.4</HeaderCost5>
<HeaderText1>string</HeaderText1>
<HeaderText2>string</HeaderText2>
<ArchiveDate>2019-12-31T22:22:22</ArchiveDate>
<ReceptionDate>2019-12-31T22:22:22</ReceptionDate>
<BookingNumber>string</BookingNumber>
<BookingDate>2019-12-31T22:22:22</BookingDate>
<BookingYear>string</BookingYear>
<BookingMonth>string</BookingMonth>
<DocumentStatus>string</DocumentStatus>
<Journal>string</Journal>
<TotalVatRate>string</TotalVatRate>
<Dimension1>string</Dimension1>
<Dimension2>string</Dimension2>
<Dimension3>string</Dimension3>
<Dimension4>string</Dimension4>
<Dimension5>string</Dimension5>
<Dimension6>string</Dimension6>
<Dimension7>string</Dimension7>
<Dimension8>string</Dimension8>
<RequesterId>string</RequesterId>
<VatSystem>string</VatSystem>
<SupplierNumber>string</SupplierNumber>
<SupplierName>string</SupplierName>
<SupplierRegistrationNumber>string</SupplierRegistrationNumber>
<SupplierIban>string</SupplierIban>
<BuyerNumber>string</BuyerNumber>
<BuyerName>string</BuyerName>
<BuyerRegistrationNumber>string</BuyerRegistrationNumber>
</PurchaseInvoiceHeader>
<PurchaseInvoiceLines>
<PurchaseInvoiceLine>
<RowId>string</RowId>
<ExtraReference>string</ExtraReference>
<ArticleCodeSupplier>string</ArticleCodeSupplier>
<ArticleCodeBuyer>string</ArticleCodeBuyer>
<ArticleDescription>string</ArticleDescription>
<EANCode>string</EANCode>
<Quantity>3.4</Quantity>
<UnitCode>string</UnitCode>
<Price>3.4</Price>
<DiscountAmount>3.4</DiscountAmount>
<DiscountRate>string</DiscountRate>
<LineAmount>3.4</LineAmount>
<Status>string</Status>
<DeliveryNote>string</DeliveryNote>
<Dimension1>string</Dimension1>
<Dimension2>string</Dimension2>
<Dimension3>string</Dimension3>
<Dimension4>string</Dimension4>
<Dimension5>string</Dimension5>
<Dimension6>string</Dimension6>
<Dimension7>string</Dimension7>
<Dimension8>string</Dimension8>
<VatAmount>3.4</VatAmount>
<VatRate>string</VatRate>
<GrossAmount>3.4</GrossAmount>
</PurchaseInvoiceLine>
</PurchaseInvoiceLines>
<PurchaseInvoiceCodingLines>
<PurchaseInvoiceCodingLine>
<RowId>string</RowId>
<GlAccount>string</GlAccount>
<Journal>string</Journal>
<CostCenter>string</CostCenter>
<DebitAmount>3.4</DebitAmount>
<CreditAmount>3.4</CreditAmount>
<VatAmount>3.4</VatAmount>
<VatRate>string</VatRate>
<VatCode>string</VatCode>
<VatSystem>string</VatSystem>
<Dimension1>string</Dimension1>
<Dimension2>string</Dimension2>
<Dimension3>string</Dimension3>
<Dimension4>string</Dimension4>
<Dimension5>string</Dimension5>
<Dimension6>string</Dimension6>
<Dimension7>string</Dimension7>
<Dimension8>string</Dimension8>
<Status>string</Status>
</PurchaseInvoiceCodingLine>
</PurchaseInvoiceCodingLines>
<PurchaseInvoiceIntrastatLines>
<PurchaseInvoiceIntrastatLine>
<RowId>string</RowId>
<PartnerCountry>string</PartnerCountry>
<TransactionCode>1</TransactionCode>
<Region>1</Region>
<CommodityCode>3.4</CommodityCode>
<NetMass>3.4</NetMass>
<Units>3.4</Units>
<Value>3.4</Value>
<PC>1</PC>
<DeliveryTerms>string</DeliveryTerms>
</PurchaseInvoiceIntrastatLine>
</PurchaseInvoiceIntrastatLines>
<MatchingExceptions>
<MatchingException>
<RowId>1000</RowId>
<Reference>string</Reference>
<ArticleCode>string</ArticleCode>
<InvoiceAmount>3.4</InvoiceAmount>
<PoAmount>3.4</PoAmount>
<InvoicePrice>3.4</InvoicePrice>
<PoPrice>3.4</PoPrice>
<InvoiceQuantity>3.4</InvoiceQuantity>
<PoQuantity>3.4</PoQuantity>
<GrQuantity>3.4</GrQuantity>
<ExceptionCode>string</ExceptionCode>
<ExceptionDescription>string</ExceptionDescription>
</MatchingException>
</MatchingExceptions>
<ArchiveLinks>
<Link>string</Link>
</ArchiveLinks>
</PurchaseInvoice>
</PurchaseInvoiceList>
Fields
Header
Field | Description | Datatype | Required | Possible value |
DocumentReference | Internal Reference | Nvarchar(50) | Yes | Numerical characters |
ExtraReference | Additional reference | Nvarchar(128) | No | Numerical characters |
DocumentDate | Date of the document | Datetime | Yes | Numerical characters |
DueDate | Due date of invoice | Datetime | No | Numerical characters |
PaymentReference | Payment reference | Nvarchar(50) | No | Alphabetic values and/or numerical characters |
DocumentType | Document type | Nvarchar(64) | Yes | Invoice/Credit note |
DocumentSubType | Document sub type | Nvarchar(64) | Yes | GE/PO |
Currency | Currency | Nvarchar(64) | Yes | Alphabetic values |
CurrencyRate | Exchange rate for the currency | Decimal(13,8) | No | Numerical characters |
TotalNetAmount | Total net amount | Decimal(18,2) | Yes | Numerical characters |
TotalVatAmount | Total Vat amount | Decimal(18,2) | Yes | Numerical characters |
TotalVatRate | Total vat rate | Nvarchar(50) | No | Numerical characters |
TotalGrossAmount | Total gross amount | Decimal(18,2) | Yes | Numerical characters |
TotalDiscountAmount | Total discount amount | Decimal(18,2) | No | Numerical characters |
PONumber | Linked PO number | Nvarchar(128) | No | Numerical characters |
DNNumber | DN number | Nvarchar(128) | No | Numerical characters |
SupplierNumber | The ID of the supplier | Varchar(50) | Yes | Numerical characters |
SupplierName | The name of the supplier | Varchar(255) | No | Alphabetic values |
SuppliersRegistrationNumber | The VAT number of the supplier | Varchar(50) | No | Alphabetic values and/or Numerical characters |
SupplierIban | The IBAN number of the supplier | Varchar(50) | No | Alphabetic values and/or Numerical characters |
BuyerNumber | The ID of the buyer | Varchar(50) | Yes | Numerical characters |
BuyerName | The name of the buyer | Varchar(255) | No | Alphabetic values |
BuyerRegistrationNumber | Registration number of supplier | Varchar(50) | No | Alphabetic values and/or Numerical characters |
NetAmount[1-5] | Net amount | Decimal(18,2) | Yes | Numerical characters |
VatAmount[1-5] | Vat amount | Decimal(18,2) | Yes | Numerical characters |
VatRate[1-5] | Vat rate | Nvarchar(64) | Yes | Numerical characters |
VatSystem | Vat system | Nvarchar(50) | No | |
HeaderCost[1-5] | Header Cost | Decimal(18,2) | Yes | Numerical characters |
HeaderText1 | Header text field | Nvarchar(255) | No | Alphabetic values and/or numerical characters |
HeaderText2 | Header text field | Nvarchar(255) | No | Alphabetic values and/or numerical characters |
CreateTimeStamp | Timestamp created at | Datetime | Yes | Numerical characters |
ArchiveDate | Date of archive | Datetime | No | Numerical characters |
ReceptionDate | Date of reception | Datetime | Yes | Numerical characters |
BookingNumber | Id of the booking | Nvarchar(64) | No | Numerical characters |
BookingsDate | Date of booking | Datetime | No | Numerical characters |
BookingsYear | Year of booking | Nvarchar(64) | No | Numerical characters |
BookingsMonth | Month of booking | Nvarchar(64) | No | Numerical characters |
DocumentStatus | Status of the PO (Open or Closed) | Nvarchar(64) | No | Alphabetic values and/or numerical characters |
Journal | The linked journal | Nvarchar(50) | No | Alphabetic values and/or numerical characters |
RequesterID | The person that created the invoice | Nvarchar(64) | No | Alphabetic values and/or numerical characters |
Dimension[1-8] | To be specified | Nvarchar(128) | No | Alphabetic values and/or Numerical characters |
Lines
Field | Description | Datatype | Required | Possible value |
RowID | Row ID | Nvarchar(64) | Yes | Numerical characters |
ExtraReference | Extra reference indication of the PO number | Nvarchar(128) | No | Alphabetic values and/or numerical characters |
ArticleCodeSupplier | Article code of the supplier | Nvarchar(128) | No | Numerical characters |
ArticleCodeBuyer | Article code of the buyer | Nvarchar(128) | No | Numerical characters |
ArticleDescription | Article description | Nvarchar(512) | No | Alphabetic values and/or numerical characters |
EANCode | EAN code | Nvarchar(128) | No | Numerical characters |
DeliveryNote | Delivery note | Nvarchar(128) | No | Alphabetic values and/or numerical characters |
Quantity | Quantity | Decimal(18,2) | No | Numerical characters |
UnitCode | Unit code | Nvarchar(64) | No | Alphabetic values and/or numerical characters |
Price | Price | Decimal(18,2) | No | Numerical characters |
DiscountAmount | Discount amount | Decimal(18,2) | No | Numerical characters |
DiscountRate | Discount rate | Nvarchar(64) | No | Numerical characters |
LineAmount | The netto line amount | Decimal(18,2) | No | Numerical characters |
VatAmount | The VAT amount | Decimal(18,2) | No | Numerical characters |
VatRate | Vat rate | Nvarchar(50) | No | Numerical characters |
GrossAmount | Gross amount | Decimal(18,2) | No | Numerical characters |
Status | Internal field to indicate the line item status | Nvarchar(64) | No | Alphabetic values and/or numerical characters |
PurchaseInvoiceHeaderId | Header ID | Nvarchar(64) | No | Alphabetic values and/or numerical characters |
Dimension[1-8] | To be specified | Nvarchar(128) | No | Alphabetic values and/or numerical characters |
Coding lines
The following fields are the output of the coding lines and form the basis of the booking proposal.
Field | Description | Datatype | Required | Possible value |
WindreamId | Legal archive document ID | Nvarchar(50) | Yes | Alphabetic values and/or numerical characters |
GlAccount | GL account (from masterdata) | Nvarchar(50) | Yes | Alphabetic values and/or numerical characters |
Journal | The linked journal | Nvarchar(50) | No | Alphabetic values and/or numerical characters |
CostCenter | Cost center (from masterdata) | Nvarchar(50) | No | Alphabetic values and/or numerical characters |
DebitAmount | The debit amount on the invoice line | Decimal(18,2) | Yes | Alphabetic values and/or numerical characters |
CreditAmount | Credit amount on the invoice line | Decimal(18,2) | Yes | Numerical characters |
VatAmount | Vat amount on invoice line | Decimal(18,2) | No | Numerical characters |
VatRate | Vat rate on invoice line | Nvarchar(50) | No | Numerical characters |
VatCode | VAT code (from masterdata) | Nvarchar(50) | No | Numerical characters |
Dimension[1-8] | To be specified | Nvarchar(128) | No | Alphabetic values and/or numerical characters |
Status | Additional information on the invoice status | Nvarchar(64) | Yes | Alphabetic values and/or numerical characters |
Feedback
Accounting Feedback
Description
Feedback from the ERP system before or after posting an invoice can be relayed via an accounting feedback document. The feedback document can be used to update the status of an invoice that is posted in an external ERP system.
To be able to link back to the document in Routty, either the document GUID or Set Identifier should be provided. There are 3 options to do so:
Feedback the GUID as (a prefix of) the filename. Routty will (by default) name the accounting document as the GUID. The ERP system could use the same naming convention to link back to the document, e.g. “EEBF3406-095B-4717-B659-BD2601542135.xml”, “EEBF3406-095B-4717-B659-BD2601542135_20191016othertext.xml”. Note that everything following the underscore (“_”) in the last example is ignored by Routty.
Provide the GUID in the DocumentGuid tag in the feedback document
Provide the Set Identifier in the DocumentSetId tag
Example
<?xml version="1.0" encoding="utf-8"?>
<RouttyFeedbackDocuments>
<RouttyFeedbackDocument>
<Status>string</Status>
<DocumentGuid>string</DocumentGuid>
<DocumentSetId>1000</DocumentSetId>
<ProcessDate>string</ProcessDate>
<Messages>
<Message>string</Message>
</Messages>
<FeedbackAccounting>
<BookingNumber>string</BookingNumber>
<BookingDate>2019-12-31T22:22:22</BookingDate>
<BookingYear>string</BookingYear>
<BookingMonth>string</BookingMonth>
<Journal>string</Journal>
</FeedbackAccounting>
<Dimensions>
<Dimension1>string</Dimension1>
<Dimension2>string</Dimension2>
<Dimension3>string</Dimension3>
<Dimension4>string</Dimension4>
<Dimension5>string</Dimension5>
<Dimension6>string</Dimension6>
<Dimension7>string</Dimension7>
<Dimension8>string</Dimension8>
</Dimensions>
</RouttyFeedbackDocument>
</RouttyFeedbackDocuments>
Fields
Field | Description | Datatype | Required | Possible value |
Status | Status of posting in ERP system | String | Yes | Success or Error |
DocumentGuid | Uniquely identifies document in Routty | GUID | Yes | GUID |
DocumentSetId | The document Set ID of the document | Long | Yes | Has to be filled in (default: 0), even if a GUID is used to identify the document |
Message | Human-readable status message, can be multiple messages | String | No | Alphabetic values and/or numerical characters |
BookingDate | Posting date | DateTime | No | Date time |
BookingNumber | Number of invoice assigned by ERP system | String | No | Alphabetic values and/or numerical characters |
BookingYear | Fiscal year of booking period | String | No | Numerical characters |
BookingMonth | (Month of) booking period | String | No | Numerical characters |
Journal | Journal entry | String | No | Alphabetic values and/or numerical characters |
Dimension[1-8] | To be specified | Nvarchar(128) | No | Alphabetic values and/or numerical characters |