Patch AP settings
Partially update the Client’s accounts-payable matching settings — rounding tolerance, fuzzy line/supplier thresholds, the supplier name/address weighting, the date-proximity window, the header-affinity weights (reference/currency/date + floor), and the line-affinity weights (price/quantity + floor). Applies to every organisation under the client. Only supplied fields change; a settings row is created on first write. Caller must be Admin/Owner of the Client. See eng-docs “AP - Three-way Matching Engine” §1a.
Body
Per-line rounding tolerance (in the bill's currency) for three-way matching. Must be >= 0.
Minimum description-similarity score to suggest a fuzzy PO/DN line match. Must be between 0 and 1.
Soft date-proximity window in days preferring bills close to a candidate PO's expected delivery date. Must be >= 0.
Minimum combined supplier-match score to suggest a fuzzy supplier link. Must be between 0 and 1.
Relative weight of supplier-name similarity in the combined supplier-match score. Must be >= 0; cannot be 0 alongside a 0 address weight.
Relative weight of delivery-address similarity in the combined supplier-match score. Must be >= 0; cannot be 0 alongside a 0 name weight.
Header-affinity weight (§1a.6) for a bill↔PO currency match. Must be >= 0.
Header-affinity weight (§1a.6) for bill↔PO/DN date proximity. Must be >= 0. The two header weights cannot both be 0.
Lower bound (0-1) on the combined header affinity, so a header mismatch never buries a genuine line match below this fraction of its line-similarity score. Must be between 0 and 1.
Line-affinity weight (§1a.7) for a bill-line↔PO-line unit-price match. Must be >= 0; cannot be 0 alongside a 0 quantity weight.
Line-affinity weight (§1a.7) for a bill-line↔PO-line ordered-quantity match. Must be >= 0; cannot be 0 alongside a 0 price weight.
Lower bound (0-1) on the combined line affinity, so a price/quantity mismatch never buries a genuine line match below this fraction of its line-similarity score. Must be between 0 and 1.
Response
OK
Per-line rounding tolerance (in the bill's currency) for three-way matching. Line amounts within this of each other are treated as reconciled. Default 0.01 (1p).
Minimum description-similarity score (0-1) for the matching engine to suggest a fuzzy PO/DN line match. Exact SKU matches bypass this. Default 0.7.
Soft date-proximity window (days): bills whose invoice date is within this many days of a candidate PO's expected delivery date are preferred when scoring. Never excludes a PO. Default 7.
Minimum combined supplier-match score (0-1) to suggest a fuzzy supplier link. Exact tax-id/email/name matches bypass this and auto-link. Default 0.7.
Relative weight of supplier-name similarity in the combined supplier-match score. Normalised against the address weight, so the two need not sum to 1. Default 0.7.
Relative weight of delivery-address similarity in the combined supplier-match score. Normalised against the name weight. Default 0.3.
Header-affinity weight (§1a.6) for a bill↔PO currency match. Normalised at use against the other header weights. Default 0.3.
Header-affinity weight (§1a.6) for bill↔PO/DN date proximity. Normalised at use against the other header weights. Default 0.2.
Lower bound (0-1) on the combined header affinity — a header mismatch never buries a genuine line match below this fraction of its line-similarity score. Default 0.5.
Line-affinity weight (§1a.7) for a bill-line↔PO-line unit-price match. Normalised at use against the quantity weight. Default 0.7.
Line-affinity weight (§1a.7) for a bill-line↔PO-line ordered-quantity match. Normalised at use against the price weight. Default 0.3.
Lower bound (0-1) on the combined line affinity — a price/quantity mismatch never buries a genuine line match below this fraction of its line-similarity score. Default 0.3.