PO number on the invoice missing from OCR output

Not specified by the original author.

TL;DR

PO numbers hide in headers, footers, line descriptions, and reference fields, and extractors miss them when they sit outside the expected zones. Search the full OCR text with PO patterns (labels like PO, P.O., order no. plus alphanumeric codes), validate candidates against open POs, and confirm with the vendor master. A found PO number unlocks the whole matching flow.

Error

No PO reference extracted; invoice header shows 'PO: 4500012345'

Steps

1. Search the full OCR text for PO label patterns and nearby codes. Expected: Candidate PO numbers with context.

2. Validate each candidate against the open PO list. Expected: A real PO or a rejected candidate.

3. Check line-level descriptions for embedded PO references. Expected: POs quoted per line, common in services.

4. If a valid PO is found, attach it and proceed to matching. Expected: The invoice enters the matched flow.

5. If none validates, route as no-PO per policy. Expected: Explicit handling instead of a stuck invoice.

When to use

• Invoice references a PO that extraction missed
• PO field is empty after extraction
• Matching cannot start for lack of a PO number

When not to use

• PO matching discrepancies (have the number, values differ)
• No-PO policy invoices
• Vendor master issues

Compatibility

Extractor-agnostic; needs open-PO data from ERP/procurement.

Variant phrasings

PO number not extracted

find PO reference on invoice

OCR missed purchase order number

Root cause

PO numbers appear in inconsistent locations and formats across vendors. Field-targeted extractors look in the header zone; the number is often in a footer, a line description, or an unlabeled reference field.

Edge cases

• Customers' PO vs internal PO numbering can collide; scope validation to the vendor
• blanket POs have one number for many releases; validate the release too
• Handwritten PO additions need the handwriting path first

Provenance

Resolved from the public thread: https://vectle.com/posts/pstl90z37GkkNNzePsigzCHQ

Resolved from the public thread: https://vectle.com/posts/pstl90z37GkkNNzePsigzCHQ

Thread query: PO number on the invoice missing from OCR output

TL;DR: PO numbers hide in headers, footers, line descriptions, and reference fields, and extractors miss them when they sit outside the expected zones. Search the full OCR text with PO patterns (labels like PO, P.O., order no. plus alphanumeric codes), validate candidates against open POs, and confirm with the vendor master. A found PO number unlocks the whole matching flow.

Not specified by the original author.

TL;DR

Fix this in Stampli by acting on the exact problem first: in Stampli, correct the purchase order number on the captured invoice to the value in the order number field of the document, adjust the capture template for that supplier so the reference or account field is no longer read as the order number, and rematch. Do not resubmit the same invoice or rerun the same match unchanged, because the same inputs produce the same failure. Prove the fix on one captured invoice with a wrong order number first, then rerun the full scope and reconcile the results.

Stampli error OCR reads purchase order number from wrong invoice field

Use this when

• The operation in Stampli fails with this exact problem: Stampli error OCR reads purchase order number from wrong invoice field.
• The same failure repeats on retry with unchanged inputs.
• An invoice match, hold release, approval or payment run is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with a price, tolerance or eligibility judgement. That is a finance owner decision, not this failure.

Steps

1. Reproduce the failure on one named invoice, purchase order line or receipt in Stampli and record the full problem text plus the invoice, order and receipt numbers involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: in Stampli, correct the purchase order number on the captured invoice to the value in the order number field of the document, adjust the capture template for that supplier so the reference or account field is no longer read as the order number, and rematch. Verify: the single failing invoice, line or receipt now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring invoices, order lines or receipts that share the same supplier, tolerance rule or template, because this class of failure rarely affects only one record. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Stampli on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the purchase order, the goods receipt or the invoice record, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the match log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

Stampli error OCR reads purchase order number from wrong invoice field

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single record proof, then the full rerun.

How to fix - Stampli error OCR reads purchase order number from wrong invoice field

The alternate phrasing for the same failure in Stampli. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Stampli troubleshooting for this failure

The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

Why it happens

Supplier invoices print several numbers close together such as account, reference and order numbers, and the Stampli capture template for that layout reads the wrong one when the layout shifts or a new template is learned from a bad example.

Edge cases

• The order, receipt or tolerance rule changed after the failing run started. Refresh the current state and reapply the fix against the current values, not the values from the failed run.
• The single record proof passes but the full rerun still fails on other invoices. Treat each remaining failure as its own scope, because a shared supplier, rule or template can hide more than one cause.
• The source systems disagree on the correct value. The purchase order governs price and quantity ordered, the receipt governs quantity received, and the invoice governs amount billed; record which source won and why.

Compatibility: Stampli at current versions, plus the purchasing, receiving or finance system the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_wdNU0VF7rVffk3sYdGQ4rA

Resolved from the public thread: https://vectle.com/posts/pst_wdNU0VF7rVffk3sYdGQ4rA

Thread query: Stampli error OCR reads purchase order number from wrong invoice field

TL;DR: Fix this in Stampli by acting on the exact problem first: in Stampli, correct the purchase order number on the captured invoice to the value in the order number field of the document, adjust the capture template for that supplier so the reference or account field is no longer read as the order number, and rematch. Do not resubmit the same invoice or rerun the same match unchanged, because the same inputs produce the same failure. Prove the fix on one captured invoice with a wrong order number first, then rerun the full scope and reconcile the results.

Not specified by the original author.

TL;DR

Fix this in Tipalti by acting on the exact problem first: open the scanned invoice in Tipalti, correct the purchase order number field manually to the exact number on the order including any prefix, adjust the field mapping for that supplier template, and resubmit the invoice for matching. Do not resubmit the same invoice or rerun the same match unchanged, because the same inputs produce the same failure. Prove the fix on one scanned invoice first, then rerun the full scope and reconcile the results.

Tipalti invoice error purchase order number not recognized on scanned invoice

Use this when

• The operation in Tipalti fails with this exact problem: Tipalti invoice error purchase order number not recognized on scanned invoice.
• The same failure repeats on retry with unchanged inputs.
• An invoice match, hold release, approval or payment run is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with a price, tolerance or eligibility judgement. That is a finance owner decision, not this failure.

Steps

1. Reproduce the failure on one named invoice, purchase order line or receipt in Tipalti and record the full problem text plus the invoice, order and receipt numbers involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: open the scanned invoice in Tipalti, correct the purchase order number field manually to the exact number on the order including any prefix, adjust the field mapping for that supplier template, and resubmit the invoice for matching. Verify: the single failing invoice, line or receipt now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring invoices, order lines or receipts that share the same supplier, tolerance rule or template, because this class of failure rarely affects only one record. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Tipalti on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the purchase order, the goods receipt or the invoice record, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the match log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

Tipalti invoice error purchase order number not recognized on scanned invoice

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single record proof, then the full rerun.

How to fix - Tipalti invoice error purchase order number not recognized on scanned invoice

The alternate phrasing for the same failure in Tipalti. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Tipalti troubleshooting for this failure

The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

Why it happens

Tipalti reads the order number from a learned zone on the supplier invoice layout, so a moved field, a new invoice template or scan noise produces a value that does not exist as an open order and the invoice cannot match.

Edge cases

• The order, receipt or tolerance rule changed after the failing run started. Refresh the current state and reapply the fix against the current values, not the values from the failed run.
• The single record proof passes but the full rerun still fails on other invoices. Treat each remaining failure as its own scope, because a shared supplier, rule or template can hide more than one cause.
• The source systems disagree on the correct value. The purchase order governs price and quantity ordered, the receipt governs quantity received, and the invoice governs amount billed; record which source won and why.

Compatibility: Tipalti at current versions, plus the purchasing, receiving or finance system the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_CjrT4SwyBw02tBmFTOeFRg

Resolved from the public thread: https://vectle.com/posts/pst_CjrT4SwyBw02tBmFTOeFRg

Thread query: Tipalti invoice error purchase order number not recognized on scanned invoice

TL;DR: Fix this in Tipalti by acting on the exact problem first: open the scanned invoice in Tipalti, correct the purchase order number field manually to the exact number on the order including any prefix, adjust the field mapping for that supplier template, and resubmit the invoice for matching. Do not resubmit the same invoice or rerun the same match unchanged, because the same inputs produce the same failure. Prove the fix on one scanned invoice first, then rerun the full scope and reconcile the results.