Accounts Payable β€” Reports
Aging, cash requirements, audit support, and operational analysis

Overview

The Accounts Payable (AP) Reports menu provides operational and accounting reports used to manage vendor balances, forecast cash needs, validate check activity, and support month-end reconciliation. These reports are designed to answer two key questions: What do we owe? and What did we pay?

Aging & Payables Management

  • Vendor Aging β€” open balances by vendor and aging bucket.
  • Outstanding Open Invoices β€” invoice-level listing of unpaid items.
  • Scheduled Invoices Aging β€” open items already staged for future payment.

Cash Planning

  • Cash Requirements β€” forecast upcoming payment needs.
  • Paid not Billed β€” identify timing gaps where payment occurred without matching billing/record.

Audit & Reconciliation

  • Check Register β€” listing of issued checks by bank/date range.
  • Check Reconciliation β€” reconcile checks to bank clearing activity.
  • AP Audit Report β€” control/audit support for AP postings and changes.

Operational / Analysis

  • AP Activity by File# β€” payables activity tied to operational files.
  • AP Activity by GL Acct# β€” vendor payments and postings by GL account.
  • File Profitability Report β€” profitability analysis including AP impact.
Tip: For most teams, daily use centers on Vendor Aging, Cash Requirements, and Check Register. Month-end typically uses Check Reconciliation, AP Audit, and GL-based activity reports.

Which Report Should I Use?

Use this quick decision table to choose the best Accounts Payable report based on the question you are trying to answer. Each report is optimized for a specific purpose (cash planning, vendor visibility, file analysis, audit, or coding review).

Cash Planning & Payment Timing

  • What vendors are owed money right now? β€” Vendor Aging
  • What payments are coming due based on schedule? β€” Scheduled Invoices Aging
  • How much cash will be required by specific dates? β€” Cash Requirements
  • How many checks and dollars were issued? β€” Check Volume Summary

Vendor & Invoice Visibility

  • What invoices are still open? β€” Outstanding Invoices
  • What activity has occurred for a vendor? β€” Vendor Activity
  • Which vendors exist and how are they configured? β€” Vendor Listing

File-Based Analysis

  • What A/P activity exists for a file? β€” AP Activity by File Number
  • Are files profitable after A/P activity? β€” File Profitability
  • Were advances issued before vendor invoices or customer billing? β€” Advanced Checks
  • Were vendors paid but customers not billed? β€” Paid Not Billed

Accounting, Audit & Reconciliation

  • What vouchers were entered in a period? β€” Voucher Register
  • How does A/P reconcile to the General Ledger? β€” AP Activity by GL Acct#
  • What A/P control transactions occurred (adjustments, reconciliations, renumbering, etc.)? β€” AP Audit Journal
  • Which checks cleared or remain outstanding? β€” Check Reconciliation
  • What checks were issued in a period? β€” Check Register

Coding & Classification

  • How were invoices and payments grouped by cost category? β€” AP Report by Bill Code
Tip: If you are planning cash outflows, use reports driven by Scheduled Payment Date. If you are reconciling or auditing, use reports driven by Voucher / GL / Check activity.

Reports Menu

The Reports menu is organized around vendor balance reporting, cash planning, operational file analysis, and check reconciliation. Each report may be filtered by company, department/group, vendor, date range, and output format depending on the report.

Best Practice: Standardize a weekly reporting routine (Aging + Cash Requirements + Check Register) and a month-end package (Audit + Reconciliation + GL Activity) so results remain consistent across periods.

Vendor Aging Report

The Vendor Aging Report summarizes outstanding payables by vendor and aging bucket as of a selected aging ending date. It supports planning, cash forecasting, and prioritizing payments by vendor, department/group, and transaction type.

You can run the report for Trade/Operations, Overhead, or Both, and optionally filter to a specific vendor, exclude small balances, or include items already closed after the aging date.

Report Options

  • Aging Ending Date β€” β€œas-of” date used to age open balances.
  • Specific Vendor (ALL) β€” run for one vendor or all vendors.
  • (D)etail / (S)ummary β€” summary totals vs detail invoice-level lines.
  • (T)rade / (O)verhead / (B)oth β€” limit report to operational trade items, overhead, or both.
  • Dept#/Group Code (All) β€” filter by a department/group (or run for all).
  • Print Credits Only (Y/N) β€” show only credit balances if needed.
  • Print Items Already Closed? (Y/N) β€” include items that were closed after the aging date (helpful for audit snapshots).
  • Minimum Open Balance Amount β€” suppress vendors/items below a threshold (reduces noise).
  • Print Report to (R/S) β€” output to Report or Spreadsheet (if enabled).
  • Vendor Type (ALL) β€” limit to a vendor classification if used.
  • Include GL Summary (Y/N) β€” include GL rollups (useful for reconciliation).
Best Practice: Use a consistent β€œas-of” date (week-end or month-end) and set a reasonable minimum balance to reduce clutter and focus on actionable payables.
Workflow note: Run Vendor Aging before check runs to validate which vendors are due and to spot unexpected credits or old open items that may need cleanup (voids, adjustments, or credit application).

Cash Requirements Report

The Cash Requirements Report forecasts upcoming cash needs based on invoices that have been assigned a Scheduled Payment Date. You provide up to three cutoff dates, and the report groups invoices into β€œbuckets” to show how much is due by each date range.

This report is commonly used to plan weekly/bi-weekly check runs and to verify whether current bank balances can support upcoming vendor payments.

Report Criteria

  • Company β€” selects the company/entity owning the payables.
  • Scheduled Payments by (1st date) β€” includes invoices scheduled to pay on or before this date (first bucket).
  • Payments by (2nd date) β€” includes invoices scheduled after the 1st date and up to this date (second bucket).
  • Payments by (3rd date) β€” includes invoices scheduled after the 2nd date and up to this date (third bucket).
  • (D)etail or (S)ummary β€” prints vendor-level totals (Summary) or invoice lines (Detail).

How the Date Buckets Work

  • Column 1: all open invoices with a scheduled pay date ≀ the 1st date.
  • Column 2: scheduled pay date between (1st date + 1 day) and the 2nd date.
  • Column 3: scheduled pay date between (2nd date + 1 day) and the 3rd date.

Output (Typical Columns)

  • Acct No / Vendor Name β€” vendor identifier and name.
  • Invoice No / Inv Date β€” invoice reference and invoice date.
  • Sch Date β€” scheduled payment date used to bucket the invoice.
  • Sch Pmt β€” scheduled payment amount (or open amount scheduled).
  • Date Columns β€” amounts due by each cutoff date bucket.
  • Vendor total β€” subtotal per vendor for quick cash planning.
Best Practice: Use the same three cutoff dates each cycle (e.g., end of week, mid-month, end of month) so trends are comparable and cash planning stays consistent across periods.
Tip: If results look β€œtoo low,” confirm invoices have a Scheduled Payment Date assigned in Modify Payment Schedule Date or in the batch scheduling workflow.

Outstanding Invoices Report

The Outstanding Invoices Report lists open A/P invoices by vendor and shows key payment planning fields (invoice/reference, file number, invoice date, scheduled pay date, scheduled amount, and open balance). Use this report to quickly identify what is still unpaid and confirm what is staged for upcoming check runs.

This report is especially helpful as a β€œpre-check-run review” to confirm invoices are present, scheduled dates look correct, and vendor totals match expectations.

Report Criteria

  • Company β€” selects the company/entity owning the payables.
  • Dept/Group, (O)verhead, (A)ll β€” filter results to a department/group, overhead invoices only, or all.
  • (R)eport or (S)preadsheet β€” choose a printed report format or a spreadsheet export (for sorting, filtering, and pivoting).

Output (Typical Columns)

  • Account / Vendor Name β€” vendor identifier and name.
  • Inv/Ref# β€” invoice number or internal reference number.
  • File No. β€” operational file tied to the payable (when applicable).
  • Inv Date β€” invoice date (used for aging/review).
  • Inv Amount β€” original invoice amount.
  • Sch Date β€” scheduled payment date (if assigned).
  • Sch Amount β€” amount currently scheduled to pay.
  • Open Balance Amount β€” remaining unpaid balance.
  • Vendor Totals β€” subtotal per vendor for quick review.

When to Use

  • Review unpaid invoices before selecting/printing checks.
  • Confirm scheduled pay dates and scheduled amounts are populated.
  • Export to spreadsheet to reconcile against vendor statements or internal accruals.
Best Practice: Run this report right after scheduling (or batch selection) to confirm that invoices expected in the next check run have a Sch Date and a non-zero Sch Amount.
Tip: If an invoice shows an open balance but no scheduled date/amount, assign it in Modify Payment Schedule Date (date-based workflow) or include it in a payment batch (batch workflow).

AP Activity by File Number

The Accounts Payable Activity by File Number report provides a consolidated view of vendor invoice and payment activity grouped by operational File Number. This report is commonly used to analyze payables tied to specific shipments, jobs, or operational files.

The report supports multiple selection methods, including date range, file number, customer number, or vendor number, and can be limited to open balances only.

Selection Options

  • Date Range β€” report activity within a specific posting period.
  • File Number β€” isolate activity for a single operational file.
  • Customer Number β€” report payables tied to a specific customer.
  • Vendor Number β€” limit activity to a single vendor.

Additional Filters

  • Dept/Group Code or (A)ll β€” restrict by department or include all.
  • (O)pen Balance or (A)ll β€” include only unpaid items or full history.

Report Output

  • Reference # β€” internal reference or invoice identifier.
  • Vendor / Customer β€” party associated with the payable.
  • Invoice Amount & Date β€” original obligation.
  • Payment Amount, Date & Check # β€” applied payments.
  • Balance β€” remaining open balance per file.
Use Case: This report is frequently used to reconcile vendor costs at the shipment or job level and to validate profitability by file.
Best Practice: Run this report with Open Balance enabled during month-end close to identify unpaid vendor charges tied to active files.

Voucher Register

The Voucher Register is an A/P audit report that lists invoices/vouchers entered into the system for a selected date range or accounting period. It’s commonly used to support period-end review, reconcile A/P activity, and provide an audit trail of what was vouchered (and when).

Use this report to answer questions like: β€œWhat invoices were entered this period?”, β€œWhich vendors were vouchered?”, and β€œWhat amounts were posted (invoice vs. pay/advance)?”

Report Criteria

  • Selection for Report β€” choose the report basis: 1 = Date Vouchered or 2 = Accounting Period.
  • Starting Date / Ending Date β€” used when running by Date Vouchered.
  • Period β€” used when running by Accounting Period (e.g., YYYYMM or your period format).
  • Print Transactions β€” include transaction detail (when enabled) rather than summary-only output.
  • (O)pen, (C)losed, (B)oth β€” include open items, closed items, or both.
  • (R)eport or (S)preadsheet β€” output to a printable report or spreadsheet format.

What You’ll See on the Output

  • Entered Date β€” when the voucher/invoice was entered.
  • Acct Prd β€” accounting period associated with the voucher.
  • Vendor Reference No. β€” vendor invoice/reference number (or internal reference).
  • File Number β€” operational file tied to the cost (where applicable).
  • Doc Src β€” source/type (example: OPS vs INV or your internal doc source codes).
  • Vendor Number / Vendor Name β€” vendor identity.
  • Invoice Amount β€” original voucher amount entered.
  • Pay/Adv Amount β€” amount paid and/or advanced depending on configuration and processing stage.
  • Vendor Totals β€” subtotal breaks by vendor to support reconciliation.
Tip: For period-end support, run the Voucher Register by Accounting Period and output to Spreadsheet to quickly filter by vendor, file number, or amount.
Best Practice: If results look incomplete, verify you selected (B)oth open/closed and that your date/period matches the posting rules used for vouchering in your environment.

Vendor Activity Report

The Vendor Activity Report provides a chronological view of invoice and payment activity for one or more vendors over a selected date range. It is commonly used to research vendor balances, verify payment history, and support vendor inquiries.

This report can be run for invoiced items, paid items, or both, and supports multiple sorting and output options depending on the analysis required.

Report Selection Options

  • Vendor Name or (A)ll β€” run the report for a specific vendor or all vendors.
  • (I)nvoiced, (P)aid, (B)oth β€” control whether the report includes open invoices, payments, or the full activity history.
  • Starting Date / Ending Date β€” define the activity date range.
  • (S)ummary or (D)etail β€” summary totals by vendor or detailed line-item activity.
  • Vendor Type or (A)ll β€” limit by vendor classification if configured.
  • Sort Option:
    • A β€” By Vendor / Reference Number
    • B β€” By GL Codes & Vendors
    • C β€” By Charge Codes & Vendors
  • (R)eport or (S)preadsheet β€” output to on-screen report or spreadsheet format.

Report Output

  • Reference No / File No β€” internal reference and operational file linkage.
  • Invoice Amount & Date β€” original vendor invoice details.
  • Payment / Adjustment Amount β€” applied payments or adjustments.
  • Check Number β€” check or payment reference used.
  • Balance β€” remaining open balance after activity.
Use Case: This report is frequently used to respond to vendor balance disputes, trace payment history, and support audit or reconciliation requests.
Tip: Use Detail + By Vendor/Reference when researching a single invoice, and Summary + Spreadsheet for month-end or audit support.

Check Register Report

The Check Register Report prints a list of checks issued for a selected bank account and date range. This report is commonly used after a check run (or manual check entry) to verify what was issued, confirm payees and amounts, and support bank reconciliation and audit review.

The report can be produced in Summary or Detail format and may be sorted by Vendor, Check, or Account. You may also export the output as a Spreadsheet for analysis or archiving.

Report Criteria

  • Bank Code / Company Code β€” selects the bank account and company issuing checks.
  • Starting Check Date β€” beginning date for checks to include.
  • Ending Check Date β€” ending date for checks to include.
  • Sort Sequence β€” sort by (V)endor, (C)heck, or (A)cct No.
  • Vendor Code or * for all β€” limit to one vendor or include all vendors.
  • (S)ummary or (D)etail β€” vendor/check totals vs. full line detail.
  • Dept#, Group# or (A)ll β€” filter checks by department/group or include all.
  • (O)perations, (V)erhead, (D)irect or (A)ll β€” limit by check type/source.
  • Include Adjustments? β€” include adjustment lines (if applicable).
  • (R)eport / (S)preadsheet β€” output to standard report or export to spreadsheet format.

Common Uses

  • Verify checks issued immediately after printing.
  • Support bank reconciliation and check clearing research.
  • Provide documentation for auditors and month-end close.
Workflow note: Run this report after Prepare and Print Checks (and after any manual check entry) to confirm issued checks and retain a supporting register for reconciliation.
Best Practice: Use Sort = (C)heck and Detail for reconciliation and troubleshooting. Use Summary for quick sign-off and management review, and export to Spreadsheet for audit packages.

Check Reconciliation Report

The Check Reconciliation Report supports the month-end bank reconciliation process by listing checks that have been cleared, not cleared, voided, missing, or processed via ACH. This report is typically run in conjunction with the Bank Reconciliation function to validate check activity against the bank statement.

Users may generate reconciliation results by date range or by check number range, allowing precise alignment with bank statements.

Selection Criteria

  • Bank Code β€” bank account being reconciled.
  • Company β€” company/entity issuing the checks.
  • Range Option β€” reconcile by Date Range or Check Number.
  • Start / End Range β€” date or check number boundaries.
  • Cleared or Issued Date β€” controls which date is used for matching.
  • Include Checks Cleared After End Date β€” useful for late bank postings.

Report Options

  • Cleared Checks β€” checks matched to the bank statement.
  • Un-Cleared Checks β€” issued but not yet reconciled.
  • Voided Checks β€” checks voided in A/P.
  • Missing Checks β€” gaps in check sequencing.
  • ACH Checks β€” electronic payments.
  • All of the Above β€” comprehensive reconciliation listing.
Workflow note: This report is commonly run after importing or reviewing the bank statement to identify checks that remain outstanding or require follow-up.
Best Practice: Always reconcile checks using the same cutoff dates as the bank statement to prevent timing differences from appearing as discrepancies.

A/P Audit Journal Report

The A/P Audit Journal Report provides a chronological audit trail of key transactional activity within Accounts Payable. It is primarily used for internal review, period-end verification, and compliance auditing.

This report captures system-generated journals for adjustments, reconciliations, check activity, and inter-module transfers, allowing management and auditors to trace how and when financial changes were made.

Report Selection Criteria

  • Start Date / End Date β€” limits the audit window for reported activity.
  • Transaction Type β€” filters the report by journal category.
  • Dept # / Group # β€” restricts results to a specific department or group.
  • Sort Order β€” organize output by:
    • File #
    • Adjustment Date
    • GL Account
  • Summary or Detail β€” choose high-level totals or line-level detail.
  • Report or Spreadsheet β€” output format for review or analysis.

Supported Transaction Journals

  • ADJ β€” A/P Adjustment Journal
  • VIR β€” Vendor Invoice Reconciliation Journal
  • AVC β€” Vendor Credit Application Journal
  • CRN β€” Check Re-Numbering Journal
  • CRM β€” Check Removal Journal
  • ARX β€” A/R to A/P Transfer Journal
Audit Note: This report is commonly used during month-end close, internal audits, and troubleshooting unexpected balances or check activity.
Best Practice: Run the A/P Audit Journal immediately before and after period close to preserve a clear before/after snapshot of system activity.

Scheduled Invoices Aging Report

The Scheduled Invoices Aging Report provides an aging analysis of invoices that have been scheduled for payment, based on their scheduled payment date rather than the original vendor invoice date.

This report is especially useful for cash planning and payment forecasting, as it shows how scheduled obligations age relative to the date they are intended to be paid.

Report Selection Criteria

  • Aging Ending Date β€” date through which scheduled invoices are aged.
  • Specific Vendor (ALL) β€” limit results to a single vendor or include all.
  • Detail or Summary β€” choose invoice-level detail or vendor totals only.
  • Trade / Overhead / Both β€” include operational invoices, overhead expenses, or both.
  • Dept#/Group Code or All β€” restrict results to a department or reporting group.
  • Print Credits Only β€” optionally limit the report to credit balances.

Aging Buckets

  • Current β€” scheduled invoices not yet past due.
  • 16–30 / 31–45 / 46–60 / 61–90 β€” aging buckets based on the scheduled payment date.
  • Total Open Balance β€” total scheduled amount outstanding.
Key Difference: Unlike the standard Vendor Aging Report, this report ages invoices based on the scheduled payment date, not the vendor’s invoice date.
Best Practice: Use this report prior to check runs to identify upcoming payment concentrations and to avoid overdue scheduled obligations.

AP Activity by GL Acct#

Accounts Payable GL Activity produces an audit-friendly report that ties A/P activity back to your General Ledger. Use it to validate A/P postings by GL Account for a date range.

Detail output is typically used to compare against the GL Trial Balance (audit trail by vendor/invoice). Summary output is typically used to compare against the Profit & Loss (roll-up totals by GL account).

Report Criteria

  • Department or (A)ll β€” limit the report to a department, or include all departments.
  • Starting Date / Ending Date β€” defines the activity window to report.
  • (S)ummary or (D)etail β€” choose a roll-up (summary) or transaction-level (detail) report.
  • Vendor Account or (A)ll β€” optionally filter to a specific vendor account; otherwise include all.
  • Starting GL Account / Ending GL Account β€” restrict the GL range (useful for expense-only runs).
  • (O)pen, (C)losed or (B)oth β€” include only open items, only closed items, or both.
  • Summarize by Account? β€” controls whether totals are grouped by GL account (recommended for Summary output).
  • Print Option (R/S/E) β€” output destination/format (e.g., report/spreadsheet/export depending on setup).

What You’ll See on the Output

  • GL Account & Description β€” the GL buckets being reported.
  • Inv Amount / Pay Amount / Adj Amount β€” totals by activity type.
  • Xfer Amount β€” transfers impacting AP/GL totals (when applicable).
  • Net Amount β€” net impact for the account in the selected range.
  • Detail mode includes vendor/invoice references per GL account to support audit tracing.
Audit tip: When investigating a variance, run Detail for the specific GL account range, then trace the vendor/invoice references back to the posting source (invoice entry, adjustment, credit application, etc.).
Best Practice: Run Summary monthly for expense accounts and file it with month-end close support. Use Detail as needed for exception review and audit requests.

Accounts Payable – Bill Code Report

The Accounts Payable – Bill Code Report provides visibility into vendor invoices and payments grouped by Bill Code. This report is commonly used to analyze how specific cost categories (such as overhead, customs, freight, or other billable charges) are being billed and paid across vendors and time periods.

The report can be run in summary or detail format and optionally includes paid amounts, making it useful for both operational review and accounting reconciliation.

Selection Criteria

  • Dept#/Group or (A)ll β€” limit results to a specific department or include all.
  • Starting / Ending Date β€” restrict activity to a defined date range.
  • Starting / Ending Bill Code β€” focus on a specific range of bill codes.
  • Vendor Code or (A)ll β€” report on one vendor or all vendors.
  • Vendor Type or (A)ll β€” filter by vendor classification.
  • Sort by Vendor or Code β€” control report grouping and readability.
  • Include Paid Amount? β€” include or exclude payments already disbursed.
  • Summary or Detail β€” choose rolled-up totals or line-level transactions.
  • Report or Spreadsheet β€” output to on-screen report or spreadsheet format.

Report Output

  • Reference / Invoice Number β€” vendor invoice identifiers.
  • Invoice Date β€” date the invoice was entered.
  • Billed Amount β€” original invoice amount by bill code.
  • Paid Amount β€” amount paid (if included).
  • Adjustment Amount β€” credits or adjustments applied.
  • Bill Code & Description β€” identifies the cost category.
Audit Tip: Use the Summary option to reconcile totals against GL expense accounts, and the Detail option when tracing individual invoices or vendor activity.
Best Practice: Run this report regularly for overhead bill codes to ensure costs are being billed and paid consistently and no charges are overlooked.

Check Volume Summary Report

The Check Volume Summary Report provides a high-level overview of check activity for a selected date range. It summarizes the number of checks issued and the total dollar amount, grouped by vendor or bank.

This report is commonly used for cash management review, bank analysis, and internal audit support to validate payment volume and frequency.

Report Parameters

  • Bank Code or (A)ll β€” limit results to a specific bank or include all banks.
  • Company Code β€” company/entity issuing the checks.
  • Starting Check Date β€” beginning of the reporting period.
  • Ending Check Date β€” end of the reporting period.
  • Sort By β€” group results by Vendor or by Bank.
  • Summary by Period β€” optionally aggregate totals by period.

Report Output

  • Vendor / Account β€” payee receiving checks.
  • Total Amount β€” total dollars paid during the period.
  • Count β€” number of checks issued.
  • Report Total β€” grand total of all checks included.
  • Total Number of Checks β€” overall check count.
Audit Tip: Use this report to reconcile total check volume against bank statements and the Check Register for the same period.
Best Practice: Run this report monthly by bank to identify unusually high check counts that may indicate opportunities for ACH conversion.

Advanced Checks Report

The Advanced Checks Report identifies checks that were issued as advancesβ€”meaning the check was created and disbursed before the vendor invoice (and/or the customer billing record) was created in the system.

This is especially useful for auditing β€œmoney-out-first” scenarios (e.g., rush payments, deposits, customs/port advances, or operational advances) where the check exists but the invoice trail may be created later.

Selection Criteria

  • Department Code β€” limits the report to a specific department/group.
  • Starting Date / Ending Date β€” defines the date window for reporting (typically check date range).
  • Sorting Option β€” controls how the results are grouped:
    • A. Initials β€” groups by the operator/initials who created the advance.
    • B. Opened Date β€” sorts by the operational file open date.
    • C. File Number β€” groups/sorts by file number (common for audits by job/file).
  • Minimum Amount β€” filters out small advances; helps focus on material items.

What the Report Shows

  • File Number / Importer β€” operational context for the advance.
  • Initials β€” user/agent associated with the advance check.
  • Open Date β€” file open date (helps validate timing of the advance vs. activity).
  • Check Date / Check Amount β€” when/how much was disbursed.
  • Invoice-related dates (if present) β€” fields such as Inv. Date and other milestone dates shown on the report help confirm whether the invoice/billing record was entered later.
Best Practice: Run this report monthly (or at period close) with a meaningful Minimum Amount to quickly identify large advances that still need matching vendor invoices and/or customer billing entries.
Audit Tip: When researching an item, start from the File Number and confirm: (1) check creation/disbursement, (2) vendor invoice entry timing, and (3) whether the customer was billed (if the advance is billable).

File Profitability Report

The File Profitability Report provides a consolidated view of revenue, disbursements, adjustments, and net profit or loss by operational file. It is used to evaluate financial performance at the file level and supports both operational review and accounting audit workflows.

This report combines billing, A/P disbursements, cash receipts, and adjustments to calculate an estimated profit or loss for each file over a selected date range.

Report Selection Criteria

  • Dept # or (A)ll β€” limit results to a specific department or include all.
  • Starting / Ending Date β€” reporting period for file activity.
  • Report Option β€”
    • Loss Only Files β€” show files operating at a loss.
    • Profit Less Than β€” threshold-based filtering.
    • All Files β€” include all qualifying files.
  • Profit Less Than Amount β€” optional numeric cutoff.

Break & Output Options

  • Break Options β€”
    • Days
    • Month
    • Department
    • Department & Days
    • Department & Month
    • No Breaks
  • (O)per, (M)anual or (B)oth β€” operational vs manual files.
  • (S)ummary or (D)etail β€” level of financial detail.
  • Acct# or (A)ll β€” restrict to a specific GL account if needed.
  • (R)eport or (S)preadsheet β€” formatted report or export.
Audit Use: The Detail version is commonly used to reconcile file-level profitability against A/R, A/P, and GL activity during financial review.
Management Insight: The Summary version is ideal for identifying underperforming files and analyzing margin trends across departments or time periods.

Vendor Listing Report

The Vendor Listing Report provides a comprehensive directory of vendors defined in the Accounts Payable system. It is commonly used for compliance review, vendor audits, contact verification, and year-end reporting (e.g., 1099 preparation).

The report supports multiple sorting and filtering options, allowing users to generate listings by vendor number, name, type, or geographic location, with optional inclusion of tax identifiers and contact details.

Report Selection Options

  • Sorting Option β€” control report order:
    • By Vendor Number
    • By Vendor Name
    • By Vendor Type & Name
    • By Vendor City & Name
  • Vendor Type β€” limit report to a specific vendor classification or include all.
  • Flagged 1099 β€” include only vendors marked for 1099 reporting.
  • Contains EIN β€” filter vendors based on EIN availability.
  • State / City / Zip Code Range β€” geographic filtering options.
  • Activity Start / End Date β€” limit vendors based on transaction activity.

Output Options

  • Complete Address β€” include full mailing address.
  • Include Contact Info β€” print phone numbers, contact names, and email addresses.
  • Report / Spreadsheet β€” generate formatted report or exportable spreadsheet.
Use Case: This report is frequently used for vendor audits, compliance reviews, contact verification, and preparation for 1099 filing.
Best Practice: When preparing year-end tax reports, filter vendors by 1099 flag and include EIN and contact details to simplify reconciliation.

Tips & Best Practices

  • Start with Aging, then drill down. Use Vendor Aging or Scheduled Invoices Aging to identify exposure, then validate details using Outstanding Invoices, Vendor Activity, or AP Activity by File.
  • Use Scheduled reports for cash planning. Pair the Cash Requirements Report with Scheduled Invoices Aging to forecast near-term cash needs and avoid surprise check runs.
  • Separate operational vs overhead reviews. Most reports allow filtering by Trade / Operations vs Overhead. Use this consistently to keep freight costs, advances, and internal expenses clearly separated.
  • Validate before printing checks. Always run the Check Run Audit Report or Batch Proof Report before printing checks to confirm invoice selection, amounts, and departments.
  • Reconcile regularly, not just at month-end. Use the Check Reconciliation Report throughout the month to monitor cleared vs uncleared checks and identify missing, voided, or ACH transactions early.
  • Use File Profitability as a management tool. The File Profitability Report is not just for accounting β€” review loss-only or low-margin files to identify pricing issues, missed billings, or unbilled advances.
  • Leverage summary vs detail intentionally.
    • Summary β†’ management review, trend analysis, executive reporting
    • Detail β†’ audit support, GL tie-outs, transaction research
  • Use GL Activity reports for audit tie-outs. The AP Activity by GL Account (detail) should reconcile directly to the General Ledger trial balance and Profit & Loss statements.
  • Track advances explicitly. Run Paid Not Billed and Advanced Checks reports together to ensure all advances are eventually billed and cleared.
  • Export when reconciling externally. When sharing data with auditors or finance teams, use the Spreadsheet output option to speed reconciliation and documentation.

Frequently Asked Questions

Which report should I use to see what we owe vendors right now?

Start with the Vendor Aging Report for unpaid invoices based on invoice date. If invoices are already scheduled for payment, use the Scheduled Invoices Aging Report instead.

What’s the difference between Vendor Aging and Scheduled Invoices Aging?

Vendor Aging groups invoices by invoice date, while Scheduled Invoices Aging groups them by scheduled payment date. Scheduled Aging is more accurate for short-term cash forecasting.

How do I forecast upcoming cash requirements?

Use the Cash Requirements Report in conjunction with scheduled payment dates. This allows you to see expected cash outflows across multiple future date buckets.

Which report should I run before printing checks?

Run the Check Run Audit Report (or Batch Proof Report if using batch control) to verify invoice selection, amounts, and departments before printing checks.

How do I find invoices that were paid but never billed to customers?

Use the Paid Not Billed Report. This identifies advances and disbursements that have not yet been billed, helping prevent lost revenue.

What report should accounting use for month-end reconciliation?

Accounting typically uses:

  • AP Activity by GL Account (Detail) β€” GL tie-out
  • Check Reconciliation Report β€” bank reconciliation
  • AP Audit Journal β€” transaction history and controls
How can I review vendor-specific history?

Use the Vendor Activity Report for a timeline of invoiced and paid activity, or the Vendor Listing Report for vendor master data review.

What is the File Profitability Report best used for?

It is used to analyze revenue vs disbursements at the file level. Management often uses it to identify loss-making files, while accounting uses it to validate billing and cost allocation.

Why do some reports offer Summary vs Detail?

Summary reports are optimized for high-level review and trends, while Detail reports provide transaction-level data for audits, reconciliations, and troubleshooting.

When should I use spreadsheet output?

Spreadsheet output is recommended when reconciling with external accounting systems, sharing data with auditors, or performing custom analysis outside of FasTrax.