📘 Screen: Entity

The Entity screen is used to register people or companies that have some relationship with the farm. It covers suppliers, customers, carriers, drivers, agronomists, and others.

📍 Location in the system

Menu: Inventory > Entity

The same screen also appears under Financial > Entity — it is a single record, used by both areas.


🧩 Main function

Record the entity's registration data and define the kind of relationship it has with the farm. This record is the basis for modules such as financial, tax, contracts, inventory movements and harvest.


📝 Main record fields

FieldDescription
TypeRequired. Legal Entity or Individual — this is what determines whether the screen asks for a CNPJ (company tax ID) or a CPF (individual tax ID).
ActiveUncheck it to remove the entity from selection lists without erasing its history.
CNPJ / CPFThe entity's document. Next to it is the Retrieve data button, which looks up the registration data from the CNPJ entered — it saves typing and avoids mistakes in the legal name.
Legal name and Trade nameHow the entity appears on documents and in selection lists.
State registration and Municipal registrationTax data.
AddressBlock with street address, number, neighborhood, ZIP code (CEP), city and additional details.
Phone, Website and EmailGeneral contacts.
Code, Reference ID and IBGE Municipality CodeControl and integration codes.
Account and Cost Center Defaults used in the entity's financial entries.
NotesFree note.

What the entity is

A set of checkboxes defines the role — and you can check more than one: the same company is often both a supplier and a carrier.

  • Supplier, Customer, Third party and Third party for harvest intake
  • Cotton gin, Carrier, Driver and Agronomist
  • Require Cost Center — makes the cost center mandatory in that entity's entries

These checkboxes are what make the entity appear (or not) on each screen: only entities checked as Driver show up in the driver selection of the MDF-e, for example.


🗂 Additional tabs

  • Address: lets you register multiple addresses, each with its own state and municipal registration, used mainly for tax purposes (e.g., a customer with several locations). It also has the same payment details block described below
  • Payment details: the supplier's bank, branch, account and PIX key — this is what lets you pay them by file, in the payment batch
  • Movements (invoices): lists all movements made with the entity (purchases, sales, services)
  • Contract: informational tab with the contracts linked to the entity
  • File: lets you attach various documents, such as PDFs, spreadsheets and images
  • Contact: the contact people at that entity — the salesperson, the manager, whoever handles things day to day

💳 Tab: Payment details

This is where you state how the supplier gets paid. Without these fields, the farm can record the account payable, but cannot send the payment to the bank by file: the payment batch does not generate the remittance for a supplier with no PIX key and no account.

FieldDescription
Bank and Bank codeThe payee's bank. The code is the three-digit clearing code — "077 for Inter, 001 for Banco do Brasil, 341 for Itaú", as the field help says.
Branch and Branch check digitThe branch, with the check digit in its own field.
Account No. and Account check digitThe account, with the check digit in its own field. The help explains why: "Required in the file: an account without it does not receive."
Account typeChecking, Payment or Savings. It matters: "A savings account sent as checking comes back as an invalid account."
PIX key typeCPF/CNPJ, Email, Phone or Random key. The type is what tells the bank what to look up — a key saved without its type is not used.
PIX keyThe key exactly as registered at the payee's bank. "A truncated key does not exist in DICT and the payment bounces."
ISPBThe first eight digits of the CNPJ of the payee's bank. Only required for banks without a clearing code and for PIX by bank details.
Payment noteFree note about paying that supplier — it appears as a tip in the batch's "How it will be paid" column.
💡 The same block exists on the Address tab, and there it overrides this one. This is the case of a head office and its branches: each location is paid into its own account. The screen says so above the block — "Payment details of this address. Filled in here, they REPLACE the ones on the Payment details tab; left blank, the entity's are used." The data comes entirely from one of the two, never half from each, and the name and CPF/CNPJ are always the entity's — that is the account holder the bank checks against the account.

The PIX key takes priority over the account when both exist: it settles instantly, has no fee and does not depend on business days. To see how each payment will go out before generating the file, use the How it will be paid column on the Installments tab of the payment batch.


🔧 Features in the list

The list shows Code, Legal name/Name, Trade name, CNPJ, CPF, Management account/Category, Cost Center and Active, with a quick filter by role at the top: All, Customer, Supplier, Third party, Driver, Cotton gin, Agronomist and Harvest third party.

  • Change multiple: bulk editing tool that lets you change:
    • The entity's cost center
    • The account used in financials

📊 Related reports

CAD.02.01 (formerly 011.E) - Entity Report: complete list with the entities' registration data
FIN.01.02 (formerly 15.06) - Accounts payable/receivable by Entity - General: shows the balances aggregated by entity
FIN.01.01 (formerly 15.07) - Accounts payable/receivable by Entity - Installments: details each installment linked to the entity
EST.02.02 (formerly 011.D) - Movements: shows all inbound and outbound movements related to the entity
✅ Result: With entities registered correctly:
  • The tax, financial and operational modules work together
  • Documents can be kept organized by entity
  • Harvest, transport and contract operations run more efficiently

❓ Frequently asked questions

Do I need to register suppliers and customers on different screens?

No. This screen registers any person or company related to the farm. The role is defined by the entity type, and you can check more than one option: Supplier, Customer, Third party, Cotton gin, Carrier, Driver, Agronomist, among others.

A customer with several locations: how do I register the addresses?

Through the Address tab, which lets you register multiple addresses for the same entity — used mainly for tax purposes.

Where can I see everything I have bought from a supplier?

On the record's Movements (invoices) tab, which lists all movements made with that entity: purchases, sales and services.

Do I have to type in all the company's data by hand?

No. Enter the CNPJ and click Retrieve data: the system brings in the legal name, trade name and address, and you just check them. Besides saving typing, it avoids legal-name mismatches when you enter the invoice.

The entity does not show up for selection on a screen. What should I check?

The record's checkboxes. Each screen only offers entities checked with that role — a driver shows up where you choose a driver, a carrier where you choose a carrier. Also check that it is Active.

Can I attach documents to the record?

Yes, through the File tab, which accepts PDFs, spreadsheets and images.

How do I change the cost center of several entities at once?

With the Change multiple tool in the screen's list, which bulk-edits the cost center and the account used in financials.

Where do I register the supplier's PIX key and bank account?

On the Payment details tab of the entity record, in upCampo. For PIX, fill in the PIX key type and the PIX key; for a wire transfer (TED), the bank with its code, the branch and the account with their check digits, and the Account type. When one of the supplier's branches is paid into a different account, register the block on that branch's address: there it overrides the entity's. This data is what the payment batch uses to generate the bank remittance file.