Contract qualification
Why qualify a contract
A contract is more than its amount. To manage it, you also need to know what it covers (hardware, software, services), who signed it within the group, and above all until when you can get out of it: a tacitly renewed contract whose notice date you miss starts again for a whole term.
The Qualification section of a contract's panel brings this information together. It is the same in both modules:
- Clients → Contracts, for client contracts;
- Suppliers → Contracts & orders, for framework agreements and orders.
Nothing in it is mandatory, with one exception: the currency rule.
The fields
| Field | Content |
|---|---|
| Folder | The contract type — Hardware, Software, Services… — chosen from a workspace list |
| Purchasing category | The purchasing family — IT, Consulting services, Overheads… — chosen from a workspace list |
| Company | The group company that signs the contract. This is not a new list: it is the Companies list of the resource description |
| Product / service description | What the contract covers, as free text |
| Signature date | The date the contract was signed |
| Contract currency | The ISO code of the contract currency (EUR, USD, CHF…) — for information, see the currency rule |
| Estimated amount | The amount in the workspace currency |
| Estimated amount in contract currency | The amount in the contract currency; shown only when it differs from the workspace currency |
| Duration type | Instant execution, Fixed term, Indefinite term or Tacit renewal — a workspace list |
| Notice | A duration (days, weeks, months or years), or the No prior notice checkbox |
| Renewal duration | The length of a tacit renewal, or the Not applicable checkbox |
| Renewal maximum fees (%) | The cap on the price increase at each renewal |
| Active price | The price currently applied |
| Price revision | Checkbox; it opens the Revision formula and the Revision % |
| Penalty | The penalties provided for, as free text |
| Billing in arrears / in advance | The billing term, chosen from the billing terms list |
The billing term already existed on client contracts; supplier contracts now have it too, in their Qualification section, with the same list.
Qualification relies on what the contract already holds: the start date, the reference (the contract identifier), the amount — contract amount on the client side, committed amount on the supplier side — and the payment term. They are still entered in their usual place.
Notice, renewal and calculated dates
Two dates are shown under the duration fields. They are calculated, never entered:
| Date | Calculation |
|---|---|
| End of current term | The contract end date, pushed back by one renewal duration for each tacit renewal already passed |
| Notice deadline | The end of the current term, minus the notice: the last day to terminate the contract |
A contract ends on 31/12/2026, with a 3-month notice and a one-year tacit renewal.
- The notice deadline is 30/09/2026: after that day, the contract renews for one year.
- If nothing is done, once 31/12/2026 has passed, the end of the current term becomes 31/12/2027 and the new notice deadline 30/09/2027.
Without an end date, both dates stay empty. A contract with no prior notice has no notice deadline: only the end of the term counts. A not applicable renewal keeps the end of the term equal to the contract end date.
Getting warned before the deadline
The Notify me of contract end or tacit renewal date checkbox turns on an alert, with a number of days before (30 by default).
Every day, FoxPlan checks the contracts concerned and warns the leaders of the party — the client leaders for a client contract, the supplier's purchasing leaders for a supplier contract:
- an in-app notification (the bell);
- an email, with a View the contract link that opens the contract directly.
The alert is sent once before the notice deadline, then once before the end of the term. A new end date — after a tacit renewal or an edit of the contract — re-arms the alert for the next term. Cancelled or closed contracts are ignored.
The currency rule
A contract may be denominated in a currency other than the workspace's: an American software vendor bills in dollars, a Swiss provider in francs. Qualification records it without distorting the budget:
- the Estimated amount in the workspace currency is the one that counts. It is mandatory once the contract is no longer a draft when the contract currency is foreign;
- the Estimated amount in contract currency is for information only.
No qualification field flows into the budget envelopes. The budget still comes from the committed amount, the schedule and the allocation for a supplier order, and from the envelopes for a client contract, exactly as before. The contract currency converts nothing.
Finding contracts by their qualification
The grids of both contract screens offer new columns, hidden by default: Folder, Purchasing category, Company, Duration type, Signature date, Currency, Estimated amount, End of current term, Notice deadline and Product description.
Show them from the grid's column side bar; your favorite remembers the layout. Sorting on Notice deadline shows at a glance the contracts to handle first.
Setting up the lists
Settings → Workspace → Client, Contract qualification block, under the billing lists. Three lists can be edited there:
- Folders (contract types);
- Purchasing categories;
- Duration types.
Each item has a label, a description and an Active checkbox. The lists are shared by client and supplier contracts. They are pre-filled on first use, in the user's language, with common values to adapt.
As with the billing lists, an item used by a contract cannot be deleted: deactivate it. The lists have their own Save the qualification lists button. Only workspace administrators edit them. Details are in Settings → Client.
Companies are managed in the resource description, billing in arrears / in advance in the billing terms.
AI and qualification
When reading a contract
Fill from a contract and Create from a document (see Filling the record from a contract) also propose the qualification of the created contract:
- the folder, purchasing category, duration type, billing term and company are chosen only from the workspace lists. A label that is not in the lists is shown in the review, but not applied;
- the notice, renewal, signature date, price revision and penalties are read from the document.
If the contract is denominated in a currency other than the workspace's, the AI does not copy its amounts into the fields that feed the budget: amount, recurring amount, cap, installment amounts, rates. The total goes into Estimated amount in contract currency, and a warning asks you to enter the converted amount yourself.
In the AI chat
The assistant tools that list contracts now return their qualification. A dedicated tool looks up notice deadlines and tacit renewals, across clients and suppliers.
Two predefined tasks ship with FoxPlan:
| Predefined task | What it produces |
|---|---|
| Contract deadlines | Contracts to terminate, renegotiate or let renew within a given horizon (90 days by default): notice deadlines, term ends, tacit renewals, price revisions |
| Contract qualification | Contracts whose qualification is incomplete or inconsistent — for example a contract in a foreign currency without an amount in the workspace currency |