Settle announced its public API and Model Context Protocol server on October 29, 2026, connecting its platform with business software and AI assistants. The current product page labels the offering Beta and makes an important limit explicit: the API and MCP tools are read-only today. Write access is planned for future releases.
Settle’s October 29 API and MCP announcement
Settle’s page describes access to purchasing, bill-pay and working-capital data. Businesses need API access; tokens inherit their creator’s role, and connections can be scoped and revoked. Data sent to an AI provider is handled under that provider’s terms. These are documented product boundaries, not results from an independent security or account-access test.
Settle’s current product page, access requirements and read-only FAQ
Choose one question for the first trial
Start with a narrow question that has an answer your finance team can reproduce, such as the unpaid balance of one selected supplier bill at a stated cutoff. Agree on the bill, currency, cutoff and treatment of pending payments before asking an assistant. This preparation helps reviewers identify whether a difference comes from the source records or from the way the question was understood.
Use a fictional purchase-to-payment example
For a teaching exercise, imagine a purchase order for $1,000, a related supplier bill for $600 and a completed payment of $200 allocated to that bill. Assume there are no taxes, fees, credits, other bills or other payments. Define the exercise’s unpaid billed balance as the bill amount less the completed payment allocated to it. The expected answer is $400.
Keep the purchase order, bill and payment as linked records. The order describes the purchase in this exercise; the bill and allocated payment supply the inputs to its narrowly defined unpaid billed balance. Adding $1,000, $600 and $200 would produce $1,800, but it would not answer that question. The remaining $400 of the order that has not been billed is a separate planning item in this invented example.
These figures and definitions are fictional. They are not Settle account data, API field names or an accounting policy. Ask your data owner how the records in your real account link together, including partial invoices, pending payments and credits. Do not assume the example covers those cases.
Ask for the evidence behind the answer
For the trial, request the selected bill reference, bill amount, completed payment allocation, cutoff and calculation alongside the result. Compare those items with the records your reviewer can inspect. If an item is missing or inaccessible, record that limitation rather than filling the gap with a plausible value.
Next, change the fictional payment to $250 in your training worksheet. The expected unpaid billed balance becomes $350. This is a worksheet exercise; it does not instruct an assistant to edit a Settle payment. Use the changed example to see whether the reviewer understands which input controls the result.
Keep the trial outcome specific
Save the question, the returned references, your independent calculation and any unresolved difference. A useful outcome is a reproducible answer for the selected records, with clear limits on what was checked. It is not evidence that every supplier report or cash forecast will be correct.
Before connecting a real account, confirm the access offered to your business and which data the intended connection can read. Keep any payment execution in the existing authorized payment process: the current API and MCP tools do not provide write actions. Recheck the product documentation when planning a later phase, since a roadmap statement does not establish that a feature has shipped.
Check the payables trial
