Vendor Payment Validation with Compliance Checks
Accounts payable needs to approve invoices quickly while catching duplicates, verifying vendor legitimacy, and maintaining SOX audit compliance.
Das Problem
Invoices routed for payment are evaluated before disbursement. Corules checks: vendor against approved list, invoice against open PO, duplicate detection against recent payments, and amount against authority limits. Non-approved vendors or mismatched invoices escalate. Every payment decision is logged with policy version for SOX audit.
So löst Corules es
BLOCK: vendor_id 'VND-9921' not in approved_vendors list. Payment blocked pending vendor approval.
Richtlinienbeispiel
// Vendor payment policy (CEL)
context.vendor_id in params.approved_vendors
&& !context.is_duplicate_invoice
&& context.invoice_amount <= context.po_amount * 1.05
&& context.payment_amount <= params.authority_limits[context.approver_role]Integrationsoptionen
Frequently Asked Questions
What is the 5% tolerance on invoice vs PO amount?
Many organizations allow minor variances (freight, taxes). The 1.05 multiplier is a parameter — set it to 1.00 for zero tolerance.
How does duplicate detection work?
The context object includes a `is_duplicate_invoice` flag computed from invoice number + vendor ID + amount. The calling system is responsible for querying recent payments and populating this field.