Skip to review results

Accounts payable · Experimental workspace

See the whole PO story.

Bring deliveries, invoices and payment allocations into one clear review. Find the differences. Understand what to check next.

Local by design

CSV stays in this browser. No analytics, document API or browser storage on this page.

Use fictional data for evaluation. Downloads, printouts and browser/OS restoration remain under your control.

Start your review

Try the fictional examples first. For manual uploads, use only fictional or explicitly authorized sanitized CSV files. No account needed.

Testing LineAudit? Select Try sample data, open a highlighted discrepancy and one source reference, then share three quick observations. No company records needed.

Review overview

LineAudit v2.4 — cumulative review

Snapshot quantities only. Findings require human verification. This report never authorizes or confirms a payment. Bank payment status: Not verified.

Positions reviewed—Across the supplied POs
Quantity differences—Check the cited source documents
Needs human review—Missing data or unresolved context
Within supplied limits—No payment approval implied

A position can have a quantity difference and also need context review. These counts may overlap.

How to use this report

  1. Check quantity differences against the cited PO, invoice and receiving records.
  2. Resolve missing history, credits, returns and payment allocations with the responsible AP or receiving colleague.
  3. Use your normal approval controls before changing payment decisions. Within supplied limits is not payment authorization.

Scope: a manually supplied CSV snapshot. No automatic verification of bank settlement, approved PO amendments, currency conversion, tax or discounts. All positions and source references follow, irrespective of screen filters.

1 · Choose files

Add your documents

Choose CSV exports for purchase orders, deliveries and supplier invoices below. One file can contain several documents. Payment allocations are optional. PDF files cannot be imported.

  1. Purchase orders

    The quantities, units and prices you agreed.

  2. Deliveries & returns

    What arrived, including linked returns.

  3. Invoices & credits

    All supplier invoice lines and credit notes.

  4. Payment allocations

    Explicit quantity allocations per invoice line; bank status is not verified.

More sample examples

Explore another fictional dataset. Selecting it replaces the current inputs and review; no documents are sent anywhere.

Advanced settings · CSV editors & format guide

Use exact sample headers. Commas or semicolons, quoted cells and BOM are supported; semicolon files support decimal commas. Maximum 75 KB / 500 rows per CSV. A header-only transaction file represents no imported records, not proof of zero.

Identity is supplier + PO + line ID, not SKU alone. IDs are case-sensitive; SKU, units and currency are uppercased. No currency/unit conversion, tax/discount calculation, approved-variation inference or PDF/OCR input.

Quantities use unsigned decimals with up to 3 fractional places; prices allow 4. ISO dates: YYYY-MM-DD. Empty required numbers are invalid, never zero. Returns/credits/refunds use positive quantities and an explicit reversal kind. reference_id + reference_line_id identify the original document line.

Allocated paid qty means an explicitly supplied quantity allocation, not an amount or verified bank settlement. Payments name an invoice and its line. Refunds also reference their original payment line. Different IDs for the same real document cannot reliably be detected.

2 · Confirm which records are included

Check a box only when all those records for the supplied purchase orders are included. If you are unsure, leave it unchecked: missing values stay Unknown. Changing a file or editing the data clears these confirmations.

3 · Check documents

Read each reason and recommended action below. Select a source reference to see its document history. Nothing is sent to a server.

Position details

Know what needs attention.

CSV and PDF include every position, source reference and recommended action, regardless of filters.

Practitioner feedback

Could this save your team time?

After trying the fictional examples, please reply wherever you received this demo link (for example, in the Reddit discussion). If you were invited by email, reply to that email instead. Three quick questions help us improve it:

  1. Which example or explanation was unclear?
  2. What supporting evidence would you expect to see?
  3. Would this help you investigate real invoice discrepancies? Why or why not?

Feel free to be critical. Please do not share actual invoices, supplier details or confidential documents.

Send a quick email review Request a free 10-minute pilot

Opens your own email application. No messages or documents are submitted by LineAudit; please do not include real company documents or confidential information.

Share your observations in the public LinkedIn discussion (sign-in may be required), or reply directly to whoever sent you this demo. We never send your CSV or report to LinkedIn.