> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thickdot.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Configure Receipt Routing and Auto-Approval Policies
> Set your partial receipt policy, understand every condition that routes a document to human review, and learn the auto-approval criteria.
Routing config determines what the platform does with a document once the match stage is complete. The core question routing answers is: does this document post automatically, or does it go to a human reviewer? The most impactful setting is your **Partial Receipt Policy**, which governs how the platform handles deliveries that don't cover every line on the purchase order. Access these settings at **Admin > Config > Route**.
***
## Partial Receipt Policy
A partial receipt occurs when the delivery document only covers some of the lines on the linked purchase order — for example, when a vendor splits a ten-line order into two separate shipments. How you handle this situation depends on your supplier relationships and operational preference.
**Best for: split-delivery vendors and made-to-order suppliers**
Only the lines present on the current document are auto-posted to the ERP. The platform creates a goods receipt for the received lines and leaves the remaining PO lines open, ready to be fulfilled by a future shipment.
This is the most permissive policy and typically yields the highest straight-through processing rate for vendors who routinely ship in multiple consignments.
When using Allow Partial, make sure your ERP lookup strategy and writeback config correctly target individual lines rather than the full PO, so open quantities are decremented accurately.
**Best for: vendors expected to always ship complete orders**
Any document that does not account for every open PO line is held back from auto-posting and placed in the **Needs Review** queue. A human reviewer can then confirm whether the partial shipment was intentional or a processing error before approving.
This policy adds a human checkpoint without fully rejecting the document, making it a good default during initial rollout when you are still building confidence in your matching rules.
**Best for: strict contractual compliance or high-value single-shipment orders**
If the document does not cover all open PO lines, it is **automatically rejected**. No receipt is posted to the ERP. The vendor or procurement team must resubmit a compliant document.
Use this policy when your contracts require complete shipments and any partial delivery should be treated as non-conformant.
Reject Partial Receipts is the strictest option available. Before enabling it, confirm with your procurement team that vendors are aware deliveries must be complete — unexpected rejections can disrupt supplier relationships.
***
## When Documents Go to Human Review
Even with a permissive routing policy, certain conditions always trigger a **Needs Review** routing and prevent automatic posting. Understanding these conditions helps you tune your extraction and matching config to minimise unnecessary review queues.
A document is sent to human review when any of the following is true:
* **Quantity mismatch** — the extracted quantity falls outside the configured tolerance for one or more lines.
* **Part number not matched** — fuzzy similarity for a line item falls below your configured threshold, and no confident pairing can be made.
* **Required field missing from OCR** — a field marked Required OCR was not found on the scanned document with sufficient confidence.
* **Required field missing from ERP** — a field marked Required PO does not exist on the purchase order record in your ERP.
* **PO not found in ERP** — none of the configured ERP lookup strategies returned a matching purchase order.
* **Low AI confidence on extraction** — the AI Brain's overall confidence score for the document falls below the minimum threshold, even if no individual required field failed.
* **Partial shipment with policy = Require Review** — the document covers only some PO lines and your Partial Receipt Policy is set to Require Review.
* **Multi-PO or Blanket Release detected but not configured** — the platform identifies a multi-PO or blanket release context but no matching context rule is configured to handle it.
***
## Auto-Approval Criteria
A document is eligible for **automatic approval and straight-through posting** only when all of the following conditions are simultaneously true:
Every field marked Required was found on the document and the AI's confidence score meets the minimum threshold.
Every extracted document line was successfully paired with a line on the purchase order, meeting the configured Exact or Fuzzy threshold.
No line item's extracted quantity deviates from the ERP PO quantity by more than the configured ± tolerance (including any vendor-specific overrides).
At least one of the configured ERP lookup strategies successfully located the purchase order.
Either the document covers all open PO lines, or your Partial Receipt Policy is set to Allow Partial.
If any single criterion is not met, the document is routed to the **Needs Review** queue rather than being auto-posted. The review interface highlights exactly which criterion failed so the reviewer can make an informed decision quickly.
During initial rollout, set your Partial Receipt Policy to **Require Review**. Once you have reviewed several weeks of documents and are confident your matching tolerances are well-tuned, switch to **Allow Partial** for vendors you trust to split shipments legitimately. This staged approach avoids surprise auto-posts before you have validated your configuration end-to-end.