01An ONYX productProcurement and supplier management

From request to invoice, in one place

Tedaro runs purchase requests, price quotes, tenders, approvals, purchase orders and goods receipt in one system instead of email, Excel and paper. Every decision leaves a record.

  • 01Purchase requests
  • 02Sealed tenders
  • 03Approvals
  • 04Orders and receipt
Flow
Example datapending approval
02RFQ

RFQ-2026-0142

03Deadline

2026-11-04 12:00 UTC

ItemQuantityStatus
A4 paper, 500 sheets40waiting
Printer toner6waiting
Folder120waiting

Not a real company or price.

02

How it works today

Every decision gets lost in inboxes

The request arrives in one email, the quotes sit in other threads, the comparison lives in an Excel file, the approval is in a messenger or on paper, and the invoice is back in email. A year later, answering "why was this supplier chosen?" means searching several folders and mailboxes.

  1. 01Nobody can say who held the quotes before the deadline.
  2. 02Nobody knows how many versions of the comparison file exist.
  3. 03Proving who approved what, and when, is hard.
  4. 04Invoices are checked against orders and receipts by hand, by eye.
  5. 05The ERP holds only the final result; the tender and supplier side stay in email.

Tedaro brings these stages together and records every step.

03

Flow

Request to invoice: eight steps, one system

Each step starts from the result of the previous one. Data is not re-entered.

  1. 01

    Purchase request

    A user creates the request from a form or the catalog; cost centre and documents are attached.

  2. 02

    RFQ or tender

    Procurement picks the method: catalog call-off, quick RFQ or tender.

  3. 03

    Sealed bids

    In a tender, bids stay encrypted until the deadline.

  4. 04

    Comparison

    Quotes are compared line by line, side by side; in a tender the committee scores against criteria.

  5. 05

    Approval

    The award goes through the approval chain your company has defined.

  6. 06

    Purchase order

    The approved result produces a purchase order per supplier, sent to the supplier, who confirms it.

  7. 07

    Receipt

    Goods receipt (partial receipts are allowed) is recorded in the system.

  8. 08Coming soon

    Invoice matching

    The supplier's invoice is checked automatically against the order and the receipt.

At every step the system records who did what, and when.

04

Sealed tenders

Bids are not readable until the deadline

In a tender, each bid is encrypted before it is stored. The key that decrypts it is created when the tender is published and is not kept in the open; only a separate "opening" process can use it, and that process runs only after the deadline and the required confirmations. Procurement staff, administrators and the application itself cannot see prices before the deadline.

  • A separate key per tender. The key for one tender is useless for another.
  • Two-person confirmation. A tender is opened only after two different committee members confirm.
  • Deadline on the server clock. A bid submitted one second late is refused.
  • Emailed receipt. After each submission the supplier receives a receipt with a timestamp and a cryptographic fingerprint of the bid.
  • No price leaks. Before opening, prices do not appear in logs, notifications, errors, exports or webhooks.

Honest limit

Open RFQs and quotes entered by a buyer on behalf of a supplier carry no sealing guarantee; this is by design, and such quotes are flagged in the comparison grid.

Example data
  1. 01Published
  2. 02Bids accepted, encrypted
  3. 03Deadline
  4. 04Two confirmations
  5. 05Opening
  6. 06Comparison
Event number

TND-2026-0031

Revision

2

Time (UTC)

2026-11-04T09:58:41Z

Fingerprint (hash)

sha256:7c1e9a40…d2b04f

05

Comparison and approval

Make the choice defensible later

Quotes appear in one grid, line by line and side by side, with the lowest price highlighted. You can pick the winner per line and split an order between suppliers. If the lowest price is not chosen, or fewer quotes arrived than your company's minimum, a justification is required; it is stored with the result and in the audit log.

Example dataRFQ-2026-0142
ItemQuantitySupplier ASupplier BSupplier C
A4 paper, 500 sheets4011.8010.95awarded supplier11.40
Printer toner689.00awarded supplier94.5086.50
Folder1202.402.15awarded supplier2.60

0.00lowest price0.00entered by buyer on behalf of supplier

Justification

Printer toner awarded to Supplier A: Supplier C's quote was taken by phone and its delivery time is longer.

ProcurementFinanceDirectorapproved

Example data. Prices are invented.

  • 01Side-by-side comparison in an RFQ; in a tender, the committee's criteria scores as well.
  • 02A quote the buyer received by phone or email is entered with its document and a reason, and is flagged in the grid as "entered by buyer on behalf of supplier".
  • 03Approval rules are set by your company by amount, category and department; approval actions are written to an append-only record.
  • 04Approvers above a set threshold can be required to use a second factor (TOTP).
  • 05Approval thresholds, the minimum number of quotes and similar rules are settings your company configures, not fixed values.
06

Order, receipt, invoice

Invoices are checked against orders and receipts

The approved result produces a purchase order, which is sent to the supplier; the supplier accepts it, proposes changes or rejects it. When goods arrive, the receipt is recorded. The supplier enters the invoice in the portal against the order, and the system checks it line by line against the order and the receipt.

  • 01Quantity: the invoiced quantity cannot exceed what was received (the allowed difference is your setting).
  • 02Price: compared with the accepted price on the order, within the tolerance your company sets.
  • 03VAT and total: the VAT rate and the total are recalculated.
  • 04Duplicates: a repeated invoice for the same supplier, number and year is refused.

The result is one of three: matched, on hold (goods not yet received) or disputed. For a disputed invoice the supplier sends a credit note or a corrected invoice, or an accounts-payable user overrides with a written reason; that too stays in the log.

Honest limit

Tedaro does not make payments or keep the accounts. The invoice in the system is not the legal tax document; the e-qaimə in the state system is, and the system keeps only the reference to it.

Example dataPO-2026-0087
ItemOrderedReceivedInvoicedStatus
A4 paper, 500 sheets404040matched
Folder120120120disputed
Reason / Price 2.15 vs 2.35 AZN

Price is above the accepted price on the order.

07

Supplier portal

Suppliers quote from their phone, no password

A supplier enters by invitation only. A one-time sign-in link arrives by email (valid for a limited time), then the supplier enters a 6-digit code sent by email. The portal works comfortably on a phone: submit a quote, confirm an order, send a delivery notice and an invoice. Delivery notice and invoice: Coming soon. A supplier needs no registration or password to take part. One email address sees invitations and orders from every buyer company that has invited it.

  • 01No open registration and no marketplace; only the suppliers you invite can sign in.
  • 02Each supplier contact has roles: sales (quotes), orders, invoicing. A contact without the invoicing role does not see invoices.
  • 03Uploaded files are checked against an allowed-format list and size limits.
  • 04A supplier sees only its own orders and invoices.

Honest limit

Email is the supplier's only factor; if a mailbox is compromised, the supplier account is at risk. Matching against the order and receipt (coming soon) limits the damage.

Supplier portal01
  1. 01Invitation email
  2. 02One-time link
  3. 036-digit code

Code

RFQ-2026-0142waiting
Example data
08

Working with your ERP

Adopt it without changing your ERP

You do not change your ERP. Tedaro connects to it. Tedaro works in two modes. Same screens, different split of responsibility.

A

Without an ERP (standalone).

Requests, approvals, budgets, orders, goods receipts and invoices run in Tedaro. The full procurement cycle works without waiting for an ERP.

B

With an ERP (integrated).

Requests, orders and budgets stay in the ERP. Tedaro runs the tender and RFQ, the supplier side, sending and confirming orders, delivery notices and invoice matching, and returns the results to the ERP. The last two: Coming soon.

Who owns what (integrated mode)
AreaERPTedaro
Purchase request and its approval, budgetERP-
RFQ, tender, comparison, award proposal-Tedaro
Order content and approvalERPRead from the ERP
Sending the order to the supplier and its confirmation-Tedaro
Goods receipt, returnsERPRead from the ERP
Invoice intake and matching-Tedaro (only the status goes to the ERP)Coming soon
Payment, accountingYour systemsNot handled
  • 01REST API and API keys; events are delivered by signed webhooks.
  • 02The supplier list is synchronised with the ERP by a key (external reference).
  • 03Tedaro posts nothing from invoices to the ERP's ledger.
  • 04The mode is set per company account and changed only by platform operations.

Honest limit

In integrated mode Tedaro relies on the ERP's request and order approvals and goods receipt postings; it cannot verify them.

We will show how it fits your ERP in the demo

09

Security and audit

Security: what is protected, and where the limits are

This section is for the person responsible for IT. Each item follows from how the system is built.

01

Isolation

  • Each company is a separate account. Row-level security in the database prevents one company's data from being visible to another; isolation tests exist for every endpoint.
  • A supplier never names a company in a request; access is decided by invitation and role.
  • A company administrator has administration rights only; without another role they see no procurement data.
02

Encryption

  • Sealed bids are encrypted as described above (a key per tender, a separate opening process).
  • The decryption code exists only in the opening process; the API and portal processes do not contain it, and an automated test enforces this.
  • Two-factor sign-in (TOTP) is mandatory for administrators, committee members and accounts-payable users.
03

Audit log

  • Tender events are written as a hash chain: each record carries the fingerprint of the previous one, and no update or delete is permitted. The chain can be verified for integrity.
  • Approval actions, budget entries and order changes are append-only records.
  • An invoice-match override cannot be made without a written reason and is logged.
04

Portal hardening

  • Separate host and cookie, strict content policy, rate limits on links, codes and uploads.
Example data
API / Portal

API and portal: encrypt only

Opening process

Opening process: the only one that decrypts

Audit log (example rows)

#RoleActionhash
118Supplierbid.submitted7c1e…b04f
119Systemevent.closeda93d…11c7
120Committee memberopening.confirmed (1/2)52f0…9e3a
121Committee memberopening.confirmed (2/2)e6b8…0d45

Tamper-evident, not tamper-proof

The audit chain makes changes detectable. It does not make them impossible.

Honest limits

Deadlines use the server clock; the emailed receipt is the evidence.

Honest limits

Tedaro does not provide a qualified electronic signature (ASAN İmza). It suits private procurement, not state tenders.

Bring your IT specialist to the demo for security questions

10

FAQ

01Does Tedaro replace our ERP?

No. In integrated mode, requests, orders and budgets stay in the ERP; Tedaro runs the tender, the supplier side and invoice matching, and returns the results to the ERP. If you have no ERP, Tedaro runs this cycle itself. We go through fit with your specific ERP together in the demo.

02How do suppliers join?

You send the invitation. There is no password and no registration: an email link and a 6-digit code.

03Can a sealed bid really not be read?

In a tender, bids stay encrypted until the deadline, and only a separate opening process can decrypt them, after two committee members confirm.

04Is it suitable for state procurement?

No. Tedaro does not provide a qualified electronic signature (ASAN İmza). It is for the internal procurement of private companies, holdings and organisations that run tenders.

05Does it handle payments and accounting?

No. Payments, ledger postings and the legal tax-document role of the invoice are outside Tedaro. The system shows invoice status (for example matched, disputed) and keeps the e-qaimə reference.

06Which languages does it support?

Azerbaijani and English; each user chooses. The base currency is the manat; there are fields for VÖEN and the e-qaimə reference.

07How do we set up our own approval rules and limits?

Approval rules are built by amount, category and department, with conditional steps and delegation. Values such as the minimum number of quotes, the tender threshold and matching tolerances are your company's settings. In the demo we configure them to your process.

11

An ONYX product

Let us show you your process in a demo

In the demo we walk through your procurement process, from request to invoice, with example data, and show how it works with your ERP. Your IT specialist is welcome to join.

Your details are used only to contact you about the demo.