Why look at these tabs?
When a receipt comes out differently to how you expected, these two tabs show you XBert's working:
Extracted Text is what XBert read off the receipt.
Audit Trail is every step XBert took, in order, with times.
Between them, they answer the question you'll actually be asking: did XBert misread the document, or did it read it correctly and code it differently to how you would have?
š” You don't need these for everyday receipts
They're there for when something looks wrong, when a receipt has failed, or when you want to see exactly what happened before you publish.
Open the tabs
In the left-hand menu, click Receipt Capture.
Click the receipt in the list.
The preview panel opens on the right, on the Details tab.
Down the right-hand side of the panel, click Extracted Text or Audit Trail.
Hover over each icon to see its name.
You can also get here from a Receipt Capture work item by clicking View.
š Read more here: How To: Open and Preview a Captured Receipt
Extracted Text: what XBert read
The Extracted Text tab shows the text XBert read off the receipt, tidied up so it's easy to read.
Use it to check:
whether the supplier, date, reference or total were printed on the receipt at all
whether a line XBert got wrong was actually printed that way
whether a photo was too blurry, too dark or too crooked to read properly.
If a detail isn't in the extracted text, XBert couldn't read it off the receipt. Correct it on the edit screen before you publish.
š” If you see No extracted text available
XBert hasn't read the receipt yet, or reading it failed. Check the receipt's Stage on the Receipt Capture page.
š Read more here: How To: Resolve and Reprocess Failed or Duplicate Receipts
Audit Trail: what happened, and when
The Audit Trail tab lists every step, newest first, grouped by day under Today, Yesterday or the date.
Each entry shows:
what happened
a System badge if XBert did it, or the person's name if someone on your team did
the time. Hover over it for the full date and time.
Some entries have more behind them. Open one to see the detail, such as the suppliers XBert matched against and how closely each one matched, or the totals it pulled off the receipt.
If you see No audit trail available, nothing has been recorded for that receipt yet.
What you'll see in the audit trail
Entry | What it means |
Document '...' uploaded for processing | The receipt arrived, whoever sent it and however it came in. |
Document queued for processing | It's waiting its turn to be read. |
Document processing started | XBert started reading it. |
Account code predictions completed for N line item(s) | XBert coded the lines to accounts. |
Tax code predictions completed for N line item(s) | XBert set the tax rate on each line. |
Tracking category predictions completed | XBert set your client's tracking categories on the lines. |
Extraction summary created for [supplier] | XBert finished pulling the receipt's details together. |
Notification N created from receipt capture | The Receipt Capture work item was created. Notification is the work item. |
Document processing completed successfully | XBert finished with the receipt. It's ready for you to check. |
Memory considered when ...: N presented, N cited | XBert used what it remembers about this supplier. Cited means it acted on it. |
Duplicate of '...' detected | The same file had already been sent in, so this copy was paused. The entry names the original. |
Processing failed at step '...' | Reading the receipt failed. The entry names the step it failed at and why. |
Document flagged for manual review | XBert couldn't finish on its own and someone needs to look at it. |
User corrected ... or User reverted ... | Someone on your team changed the receipt. Their name is on the entry. |
You may see other entries too. XBert records each check it runs, including how it reconciled the tax against the total.
What the audit trail is good for
A receipt that's stuck. The failed entry names the step, so you know whether it's worth reprocessing.
Working out who changed what. Every entry is either System or a person's name.
Checking whether a memory was used. If XBert coded something an unexpected way, a memory entry usually explains it.
Seeing how long a receipt took, from arriving to finishing.
š Read more here: How To: Add and Manage Supplier Memories from a Captured Receipt
What's next
Need help?
If you have any questions, our support team is here to help!
Reach out via the chat widget on the bottom left of your XBert screen (Help), or email us at support@xbert.io