How to Verify Paxy Answers

Last reviewed: June 9, 2026

On this page

Use this workflow to review a Paxy answer before making a business decision from it.

When to verify

Verify Paxy answers whenever the result affects accounting, customer communication, purchasing, inventory, production, shipping, or management decisions.

Paxy is useful for fast reporting, but users should still confirm important answers against source records, formal reports, or the workflow that owns the data.

Before you start

You need:

The original Paxy question.
The Paxy answer, findings, notes, and row count.
CSV export if you need row-level support.
Access to the PAX screen or report that owns the data.

Screen path

Dashboard > Paxy launcher > Review answer

Steps

Read the answer sentence.
Review Findings.
Review Notes for caveats, row caps, or interpretation warnings.
Check the row count and whether a preview cap was applied.
Export CSV if you need the supporting rows.
Compare the source rows against the normal PAX screen or report.
Ask a narrower follow-up question if the answer is too broad.
Use the normal PAX workflow for any correction, posting, adjustment, or record change.

Do not use a Paxy answer alone to justify forcing accounting, inventory, costing, or audit results.

Where to verify common answers

Paxy question type	Verify in PAX
Customer sales, invoice totals, overdue invoices, customer statements	Invoicing Overview, Invoice Report Overview, Sales Analysis Report Overview, AR Aging Report Overview
Open orders, backlog, backorders, part demand	Open Orders Overview, Open Orders by Part Number Overview, Backlog Report Overview, Backorder Report Overview
Inventory on hand, lot details, inventory value, usage	Parts Overview, Inventory Item Detail Overview, Inventory Lot Detail Overview, Detailed Inventory Report Overview
Manufacturing, work orders, BOMs, routers, labor, completions	Work Orders Overview, Work Order Detail Overview, BOMs Overview, Routers Overview, Log Labor / WIP to FG Overview
Vendor activity, purchase orders, receipts, payables	Purchase Orders Overview, Open Purchase Orders Overview, Receiving Overview, Vendor Invoices Overview, AP Aging Report Overview
GL, trial balance, income statement, balance sheet, projects	General Ledger Overview, Trial Balance Overview, Income Statement Overview, Balance Sheet Overview, Projects Overview
Tax and compliance	Sales Tax by City Overview, 1099 Vendor Report Overview, Invoice Revenue Reconciliation Overview

What happens behind the scenes

Paxy answers are based on a capped reporting result. The chat preview is capped at 500 rows and 50 columns. PDF supporting detail is capped at 50 rows and 6 columns. CSV export can include more rows, up to the export cap.

Paxy includes source tables, source fields, and calculation notes when available. Use those notes to understand whether the answer is based on invoices, sales orders, receipts, journal entries, or another data source.

Troubleshooting

The answer looks too high or too low

Likely cause: The question may have used a different basis than expected, such as invoice date instead of order date, invoice totals instead of line totals, or all statuses instead of open records.

Safe fix: Ask a narrower follow-up question that states the basis clearly.

Contact support if: The source rows are wrong or contradict the normal report.

The CSV rows do not match the answer I expected

Likely cause: The question may have been interpreted differently than intended.

Safe fix: Review the report basis lines at the top of the CSV and ask a corrected question.

Contact support if: The report basis is correct but the rows are inaccurate.

I need to correct a record after reviewing Paxy

Likely cause: Paxy found a data issue, but Paxy cannot make changes.

Safe fix: Use the normal PAX screen or workflow that owns the record. Do not make a manual journal entry, inventory adjustment, or workaround unless that is the correct approved workflow.

Contact support if: The correct workflow is blocked or unclear.