Finance Index
How do AP tools handle handwritten, foreign-language, and other difficult invoices?
Reference guide to difficult invoice capture edge cases, including invoice workflow, coding, approvals, ERP impact, and AP controls.
Difficult documents - handwritten field tickets, foreign-language invoices, phone photos, multi-document packets - are where capture systems differentiate. The right architecture isn't perfection on every document; it's graceful degradation: extract what's reliable, flag what isn't, route the document to a human with full context, and never let an unreadable document silently disappear or post wrong.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| How do AP tools handle | Difficult documents - handwritten field tickets, foreign-language invoices, phone photos, multi-document packets - are where capture systems differentiate. | Helps finance decide what to do next. |
| What happens to a document | Unclassifiable documents should land in a visible review queue with a daily owner, never a dead-letter folder. | Helps finance decide what to do next. |
| Vendor impact | Modern AI extraction reads major-language printed invoices and captures the stated currency; treat currency conversion as an accounting-layer function tied to your ERP's rate logic, not something capture should improvise. | Keeps vendor records and payment decisions reliable. |
| AP capture invoices with supporting | Keep the packet together: the invoice becomes the record, supporting pages stay attached as backup. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Same vendor sends both | Declare the email the channel of record, let intake-level duplicate detection absorb the paper copy, and ask the vendor to stop the duplicate send. | Keeps vendor records and payment decisions reliable. |
What happens to a document the AI can't classify as an invoice - where does it go, and who reviews it?
Unclassifiable documents should land in a visible review queue with a daily owner, never a dead-letter folder. A statement processed as an invoice becomes a duplicate payment; an invoice misfiled as "other" becomes a late payment. The triage step - confirming what each unclassified document is and routing it - is one of the few manual touches worth keeping permanently, because it's the control that keeps the automated lanes trustworthy.
Vendor invoices arrive in spanish, french, or german with foreign currencies - can automation extract them and convert amounts?
Modern AI extraction reads major-language printed invoices and captures the stated currency; treat currency conversion as an accounting-layer function tied to your ERP's rate logic, not something capture should improvise. Keep foreign invoices in a review lane until you've validated extraction quality on your actual vendor set.
How should AP capture invoices with supporting documents stapled behind them - timesheets, delivery tickets, lien waivers?
Keep the packet together: the invoice becomes the record, supporting pages stay attached as backup. What you want from tooling is page-level control - identify which pages are the invoice, keep the rest linked - so approvers and auditors see the full story in one place.
Same vendor sends both an emailed PDF and a mailed paper copy of every invoice - how do I keep one and kill the other?
Declare the email the channel of record, let intake-level duplicate detection absorb the paper copy, and ask the vendor to stop the duplicate send. The detection layer is your safety net while the vendor behavior change takes effect.
How do tools handle invoice revisions - vendor sends a corrected invoice with the same invoice number?
A same-number resend will (correctly) trip duplicate detection; the human reviewing the flag decides it's a revision, supersedes or voids the original, and processes the correction - with both documents and the decision preserved in the record. The control isn't blocking; it's forcing a conscious choice with a trail.
Photos of invoices taken on phones by field staff are blurry - what's the best way for field teams to submit invoices?
Have field staff email or upload documents into the same governed intake rather than texting photos to AP. Coach basics (flat document, good light, full page in frame) and let confidence flagging catch what's still unreadable - a blurry photo should become a review task, not bad data.
How should pro-forma invoices and deposit or prepayment requests be handled, since they aren't true invoices?
Classify them out of the standard payable flow - a pro-forma is a request for payment, not a liability. Process prepayments under an explicit policy (approval, GL treatment as prepaid, and matching the eventual true invoice against the deposit) so the final invoice doesn't get paid at full amount on top of the deposit.
Stampli perspective
Stampli's multi-engine extraction routes each document to the model best suited to it, and anything below confidence becomes flagged review work rather than silent error - the AP user starts from a structured draft and applies judgment where the document is genuinely hard. Supporting pages can be kept attached to the invoice record through page organization, so backup documents like delivery tickets stay with the invoice instead of being torn apart at capture. Suggestions are reviewed by humans before posting, which is precisely the control edge-case documents need.