These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Accounts Payable Automation
- Features
- Vendor reporting
Vendor reporting
Vendor reporting brings the AP team’s operational questions into one place: what is due, what is waiting for review, which payments cleared and which supplier documents still need attention. Reports keep their source records and reporting period visible, so a total can be explained without treating every draft or transmitted item as settled spending.
OverviewMy Bills (Vendor User)×
Accounts Payable Automation · Vendor reporting
New
My Bills (Vendor User)
Bills
| Bill number | Vendor invoice number | Bill date | Due date | Total | Amount paid | |
|---|---|---|---|---|---|---|
| BLL-38639 | BLL-44507 | 20 Oct | 29 Oct | 9,648.40 | 9,822.99 | |
| BLL-93137 | BLL-57945 | 11 Oct | 15 Oct | 34,050.51 | 30,365.21 | |
| BLL-96491 | BLL-89840 | 30 Oct | 02 Nov | 4,988.04 | 27,283.96 | |
| BLL-51662 | BLL-60219 | 18 Oct | 22 Oct | 4,940.36 | 27,425.08 | |
| BLL-62147 | BLL-54061 | 24 Oct | 26 Oct | 26,379.40 | 1,564.21 |
6 of 6 records
BLL-38639Bills · BLL-38639
DraftVendor invoice numberBLL-44507
Bill date20 Oct
Due date29 Oct
Total9,648.40
Amount paid9,822.99
What you can do
Understand outstanding balances
AP Aging groups open approved and partly paid bills by supplier and due date. It uses the remaining balance after valid payment and credit applications. A bill with a future due date is different from an overdue balance, and a disputed item needs its own context rather than disappearing from the team’s work list. Retain the report’s as-of date when sharing an aging view.
Supplier-spend reporting aggregates the appropriate payment population for the selected period. An active-vendor list shows actual vendor records; calculated spend belongs in its report with a defined basis. This avoids presenting a cached supplier total as though it were a transaction ledger. Reviewers can connect a report to the underlying bill, payment and bank outcome.
Follow exceptions and discounts
The match and dispute reports show why invoices cannot progress. The payment-run views separate proposals awaiting release from actual payment records. Discount reporting compares available, taken, expired and skipped opportunities using their original terms. A potential saving is not reported as a realized discount until the payment application supports it.
Choose views for the reader’s role. The AP Clerk needs processing detail, while a restricted executive viewer receives the permitted summary. Vendor users see only their own bill and payment information. Report exports and drill-down links must enforce the same access boundaries as the visible page, including protection of bank and tax identifiers.
Prepare tax documents with a verified basis
Form1099 tracking retains the tax year, form and box, payment total, reporting decision, applied threshold and rule source. Rules depend on the relevant year and payment category; the website does not treat one threshold as permanently correct. Missing W-9 information remains an exception in the population requiring review, rather than a reason to omit a potentially reportable payee.
Controller / CFO reviews readiness before the configured filing partner receives the handoff. Keep one declared filing owner for each payment population, including subcontractor-originated bills, to avoid duplicate filings. Form1099 filings hold the handoff identity and result. A prepared file, recipient copy and accepted filing are separate outcomes; corrections retain their connection to the original reporting record.
What your team sees
- AP Aging. Review the underlying records within your permitted scope.
- 1099 Readiness (Current tax year). Review the underlying records within your permitted scope.
What it keeps track of
Data model- Bills
- Vendor bill header. The center-of-gravity table. Lifecycle: Draft → pending match → pending approval → Approved → partially paid / Paid / Voided / Disputed.
- Payments
- The actual disbursement record — one per Bill (or one off payee) per actual payment movement. Joins the payment run items intent to the bank’s confirmation.
- Vendors
- The AP-side vendor master. Includes legal-name + EIN identity, W-9 status, default 1099 eligibility, remit-to address, ACH bank details (masked), and default payment terms. Bank-account changes go through a two-person verify before the new details are usable on a payment run.
- Disputes
- Bills under dispute — three-way mismatch, vendor-billing error, quality issue, duplicate-bill flag. Tracked through to resolution with a vendor credits or bill status: Voided outcome.
- Early pay discounts
- Per-Bill early-pay discount opportunities — computed from the vendor payment terms discount clause and the Bill’s window. The AP Manager dashboard surfaces Available rows; inclusion in a payment run item flips Status to Taken.
- Form 1099tracking
- Annual aggregator — cumulative 1099-NEC reportable payments per Vendor per tax year, with the verified tax-year reporting decision and the IRS filing reference once Payroll’s filing partner transmits.
- Form 1099filings
- The handoff artifact to Payroll’s filing partner — one row per Vendor per tax year per form type, snapshotting recipient identity at filing time so amendments and audits resolve cleanly even if the underlying Vendor record changes.
- Vendor tax withholdings
- Per-Vendor backup-withholding configuration — typically driven by an IRS B-Notice (incorrect TIN), missing W-9, or voluntary withholding. Drives Payments to apply the withholding rate against 1099-reportable disbursements.
Who uses it
Permissions- AP Manager
- Tracks aging and document exceptions.
- Controller / CFO
- Reviews release and filing readiness.
- AP Clerk
- Follows processing queues.
- Viewer
- And Vendor User receive their defined reporting scope. the configured filing partner performs the external submission.
Set up Accounts Payable Automation your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.