Receipt review notes

These notes do not usually change the daily review flow, but they do matter when a receipt behaves differently than a reviewer expects.

Header Corrections Are Limited

In Sifterra Expense Review, the main editable header field is the Document Date.

These header fields are shown for review but are not editable on the expense review page:

• merchant name
• receipt type
• total amount
• status and confidence details

If one of those values is wrong, you can still review the document and correct the line coding, but the header itself is not designed for direct correction in the current page.

Line Review Focuses On Amount And Coding

The expense line staging table includes fields for Quantity and Unit Price, but the current expense processor and review page do not populate or present them as part of the normal receipt review flow.

In practice, reviewers are working mainly with:

• description
• total amount
• expense account
• pattern information
• dimensions
• balancing account
• confidence

Pattern Dimensions Are Not Applied Automatically

Expense patterns can store default dimension values, but the current receipt processing flow does not automatically copy those dimension defaults onto the expense lines during matching.

If your team needs dimensions on the final journal lines, reviewers should check and enter them during review.

Auto-Learning Can Create Broad Rules

When auto-learning is enabled, Sifterra creates learned patterns from approved receipts. In the current implementation, those learned patterns are based on a shortened text match rather than the full merchant or line description.

That can be useful for repeated spending, but it can also produce rules that are broader than expected. Review auto-created patterns regularly, especially if multiple merchants or charge types begin landing in the same account.

”Complex” Means More Than One Item

The current system marks a receipt as complex when it detects more than one itemized line. That is useful, but it is simpler than a human review standard.

A receipt may still need careful review even if it is not marked complex.

Pattern Detail Tracking Is Partial

Reviewers can see whether a pattern matched and can see the matched pattern text. The underlying line record also has a field for the matching pattern entry number, but the current processor path does not fully populate that deeper link during normal matching.

For day-to-day review, this usually does not block work, but it limits detailed traceability.