Run a Test of Details
This guide provides a quick reference for running a Test of Details. For the full walkthrough, see Your first dive: Test of Details.
Quick reference
- Go to Tests of Details → Click New
- Choose a TOD model (or create from scratch)
- Give the job a name (auto-suggested)
- Upload or select test sample (Excel) — download template first if needed
- Select documents to match from workspace
- Fill analysis/extraction variables (if required by model)
- Choose AI speed (fast or thorough)
- Click Launch
Test sample requirements
Your test sample (Excel file) should include:
- Unique identifier for each transaction (row number, transaction ID)
- Key matching fields — invoice number, date, amount, vendor name
- Clear column headers in the first row
Configuring the test
When creating a new TOD, you'll specify:
| Setting | Description |
|---|---|
| Test sample | Your Excel file with transactions |
| Document sources | Workspace folders containing evidence |
| Matching criteria | Fields to use for automatic matching |
| Extraction model | What data to extract from matched documents |
For a complete guide on building TOD templates — including a step-by-step revenue recognition example with 5 document types — see Create & Configure TOD Templates.
Processing time
Processing time depends on:
- Number of transactions in your test sample
- Number of documents to search through
- Complexity of extraction model
Typical jobs complete in 5-30 minutes.
Matching Documents
Matching links supporting documents to transactions in your Test of Details. This section covers how Moby matches automatically and how to handle manual matching.
How Moby matches automatically
Moby analyzes your test sample and supporting documents to find matches. It looks for common identifiers like:
- Invoice numbers
- Dates
- Amounts
- Vendor names
- PO numbers
- Other reference fields
The AI uses multiple signals together to find the best match, even when identifiers aren't exact.
Writing matching instructions
When creating a Test of Details, you can provide matching instructions to guide Moby. Good instructions dramatically improve matching accuracy, especially for complex documents.
Easy case — Unique identifiers available:
When documents have clear unique identifiers (invoice numbers, PO numbers), keep instructions simple:
Match invoices to transactions using invoice number.
If invoice number is missing, use vendor name + amount + date within 5 days.
Difficult case — No unique identifier (e.g., Bills of Lading):
For documents without unique IDs, guide Moby on what to look for:
Match Bills of Lading (BL) to shipment transactions.
Look for: shipper/supplier name, consignee, ports, shipment dates,
cargo description, container numbers.
Dates may differ by up to 2 weeks due to shipping delays.
Tips for matching instructions:
- Name key fields — Tell Moby what to look for (dates, amounts, names, references)
- Give context — "Dates may differ due to shipping delays", "Amounts include tax"
- Mention variations — "Supplier may appear as vendor, seller, or shipper"
- Indicate priority — "Supplier name is most important"
Handling bundled documents
If you have multiple documents packed into a single PDF (e.g., a bundle of invoices), Moby may struggle to match correctly.
Solution: Split the PDF first, then re-run your test on the separated files.
See Workspace Tools → Split PDF.
Manual match
If Moby can't find a match automatically, you can manually link a document to a transaction:
- Click the transaction row
- Select Match Document
- Browse or search for the correct document
- Confirm the match
Manual unmatch
If Moby matched the wrong document:
- Click the unlink icon on the matched document
- Confirm unmatch
- Manually select the correct document if needed
Handling low-confidence matches
Moby shows confidence scores for matches. Low-confidence matches are flagged for review.
What to check:
- Is the matched document actually related to this transaction?
- Are the key values (amount, date, vendor) correct?
- Is there a better matching document?
Low-confidence matches should always be manually verified before finalizing your workpaper.
Reviewing AI Results
Watch: Reviewing and Validating Results Learn how to use Grounding to verify data, handle exceptions, and export your workpaper.
Once Moby completes processing, you'll review and validate the AI's work. This is a critical step in ensuring audit quality.
Track your progress
Two progress bars help you track completion:
| Progress Bar | What it tracks |
|---|---|
| Documents Matched | How many documents have been linked to transactions |
| Control Progress | How many cells have been validated |
Understanding row statuses
| Status | Meaning | Action Required |
|---|---|---|
| Validated | All criteria met, transaction verified | None — ready for export |
| Review | Requires manual attention | Click to investigate |
| Exception | Discrepancy found | Review and document the exception |
| No match | No supporting document linked | Match manually or exclude |
Verify faster with grounding
Grounding is Moby's visual proof feature — showing exactly where extracted values came from in the source document.
How to use grounding:
- Click on any cell to see the grounding — a highlighted bounding box in the PDF preview
- Verify the highlighted area matches what you expect
- Check surrounding context to ensure the value is from the correct section
- Use keyboard shortcuts — Tab moves to the next cell, keeping the grounding panel open
Use grounding to quickly verify values without manually searching through documents. The highlighted area shows you exactly where Moby found each value.
If grounding is missing or incorrect:
- Click on the cell with missing grounding
- In the PDF preview, click Select grounding (or use the selection tool)
- Draw a box around the correct value in the document
- The grounding is saved automatically
For more comfort, detach the PDF preview into a separate window. This lets you view the document full-screen while keeping the results table visible.
Validating cells
Once you've verified a value is correct:
- Select cells — Click to select one, or Ctrl+Click for multiple
- Click the Validate button (✓) in the toolbar
- The cell status changes to validated
Batch validation: Select multiple cells or entire rows to validate in bulk when you've verified a group of similar transactions.
Making corrections
If Moby extracted incorrect data:
| Issue | Solution |
|---|---|
| Wrong value extracted | Double-click the cell to edit directly |
| Matched to wrong document | Use the unmatch button, then manually match the correct document |
| Missing document | Upload the document, then manually match it |
| Document not needed | Mark as excluded so it doesn't affect your progress |
Common review scenarios
Low confidence match:
- Moby matched a document but isn't certain
- Review the document carefully before validating
- Consider if matching criteria need adjustment
Value within tolerance:
- Small differences between reference and extracted values
- Decide if the variance is acceptable
- Document your conclusion
Multiple documents per transaction:
- Some transactions may have several supporting documents
- Review each document's extracted values
- Validate once all documents are reviewed