Extract the tenderer, buyer, RFQ reference, priced bid line items, totals, delivery terms, and qualifications from a bid or tender submission PDF.
The full guide: Bid submission: RFQ reference and UBL 2.1 fields
Need to scale? Create an API key, then run this from your own code or an agent.
Create an API keyFree account required
Upload a file or pick a sample, and see the fields come back.
No signup · nothing stored
The submission number and date, the tenderer (bidding company) name, address, and contact person with email and phone, the buyer (issuing organization) name and address, the referenced request-for-quotation or tender number, and the customer reference and accounting cost centre the buyer assigned.
Yes. The bid items table returns one row per item with its line number, item code, description, quantity, unit price, line amount, line tax amount, line delivery date, and a partial-delivery indicator, so a multi-line offer comes back priced line by line.
The total amount (payable), the line-extension total (net of tax), and the tax amount come back as fields, alongside the payment terms, the payment means code, and the currency, so the priced offer reconciles against its line rows.
The proposed delivery date, delivery terms and Incoterm location, delivery address, destination country, and the bid validity end date are read, and a qualifications table returns each certification name, code, issue date, and expiry date, alongside the claimed years of experience.
PDF only, up to 10MB and 100 pages. The submission is processed via the Talonic API for extraction, is not retained for training, and is not shared.
The tool reads a single document. The platform reads the whole estate once and keeps it queryable — the same engine, with a memory.
See PDF to Markdown if you run this for data and platform teams, or the extraction API if you are building it in.