brc_create_sales_entry
Create a BRC sales entry by first submitting a draft to receive a plain-English preview, then retrying with explicit user confirmation and confirmed counterparty before posting.
Instructions
Creates a BRC sales entry using structured MCP fields. First call without confirmWrite: true returns confirmation_required and a payload preview — show a plain-English draft in chat, then retry with confirmWrite: true only after explicit user confirmation in a later message. Passing preflight is not confirmation. Also requires confirmCounterpartyExplicit: true once the user has explicitly named or confirmed the customer/supplier in the current conversation. Do not reuse a counterparty from an earlier draft without that confirmation.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| note | Yes | ||
| acCode | Yes | ||
| procDate | Yes | ||
| entryDate | Yes | ||
| netAmount | Yes | ||
| vatRateId | Yes | ||
| customerId | Yes | ||
| accountCode | Yes | ||
| companyName | Yes | Company context name, for example YOUR-COMPANY-NAME. | |
| description | Yes | ||
| confirmWrite | No | Must be true only after a plain-English draft has been shown in the current conversation and the user explicitly confirmed posting (for example yes, create it / post it now / confirm). Never set true on the first call or because the user initially asked to create something. | |
| vatPercentage | Yes | ||
| bookTranTypeId | Yes | ||
| analysisCategoryId | Yes | ||
| confirmCounterpartyExplicit | No | Must be true only after the user explicitly named or confirmed the customer, supplier, or other counterparty in the current conversation. Never set true because a customer or supplier appeared in an earlier draft, was inferred from context, or was filled in without the user's explicit choice in this conversation. |