Check invoice data
check_invoiceChecks invoice data against the Peppol / EN 16931 business rules without producing XML: returns ready=true, or the list of problems to fix. Same input as create_einvoice.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"number": "<number>",
"issueDate": "<issueDate>",
"seller": "<seller>",
"buyer": "<buyer>",
"lines": "<lines>"
},
"name": "check_invoice"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| bic | No | ||
| iban | No | ||
| note | No | ||
| buyer | Yes | ||
| lines | Yes | ||
| format | No | peppol | |
| number | Yes | ||
| seller | Yes | ||
| docType | No | invoice | |
| dueDate | No | Invoices only. Give dueDate or paymentTerms. | |
| currency | No | EUR | |
| issueDate | Yes | ||
| adjustments | No | Document-level discounts (allowance) and surcharges (charge), each with the VAT rate it applies to. | |
| deliveryDate | No | Date of supply of goods or services, if different from the issue date. | |
| paymentTerms | No | ||
| buyerReference | No | ||
| orderReference | No | ||
| exemptionReason | No | Required when a line uses category E. | |
| paymentReference | No | ||
| precedingInvoice | No | Credit notes: number of the invoice being corrected. | |
| precedingInvoiceDate | No |