Open a purchase requisition, route it through automatic approval based on its amount band, convert it into an order, receive the goods, and three-way match the invoice against the order and the goods receipt. Open a tender/RFQ to external suppliers, collect their bids, compare them side by side, score them by weighted criteria and make the award. Your ERP keeps holding the order and the invoice; the portal writes the approved outcome back to it.
Your ERP (Logo/Mikro/SAP/Netsis) records the order and the invoice, but it leaves out three critical links: (1) the multi-step internal approval that routes a request based on its amount band, (2) the three-way match between order, goods receipt and invoice, plus the resolution of any discrepancies, and (3) a competitive tender/RFQ object opened to external suppliers — collecting bids, comparing them side by side, applying weighted scoring and reaching a decision. Building these inside the ERP is either impossible or tied to an expensive upper-tier package like SAP MM and heavy customisation. Most companies end up running the tender in Excel and the approval over email. The Intranet Portal delivers this flow out of the box, and writes the tender decision and the approved order back to the ERP as the single source of truth.
A department opens a purchase requisition (as a draft), enters the line items and submits it for approval. Once approved, the requisition converts into an order with a single click; the order is dispatched and closed off against a goods receipt (full or partial delivery). Every document runs through its own state machine: requisition draft → in approval → approved → converted to order, and order approved → sent → partially/fully received → invoiced → closed.
Requisitions and orders enter the approval engine based on their estimated/total value. Orders below a defined threshold (e.g. TRY 100,000) are approved directly, while those above it drop into a hierarchical approval chain. Approval steps are selected dynamically according to the document value, and every decision is written to the audit trail.
Incoming invoice lines are automatically matched against the order line and the goods receipt quantity. The system classifies each line: matched, quantity discrepancy, price discrepancy, no goods receipt, over-invoicing, or unmatched item. Quantity differences and percentage price variances are calculated, catching errors before payment.
Every unmatched line is raised as an exception: open, accepted or rejected. An authorised user makes the decision along with a note; who resolved it and when is recorded. An invoice cannot proceed to payment until its discrepancies are cleared.
Supplier e-invoices land in the inbox with their UUID, GİB status and full XML/JSON payload (new). An authorised user imports the invoice (imported) or ignores it. An imported e-invoice is linked directly to the system invoice and enters three-way matching, eliminating manual data entry.
A procurement specialist opens a tender (tender number, line items, estimated budget, start–end date, currency, visibility, documents). Invitations are sent to selected suppliers; once the tender is published, it opens for bid collection. Both public and invitation-only tenders can be configured.
Invited suppliers log into the portal and submit their bid: cover letter, delivery lead time, validity, payment terms, line-level pricing and supporting files. Suppliers can raise clarification questions on the tender specification, which procurement answers. A bid remains editable until it is submitted.
Incoming bids are gathered on a side-by-side comparison screen. Evaluators score each bid 0–100 per criterion; the decision screen calculates each bid's average score and ranks the bids first by score (highest to lowest) and, in a tie, by price (lowest to highest). Your decision emerges from a single table.
The winning bid is selected; the tender status becomes 'awarded', and the winning bid, the decision note, the person who made the decision and the date are recorded. A notification is sent to the winning supplier. The decision is auditable, and the approved outcome can be carried over to the order/ERP.
A department opens a purchase requisition (priority, need-by date, justification, line items). The estimated total is calculated automatically from the line items. The requisition is submitted for approval.
The requisition enters the approval engine based on its amount band, and the hierarchical chain runs. Once approved, the requisition becomes ready to convert into an order.
The requisition converts into an order for the supplier — or, where competition is required, a tender/RFQ is opened: invitation, bid collection, side-by-side comparison, weighted scoring and selection of the winner. The order too runs through its own approval based on its value.
The goods are received; a full or partial receipt is entered, and the delivery note number and the receiving person are recorded. The order moves to a 'partially/fully received' status.
The incoming e-invoice is matched against the order and the goods receipt, and discrepancies are resolved. The cleared, approved outcome (order, invoice match, tender decision) is written to the ERP as the single source of truth.
The ERP remains the single source of truth: the supplier account, stock, accounting and the final invoice record are held in the ERP. The portal runs the internal procurement flow (requisition, approval, tendering, goods receipt, three-way matching) on top; it reads from the ERP and writes back only the approved, cleared outcome.
Supplier e-invoices are pulled into the inbox with their UUID and GİB status, the full XML/JSON payload is stored, and an imported invoice is linked to the ERP invoice record so it can enter three-way matching.
Contracts held in the ERP (e.g. Oracle) are synchronised into the portal read-only (contracts:sync). The portal never writes to a contract; the procurement team uses the current contract data as a reference during approvals and price checks.
An order that has passed internal approval, a resolved invoice match and a tender decision are transferred to the ERP, eliminating duplicate records and the 'which one is correct' chaos.
Master data such as the supplier account, stock item and currency/exchange rate is fed from the ERP; the portal uses this data across requisition, order and bid line items.
Tell us your ERP and your process. We’ll show how this module works and scope it into your subscription — no man-day, licence or setup fee.
Book a Demo →