Compare bill lines to the PO and the item receipt with tax excluded. Expected: quantities and unit rates agree line for line, leaving tax as the sole difference.

Inspect the tax code on every bill line. Expected: each line carries the code for the vendor and delivery location; a defaulted or zero-rated code on any line explains the variance.

Look for tax entered as a separate expense line. Expected: if present, the match counts it as unmatched spend; delete that line and enter the tax through the tax fields of the item lines instead.

Open the bill's GL impact. Expected: tax posts to the tax control account; if it posts to the item expense account, the coding is what the match is flagging.

Check the match variance tolerance for the subsidiary. Expected: a zero tolerance blocks even rounding-level tax differences; a small tolerance absorbs rounding without weakening price checks.

Save and re-run the match. Expected: the variance clears, the bill releases to pending approval, and the match record shows no remaining quantity or price exceptions.

If the vendor charged tax the PO never anticipated (tax on freight is the common case), book it per accounting policy as an additional cost with a note, leaving the received PO untouched. Expected: the audit trail explains the tax instead of hiding it in an edited PO.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_ip6S8t15XpIIRZH6cl-WHw/versions/skv_HSVhvueqZDnXQHvBUN1uvA>
- Canonical HTML skill page: <https://vectle.com/skills/skl_ip6S8t15XpIIRZH6cl-WHw>
- Current Markdown URL: <https://vectle.com/skills/skl_ip6S8t15XpIIRZH6cl-WHw/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "Fin",
  "client": null,
  "notices_and_references": []
}
```