Skip to main content

Commitments and installments

Committed in the budget​

As soon as a firm order is allocated to an envelope, a Committed scenario appears under the Cost family of that envelope — next to Budget, Forecast, Planned and Actual. It reads wherever scenarios read:

  • in a project's budget tree;
  • in the budget summaries of the project and the portfolio, as a column;
  • in the Analysis tabs, as a pivot dimension.

The commitment is spread over time: on an order with a schedule, it follows the weight of each installment; otherwise it is carried by the order's start date.

The amount used is the order's committed amount, or failing that the sum of its schedule — a down payment entered without a global amount is still a commitment.

Unfolding the Committed​

A commitment total does not say where it comes from. In the project's budget tree, the Committed row unfolds over two levels:

Committed 15,000 €
├── Hardware order 10,000 €
│ ├── Down payment 3,000 €
│ └── Balance 7,000 €
└── Licence order 5,000 €
  • the first level gives one row per order allocated to the envelope;
  • the second gives one row per installment of that order, each placed on the period where it falls.

An order without a schedule, or with a single installment, stays a single row: a grandchild identical to its parent would teach you nothing.

An installment is shown under its label when it carries one ("Down payment", "Balance"), otherwise under its rank. Its date is read from the column where its amount lands.

The total and its detail come from the same calculation

The child rows are not a second source: they are the breakdown of which the total is the sum. They cannot diverge from it.

This unfolding exists in the project's budget tree. Summaries and Analysis tabs keep the commitment as a single aggregated value — a total flanked by its own detail would be counted twice there.

Orders also feed the Planned and the Actuals​

An order only weighed on the Committed, whereas an expense entered by hand on a project weighs on the Planned and the Actuals. The same expense therefore did not read in the same place depending on how it had been recorded.

The setting “An expense weighs in the same place, however it was entered” (Settings → Budget) closes the gap, using the status the schedule already carries:

InstallmentVersion fedAt which date
OrderedPlannedits expected due date
Received, invoiced or paidActualsits reception date

It is the service being done that dates the cost, not the contractual date: an installment due in March and received in April weighs on April.

An order without a schedule stays entirely in the Planned — nothing there records the service as done. That is a good reason to fill in the schedule: without it the expense will never reach the Actuals.

Time and materials is excluded

The days of a time and materials order's consultants already flow up through resource planning (Planned) and timesheets (Actuals). Counting them here would double the expense.

The gap becomes readable: Committed = Planned(orders) + Actuals(orders). Versions are never summed with each other, which is already true of the Budget and the Actuals.

The setting also works the other way round: an expense entered on a project feeds the Committed as soon as its status declares it committing.

The Forecast can include the Committed​

By default, the Forecast and the Committed are two independent readings: the re-forecast on one side, the contractual on the other.

The workspace can ask the Forecast to include commitments — see Settings → Budget. The setting is off by default: it changes the value of an existing indicator, so it is only ever switched on deliberately.

When it is on, two safeguards prevent double counting:

  • only commitments after the budget cut-off date are added — before the cut-off, the expense is already in the Actuals;
  • time and materials orders are excluded — their consumption already flows up through resource planning, which feeds the Planned.
Can't see your commitment in the budget?

The order panel tells you, right where the problem is fixed. Four possible causes, listed under the committed amount:

  • the order is still a price request;
  • it is cancelled;
  • it has neither a committed amount nor a priced installment;
  • it has no allocation to a budget envelope.

A framework agreement carries nothing down either, by construction: its totals are the sum of its orders.

No effect without the Suppliers module

The scenario is produced only for envelopes that carry a commitment. A workspace that does not use the module sees exactly the same screens as before.

Committed exists on the Cost side only: neither revenue nor margin has one, and margin remains the difference between revenue and cost.

Left to commit

The project and portfolio budget summaries carry a Left to commit column: the envelope's Budget minus its Committed. That is your room for manoeuvre before having to arbitrate — negative, it flags an envelope that is already over-committed.

An order's consumption​

Consumption is not read in the same place depending on the commitment type.

TypeSource of the consumption
Fixed price, SubscriptionInstallments received, invoiced or paid
Time and materials, Capped contractThe days of the consultants linked to the order, valued by the rate grid
One-off purchaseIts single installment, once received, invoiced or paid

The goods receipt records the consumption​

It is the receipt date — the service being done — that brings an installment into the consumption, regardless of when the invoice arrives. An order may be committed long before it is received, and invoiced well after.

Time and materials requires linking the consultants​

On a time-and-materials order, the Supplier consultants section names the people working under that order. Without them, the days booked on the projects do not say which supplier they come from.

Each consultant appears on one line with their profile and the rate that will apply to them:

ColumnContent
ResourceThe person linked to the order
ProfileThe one on their record (Description tab) — it is what ties them to the purchase rate grid
Purchase daily rateEmpty, the rate of their profile applies (shown as a hint); entered, it overrides the grid for them alone

Grid lines are chosen from the workspace profile catalog (Settings → Workspace → Resource description tab), the same one used by the envelope profile rates and the client contract grid. A line entered before the catalog keeps its former label, flagged under the line: it still applies as long as that label matches the name of the resource's profile, in any language. Choosing the profile from the list replaces the label.

This override covers the special case — a rare profile, an individually negotiated rate — without forcing you to retype the same amount for ten consultants of the same profile. A consultant whose profile has no line in the grid is flagged right there, before they have booked any time.

The Consumption table then aggregates their days by profile and values them with the matching purchase daily rate, over a period you set. A profile missing from the grid is flagged: its days appear, but are not valued.

The scope is that of the allocation, down to the envelope: only days booked on a project / envelope pair the order commits are counted. A resource assigned to a task and to a committed envelope therefore feeds the order's consumption directly.

Days out of scope

A consultant of the order may book time on another envelope of the same project. Those days consume the envelope they are booked on, not the committed one: they do not count in the order's consumption. They are nonetheless displayed apart, under the table — otherwise time the supplier will invoice would stay invisible. The signal usually points to an allocation to complete or an imputation to fix.

"Not computable" is not "zero"

A time-and-materials order with no linked consultant shows Not computable, never 0: its consumption is unknown, not nil. A framework agreement with a single order in that situation signals that its total is partial.

Two differences with a client contract's consumption are worth knowing:

  • days are not weighted by the allocation percentage, which splits the committed amount and says nothing about the time spent;
  • actuals marked non-billable still count. That type means the day is not re-invoiced to your client, not that the supplier does not charge you for it.

The purchase rate also values the plan​

The purchase rate does not only serve consumption: as soon as a time-and-materials order commits an envelope, the planned figures of that envelope are valued at the contracted rate for the order's consultants — no longer at the workspace default rate.

That is what makes a planned budget reflect what you will actually pay, rather than an internal estimate the invoice will contradict.

A person's rate on an envelope resolves from the most binding to the most general:

RankSourceWhen it applies
1Supplier contractThe person is a consultant of a time-and-materials order committing this envelope
2Envelope rateA rate was explicitly entered for them on this envelope
3Workspace defaultNeither of the above
Cost only

A purchase rate has no meaning on the revenue side: revenue valuation stays that of the client contract. An envelope no order commits behaves exactly as before.

The Installments screen​

Suppliers → Installments gathers every slice of the active supplier's orders.

ColumnContent
OrderThe carrying order
LabelEntered, or derived from the period for a generated installment
Milestone and Milestone dateThe linked plan milestone, whatever the billing type
StatusOrdered → Received → Invoiced → Paid
Due dateThe expected date — in red if it has passed without a receipt
ReceivedThe date the service was done
Expected paymentSee below
Invoice no., AmountThe reference of the invoice received and the slice amount

The screen filters, sorts, exports and accepts favourites, like the other grids.

Importing an invoice​

The Import an invoice button (Installments screen, and Invoices section of an order's panel) reads an uploaded invoice and matches it:

  • to the supplier, by VAT number then by name;
  • to the order, by the reference quoted on the invoice, otherwise the supplier's only open order;
  • to the installment with the same amount (within 1%), otherwise the first non-invoiced one.

You confirm or correct each match. On saving, the invoice joins the order's Invoices register, the installment moves to Invoiced (or Paid if the invoice already is) with its invoice number, and the document is filed in the supplier's documents. A time-and-materials order has no schedule: the invoice goes to the order's register, which feeds its invoiced and paid amounts.

The cash-out forecast​

The Expected payment column answers a question neither the plan nor the accounting handles: when does the money go out?

It adds the payment terms to a starting date:

  • the order's terms apply first; failing that, those of its framework agreement, then the supplier's;
  • at each level, terms picked from the workspace list (the same one client contracts use) count for the first number in their label — "45 days end of month" counts as 45;
  • the countdown starts from the receipt as soon as it is recorded, otherwise from the expected due date — it is the service being done that triggers invoicing.

Without payment terms, the column stays empty: FoxPlan would rather announce nothing than announce a wrong date.

Always recomputed

The payment date is never stored. Change the payment terms of the supplier or of the order, and every forecast follows.