Client Configuration defines the registration data a company maintains about each client — an individual or a business — independent of whichever specific credit process that client happens to be going through at a given moment. While a credit process is born, moves forward, and closes with every new operation, the client record persists: it is the accumulated body of knowledge about who that rural producer, that agribusiness company, or that guarantor actually is, available to be consulted and enriched no matter how many different processes that same person or business goes on to be part of over time.Each company organizes this record in its own way, grouping information into thematic sections — personal data, properties, production activity, references, corporate documentation — and defining, within each section, the fields that make sense for the type of client it serves. A company working mostly with individual rural producers prioritizes fields such as planted area, dominant crop, or land tenure arrangement; a company focused on agribusiness corporate clients prioritizes ownership structure, revenue, and regulatory certificates. This flexibility exists because there is no single standard client in agribusiness — the record adapts to the profile of whoever the company serves, rather than forcing everyone into the same generic mold.The strategic value of this configuration lies in turning scattered information into reusable knowledge. Without a structured record, every new credit analysis would start from zero, asking the client for data already provided before. With Client Configuration properly designed, the right information about each client stays consistently available — ready to be consulted, updated, and cross-referenced in any future analysis, approval, or technical opinion, regardless of which flow or phase originated the first contact. It is the foundation that sustains the continuity of the client relationship throughout that client's entire credit journey with the company.Simplified example#
{
"companyId": "<company-id>",
"sections": []
}
For the complete data model and all implementation rules, see the full technical reference in the 🇺🇸 English tab. Modificado em 2026-07-28 20:38:32