Resolve a match line
Record a resolution against ONE bill line’s variance (billLineId in the body): accept / accept_and_update_catalog settle that line whatever the variance kind (price, short delivery, or over-order surplus); dispute / request_credit_note keep the bill blocked. Once every varianced line is accept-resolved the group settles and emits the BillMatchResolved fact (an audit / webhook record of the settlement). This does NOT auto-approve the bill: it leaves PendingReview only when re-submitted, at which point the submit-time match gate re-evaluates the now-clean group. accept_and_update_catalog only records the intent — it does not mutate any catalog. Re-posting overrides a line’s prior decision; DELETE the resolution to undo.
Path Parameters
Body
Records a human decision against one bill line's variance. Accept settles that line; Dispute and RequestCreditNote keep it (and so the bill) blocked.
The bill line whose variance is being resolved.
The decision to record (e.g. Accept, RequestCreditNote, Dispute).
Accept, AcceptAndUpdateCatalog, RequestCreditNote, Dispute Optional free-text note to capture with the resolution.
Response
OK
A bill's three-way match: each bill line with its allocations and derived price/quantity variances (computed at read time, never stored), plus fuzzy purchase-order and delivery-note suggestions for lines that still need matching.
Unique identifier of this match group.
The bill under review.
Lifecycle status of the match: Open (nothing to settle), Variance (a flagged difference awaits a human decision), Resolved (settled), or Synced (exported — not reachable yet).
Open, Variance, Resolved, Synced Per-line rounding tolerance, in the bill's currency, that every variance was judged against. Configured per organisation; a difference within tolerance is treated as clean.
True when every line is fully allocated with no outstanding variance.
One entry per bill line, carrying its allocations and derived variances.
Fuzzy purchase-order-line suggestions for bill lines with no exact (SKU) match. Derived, never stored; confirm one (POST an allocation) to create a real match.
Fuzzy delivery-note-line suggestions — the receipt-quantity counterpart of Suggestions. Lets the UI ask 'which delivery does this line belong to?' without the caller knowing line ids.