The Finofo blog

Expense tools assume employees will install an app and code their own spend. Most will not, and the coding gets redone anyway. A better split between capture and accounting.

Why Canadian AP still miscodes PST after OCR works, and how vendor plain-language rules put PST on the product GL instead of a fake tax bucket.

Multi-division AP fails when the segment cue is inside a vendor account number. How plain-language vendor rules map those patterns to cost centers.

Card feeds without receipts still burn AP time. Why SMS capture into an AP-native expense (finance-owned coding, Canadian tax) matters more than matcher slogans.

Large compound vendor packs stall AP before coding starts. How split plus Unclassified turns one PDF into discrete bills without posting appendix pages.

Logistics bills need unique ship-to and lane narratives, not the word freight. How vendor rules draft bill descriptions beyond OCR fields.

Total only PO matching clears invoices that are wrong on every line that matters. How item by item match, UOM memory, and variance actions change the review.

Oilfield invoices often print location and miss the cost center. Why history based coding fails, and how NL rules plus a wells master cross check fix the rekey loop.

When clerks file invoices, emails, and attachments in SharePoint, approvals lose SLA age. What to use instead: one invoice object with inbox, comments, and supporting docs.

Controllers burned by convincing AP demos share what fails in production: provincial tax, multi currency, two cent locks, and AI lines you delete by hand.

Repeating vendors and SKUs across jobs break memory based AP coding. Why project must live on the PO so invoices inherit job codes at match.

description: Airlines often send HTML receipts with no PDF. How email body conversion and sender based routing keep attachment less documents in the AP pipeline.

Invoices print ordinary HST. Canadian PSB rebates need a policy split OCR cannot see. What to automate, what to configure, and which CRA factors to verify.

Flat kilometre entry hides audit risk. How address search, map paths, and configured rates help approvers see the route, plus CRA 2026 rate context.

Vendor statements are control documents, not invoices. How multi-page hotel and supplier statements get matched to invoices and payments, with a discrepancy view you can share.

Inferred AP coding can copy messy history. Why resemblance fills need labels, how explicit vendor rules differ from guesses, and what to ask before you trust auto-coding.

OCR reads the trade name; your DMS holds the legal name. Why vendor aliases are a teach-once clerk-time fix, and why auto-merge is the wrong shortcut.

Qty-only purchase orders break total-only match. How quote, PO, and invoice need to travel as a bundle when price authority starts on the quote.