Is it built in-house with Flow, handled through a third-party AP tool, or still manual? Curious what's working and what's painful for teams managing this at scale.
Disclosure: I work on Quick Payable, a Salesforce-native AP automation app. I'm trying to understand what's actually working for teams in this space before assuming we have the answer.
답변 1개
TL and DR on multi plant invoice routing/PO matching in Salesforce:- Manual/Excel still common, especially where plants ran separate AP pre-consolidation. No audit trail, biggest pain point.
- Homegrown Flow + Apex - Flow for routing, Apex for 3-way match logic. Breaks down on: plant-specific approval matrices (hardcoded → brittle), no native OCR (bolt-on needed), multi-currency/GL mapping gets messy.
- AppExchange AP tools (your category) - wins when: multiple ERPs across plants, need line-level tolerance matching, want standard AP reporting out of the box.
- Middleware + ERP-as-source-of-truth - larger manufacturers often let SAP/NetSuite do the matching, sync status to Salesforce for visibility only.
Universal pain points regardless of approach:
- Plant-level approval matrices as hardcoded logic vs. data-driven config
- Partial receipts/partial invoicing against a PO
- Vendor invoice format variance across plants
- GL/cost center mapping drift when a plant's chart of accounts changes
I hope you find the above information helpful. If it does, please mark it as Best Answer to help others too.
