Best fit
An invoice can be sent successfully yet never enter the buyer's AP system because it went to the wrong destination, omitted a PO or attachment, was silently rejected, or has no acceptance receipt.
// Finance, Legal & Accounting
Invoice Acceptance Evidence Gate
Verify customer-specific invoice fields, attachments, destination, submission receipt, acceptance status, correction version, and aging start.
What problem does Invoice Acceptance Evidence Gate solve?
An invoice can be sent successfully yet never enter the buyer's AP system because it went to the wrong destination, omitted a PO or attachment, was silently rejected, or has no acceptance receipt.
Use it to
- Preflight customer-specific invoice packages
- Prove the latest corrected version reached the right destination
- Keep silent rejection out of the aging clock
- Preserve AP acceptance evidence before collection follow-up
What it returns
- Invoice-to-customer submission ledger
- Field, attachment, destination, receipt, and rejection findings
- JSON accepted-for-aging gate
- Accounts-receivable review memo
A representative input and result
input An invoice was emailed although the customer profile requires Coupa, omits the PO field and timesheet attachment, and its latest submission is rejected without a verified receipt.
result Gate: BLOCK. Wrong destination, missing field and attachment, rejection, and missing acceptance receipt prevent aging.
Access and approval boundaries
- Read access to one user-supplied local JSON evidence file.
- Write access only to the selected local output directory.
- No browser, network, credential, account, environment-variable, or external-action permission is required.
Known limitations
- The package uses owner-supplied customer requirements and does not connect to an AP portal, send an invoice, or contact a customer.
- A portal or email receipt does not prove legal delivery, correctness, approval, or eventual payment.
- Accepted-for-aging means the supplied evidence supports the recorded acceptance time; finance retains responsibility for follow-up and accounting treatment.
// choose with context
Is Invoice Acceptance Evidence Gate the right skill?
It returns
Invoice-to-customer submission ledger. Field, attachment, destination, receipt, and rejection findings.
Do not use it as
The package uses owner-supplied customer requirements and does not connect to an AP portal, send an invoice, or contact a customer.
Compatibility, access, version, and licence
- Reads or accesses
- Declared local scope: invoice-acceptance.json, invoice-acceptance-output/**.
- Compatibility
- Documented normalized UTF-8 JSON input. Python 3.10 or newer on Windows, macOS, or Linux. Local files only; no live provider connection is required.
- Version
- 1.0.0
- Licence
- Review the package licence and seller terms at the linked destination.
Questions
Does it connect to a live account?
No. Version 1 reviews documented normalized local evidence only.
Does it take the external action?
No. It never submits, revokes, publishes, contacts, pays, or changes an external system.
What files does it create?
A findings CSV, evidence ledger CSV, summary JSON, and owner-review memo.
How does malformed input behave?
Missing identifiers, duplicate identifiers, bad timestamps, and invalid numbers fail before a ready result is produced.
Does a ready gate prove compliance or legal sufficiency?
No. It means the supplied records have no automated finding and are ready for the named owner or qualified reviewer.
Can the output be audited?
Yes. Every finding includes a stable code, record identifier, message, and source dataset.
Invoice Acceptance Evidence Gate keeps proof and approval boundaries visible.
The listing includes the tested package, realistic samples, declared permissions, and known limitations.
Get Invoice Acceptance Evidence Gate on Agensi