create_sales_invoice

Added value: +{
+  "description": "Name to print in this voucher's Buyer (Bill to) box, when it should differ from the customer ledger's own name — Tally's per-voucher Party Details mailing name. The ledger itself is not changed. Useful when many sales are posted against one shared ledger (e.g. cash or card sales) but each invoice needs its own readable buyer name.",
+  "type": "string"
+}

Added value: +{
+  "description": "Description lines shown under this stock line on the invoice, one array entry per line (e.g. a size, colour or service period). Optional.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Added value: +{
+  "description": "Voucher type to post as, for a company that uses its own Sales-class type in Item Invoice mode (e.g. 'Tax Invoice', 'Export Invoice'). Defaults to 'Sales'.",
+  "type": "string"
+}

Added value: +{
+  "description": "The buyer's country as it should appear on THIS invoice's Party Details (voucher-level COUNTRYOFRESIDENCE). Plain free text, e.g. 'UAE'.",
+  "type": "string"
+}

Added value: +{
+  "description": "The buyer's Emirate/state as it should appear on THIS invoice's Party Details (voucher-level STATENAME) — not inherited from the party ledger master. Match the company's existing convention (check get_company_info or an existing invoice).",
+  "type": "string"
+}

Added value: +{
+  "description": "The buyer's Tax Registration Number as it should appear on THIS invoice — a per-voucher snapshot (Tally's TRADERCONSVATTINNO/BASICBUYERSSALESTAXNO fields), separate from and not inherited from the party ledger's own trn (create_ledger). Reverse-engineered from a real Tax Invoice export: leaving this unset is exactly what leaves the invoice's Party Details showing a blank TRN even when the party ledger has one set — always pass this explicitly for a UAE VAT tax invoice.",
+  "type": "string"
+}

Added value: +{
+  "description": "Real batch/lot number for this line, if the item has batch tracking. Defaults to 'Primary Batch'.",
+  "type": "string"
+}

Added value: +{
+  "description": "Discount percentage applied to this line's amount (e.g. 10 for 10% off). Optional.",
+  "type": "number"
+}

Added value: +{
+  "description": "Per-item VAT ledger override, if this line has a different tax rate than the invoice default. Requires vatRatePercent.",
+  "type": "string"
+}

Added value: +{
+  "description": "Per-item VAT rate override, e.g. 5. Required if this item's vatLedger is set.",
+  "type": "number"
+}

Added value: +{
+  "description": "UAE VAT Place of Supply Country (Tally's PLACEOFSUPPLYCOUNTRY field), e.g. 'UAE'.",
+  "type": "string"
+}

Added value: +{
+  "description": "UAE VAT Place of Supply Emirate for this invoice (Tally's EMIRATEPOS field) — for a standard domestic B2B supply of services this is normally the SUPPLIER's own Emirate (check get_company_info), not the buyer's. Required for a compliant UAE tax invoice; omitting it is what left this blank on a real invoice this was reverse-engineered from.",
+  "type": "string"
+}

Added value: +{
+  "description": "Free-text reference for this invoice (Tally's voucher-level REFERENCE field), e.g. a purchase order or bill number the customer quoted.",
+  "type": "string"
+}

Added value: +{
+  "description": "Date for the reference above, in DD-MM-YYYY format. Independent of the invoice's own date.",
+  "type": "string"
+}

Previous value: -"VAT/tax ledger to apply against the invoice total (optional — omit for a non-taxable invoice)."New value: +"Default VAT/tax ledger applied to any item that doesn't set its own vatLedger (optional — omit for a fully non-taxable invoice)."

Previous value: -"VAT rate as a percentage, e.g. 5. Required if vatLedger is set."New value: +"Default VAT rate as a percentage, e.g. 5. Required if vatLedger is set. Items with mixed rates can override this per-line."

Added value: +{
+  "description": "Explicit voucher number. Normally omit this and let Tally auto-number — but some Tally configurations (confirmed live: after a Company Data → Rewrite in at least one case) stop auto-numbering item-invoice vouchers via the XML gateway and fail with a blank EXCEPTIONS:1/no error text unless a number is given explicitly. If a create call fails with no error text, check get_vouchers for the highest existing number of this voucher type and retry with voucherNumber set to the next one.",
+  "type": "string"
+}