Upload the invoice, its ticket pages and your PO and job list. Ticket Match matches each ticket to the invoice line, the PO and the job, and lists what is missing, billed twice or billed wrong.
| Flag | Ticket | At risk |
|---|---|---|
| Duplicate | 104511 | $1,703.52 |
| No ticket | 104540 | $1,766.25 |
| Quantity | RA-104512 | +$72.00 |
| Rate | RA-104521 | +$26.93 |
| Over PO | RA-104522 | $113.60 |
| No PO | RA-104530 | $388.24 |
| Not billed | RA-104532 |
Once a month per supplier: start a run, drop in the invoice and the ticket pages, check what was read beside each page, approve. The exception sheet is what you take to the supplier before the invoice is paid.
Reads the invoice and the tickets from text PDFs, Excel and CSV
A text PDF is read for you, and a row is marked for checking when its ticket number or quantity is not in the page's text. A spreadsheet is read by its columns, chosen once per supplier's layout.Matches every ticket to its invoice line, PO and job, not a sample of them
"RA-0104511", "Tkt 104511" and "104511" are one ticket once you give the supplier's prefix. A line with no ticket number matches on date, material and quantity.Lists tickets not billed, lines with no ticket, duplicate tickets, quantity and rate differences, and tickets with no PO or job
It also checks each line's quantity times rate against its amount, and adds up deliveries on each PO from month to month against the PO quantity.Shows the dollars at risk for each flagged line, with a CSV export for Excel and a PDF summary
Each flag stays open on the exceptions list until you resolve it with a note: the credit memo, the ticket that turned up.The reading model only reads pages into rows; matching and flagging are fixed rules, the same every month. Nothing reaches the sheet until you approve the run.
Run the sample invoice, or upload one invoice, its tickets and your PO list as CSV or Excel with just your email address. The files are read in memory and not kept.
Checking by hand runs about 90 seconds a ticket by one vendor's count, so a 200-ticket invoice is most of a day of clerk time, and most firms spot-check a few. One duplicate load or overbilled ticket a month can cost more than the subscription. Card, month to month, no sales call.
Up to 50 suppliers, invoices and ticket packs of up to 1,000 rows each, PDF, Excel and CSV reading, the exception sheet with CSV and PDF exports, and a monthly reminder on the day your invoices arrive.
Cancel any time.
Questions first? ticket-match@coinudge.com
The supplier's invoice, the ticket pages that came with it, and your PO and job list as a CSV or Excel file. You map the columns of the PO list once and it remembers them. There is no connection to your accounting system.
Not automatically. Text PDFs, Excel and CSV are read for you. A scanned page has no text to read, so you type its ticket number, date, material, quantity, job and PO beside the page preview, and it is matched with the rest.
Yes. You see each page beside the rows read from it, fix any, and approve before anything appears in the exception list. The matching itself is fixed rules, not a guess.
Tickets received but not billed, invoice lines with no ticket, the same ticket billed twice, billed quantity that differs from the ticket, billed rate that differs from the PO, tickets whose PO or job is not on your list, and lines where quantity times rate does not equal the amount.
No. It reads what you upload and gives you a list to act on. Files and rows are kept for 13 months, then deleted.
Yes. Run the sample invoice and tickets, or run your own invoice, tickets and PO list (as CSV or Excel) with just your email address, and see the exception list before you subscribe. PDFs are read in the app.