The supplier contract is created from scratch on the contracts screen, and someone retypes the legal name, CNPJ and address.
"Generate contract" button on the source screen, with the contract filled from the record and linked to it.
Business management · Contracts Integrated with Modules
The general contract is born where the relationship begins. A single catalog of 12 sources and a "Generate contract" button on the source screens fill the contract with the right record. At creation, the CNPJ is looked up in three chained sources, without depending on the CRM, and the counterparty goes through CEIS and CNEP sanctions screening. The B2B proposal total arrives intact, with price band, modifier and discount.
The problem and the fix
If any of these situations sounds familiar, it is because they happen in almost every graduation company, until the right system comes in.
The supplier contract is created from scratch on the contracts screen, and someone retypes the legal name, CNPJ and address.
"Generate contract" button on the source screen, with the contract filled from the record and linked to it.
Each module generates contracts its own way, and nobody knows where each one came from.
A single catalog with 12 sources. Each source knows which record fills the contract, and the same list applies to every screen.
The CNPJ was typed wrong, or the company changed its legal name, and the contract went out with stale data.
Automatic CNPJ lookup at creation, chained through BrasilAPI, CNPJ.ws and ReceitaWS: if one source fails, the next one answers. Without depending on the CRM.
The company signed a contract with a supplier that was barred from contracting with the public sector.
Sanctions screening against the CEIS and CNEP lists at contract creation.
The B2B proposal had a price band and a negotiated discount, and the contract went out with a different amount.
The B2B proposal total is honored in the contract, with price band, modifier and discount preserved.
The employee's contract points to the wrong record, and so does the class's.
Links point to the right record: the employee is the HR record, the class is the operational one.
In practice
Everyday situations at graduation companies, from the problem to the result, using the modules on this page.
The salesperson closed a B2B proposal with an institution, with a volume price band and a closing discount.
On the proposal, they clicked "Generate contract". The contract was born with the proposal total, price band, modifier and discount, and the institution's CNPJ looked up on the spot.
No amount retyped, and the contract linked to the proposal that originated it.
Purchasing was about to hire a security company for the semester's events.
When generating the contract from the supplier record, sanctions screening found the CNPJ on the CEIS list.
The hiring stopped before signing, and Purchasing looked for another qualified supplier.
Late one afternoon, BrasilAPI was down and the team needed to generate three contracts.
The chained lookup moved on to CNPJ.ws and, if needed, to ReceitaWS. All three contracts went out with current data.
Nobody noticed the outage, and no contract was left for the next day.
How it works
Every step is a real module, and what comes out of one goes into the next without anyone typing it again.
Module by module
4 modules and 16 features on this page, all running on the same class, graduate and event records.
Twelve records that can originate a contract, in a single catalog.
The button sits where the relationship is, and the contract is born filled in.
CNPJ looked up in three chained sources and the counterparty screened against sanctions lists.
The total negotiated in the proposal reaches the contract intact.
Compare the modules and choose the setup that fits your operation.