DBF Integration Layout - Customers

• This article introduces the fields of the customer onboarding layout. To better understand the concept behind customers, see our article on Customer Concept.

Order	Field Description	Format and Size	Required	Version	Note
1	Document Code Customer (code)	INT (11)	Yes	4.58
2	CPF/CNPJ(cpfCNPJ)	Text (18)	No	4.58	Send with mask EX:01.010.101/0001-72, field becomes mandatory when code and uniqueID are null, blank or zero.
3	Condition Code Payment(codCondicaoPagamento)	Text (20)	No	4.58	Determines this customer’s default payment condition. This is the payment condition that will be selected when you start entering a new order. *When the payment condition is blocked, it is not allowed to change the order. IfbloqueiaCondPagamento= 1, only the payment condition defined is shown when creating an Order and cannot be changed. IfbloqueiaCondPagamento= 0 and there is a payment condition defined, it is loaded as default, but can be changed. IfbloqueiaCondPagamento= 0 and you DO NOT have a payment term defined, a default payment term is not loaded, but allows you to select another payment term. This field is not cleared when sent empty from the ERP to the Demander. To clear the field, you must send a code for a payment method that is not registered.
4	Payment Method Code (codFormaPagamento)	Text (20)	No	4.58
5	Region Code(codRegiao)	INT (11)	No	4.58
6	Region Code Seller(codVendedor)	INT (11)	No	4.58
7	Price List Code(codListaPreco)	Text (20)	No	4.58	Determines the default price list for this customer. This is the price list that will be selected when you start entering a new order. *When the price list is locked, changes in the order are not allowed. IfbloqueiaListaPreco= 1, only the defined price list is shown when creating an Order and cannot be changed. IfbloqueiaListaPreco= 0 and you have a defined price list, it is loaded as default, but can be changed. IfbloqueiaListaPreco= 0 and you DO NOT have a price list defined, a default list is not loaded, but allows you to select another price list. This field is not cleared when sent empty from the ERP to the Demander. To clear the field, you must send a code from a price list that is not registered.
8	City Code(codCidade)	INT (11)	Yes	4.58
9	Branch Code(codFilial)	INT (11)	No	4.58	Determines the default branch of this customer. This is the branch that will be selected when you start entering a new order. *When the branch is blocked, changes to the order are not allowed. IfbloqueiaFilialUnidade= 1, only the defined branch is shown when creating an Order and cannot be changed. IfbloqueiaFilialUnidade= 0 and a branch is defined, it is loaded as default, but can be changed. IfbloqueiaFilialUnidade= 0 and you DO NOT have a branch defined, a default branch is not loaded, but allows you to select another branch. This field is not cleared when sent empty from the ERP to the Demander. To clear the field, you must send a code from a branchthat is not registered.
10	Name Reason(nomeRazao)	Text (100)	Yes	4.58
11	Fantasy Name(nomeFantasia)	Text (100)	Yes	4.58
12	Type of Person(tipoPessoa)	Text (1)	Yes	4.58	F = Individual; J = Legal
13	RG/IE(rgIE)	Text (20)	No	4.58
14	Telephone 1(phone1)	Text (254)	No	4.58	Send with mask. EX: (51) 3714-7017
15	Phone 2 (phone2)	Text (254)	No	4.58
16	Buyer’s Email(emailComprador)	Text (254)	No	4.58
17	Email NF-e(emailNfe)	Text (254)	No	4.58
18	Financial Email(emailFinanceiro)	Text (254)	No	4.58
19	Contact(contact)	Text (50)	No	4.58
20	Address(address)	Text (100)	No	4.58
21	Neighborhood(neighborhood)	Text (50)	No	4.58
22	CEP (cep)	Text (50)	No	4.58	Send with mask EX: 95900-000
23	UF (uf)	Text (2)	No	4.58
24	Observation (observation)	Text (254)	No	4.58
25	Number (number)	INT (11)	No	4.58	Address Number
26	Complement (complement)	Text (200)	No	4.58
27	Unique Customer Identifier (idCliente)	INT (11)	No	4.58	ATTENTION: If the seller registered a new customer without informing CPF/CNPJ, the customer assumes code Zero, however when the ERP returns the customer information it already comes with a code, so this field is used as a key to update the customer, since the CPF/CNPJ was not filled in. Therefore, your ERP needs to store this field to return to Demander, otherwise customers will duplicate it in Demander or sellers will not be allowed to register customers without providing CPF/CNPJ.
28	Tax Customer Type Code (codTipoClienteTributario)	Text (50)	No	4.58	This field is used by some companies in IPI and ICMS ST calculations, only worry about it if you are going to integrate the Taxation configuration.
29	Prospect (prospectus)	INT (1)	No	4.58	0 - He is not a Prospect, he is already a Customer. 1 - He is a prospect, he is not yet a Customer. The Demander allows salespeople to register customers they are prospecting. Normally these Prospects do not want to provide all the registration data, which is why in the Demander application we have a separate functionality for registering prospects, including a separate mandatory configuration. Even if you are not a customer, the Prospects can be exported to the ERP in the customer table layout. If your ERP is not structured to import prospects, configure them so that they are not exported. To do this, access “Company Settings”, the “Additional Settings” tab and look for the “Export Prospects” setting and define Yes or No.(We currently do not support the import of prospectuses without code or CNPJ, unless you use the field “Demander Unique Identifier”)
30	Date of Birth (dataNascimento)	Date	No	4.58
31	Related Segments (segmentosRelacionados)	Text (254)	No	4.58	Field to identify the segments that the given customer uses. Ex.: Motorcycle utilities, Bicycle utilities
32	Credit Limit (limiteCredito)	INT (11)	No	4.58	Used to block orders for customers who exceed their credit limit. Also used for Financial Receipt Module.
33	Customer Type Code (codTipoCliente)	Text (50)	No	4.58	Table codeCustomer Type.
34	Sales Division Code (codDivisaoVendas)	Text (50)	No	4.58	Customer Code tableSales Division.

Registration Example: