Orders & Positions
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.
An order represents what the customer actually ordered, and its positions are the lines of that order. The position is where the price lives, and it is where recorded time and the commercial structure meet, so setting orders up correctly is what makes billing work later.
There are two ways in: Finance → Orders lists every order across all projects, and a project's Accounting tab lists the orders on that one project. Both open the same order detail page.
Working with orders needs Manage project billing and orders; the framework agreement and servicesheet rules sections additionally need broad billing responsibility. See the Billing concept.

The project's Accounting tab
The Accounting tab holds the commercial setup for one project, in four sections.
Framework agreement: the agreement this project belongs to, or “No framework agreement”. Click it and type part of an agreement's name, number or customer to find one; every active agreement is offered, whichever customer it is with, shown with its number and its customer. Clear the field to take the project out of its agreement. A project belongs to at most one. Where you can open Framework agreements, Open framework agreement opens the agreement's page; with Manage accounting, Create new framework agreement in the field creates one that the project then belongs to. See Framework Agreements.
Servicesheet rules: the rules used when the project's recorded time, and what is recorded beside it, is turned into what goes onto a servicesheet, with a section per recording type. New projects start from the default policy. See Servicesheet policies.
Time recording approval: its switch Approval required for recorded time decides whether this project's recorded time waits for somebody to confirm it. Off by default, in which case time is confirmed as soon as its owner hands it in, and time that arrives through the import is confirmed on arrival unless the source system sends a status of its own. Either way it is billable from then on. Shown only while your company has time recording approval switched on. See When confirmation is needed.
Orders: the orders on this project. Click Add to attach one: the picker searches your existing orders, so an order that already exists for another project can simply be added here rather than created twice. If none fits, choose Create new order in the picker.
Because an order can serve several projects, taking it off this project and deleting it are two different things, and the row's actions keep them apart:
| Action | What it does |
|---|---|
| Remove from project | Takes the order off this project and keeps the order itself, with its positions, on every other project it serves: “Do you really want to remove the order ‘Portal Build 2026’ from this project? The order itself is kept; links from its positions to this project's work packages are removed.” |
| Delete | Deletes the order itself: “Do you really want to delete the order ‘Portal Build 2026’? This deletes the whole order with all its positions on every project it is on and can't be undone.” |
Remove from project is refused once time has been recorded against the order on this project: “Can't be removed because time has already been recorded for this project.” The recorded time names this project through the order, so unlinking it would leave that time pointing at nothing. The same guard applies on the order's own page and through the import interface.

Creating an order
The order's own fields are configurable for your company, so the exact set may differ. The standard fields are:
| Field | Description |
|---|---|
| Name | Required. What the order is called. |
| Code | The customer's order number or your own reference. |
| Customer | The company that placed the order, and the one its servicesheets are addressed to. It does not have to be the customer of the projects the order is delivered on. Time recorded directly on the order, without a project, reaches Billable work only once the order has a customer; until then the Customer field on the Order details tab shows a warning sign. |
| Projects | The projects the order is delivered on. An order can serve several. |
| Currency | Required. The one currency the order is billed in. |
| Order date / Delivery date | When the order was placed and when it is due. |
| Billing address, Shipping address, Goods recipient | The commercial addresses. |
| Terms of payment, Shipping terms | The agreed terms. |
| Description, Notes | Free text. |
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 order. Data fields your company adds to orders appear in the dialog too.
Note: The currency cannot be changed once the order has servicesheets. The field is then locked and explains “The currency can't be changed because this order already has servicesheets.” Withdrawing every servicesheet on the order releases it again. On an imported order the currency is always locked, and the field gives the import as the reason. See Currencies and totals.
decídalo warns you when the order and its project do not line up in time: “The order expires on … before this project ends on …” or “The order only becomes valid on … after this project starts on …”. These are warnings, not blocks.
From an uploaded document
Rather than typing an order out, you can hand decídalo the customer's order document and let it read the fields for you. Upload from document sits next to Create on Finance → Orders, and on that page only: a project's own Orders grid does not offer it. While no order exists yet the empty state offers Create order and the upload, because a first order is exactly the case worth uploading.
The Upload order from document dialog takes one PDF, dropped on it or chosen with Select file. While the document is read you see “Analyzing the document…”, which can take a moment.
Once the document is read, the ordinary Create order dialog opens with what was found filled in: the name, the code, the customer, the currency and the dates (Order date, Valid from, Expiry date). It is a proposal, not an order:
- A customer name that matches one of your companies is pre-selected. No company is ever created from a document, so an unrecognised name simply leaves the field for you to fill.
- Extracted details, below the fields, holds what the document says that has no field of its own in the dialog, such as the description, the billing address, the terms of payment and the goods recipient: “These values were read from the document and are saved with the order. They can be edited later on the order page.”
- Extracted positions lists the lines that were found, each with its name, type, price and quantity. They become the order's positions when it is created. Use the × beside a line (Remove position) on anything the document should not have contributed.
Nothing is saved until you click Create, and the usual rules still apply: the name and the currency are required, and the code has to be free. So the upload saves the typing, not the review.

Two documents are refused, each with its own message:
- “No text could be read from this document. Scanned PDFs without embedded text are not supported.” The document is a picture of an order rather than an order: it has no text to read. Ask for a PDF exported from the sender's system.
- “No order data could be extracted from this document. Try another file or create the order manually.” Text was read, but nothing in it looked like an order, or the reading itself failed, in which case trying the same file again can work.
The upload dialog stays open in both cases, so you can try another file.
Imported orders
If your organization maintains its orders in another system, they can be transferred into decídalo through the import interface instead of being created by hand. An order the import created carries the chip Imported on its detail page, which explains on hover: “Maintained through an interface, so the order can't be edited or deleted here. Its positions can still be added, edited and deleted.” Its fields on the Order details tab and its Rates are read-only, and the order cannot be deleted, because the other system stays the single source. The interface is documented at https://import.decidalo.app/index.html.
The rest of the order works as usual: its positions can be added, edited and deleted under the same rules as on any other order, and its projects and Servicesheet rules can still be changed.
Only an order the import created is marked. An order created in decídalo stays editable, even when the import updates it later.
The order detail page
An order opens with four tabs.
| Tab | What it holds |
|---|---|
| Order details | The order's own fields, editable in place unless the order was imported. |
| Positions | The lines of the order and their prices. |
| Rates | The rates the positions are priced from. |
| Recordable activities | The positions' activity types, which apply to the order's projects and to the order itself, and who may record directly on the order. See Setting Up Time Recording on an Order. |
Alongside them the page shows the projects the order is delivered on (add one with Link project with order or Create new project, remove one with Remove project), its Delivery figures, and the order's Servicesheet rules.
The order's Servicesheet rules have a section per recording type, like a servicesheet policy. Where a distance is charged at a flat amount, the Flat amount is entered here, in the order's currency; a policy and a project's rules only decide that a flat amount is charged, so entering it keeps the order on its policy. See Rules per recording type.
Note: Changing or removing an order's project also removes the links between its positions and that project's work packages. decídalo asks before doing it.
Linking a project to the order gives that project the positions' activity types, so the people who may record on its order positions can record them from then on. Removing the project switches them off for it again.
On an imported order only the positions, the projects and the servicesheet rules can be changed here. See Imported orders.

Adding positions
Open the Positions tab and click Create to open the Add position dialog.
| Field | Description |
|---|---|
| Name | Required. What the position covers. |
| Code | Optional. The position's own code. It has to be unique within the order, but the same code may be used on a position of another order. It is also the key the Import API addresses the position by, and it stays editable after time was recorded. |
| Reference code | Optional free text naming what the position maps to in an external system, for example the SAP order position its recorded time is synchronized to. It does not have to be unique, so several positions of one order (one per rate, say) can carry the same reference. It stays editable after time was recorded. |
| Type | Fixed price or Time & material. Switching type clears the fields that no longer apply, after asking. |
| Fixed price | Fixed-price positions only: the lump sum. |
| Rate, Unit and Sold quantity | Time & material only: the price per Hour or per Person day for the time itself, and the agreed volume that Remaining is measured against. All three describe the working time, so they are hidden on a position whose activity types do not record it. Such a position has no hours to price or to agree, and is sold through its other recording types instead. |
| Recording activity types | Which activity types may be recorded against this position, and whether each is billable. |
A position has no currency of its own. It is priced in its order's.
Instead of typing a rate, pick one under Rate from catalog. The picker lists the order's own rates under From this order and the central catalogue under From the catalog; an order with no rates of its own shows only the catalogue. Either prefills the rate and the unit, and a catalogue pick also links the position to that rate, which is what fills Rate code. Leave the field empty to price the position by hand. A position is linked to one catalogue rate, whatever it records: on a position that records no work time, such as a travelled distance only, picking a rate only links it and fills in nothing.
A catalogue rate has a price per currency, and the picker shows each rate with its price in the order's currency beneath its label, and its code beside it. A rate that has no price in that currency is offered too, marked “No EUR price” (naming the order's currency). Picking it links the rate but sets the rate to 0 and leaves the unit as it was, so enter the agreed price yourself. The order's own rates are offered the same way: with their price in the order's currency, or marked when they have none. Picking one of them links nothing.
Pricing the other recording types
A position is priced per recording type, not once. Time is priced by the Rate above; every other type the position records (travel time, a travel distance) gets its own row, and each is either:
- its own rate, or
- a share of another type's rate on this position, travel time at half the work-time rate, say. The share follows its source, so re-pricing the work automatically re-prices the travel.
When you add the position, a type that records time, such as travel time, starts from the rate picked above. A travelled distance always has its own rate, in its own unit such as per kilometre, and you type it in: catalogue rates price time only.
A type with no rate is still recordable; unless the servicesheet rules charge a flat amount for it, it contributes nothing to the amount. How the priced types reach a servicesheet is described under Recording types on a servicesheet.
A fixed-price position records the same types, and prices none of them. It is set up the same way, one row per recording type saying which activity types record it, but the rows carry no rate: the lump sum covers whatever is recorded against the position. The Fixed price is stated once, above the rows, because it is what the position costs rather than the price of any one recording type. Time is then an ordinary row there and can be removed like any other, so a position that only ever records travel is possible.



The positions grid then shows one row per position with its Name, Type, Rate from catalog, Rate code, Pricing, one column per priced recording type, allowed activity types, Work packages, Recorded and a Delivery bar. A recording type's rate column appears only while that type is active. For a time & material position with a sold quantity, Recorded shows the recorded time against that quantity in the position's unit, for example “176 / 160 h”, with a thin bar below; from 75% a warning icon appears, and pointing at the cell explains it (see Budget Warnings). Suggested entries and cancelled ones are not counted as recorded. What is on servicesheets and what is paid are read from the bar and its breakdown rather than from columns of their own. The bar's info icon opens the full breakdown, the same figures described under Where you see billing information. A position with no rate or no agreed quantity has no maximum to measure against. Its bar is drawn all the same: empty while nothing has been billed, and, as soon as anything is, wholly in the warning tone, because every cent of it is beyond a volume of nothing. A note beside it says no rate or quantity is set yet.
Prices once time has been recorded
As soon as any time is recorded on a position, directly or through a work package it is connected to and whatever the entry's status, the position's prices can no longer be changed. Changing them would rewrite the value of work that is already recorded and may already be billed.
The position's drawer then shows its prices as plain text, with the reason on hover: “The pricing can't be changed because time has already been recorded on this position.” This covers Type, Fixed price, Rate from catalog, Rate and Unit, and the price of every other recording type (Priced by, its rate, Factor and Of the rate for). Everything else stays editable, including Name, Sold quantity and the position's work packages. A position with no recorded time can be re-priced freely.
A catalogue rate that such a position is priced from is locked too, and more strictly: only its Active switch stays editable, and none of its prices can be added, changed or removed, in any currency. See Rates.
Connecting work packages
A position can be connected to one or more work packages in the project. Use Connect work package to link an existing one, or type a name and choose the create option to make a new one. When the order serves several projects, Create in project decides where it goes. Disconnect work package removes the link. A connected work package's name opens that work package in a new tab. In the work package's own drawer, each connected order position's name links back to the position the same way.
Connecting changes who may record time and where:
- A position without work packages is recorded against directly. Its Allowed activity types decide what may be recorded on it. Who may record is set on the Recordable activities tab of the project the time is recorded on, by its setting for order positions, which is separate from the project's own (see Teams and who can record). Time recorded directly on the order, without a project, follows the order's own setting instead (see Setting Up Time Recording on an Order).
- A position connected to work packages is recorded against those work packages instead, and the drawer explains “This position is connected to work packages, so its activity types are recorded against those work packages.” Who may record is set on the Recordable activities tab of the work package's project, by its setting for order positions linked to work packages: the members of the work package's team, only those of them with a confirmed booking on it, or everyone.
The full rule set is under Who may record against what.
Note: Time can also be recorded on a position directly on the order, without a project, which is how an order that is not linked to any project is recorded on. A position's Allowed activity types apply there too, whether or not it is connected to work packages. Who may record directly on the order is set on the order's Recordable activities tab, and the drawer says who that is. See Setting Up Time Recording on an Order.
The Rates tab
The order's Rates tab is the pool the positions are priced from. It is grouped by rate: a row with the rate's label and the number of its prices, and its prices beneath it, each with its Rate, Currency and Unit. A rate has one price per currency, whether it is per hour or per person day.
Add a rate with Create in the toolbar. New rate takes a Label and its prices, with Add price for each further currency. To copy a rate across from the framework agreement instead, pick one of its prices under Prefill from framework agreement in the same dialog: it fills in the label and that price. An empty tab offers the same thing as Add rate, under “No rates yet. Add one or prefill from the framework agreement.”
Change a rate in place: click a price's Rate, Currency or Unit to change it, or the label to rename the rate with all its prices. The + after the price count adds prices in further currencies, several at once, and the bin icons at the end of the rows delete a single price or a whole rate, after asking.
Prefilling copies. Editing the framework agreement afterwards does not change orders already prefilled from it, and editing an order rate does not change positions already priced from it.
On an imported order the tab is read-only: its rates can be used to price positions, but not added, changed or deleted.

Deleting
Deleting an order or a position asks for confirmation first. A position's question names the position. On a project's Accounting tab an order's question names the order and spells out what is at stake: it deletes “the whole order with all its positions on every project it is on”. Finance → Orders asks only “Are you sure you want to delete this entry?”, but deleting there has the same effect. Either way, an order that serves several projects is gone from all of them, not only from the one you started on. To take it off a single project and keep it, use Remove from project instead (see The project's Accounting tab).
Once there is history behind it, decídalo refuses: a position cannot be deleted once time has been recorded against it, and an order not once time has been recorded against one of its positions or anything has been billed against it. Delete is then disabled and says why, under Finance → Orders and on a project's Accounting tab alike: “Can't be deleted because time has already been recorded against it.” on a position, and “Can't be deleted because time has been recorded against one of its positions, or something has been billed against it.” on an order.
An imported order cannot be deleted at all (“This order was imported via an interface and can't be deleted.”), while its positions follow the same rule as on any other order. See Imported orders.