Plumbline: OFAC SDN sanctions screening, SEC financials and company checks from public registries

Place an order on terms you have inspected and the buyer has authorized you to accept. Requires the exact terms hash and explicit acceptance. Follow inspect_offer later for payment links and verified payment state.

Accept or decline a remedy the business proposed on a placed order (inspect_offer thread.fulfilment.remedies with state PROPOSED). Recorded for the business, which applies it and shows the result there. Accepting a credit or refund here moves no money; the business records it when its payment processor does.

Reported values of one XBRL concept for one SEC filer, by CIK or ticker, from its SEC filings (EDGAR): each value with its period, fiscal year, form, filing date and accession number, the latest 40.

Propose a change to an issued offer on its inspected terms: other quantities (by item index in terms.items), another list of companies (where the items price companies), a delivery date, a total price for the whole, a payment plan, or a note. It is a proposal, not a change: the terms stand and can still be accepted as they are. The business answers it in inspect_offer thread.counteroffers, with a revised offer to inspect and accept, or a reason. A later proposal replaces an earlier one still awaiting an answer. Nothing here orders or pays.

Decline an issued offer on its inspected terms.

Everything about one Plumbline service, by the slug list_propositions gives: what happens to a request, what you receive, scope and limits, the request fields with examples, and the lookups it runs.

Set fields by name ({"op":"set","values":{...}}, an empty value clears) or change the list ({"op":"add"|"update"|"remove"|"replace", ...}), exactly as given: no reading. Use it to answer the open question when the answer is a value.

US federal contract actions (awards and modifications) by vendor name, NAICS code, place-of-performance state and fiscal year, ten at a time, from FPDS, the government's contract reporting system.

Read a Plumbline order draft as it stands: its fields and companies (with their keys), what it still needs before it can be sent, the indicative price, what changed since it was sent, the firm offer with its terms hash, the order, payment and report state, recent changes by the buyer in the app or by you, and what can happen next. Read it before acting on what the buyer says about the order: they may have changed it in the app.

A Plumbline requirement as it stands: each value with where it came from, what it replaced, the open question, words not yet read, whether it was sent and any offer on it.

Which legal entities a company name may mean: GLEIF LEI records that match it (legal name, country, city, status) and, for a company listed in the US, its SEC filer CIK. For choosing the exact entity to verify before ordering; these are candidates, not findings. Free.

Record the buyer's inspection of a placed order: for each item (its index in terms.items) the quantity accepted and the quantity rejected, with a reason for a rejection, optionally for one portion of the order. Whether it was accepted is computed: only when nothing is rejected. Recorded for the business, which answers a rejection in inspect_offer thread.fulfilment, with a proposed remedy. Nothing here pays or refunds.

Read the exact authorized terms, terms hash, order state and processor payment links, and the thread the business published on the offer: its answers to counteroffers (thread.counteroffers), the purchasing requirements, vendor status and purchase order matches it holds (thread.purchasing), and the portions, shortfall and remedies of delivery (thread.fulfilment). Use the offer link credentials, or credentials of the request explicitly linked to this offer.

Give Plumbline the buyer's requirement, or a correction or addition to it, in their own words: it is read into a structured requirement (each value says which words it came from), conflicting or unclear facts come back as one question, and words not yet read are kept as written. Pass the requirement (id, token) from the first answer to continue it. Nothing is sent or ordered: send_requirement sends it when the buyer says so. When you already have the fields in structured form, use submit_request instead.

List Plumbline's services (Reported financial figures for US public companies; Legal entity verification by name, LEI or CIK; US federal contract awards by recipient, industry or place; Screen a name against the OFAC SDN list): each one's slug, a one-line summary, and whether it runs instantly as a lookup or takes a requirement you send.

Confirm a payment condition only where the inspected order allows the customer to release it. This records approval; it does not pay the processor.

Report the seller's vendor standing with the buyer's organization (APPROVED, DOCUMENTS_REQUESTED or REJECTED) with the buyer's approval or case reference and any documents requested. Recorded as the buyer's own statement; the business answers it in inspect_offer thread.purchasing.

Resume a requirement using the receipt credentials. Read the recorded requirement, any replies the business has published on it (messages: where it answers a buyer with no email, it answers here) and any linked offers. Answer a reply by sending a continuation. Contact details are kept apart.

Retrieve what a paid order delivers, where the business produces it itself (a report): the exact text, its SHA-256, version, sources and any shortfall. Before payment is confirmed it says it is not yet available. Use the offer link or linked request credentials.

Screen a person or company name against the US Treasury OFAC SDN list and its aliases (US OFAC SDN only: not the EU, UK or UN lists). Returns each match with its score, SDN entry number, type and programs, and the date the list was published. A match is a lead for review, not a determination.

Send a Plumbline order draft once the buyer has said to: the first send records the request (the firm offer with its exact price and terms hash is emailed to the buyer and appears in the app when ready; promise no time); a later send of a changed list records a revision of the same request and declines the offer for the earlier list as replaced. Name the revision the buyer saw: a draft that changed since is not sent. Needs the buyer's email on the first send (where the offer and receipt go). This places no order: the buyer accepts the firm offer separately.

Send the requirement to Plumbline once the buyer says to: the first send records the request (its receipt token is the requirement's token, for request_status and offers); a later send of a changed requirement records a revision of the same request. Name the revision the buyer saw. This orders nothing: an offer comes later and is accepted separately on its exact terms.

Tell the business how the buyer's purchasing works for this offer: whether the seller must be an approved vendor, whether a purchase order is required, which documents are needed, the seller's vendor id with the buyer, where orders and invoices go, and the payment terms. Recorded as the buyer's statement; the business answers it in inspect_offer thread.purchasing. Nothing here orders or pays.

Send the buyer's purchase order for an issued offer or a placed order: number, revision, lines, total, currency and payment terms. It is matched against the accepted terms; differences are recorded and shown in inspect_offer thread.purchasing as exceptions, never silently accepted. A changed purchase order is the same number with a higher revision. This does not accept the offer and pays nothing.

Send a requirement to Plumbline (Reported financial figures for US public companies; Legal entity verification by name, LEI or CIK; US federal contract awards by recipient, industry or place; Screen a name against the OFAC SDN list). It is recorded and answered with a receipt: keep its id and token to read the request's status (request_status), to add details later (continuation), and to act on an offer made in reply. A requirement is not an order and costs nothing; nothing is bought until an offer's exact terms are accepted.

Change a Plumbline order draft the way the buyer asked: add, update, remove or replace companies (name an item by its key from the draft, or by match on its name), or clear the list (item fields: name (the company's name as the buyer has it, or its exact legal name); country (ISO 3166 two-letter code; narrows the LEI search by name); lei (20-character Legal Entity Identifier; the report then reads that exact record); cik (SEC Central Index Key; adds the SEC EDGAR registration (EDGAR is not searched by name))). The app in the conversation shows the change at once. A placed order is never changed (the draft is locked); a change after the request was sent is a revision the buyer sends again with send_order_draft. Repeat a call with the same op_id and it is applied once.

Open Plumbline's supplier verification workspace in the conversation, with the companies the buyer named. It starts an order draft the buyer and you work on together: they can add, correct and identify companies in the app, and you change the same draft with update_order_draft when they ask in words ("add Microsoft", "replace Apple with Nvidia"); both of you see the same list and price. The report screens each company against the US Treasury OFAC SDN list, reads its GLEIF LEI record and, where a CIK is given, its SEC EDGAR registration; every finding names its source and time, and the report is hashed. Price: $5.00 for one company, $1.00 for each further one, up to 25; the firm offer states the binding price. Call identify_company when the buyer names a company loosely, so they can choose the exact legal entity. Nothing is ordered until the buyer sends the request and then accepts the firm offer. Call this once per order; afterwards use get_order_draft and update_order_draft with the draft's id and token (or pass draft to show it again, or order_link to continue an order from an emailed link). Without an app-capable host, use submit_request on entity-verification.