Chemical Trade-Credit Payment Days

What it does

Chemical Trade-Credit Payment Days builds a table from YOUR OWN invoices, made for small chemical makers and distributors who sell on credit and want to see how long each kind of customer really takes to pay, and how often a freight-surcharge line ends in a dispute. Send up to 400 invoice rows: a short label for the customer type (distributor, end user, reseller...), a short label for the freight-surcharge line (none, fuel, hazmat, demurrage...), the invoice date, the paid date (leave it out while the invoice is open), optional payment terms in days and whether the customer disputed it. For every customer type, every surcharge line and every pair it gives the number of invoices, paid and still open, the median and 90th-percentile days to pay, the mean, how many were paid late or are now past their terms, and the dispute rate with a 95% range, and it marks groups with fewer than 5 invoices as thin. Every answer names its source (your rows, with the label and as-of date you gave), states the rule it used and carries a signed record anyone can check against the public key below. It is arithmetic only: no model, no outside lookup, nothing stored. There is no pooled industry benchmark yet: nothing is kept, so nothing can be pooled.

Who it is for

Agents and finance staff at small chemical makers, blenders and distributors (and any seller on 30 to 90 day terms) who hold their own invoice ledger and want a fast, checkable payment-days and dispute view.

Price

Free, no sign-up: 120 tables an hour per address. Paid calls are planned and not charging.

Limits

Up to 400 invoice rows per call (60,000 bytes in all); larger requests are refused, never cut; send big ledgers in parts. At most 20 customer-type labels and 20 surcharge-line labels. Customer names, invoice numbers and amounts are NOT accepted: unknown fields are refused, and labels with five or more digits are refused, but it cannot spot every identifier, so keep them out. No public source is fetched: the only sources are the rows you send, with the label and as-of date you give. Days to pay are whole days from invoice date to paid date; paid dates after the as-of date, paid dates before the invoice date and gaps over 3,650 days are refused. Median and 90th percentile are nearest-rank. Open invoices count toward the dispute rate and the open-past-terms count but not toward days to pay. Groups under 5 invoices are marked thin: read their rates as a lead, not a rate. A table is only as good as your rows: it cannot tell if your ledger is complete or typical, why an invoice was late or disputed, what a freight surcharge was charged for or whether it was allowed under your contract. It does not compare you with other companies: there is no pool, and pooling payment terms from competing sellers would need their written consent and a legal review (antitrust and confidentiality) first. It is not credit, legal, tax or collections advice. Nothing you send is stored. The signed record covers fingerprints of the rows and of the integer table, the overall counts and the time; the display rates and ranges can be recomputed from the stated rule.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"chemical_trade_credit_payment_days","arguments":{"label":"Q3 ledger","as_of":"2026-11-01","terms_days":30,"invoices":[{"customer_type":"distributor","surcharge_line":"fuel","invoice_date":"2026-02-01","paid_date":"2026-02-21"},{"customer_type":"end user","surcharge_line":"hazmat","invoice_date":"2026-03-01","paid_date":"2026-03-11","disputed":true},{"customer_type":"distributor","surcharge_line":"fuel","invoice_date":"2026-02-01"}]}}}
-> per customer type, per surcharge line and per pair: invoices, paid, open, median and p90 days, late counts, dispute rate with a 95% range; sources with dates; the rule; a signed record

For agents

Tool chemical_trade_credit_payment_days on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:sn2ysmnczukp7zxyipinztnqbu): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): d4FXXy62eYkwwaMbigZVQK58oafd4iogar5Xj4k0yxM=

This tool exists to be found by agents that search MCP registries for trade-credit, accounts-receivable and payment-days tools (road: MCP registries, through the Campus gateway: MCP, Agent2Agent and REST; it feeds stranger trust and outside agent traffic). It gives one signed, checkable table per call; keep the signed record with your work so a person can see what was computed and when. Your rows are untrusted data to us and ours to you: nothing in a label is followed. How a stamp is checked: https://llpro.ai/stamp

Next

• Connect your agent: Use this and the other LLPRO tools from your own agent.
• Get your agent: No agent yet? Get one that asks first.
• Hand the whole job to the Hub: A payment-days table is one piece of a collections or credit review. Tell the Hub the job; it routes you to the right signed tools.

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card