Difference between revisions of "Import:Cumparare cu plata XML"

From docs
Jump to: navigation, search
Line 9: Line 9:
 
  *elements marked with this sign are mandatory
 
  *elements marked with this sign are mandatory
  
  <root>
+
<span style="color:#00008b">
   <docs>
+
  <root</b></span>>
     <doc>
+
   <docs</b></span>>
       <crtno></crtno>* - if xml contains more than one document this element is mandatory. Each document must have a unique value in this field.
+
     <doc</b></span>>
       <!--identify company-->
+
       <<span style="color:#8B0000"><b>crtno </b></span>/>* - if xml contains more than one document this element is mandatory. Each document must have a unique value in this field.
       <companyunitcode /> * - company unit code defined in ERP.
+
       &lt;!--<span style="color:green">identify company</span>--&gt;
       <companydivisioncode /> * - company division code defined in ERP.
+
       <<span style="color:#8B0000"><b>companyunitcode </b></span>/> * - company unit code defined in ERP.
       <!--document specific info-->
+
       <<span style="color:#8B0000"><b>companydivisioncode </b></span>/> * - company division code defined in ERP.
       <docid /> - document is a mandatory field. It can be determined from one of these elements: docid , doccode or docname. At least one of this elements is mandatory to have value.
+
       &lt;!--<span style="color:green">document specific info</span>--&gt;
       <doccode />
+
       <<span style="color:#8B0000"><b>docid </b></span>/> - document is a mandatory field. It can be determined from one of these elements: docid , doccode or docname. At least one of this elements is mandatory to have value.
      <docname />
+
       <<span style="color:#8B0000"><b>doccode </b></span>/>
       <doctype /> - document type – from list defined in ERP under the document identified from previous elements
+
       <<span style="color:#8B0000"><b>docname </b></span>/>
       <docdate /> * - document date
+
      <<span style="color:#8B0000"><b>doctype </b></span>/> - document type – from list defined in ERP under the document identified from previous elements
       <docoriginaldate /> - document original date – for invoices with date in a closed period in what concerns reporting
+
       <<span style="color:#8B0000"><b>docdate </b></span>/> * - document date
       <docreportingdate /> - for companies wich use 2 reportings : one for state reporting and one for reporting to group
+
       <<span style="color:#8B0000"><b>docoriginaldate </b></span>/> - document original date – for invoices with date in a closed period in what concerns reporting
       <docnumber /> * - document number
+
       <<span style="color:#8B0000"><b>docreportingdate </b></span>/> - for companies wich use 2 reportings : one for state reporting and one for reporting to group
       <grnnumber /> - Goods Received Note number
+
       <<span style="color:#8B0000"><b>docnumber </b></span>/> * - document number
       <grndate /> - Goods Received Note date
+
       <<span style="color:#8B0000"><b>grnnumber </b></span>/> - Goods Received Note number
       <duedate /> - due date
+
       <<span style="color:#8B0000"><b>grndate </b></span>/> - Goods Received Note date
       <determineduedate /> - used if duedate field has no value. If value is 1 due date is determined based on number of days configured in commercial policy of supplier, or based on number of days configured on supplier.
+
       <<span style="color:#8B0000"><b>duedate </b></span>/> - due date
       <explanations />
+
       <<span style="color:#8B0000"><b>determineduedate </b></span>/> - used if duedate field has no value. If value is 1 due date is determined based on number of days configured in commercial policy of supplier, or based on number of days configured on supplier.
       <explanations2 />
+
       <<span style="color:#8B0000"><b>explanations </b></span>/>
       <docexternalimportid /> - identification number from another system
+
       <<span style="color:#8B0000"><b>explanations2 </b></span>/>
       <docexternalimportidcheckisunique /> - if value is 1, an error is returned if exists another document with this external id.
+
       <<span style="color:#8B0000"><b>docexternalimportid </b></span>/> - identification number from another system
       <!--document context info-->
+
       <<span style="color:#8B0000"><b>docexternalimportidcheckisunique </b></span>/> - if value is 1, an error is returned if exists another document with this external id.
       <isreturnpurchase /> - set value to 1 if is return purchase
+
       &lt;!--<span style="color:green">document context info</span>--&gt;
       <simplifiedinvoice /> - set value to 1 if is simplified invoice
+
       <<span style="color:#8B0000"><b>isreturnpurchase </b></span>/> - set value to 1 if is return purchase
       <companynotregisteredforvat /> - set value to 1 if company is not registered for vat purpose
+
       <<span style="color:#8B0000"><b>simplifiedinvoice </b></span>/> - set value to 1 if is simplified invoice
       <companyvatuponcollection /> - set value to 1 if company is registered for VAT upon collection
+
       <<span style="color:#8B0000"><b>companynotregisteredforvat </b></span>/> - set value to 1 if company is not registered for vat purpose
       <partnervatuponcollection /> - set value to 1 if partner is registered for VAT upon collection
+
       <<span style="color:#8B0000"><b>companyvatuponcollection </b></span>/> - set value to 1 if company is registered for VAT upon collection
       <companyvatuponcollectionfromconfig /> - if value is 1, the element companyvatuponcollection is decided based on fiscal configuration found in ERP (on company)
+
       <<span style="color:#8B0000"><b>partnervatuponcollection </b></span>/> - set value to 1 if partner is registered for VAT upon collection
       <partnervatuponcollectionfromconfig /> - if value is 1, the element partnervatuponcollection is decided based on fiscal configuration found in ERP (on partner)
+
       <<span style="color:#8B0000"><b>companyvatuponcollectionfromconfig </b></span>/> - if value is 1, the element companyvatuponcollection is decided based on fiscal configuration found in ERP (on company)
       <accountingregisternumber /> - found in Accounting register list. The accounting register is mandatory. It can be obtained from following elements: accountingregisternumber , accountingregistername , doctype (if document type has accounting register configured). At least one of the mentioned elements must have value.
+
       <<span style="color:#8B0000"><b>partnervatuponcollectionfromconfig </b></span>/> - if value is 1, the element partnervatuponcollection is decided based on fiscal configuration found in ERP (on partner)
       <accountingregistername />
+
       <<span style="color:#8B0000"><b>accountingregisternumber </b></span>/> - found in Accounting register list. The accounting register is mandatory. It can be obtained from following elements: accountingregisternumber , accountingregistername , doctype (if document type has accounting register configured). At least one of the mentioned elements must have value.
      <reversechargecategory /> - from list defined in ERP
+
       <<span style="color:#8B0000"><b>accountingregistername </b></span>/>
       <unregisteredforvatcategory /> - from list defined in ERP  
+
       <<span style="color:#8B0000"><b>reversechargecategory </b></span>/> - from list defined in ERP
       <specialregimecategory /> - from list defined in ERP
+
       <<span style="color:#8B0000"><b>unregisteredforvatcategory </b></span>/> - from list defined in ERP  
       <!--identify partner-->
+
       <<span style="color:#8B0000"><b>specialregimecategory </b></span>/> - from list defined in ERP
       <partnerid /> - id of partner in ERP Partner is a madatory field. It can be determined from one of following elements: partnerid , partnervatnumber , partnername. At least one of this elements must have value.
+
      &lt;!--<span style="color:green">identify partner</span>--&gt;
       <partnervatnumber /> - partner vat number
+
       <<span style="color:#8B0000"><b>partnerid </b></span>/> - id of partner in ERP Partner is a madatory field. It can be determined from one of following elements: partnerid , partnervatnumber , partnername. At least one of this elements must have value.
       <partnername /> - partner name
+
       <<span style="color:#8B0000"><b>partnervatnumber </b></span>/> - partner vat number
       <!--info insert/update partner-->
+
       <<span style="color:#8B0000"><b>partnername </b></span>/> - partner name
       <partnerinsert /> - if value is 1 and partner was not identified based on criteria fields, it will be inserted in ERP. If value is 0 and partner was not identified an error will be returned.
+
       &lt;!--<span style="color:green">info insert/update partner</span>--&gt;
       <partnerupdateinfo /> - if value is 1 and partner was identified, next attributes will be updated, if elements exists in xml.
+
       <<span style="color:#8B0000"><b>partnerinsert </b></span>/> - if value is 1 and partner was not identified based on criteria fields, it will be inserted in ERP. If value is 0 and partner was not identified an error will be returned.
       <partnervatnumberprefix />
+
       <<span style="color:#8B0000"><b>partnerupdateinfo </b></span>/> - if value is 1 and partner was identified, next attributes will be updated, if elements exists in xml.
       <partnertype /> - from partner type list in ERP
+
       <<span style="color:#8B0000"><b>partnervatnumberprefix </b></span>/>
       <partnertraderegisternumber /> - number of registration in Trade Register
+
       <<span style="color:#8B0000"><b>partnertype </b></span>/> - from partner type list in ERP
       <partnercountrycode /> - country code (2 characters)
+
       <<span style="color:#8B0000"><b>partnertraderegisternumber </b></span>/> - number of registration in Trade Register
       <partnercountycode /> - county code (2 characters)
+
       <<span style="color:#8B0000"><b>partnercountrycode </b></span>/> - country code (2 characters)
       <partnercountyname /> - county name
+
       <<span style="color:#8B0000"><b>partnercountycode </b></span>/> - county code (2 characters)
       <partnerinsertcounty /> - if value is 1 and county is not found in ERP list, it will be inserted. If value is 0 and element partnercountyname has value and county is not found an error will be returned.
+
       <<span style="color:#8B0000"><b>partnercountyname </b></span>/> - county name
       <partnerlocalityname /> - from list defined in ERP
+
       <<span style="color:#8B0000"><b>partnerinsertcounty </b></span>/> - if value is 1 and county is not found in ERP list, it will be inserted. If value is 0 and element partnercountyname has value and county is not found an error will be returned.
       <partnerinsertlocality /> - if value is 1 and locality is not found in ERP list, it will be inserted. If value is 0 and element partnerlocalityname has value and locality is not found an error will be returned.  
+
       <<span style="color:#8B0000"><b>partnerlocalityname </b></span>/> - from list defined in ERP
       <partnerstreet />
+
       <<span style="color:#8B0000"><b>partnerinsertlocality </b></span>/> - if value is 1 and locality is not found in ERP list, it will be inserted. If value is 0 and element partnerlocalityname has value and locality is not found an error will be returned.  
       <partnerstreetnumber />  
+
       <<span style="color:#8B0000"><b>partnerstreet </b></span>/>
      <partnerpostalcode /> - partner postal code
+
       <<span style="color:#8B0000"><b>partnerstreetnumber </b></span>/>
       <!--partner bank account-->
+
      <<span style="color:#8B0000"><b>partnerpostalcode </b></span>/> - partner postal code
       <partnerbankaccount /> - bank account
+
       &lt;!--<span style="color:green">partner bank account</span>--&gt;
       <partnerbankname /> - bank name
+
       <<span style="color:#8B0000"><b>partnerbankaccount </b></span>/> - bank account
       <partneraccountcurrency /> - bank account currency
+
       <<span style="color:#8B0000"><b>partnerbankname </b></span>/> - bank name
       <partnerbankaccountisdefault /> - if value is 1, this account is configured in ERP as default account of partner
+
       <<span style="color:#8B0000"><b>partneraccountcurrency </b></span>/> - bank account currency
       <!--partner contact-->
+
       <<span style="color:#8B0000"><b>partnerbankaccountisdefault </b></span>/> - if value is 1, this account is configured in ERP as default account of partner
       <partnercontactinsert /> - if value is 1 and partner contact is not identified based on fields partnercontactsurname and partnercontactfirstname it will be inserted.
+
       &lt;!--<span style="color:green">partner contact</span>--&gt;
       <partnercontactupdateinfo />- if value is 1 and partner contact is identified next attributes will be updated.
+
       <<span style="color:#8B0000"><b>partnercontactinsert </b></span>/> - if value is 1 and partner contact is not identified based on fields partnercontactsurname and partnercontactfirstname it will be inserted.
       <partnercontactsurname />
+
       <<span style="color:#8B0000"><b>partnercontactupdateinfo </b></span>/>- if value is 1 and partner contact is identified next attributes will be updated.
       <partnercontactfirstname />
+
       <<span style="color:#8B0000"><b>partnercontactsurname </b></span>/>
      <partnercontactemail />
+
       <<span style="color:#8B0000"><b>partnercontactfirstname </b></span>/>
       <partnercontactemail2 />
+
       <<span style="color:#8B0000"><b>partnercontactemail </b></span>/>
      <partnercontactphonenumber />
+
       <<span style="color:#8B0000"><b>partnercontactemail2 </b></span>/>
       <partnercontactphonenumber2 />
+
       <<span style="color:#8B0000"><b>partnercontactphonenumber </b></span>/>
      <partnercontactaddress />
+
       <<span style="color:#8B0000"><b>partnercontactphonenumber2 </b></span>/>
      <partnercontactobservations />
+
      <<span style="color:#8B0000"><b>partnercontactaddress </b></span>/>
       <partnercontactcountrycode /> - country code (2 characters)
+
       <<span style="color:#8B0000"><b>partnercontactobservations </b></span>/>
      <partnercontactcountycode /> - county code (2 characters)
+
       <<span style="color:#8B0000"><b>partnercontactcountrycode </b></span>/> - country code (2 characters)
      <partnercontactcountyname /> - from list defined in ERP
+
      <<span style="color:#8B0000"><b>partnercontactcountycode </b></span>/> - county code (2 characters)
       <partnercontactinsertcounty /> - if value is 1 and county is not found in ERP list, it will be inserted. If value is 0 and element partnercontactcountyname has value and county is not found an error will be returned.
+
       <<span style="color:#8B0000"><b>partnercontactcountyname </b></span>/> - from list defined in ERP
      <partnercontactlocalityname /> - from list defined in ERP
+
       <<span style="color:#8B0000"><b>partnercontactinsertcounty </b></span>/> - if value is 1 and county is not found in ERP list, it will be inserted. If value is 0 and element partnercontactcountyname has value and county is not found an error will be returned.
       <partnercontactinsertlocality /> - if value is 1 and locality is not found in ERP list, it will be inserted. If value is 0 and element partnercontactlocalityname has value and locality is not found an error will be returned.
+
      <<span style="color:#8B0000"><b>partnercontactlocalityname </b></span>/> - from list defined in ERP
       <partnercontacttitle />
+
      <<span style="color:#8B0000"><b>partnercontactinsertlocality </b></span>/> - if value is 1 and locality is not found in ERP list, it will be inserted. If value is 0 and element partnercontactlocalityname has value and locality is not found an error will be returned.
      <partnercontactposition />
+
      <<span style="color:#8B0000"><b>partnercontacttitle </b></span>/>
       <partnercontactcode />
+
      <<span style="color:#8B0000"><b>partnercontactposition </b></span>/>
      <partnercontactisdefault /> - if value is 1, this contact is configured in ERP as default contact of partner
+
      <<span style="color:#8B0000"><b>partnercontactcode </b></span>/>
       <!--transaction details-->
+
      <<span style="color:#8B0000"><b>partnercontactisdefault </b></span>/> - if value is 1, this contact is configured in ERP as default contact of partner
      <records>
+
      &lt;!--<span style="color:green">transaction details</span>--&gt;
        <record>
+
      <<span style="color:#8B0000"><b>records>
          <nondeductible /> - if value is 1, this position is marked as nondeductible.
+
        <<span style="color:#8B0000"><b>record>
          <supplieraccount /> - account of supplier
+
           <<span style="color:#8B0000"><b>nondeductible </b></span>/> - if value is 1, this position is marked as nondeductible.
          <productaccount /> - account of product/service
+
          <<span style="color:#8B0000"><b>supplieraccount </b></span>/> - account of supplier
          <transactiontype /> - values accepted: P or S. content of transaction: product (P), service (S)
+
          <<span style="color:#8B0000"><b>productaccount </b></span>/> - account of product/service
          <valuewithoutvat />
+
          <<span style="color:#8B0000"><b>transactiontype </b></span>/> - values accepted: P or S. content of transaction: product (P), service (S)
          <vatvalue />
+
          <<span style="color:#8B0000"><b>valuewithoutvat </b></span>/>
          <vatpercent />
+
          <<span style="color:#8B0000"><b>vatvalue </b></span>/>
          <valueincurrency />
+
          <<span style="color:#8B0000"><b>vatpercent </b></span>/>
          <currencycode />
+
          <<span style="color:#8B0000"><b>valueincurrency </b></span>/>
          <exchangerate />
+
          <<span style="color:#8B0000"><b>currencycode </b></span>/>
          <accountingmode /> * - from list defined in ERP
+
          <<span style="color:#8B0000"><b>exchangerate </b></span>/>
          <!--transaction dimensions-->
+
          <<span style="color:#8B0000"><b>accountingmode </b></span>/> * - from list defined in ERP
          <businesslinecode /> - from list defined in ERP
+
          &lt;!--<span style="color:green">transaction dimensions</span>--&gt;
          <businesslinename /> - from list defined in ERP
+
          <<span style="color:#8B0000"><b>businesslinecode </b></span>/> - from list defined in ERP
          <costcentercode /> - from list defined in ERP
+
          <<span style="color:#8B0000"><b>businesslinename </b></span>/> - from list defined in ERP
          <costcentername /> - from list defined in ERP
+
          <<span style="color:#8B0000"><b>costcentercode </b></span>/> - from list defined in ERP
          <budgetitemname /> - from list defined in ERP
+
          <<span style="color:#8B0000"><b>costcentername </b></span>/> - from list defined in ERP
          <budgetitemcode /> - from list defined in ERP
+
          <<span style="color:#8B0000"><b>budgetitemname </b></span>/> - from list defined in ERP
          <asset /> - from list defined in ERP
+
          <<span style="color:#8B0000"><b>budgetitemcode </b></span>/> - from list defined in ERP
          <assetcode /> - from list defined in ERP
+
          <<span style="color:#8B0000"><b>asset </b></span>/> - from list defined in ERP
           <project /> - from list defined in ERP
+
          <<span style="color:#8B0000"><b>assetcode </b></span>/> - from list defined in ERP
        <record>
+
          <<span style="color:#8B0000"><b>project </b></span>/> - from list defined in ERP
      </records>
+
        <<span style="color:#8B0000"><b>record>
      <!--payment details-->
+
      <<span style="color:#8B0000"><b>/records>
      <paymentdocid /> - if payment document is identified (based on paymentdocid or paymentdoccode) and following fileds (paymentdate , paymentnumber , paymentvalue) have value a payment accounting note will be inserted.
+
      &lt;!--<span style="color:green">payment details</span>--&gt;
      <paymentdoccode />
+
      <<span style="color:#8B0000"><b>paymentdocid </b></span>/> - if payment document is identified (based on paymentdocid or paymentdoccode) and following fileds (paymentdate , paymentnumber , paymentvalue) have value a payment accounting note will be inserted.
      <paymentaccount />
+
      <<span style="color:#8B0000"><b>paymentdoccode </b></span>/>
      <paymentnumber />
+
      <<span style="color:#8B0000"><b>paymentaccount </b></span>/>
      <paymentdate />
+
      <<span style="color:#8B0000"><b>paymentnumber </b></span>/>
      <paymentexplanations />
+
      <<span style="color:#8B0000"><b>paymentdate </b></span>/>
      <paymentexplanations2 />
+
      <<span style="color:#8B0000"><b>paymentexplanations </b></span>/>
      <paymentvalue />
+
      <<span style="color:#8B0000"><b>paymentexplanations2 </b></span>/>
      <paymentmode /> - from list defined in ERP
+
      <<span style="color:#8B0000"><b>paymentvalue </b></span>/>
    </doc>
+
      <<span style="color:#8B0000"><b>paymentmode </b></span>/> - from list defined in ERP
  </docs>
+
    </<span style="color:#8B0000"><b>doc</b></span>>
  </root>
+
  </<span style="color:#8B0000"><b>docs</b></span>>
 +
</<span style="color:#8B0000"><b>root</b></span>>
 +
  </span>

Revision as of 08:18, 1 October 2019

Xml - Purchase invoice with payment

*elements marked with this sign are mandatory

<root</b>>
 <docs</b></span>>
   <doc</b></span>>
     <crtno />* - if xml contains more than one document this element is mandatory. Each document must have a unique value in this field.
     <!--identify company-->
     <companyunitcode /> * - company unit code defined in ERP.
     <companydivisioncode /> * - company division code defined in ERP.
     <!--document specific info-->
     <docid /> - document is a mandatory field. It can be determined from one of these elements: docid , doccode or docname. At least one of this elements is mandatory to have value.
     <doccode />
     <docname />
     <doctype /> - document type – from list defined in ERP under the document identified from previous elements
     <docdate /> * - document date
     <docoriginaldate /> - document original date – for invoices with date in a closed period in what concerns reporting
     <docreportingdate /> - for companies wich use 2 reportings : one for state reporting and one for reporting to group
     <docnumber /> * - document number
     <grnnumber /> - Goods Received Note number
     <grndate /> - Goods Received Note date
     <duedate /> - due date
     <determineduedate /> - used if duedate field has no value. If value is 1 due date is determined based on number of days configured in commercial policy of supplier, or based on number of days configured on supplier.
     <explanations />
     <explanations2 />
     <docexternalimportid /> - identification number from another system
     <docexternalimportidcheckisunique /> - if value is 1, an error is returned if exists another document with this external id.
     <!--document context info-->
     <isreturnpurchase /> - set value to 1 if is return purchase
     <simplifiedinvoice /> - set value to 1 if is simplified invoice
     <companynotregisteredforvat /> - set value to 1 if company is not registered for vat purpose
     <companyvatuponcollection /> - set value to 1 if company is registered for VAT upon collection
     <partnervatuponcollection /> - set value to 1 if partner is registered for VAT upon collection
     <companyvatuponcollectionfromconfig /> - if value is 1, the element companyvatuponcollection is decided based on fiscal configuration found in ERP (on company)
     <partnervatuponcollectionfromconfig /> - if value is 1, the element partnervatuponcollection is decided based on fiscal configuration found in ERP (on partner)
     <accountingregisternumber /> - found in Accounting register list. The accounting register is mandatory. It can be obtained from following elements: accountingregisternumber , accountingregistername , doctype (if document type has accounting register configured). At least one of the mentioned elements must have value.
     <accountingregistername />
     <reversechargecategory /> - from list defined in ERP
     <unregisteredforvatcategory /> - from list defined in ERP 
     <specialregimecategory /> - from list defined in ERP
     <!--identify partner-->
     <partnerid /> - id of partner in ERP Partner is a madatory field. It can be determined from one of following elements: partnerid , partnervatnumber , partnername. At least one of this elements must have value.
     <partnervatnumber /> - partner vat number
     <partnername /> - partner name
     <!--info insert/update partner-->
     <partnerinsert /> - if value is 1 and partner was not identified based on criteria fields, it will be inserted in ERP. If value is 0 and partner was not identified an error will be returned.
     <partnerupdateinfo /> - if value is 1 and partner was identified, next attributes will be updated, if elements exists in xml.
     <partnervatnumberprefix />
     <partnertype /> - from partner type list in ERP
     <partnertraderegisternumber /> - number of registration in Trade Register
     <partnercountrycode /> - country code (2 characters)
     <partnercountycode /> - county code (2 characters)
     <partnercountyname /> - county name
     <partnerinsertcounty /> - if value is 1 and county is not found in ERP list, it will be inserted. If value is 0 and element partnercountyname has value and county is not found an error will be returned.
     <partnerlocalityname /> - from list defined in ERP
     <partnerinsertlocality /> - if value is 1 and locality is not found in ERP list, it will be inserted. If value is 0 and element partnerlocalityname has value and locality is not found an error will be returned. 
     <partnerstreet />
     <partnerstreetnumber /> 
     <partnerpostalcode /> - partner postal code
     <!--partner bank account-->
     <partnerbankaccount /> - bank account
     <partnerbankname /> - bank name
     <partneraccountcurrency /> - bank account currency
     <partnerbankaccountisdefault /> - if value is 1, this account is configured in ERP as default account of partner
     <!--partner contact-->
     <partnercontactinsert /> - if value is 1 and partner contact is not identified based on fields partnercontactsurname and partnercontactfirstname it will be inserted.
     <partnercontactupdateinfo />- if value is 1 and partner contact is identified next attributes will be updated.
     <partnercontactsurname />
     <partnercontactfirstname />
     <partnercontactemail />
     <partnercontactemail2 />
     <partnercontactphonenumber />
     <partnercontactphonenumber2 />
     <partnercontactaddress />
     <partnercontactobservations />
     <partnercontactcountrycode /> - country code (2 characters)
     <partnercontactcountycode /> - county code (2 characters)
     <partnercontactcountyname /> - from list defined in ERP
     <partnercontactinsertcounty /> - if value is 1 and county is not found in ERP list, it will be inserted. If value is 0 and element partnercontactcountyname has value and county is not found an error will be returned.
     <partnercontactlocalityname /> - from list defined in ERP
     <partnercontactinsertlocality /> - if value is 1 and locality is not found in ERP list, it will be inserted. If value is 0 and element partnercontactlocalityname has value and locality is not found an error will be returned.
     <partnercontacttitle />
     <partnercontactposition />
     <partnercontactcode />
     <partnercontactisdefault /> - if value is 1, this contact is configured in ERP as default contact of partner
     <!--transaction details-->
     <records>
       <<b>record>
         <<b>nondeductible </b>/> - if value is 1, this position is marked as nondeductible.
         <<b>supplieraccount </b>/> - account of supplier
         <<b>productaccount </b>/> - account of product/service
         <<b>transactiontype </b>/> - values accepted: P or S. content of transaction: product (P), service (S)
         <<b>valuewithoutvat </b>/>
         <<b>vatvalue </b>/>
         <<b>vatpercent </b>/>
         <<b>valueincurrency </b>/>
         <<b>currencycode </b>/>
         <<b>exchangerate </b>/>
         <<b>accountingmode </b>/> * - from list defined in ERP
         <!--transaction dimensions-->
         <<b>businesslinecode </b>/> - from list defined in ERP
         <<b>businesslinename </b>/> - from list defined in ERP
         <<b>costcentercode </b>/> - from list defined in ERP
         <<b>costcentername </b>/> - from list defined in ERP
         <<b>budgetitemname </b>/> - from list defined in ERP
         <<b>budgetitemcode </b>/> - from list defined in ERP
         <<b>asset </b>/> - from list defined in ERP
         <<b>assetcode </b>/> - from list defined in ERP
         <<b>project </b>/> - from list defined in ERP
       <<b>record>
     <<b>/records>
     <!--payment details-->
     <<b>paymentdocid </b>/> - if payment document is identified (based on paymentdocid or paymentdoccode) and following fileds (paymentdate , paymentnumber , paymentvalue) have value a payment accounting note will be inserted.
     <<b>paymentdoccode </b>/>
     <<b>paymentaccount </b>/>
     <<b>paymentnumber </b>/>
     <<b>paymentdate </b>/>
     <<b>paymentexplanations </b>/>
     <<b>paymentexplanations2 </b>/>
     <<b>paymentvalue </b>/>
     <<b>paymentmode </b>/> - from list defined in ERP
   </<b>doc</b>>
 </<b>docs</b>>
</<b>root</b>>