Import:Cumparare cu plata XML
Revision as of 16:03, 30 September 2019 by Gheorghe Minca (talk | contribs)
Xml - Purchase with payment
- elements marked with this sign are mandatory
<root> <docs> <doc> <crtno></crtno>* 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. <companydivisioncode /> * - company division code defined in ERP. <docid /> * - one of elements docid , doccode or docname is mandatory <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. <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). <accountingregistername /> <reversechargecategory /> - from list defined in ERP <unregisteredforvatcategory /> - from list defined in ERP <specialregimecategory /> - 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. <partnervatnumber /> - partner vat number <partnername /> - 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. <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 <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 <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 <records> <record> <nondeductible /> - if value is 1, this position is marked as nondeductible. <supplieraccount /> - account of supplier <productaccount /> - account of product/service <transactiontype /> - values accepted: P or S. content of transaction: product (P), service (S) <valuewithoutvat /> <vatvalue /> <vatpercent /> <valueincurrency /> <currencycode /> <exchangerate /> <accountingmode /> * - from list defined in ERP <businesslinecode /> - from list defined in ERP <businesslinename /> - from list defined in ERP <costcentercode /> - from list defined in ERP <costcentername /> - from list defined in ERP <budgetitemname /> - from list defined in ERP <budgetitemcode /> - from list defined in ERP <asset /> - from list defined in ERP <assetcode /> - from list defined in ERP <project /> - from list defined in ERP <record> </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. <paymentdoccode /> <paymentaccount /> <paymentnumber /> <paymentdate /> <paymentexplanations /> <paymentexplanations2 /> <paymentvalue /> <paymentmode /> - from list defined in ERP </doc> </docs> </root>