Ap duplicate payment preflight
Skill oceanfsdfsvfdsvs/ap-duplicate-payment-preflight/.claude/skills/ap-duplicate-payment-preflight
Catch duplicate vendor payments before release|付款前发现重复供应商付款
npx -y skills add oceanfsdfsvfdsvs/ap-duplicate-payment-preflight --skill ap-duplicate-payment-preflightAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Inspect accounts payable invoice, bill, or payment-run exports for exact and near duplicate payments before release. Use when finance, operations, or founders need to catch duplicate supplier invoices, vendor aliases, resubmitted bills, invoice-number variants, and paid-versus-pending collisions without connecting to an ERP or exposing credentials.
SKILL.md
1.5 KB, 232 tokens by cl100k_base, as published. Nobody here has run it
AP Duplicate Payment Preflight
Use this skill when reviewing local AP exports before payment release. Prefer the full skill directory when available because it includes the deterministic scanner, rules, template, and fixtures.
Workflow
- Ask for the CSV or JSON export path and any column mapping that is not obvious.
- Run the local scanner from the skill directory:
python3 scripts/ap_duplicate_payment_preflight.py --payments scripts/fixtures/ap_payments.csv --date-window-days 14
- Classify rows as
hold_payment,ap_review,allow_with_note, orno_exception. - Do not approve or modify live payments. Produce a review report with row-level evidence and reviewer next steps.
Guardrails
- Hold high-risk exact or normalized invoice duplicates until AP disposition exists.
- Treat paid-versus-pending collisions as high risk.
- Label vendor alias matches as probable, not certain.
- Do not block recurring, tax, utility, credit, reversal, void, or corrected-bill rows without context.
- Do not use live ERP credentials unless the user explicitly asks and provides environment-based authorization.