Tracking Contract Prices, Delivery Notes and Acts After a Tender
Contract prices and facts in BEEMESTA track what happens after a tender. The winner fills in the contract price, and you record delivery notes, acts and invoices as procurement facts. Each fact puts the contracted figures next to the actual ones and shows the deviation per line. Contract fulfillment shows how much has already been delivered and how much is still to come.
What is a contract price, and who fills it in
A contract price is a document with the winner’s final prices and terms after the award. The buyer requests contract prices, and each winner gets an email with a link to the form. The form already holds quantities from the tender specification and prices from the winner’s offer. The supplier reviews and adjusts it, and every change to a quantity or price needs a reason. Until the buyer accepts an added line, it isn’t included in the total.
The buyer compares the submitted contract price with the supplier’s offer line by line. Then the buyer accepts it or returns it for rework with a reason. Acceptance locks the document for both parties.
Procurement facts: delivery notes, acts and invoices
A procurement fact is one document — a delivery note, act or invoice — recording what was actually bought and delivered. BEEMESTA groups facts by status — drafts, posted and cancelled — with filters by supplier, tender specification, period and document type. Create a new fact on one of three bases:
Enter the document type, number and date upfront. BEEMESTA won’t accept the same number from the same supplier twice. One contract price can have many delivery notes.
- From a contract price — lines and prices from an accepted contract price.
- From a tender specification without a contract price — lines from the tender specification, prices entered manually.
- Outside procurement — just the supplier and the document.
Contracted vs. actual: the deviation on every line
A fact puts the contracted quantity and price next to the actual ones. The contracted values come from the contract price when the fact is created; the actual ones come from the document. The deviation is visible on every line. BEEMESTA highlights a quantity above the contracted one and shows a price deviation over 0.5% as a percentage. This is a warning, not a block — the fact is still saved.
You add anything that wasn’t in the contract price as a separate line outside the contract. It carries its own mark, and BEEMESTA counts it in a separate subtotal. A fact without a contract price has nothing to compare against, so its contracted values are empty.
Posting a fact and contract fulfillment
Posting locks the document: a posted fact is read-only and counts toward contract fulfillment. You can post a draft that has at least one line. Correct mistakes not by editing but by cancelling the fact with a reason. The document stays among the cancelled ones as a record, and its amount leaves the totals.
For an accepted contract price, contract fulfillment answers how much is still to be delivered. It shows contracted, delivered and remaining quantities — per line and in total, with the documents behind each figure. BEEMESTA counts only posted facts, and lines outside the contract don’t count toward the delivered amount or the remainder.
Deliveries sent by the supplier
A supplier can send a delivery against its own accepted contract price. The supplier picks the accepted contract price and enters the document type, number and date. BEEMESTA fills in the lines from the contract price; the supplier corrects shipped quantities to match the delivery note.
Sending locks the document, and the buyer gets an email. On the buyer’s side, the delivery appears among the procurement fact drafts, marked as coming from the supplier. Only the buyer can post it, after checking the quantities against the delivery note. The supplier can delete an unsent draft — the buyer never saw it.