Import:Vanzare cu incasare XML: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 8: | Line 8: | ||
===Xml - Sales invoice with payment=== | ===Xml - Sales invoice with payment=== | ||
*elements marked with this sign are mandatory | *elements marked with this sign are mandatory | ||
<span style="color:#00008b"> | <span style="color:#00008b"> | ||
<root> | <root> | ||
| Line 31: | Line 32: | ||
<<span style="color:#8B0000"><b>docexternalimportidcheckisunique</b></span> /> - if value is 1, an error is returned if exists another document with this external id. | <<span style="color:#8B0000"><b>docexternalimportidcheckisunique</b></span> /> - if value is 1, an error is returned if exists another document with this external id. | ||
<!--<span style="color:green">document context info</span>--> | <!--<span style="color:green">document context info</span>--> | ||
<dociscancelled /> - document is marked as canceled | <<span style="color:#8B0000"><b>dociscancelled</b></span> /> - document is marked as canceled | ||
<iscustomerreturn /> - set value to 1 if is customer return | <<span style="color:#8B0000"><b>iscustomerreturn</b></span> /> - set value to 1 if is customer return | ||
<companyvatuponcollection /> - set value to 1 if company 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>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). | <<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). | ||
<accountingregistername /> | <<span style="color:#8B0000"><b>accountingregistername</b></span> /> | ||
<reversechargecategory /> - from list defined in ERP | <<span style="color:#8B0000"><b>reversechargecategory</b></span> /> - from list defined in ERP | ||
<specialregimecategory /> | <<span style="color:#8B0000"><b>specialregimecategory</b></span> /> - from list defined in ERP | ||
<caencode /> - from list defined in ERP | <<span style="color:#8B0000"><b>caencode</b></span> /> - from list defined in ERP | ||
<!--<span style="color:green">identify partner</span>--> | |||
< | <<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. | ||
<partnervatnumber /> - partner vat number | <<span style="color:#8B0000"><b>partnervatnumber</b></span> /> - partner vat number | ||
<partnername /> - partner name | <<span style="color:#8B0000"><b>partnername</b></span> /> - partner name | ||
<!--<span style="color:green">info insert/update partner</span>--> | |||
<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. | <<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. | ||
< | <<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. | ||
<partnervatnumberprefix /> | <<span style="color:#8B0000"><b>partnervatnumberprefix</b></span> /> | ||
<partnertype /> | <<span style="color:#8B0000"><b>partnertype</b></span> /> - from partner type list in ERP | ||
<partnertraderegisternumber /> - number of registration in Trade Register | <<span style="color:#8B0000"><b>partnertraderegisternumber</b></span> /> - number of registration in Trade Register | ||
<partnercountrycode /> - country code (2 characters) | <<span style="color:#8B0000"><b>partnercountrycode</b></span> /> - country code (2 characters) | ||
<partnercountycode /> - county code (2 characters) | <<span style="color:#8B0000"><b>partnercountycode</b></span> /> - county code (2 characters) | ||
<partnercountyname /> - county name | <<span style="color:#8B0000"><b>partnercountyname</b></span> /> - 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. | <<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. | ||
<partnerlocalityname /> - from list defined in ERP | <<span style="color:#8B0000"><b>partnerlocalityname</b></span> /> - 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. | <<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. | ||
<partnerstreet /> | <<span style="color:#8B0000"><b>partnerstreet</b></span> /> | ||
<partnerstreetnumber /> | <<span style="color:#8B0000"><b>partnerstreetnumber</b></span> /> | ||
<<span style="color:#8B0000"><b>partnerpostalcode</b></span> /> - partner postal code | |||
<!--partner bank account-- | <!--<span style="color:green">partner bank account</span>--> | ||
< | <<span style="color:#8B0000"><b>partnerbankaccount</b></span> /> - bank account | ||
<partnerbankname /> - bank name | <<span style="color:#8B0000"><b>partnerbankname</b></span> /> - bank name | ||
<partneraccountcurrency /> - bank account currency | <<span style="color:#8B0000"><b>partneraccountcurrency</b></span> /> - bank account currency | ||
<partnerbankaccountisdefault /> - if value is 1, this account is configured in ERP as default account of partner | <<span style="color:#8B0000"><b>partnerbankaccountisdefault</b></span> /> - if value is 1, this account is configured in ERP as default account of partner | ||
<!--<span style="color:green">partner contact</span>--> | |||
< | <<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. | ||
<partnercontactupdateinfo />- if value is 1 and partner contact is identified next attributes will be updated. | <<span style="color:#8B0000"><b>partnercontactupdateinfo</b></span> />- if value is 1 and partner contact is identified next attributes will be updated. | ||
<partnercontactsurname /> | <<span style="color:#8B0000"><b>partnercontactsurname</b></span> /> | ||
<<span style="color:#8B0000"><b>partnercontactfirstname</b></span> /> | |||
<<span style="color:#8B0000"><b>partnercontactemail</b></span> /> | |||
< | <<span style="color:#8B0000"><b>partnercontactemail2</b></span> /> | ||
<<span style="color:#8B0000"><b>partnercontactphonenumber</b></span> /> | |||
<<span style="color:#8B0000"><b>partnercontactphonenumber2</b></span> /> | |||
<<span style="color:#8B0000"><b>partnercontactaddress</b></span> /> | |||
<<span style="color:#8B0000"><b>partnercontactobservations</b></span> /> | |||
< | <<span style="color:#8B0000"><b>partnercontactcountrycode</b></span> /> - country code (2 characters) | ||
<<span style="color:#8B0000"><b>partnercontactcountycode</b></span> /> - county code (2 characters) | |||
< | <<span style="color:#8B0000"><b>partnercontactcountyname</b></span> /> - 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. | ||
<<span style="color:#8B0000"><b>partnercontactlocalityname</b></span> /> - from list defined in ERP | |||
< | <<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. | ||
< | <<span style="color:#8B0000"><b>partnercontacttitle</b></span> /> | ||
<<span style="color:#8B0000"><b>partnercontactposition</b></span> /> | |||
< | <<span style="color:#8B0000"><b>partnercontactcode</b></span> /> | ||
<<span style="color:#8B0000"><b>partnercontactisdefaul</b></span>t /> - if value is 1, this contact is configured in ERP as default contact of partner | |||
< | <!--<span style="color:green">transaction details</span>--> | ||
<<span style="color:#8B0000"><b>records</b></span>> | |||
<<span style="color:#8B0000"><b>record</b></span>> | |||
<<span style="color:#8B0000"><b>customeraccount</b></span> /> - account of customer | |||
<<span style="color:#8B0000"><b>revenueaccount</b></span> /> - revenue account | |||
<<span style="color:#8B0000"><b>transactiontype</b></span> /> - values accepted: P or S. content of transaction: product (P), service (S) | |||
<<span style="color:#8B0000"><b>valuewithoutvat</b></span> /> | |||
<<span style="color:#8B0000"><b>vatvalue</b></span> /> | |||
<<span style="color:#8B0000"><b>vatpercent</b></span> /> | |||
<<span style="color:#8B0000"><b>valueincurrency</b></span> /> | |||
<<span style="color:#8B0000"><b>currencycode</b></span> /> | |||
<<span style="color:#8B0000"><b>exchangerate</b></span> /> | |||
<<span style="color:#8B0000"><b>accountingmode</b></span> /> * - from list defined in ERP | |||
<!--<span style="color:green">transaction dimensions</span>--> | |||
<<span style="color:#8B0000"><b>businesslinecode</b></span> /> - from list defined in ERP | |||
<<span style="color:#8B0000"><b>businesslinename</b></span> /> - from list defined in ERP | |||
<<span style="color:#8B0000"><b>costcentercode</b></span> /> - from list defined in ERP | |||
<<span style="color:#8B0000"><b>costcentername</b></span> /> - from list defined in ERP | |||
<<span style="color:#8B0000"><b>budgetitemname</b></span> /> - from list defined in ERP | |||
<<span style="color:#8B0000"><b>budgetitemcode</b></span> /> - from list defined in ERP | |||
<<span style="color:#8B0000"><b>asset</b></span> /> - from list of assets in ERP | |||
<<span style="color:#8B0000"><b>assetcode</b></span> /> - from list of assets in ERP | |||
<<span style="color:#8B0000"><b>project</b></span> /> - from list of projects in ERP | |||
<<span style="color:#8B0000"><b>taskid</b></span> /> - from list of tasks in ERP | |||
<<span style="color:#8B0000"><b>nccode</b></span> /> - from list of NC codes defined in ERP | |||
<<span style="color:#8B0000"><b>record</b></span>> | |||
</<span style="color:#8B0000"><b>records</b></span>> | |||
< | <!--<span style="color:green">payment details</span>--> | ||
<<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. | |||
< | <<span style="color:#8B0000"><b>paymentdoccode</b></span> /> | ||
< | <<span style="color:#8B0000"><b>paymentaccount</b></span> /> | ||
<<span style="color:#8B0000"><b>paymentnumber</b></span> /> | |||
<<span style="color:#8B0000"><b>paymentdate</b></span> /> | |||
<<span style="color:#8B0000"><b>paymentexplanations</b></span> /> | |||
<<span style="color:#8B0000"><b>paymentexplanations2</b></span> /> | |||
<<span style="color:#8B0000"><b>paymentvalue</b></span> /> | |||
<<span style="color:#8B0000"><b>paymentmode</b></span> /> - from list defined in ERP | |||
</<span style="color:#8B0000"><b>doc</b></span>> | |||
</<span style="color:#8B0000"><b>docs</b></span>> | |||
</<span style="color:#8B0000"><b>root</b></span>> | |||
</span> | </span> | ||
Revision as of 08:12, 1 October 2019
- Financiar si contabilitate
- Contabilitate
- Configurare
- Import
- Import:Vanzare cu incasare
- Vanzare cu incasare XML
- Import:Vanzare cu incasare
- Import
- Configurare
- Contabilitate
Xml - Sales invoice with payment
*elements marked with this sign are mandatory
<root>
<docs>
<doc>
<nrcrt />* 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 /> * - 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
<docreportingdate /> - for companies wich use 2 reportings : one for state reporting and one for reporting to group
<docnumber /> * - document number
<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 customer.
<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-->
<dociscancelled /> - document is marked as canceled
<iscustomerreturn /> - set value to 1 if is customer return
<companyvatuponcollection /> - 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)
<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
<specialregimecategory /> - from list defined in ERP
<caencode /> - 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.
<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>
<record>
<customeraccount /> - account of customer
<revenueaccount /> - revenue account
<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
<!--transaction dimensions-->
<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 of assets in ERP
<assetcode /> - from list of assets in ERP
<project /> - from list of projects in ERP
<taskid /> - from list of tasks in ERP
<nccode /> - from list of NC codes defined in ERP
<record>
</records>
<!--payment details-->
<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>