Framework Agreements
Note: Billing is currently a beta feature and is being rolled out with pilot customers. If you would like to take part, please get in touch with us.
A framework agreement holds a commercial frame you have agreed: the agreement's name and number, the customer it is with (if it names one), the currency it is written in, how long it runs, the projects it covers and the rates that were agreed. The projects need not belong to the agreement's customer, so one agreement can cover a group of companies, for example an agreement with a group head office that covers the projects of its subsidiaries. Orders created underneath it are prefilled from those rates, so the agreement is the place to record a price once instead of on every order.
Open it under Finance → Framework agreements. The page and everything on it require the Manage accounting permission.

The list has one row per agreement:
| Column | Description |
|---|---|
| Name | The agreement's name. Opens the agreement's page. |
| Code | The code other systems identify the agreement by. |
| Framework agreement number | Your own reference number for the agreement. |
| Customer | The company the agreement is with. Empty when it names none. |
| Projects | The projects it covers. |
| Active | Whether the agreement is still in use. |
| Start date / End date | How long the agreement runs. |
| Currency | The currency it is written in. |
| Creator / Creation date | Who created the agreement, and when. |
| Updated by / Last update | Who changed it last, and when. |
Search the list, sort and filter it by its columns, and choose which columns to show. A filter can be saved for later; All framework agreements lists every agreement. Data fields your company adds to framework agreements appear as further columns (see Data fields).
Creating a framework agreement
Click Create, fill in the New framework agreement dialog and click Create again. The new agreement's page opens.
| Field | Description |
|---|---|
| Name | The agreement's name. Required. |
| Code | Optional. It identifies the agreement for other systems, so no two agreements can share it: “Another framework agreement already uses this code.” |
| Framework agreement number | Your own reference number. |
| Customer | The company the agreement is with. Optional, and it does not limit which projects you can add. You can change or clear it later. |
| Projects | The projects the agreement covers, of any customer. |
| Active | Clear this to retire an agreement without deleting it. |
| Start date / End date | The validity period. The end date must be after the start date. |
| Currency | The currency the agreement is written in, preset to your company's currency. Orders created under it are prefilled with it. |
You can also enter a customer that is not in decídalo yet: type its name under Customer and choose to add it, and the company is created as a customer along with the agreement. Data fields your company adds to framework agreements appear in the dialog too. Below the fields, the Rates section takes the agreed rates (see Agreeing the rates).

Which projects you can add
Projects of every customer are offered, whichever customer the agreement names. Type to search for a project. Each project is listed with its customer, so a selection that spans several companies stays easy to check.
A project belongs to at most one framework agreement. A project that already belongs to another agreement is greyed out with “Already in framework agreement ‘{name}’” and cannot be selected. Remove it from the other agreement first.
Note: You can also set the framework agreement from the other end: the project's Accounting tab has a Framework agreement field. Type part of an agreement's name, number or customer to find one, or choose Create new framework agreement to create one for the project. See Orders & Positions.
The agreement's page
Each agreement has a page of its own, opened from its name in the list. The header shows the agreement's name, its customer and how long it runs, and the page has two tabs: Details and Rates.

On the Details tab, click a field to change it. The change is saved as soon as you confirm it. If decídalo refuses a value, the field stays open and says why, for example “Another framework agreement already uses this code.” The Currency field comes right after End date.
The Projects panel beside the fields lists the projects the agreement covers, each linking to its project. The x beside a project takes it out of the agreement. To add one, search for it under Add project, or choose Create new project there: the project you create joins the agreement right away. As in the dialog, a project of another agreement is greyed out.
The Rates tab holds the agreement's rates (see Agreeing the rates).
Agreeing the rates
Each rate is one priced role or service: a Label, such as "Senior Consultant", with its prices.
| Field | Description |
|---|---|
| Label | What is being priced. A label can be used only once per agreement: “Another rate already uses this label.” |
| Rate | The agreed price. It cannot be negative. |
| Currency | The currency of that price. A rate has one price per currency, whatever its unit: “This currency already has a price.” |
| Unit | Hour or Person day. |
Note: A Person day rate is converted to an hourly rate by dividing it by eight when time is billed. That eight is fixed and does not follow your company's working time patterns.
In the creation dialog
The dialog's Rates section shows each rate in a box of its own, its prices beneath its label. Add price adds a price in another currency and the x beside a price removes it. A rate keeps at least one price, so remove the whole rate with the x beside its label. Add rate adds another rate.
Or start from a rate card: choose one under Prefill from rate card and click Prefill. Prefilling copies the card's rates into the agreement, each with all its prices, and it only adds: a rate the dialog already has gains the prices in the currencies it lacks, and nothing already entered changes. A rate without a price is not added. Editing the rate card afterwards leaves existing agreements untouched, which is deliberate: an agreed price should not move under a customer's feet.
Rate cards are maintained by an administrator (see Rate cards).

On the Rates tab
Once the agreement exists, its rates are kept on the Rates tab of its page, grouped by rate: a row with the rate's label and the number of its prices, and its prices beneath it. Click a rate's row to fold its prices away or show them again.
- To change a price, click its Rate, Currency or Unit. The currency offers only those the rate has no other price in.
- To rename a rate, click its label. Its prices move with it, and a label another rate already uses is refused.
- The + after the price count adds prices to the rate, several at once, in the currencies it has no price in yet. It is not shown once the rate has a price in every currency.
- The bin icon at the end of a price's row deletes that price, and the one at the end of the rate's row deletes the rate with all its prices. Both ask first.
- Create opens New rate: enter a label and its prices, with Add price for each further currency.
The tab has no rate card prefill: a rate card prefills only the creation dialog.

Changing and removing an agreement
Change an agreement on its page: its fields and projects on Details, its rates on Rates.
Because each step in the chain is a copy, changing an agreement's rates does not change orders that were already prefilled from it. Apply a price correction where it is used as well, not only at the source. On an imported order, that means in the system it was imported from. The full chain is described under Where the rate comes from.
To retire an agreement without losing its history, clear Active.
Delete an agreement from its row in the list; decídalo asks “Delete framework agreement ‘{name}’?” first. An agreement that has servicesheets cannot be deleted: the delete action is disabled and explains “This framework agreement has servicesheets and cannot be deleted.” Deactivate it instead.
Deleting a project takes it out of its agreement. A project that belongs to an agreement cannot be merged with another project, in either direction, until it is removed from the agreement, see Projects.
Data fields
Which fields a framework agreement has is up to your company. Under Administration → Data fields, the Framework agreement entity is customized like the others: its fields can be renamed, hidden or added to. A field you add appears in the list, on the agreement's Details tab and in the creation dialog. Customizing it requires Administer data fields; the Framework agreement entry is listed for users who also have Manage accounting. See Customizing data fields.
Agreements from other systems
Another system can read and maintain framework agreements through decídalo's import interface, with their projects, rates and data fields. It identifies an agreement by its Code. Unlike an imported order, an agreement the interface creates stays editable in decídalo, and one that has servicesheets cannot be deleted through the interface either.
Where the agreement is used
- On an order: when you add a rate on the order's Rates tab, Prefill from framework agreement in the New rate dialog fills in one of the agreement's prices. See Orders & Positions. An imported order is the exception: its rates come from the system it was imported from.
- On a servicesheet: the agreement is shown on the servicesheet and is a column in the servicesheet list. The servicesheet's customer stays the customer of its order or project, which can differ from the agreement's own customer.
- On billable work: the Billable orders grid shows each order's framework agreement.