Import:Cumparare cu plata XML

• Financiar si contabilitate
  • Contabilitate
    • Configurare
      • Import
        • Import:Cumparare cu plata
          • Cumparare cu plata XML

Xml - Purchase invoice with payment

*elements marked with this sign are mandatory

<root>
 <docs>
   <doc>
     <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>>