<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.grooper.com/index.php?action=history&amp;feed=atom&amp;title=AI_Transaction_Detection</id>
	<title>AI Transaction Detection - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.grooper.com/index.php?action=history&amp;feed=atom&amp;title=AI_Transaction_Detection"/>
	<link rel="alternate" type="text/html" href="https://wiki.grooper.com/index.php?title=AI_Transaction_Detection&amp;action=history"/>
	<updated>2026-04-30T11:56:19Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.42.3</generator>
	<entry>
		<id>https://wiki.grooper.com/index.php?title=AI_Transaction_Detection&amp;diff=30935&amp;oldid=prev</id>
		<title>Dgreenwood: Created page with &quot;{{stubs}} The following is a placeholder taking from the Grooper Release Notes. More information on this topic can be found on your Grooper install&#039;s Help page.   AI Transaction Detection: New LLM-enabled Section Extract Method * A “transaction” is a repeating data structure on a document, such as employee records in payroll reports or claims in an EOB. * This is a specialized AI-powered section extract method designed for documents containing multiple, similarly str...&quot;</title>
		<link rel="alternate" type="text/html" href="https://wiki.grooper.com/index.php?title=AI_Transaction_Detection&amp;diff=30935&amp;oldid=prev"/>
		<updated>2025-09-09T18:23:43Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;{{stubs}} The following is a placeholder taking from the Grooper Release Notes. More information on this topic can be found on your Grooper install&amp;#039;s Help page.   AI Transaction Detection: New LLM-enabled Section Extract Method * A “transaction” is a repeating data structure on a document, such as employee records in payroll reports or claims in an EOB. * This is a specialized AI-powered section extract method designed for documents containing multiple, similarly str...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{stubs}}&lt;br /&gt;
The following is a placeholder taking from the Grooper Release Notes. More information on this topic can be found on your Grooper install&amp;#039;s Help page.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
AI Transaction Detection: New LLM-enabled Section Extract Method&lt;br /&gt;
* A “transaction” is a repeating data structure on a document, such as employee records in payroll reports or claims in an EOB.&lt;br /&gt;
* This is a specialized AI-powered section extract method designed for documents containing multiple, similarly structured transactions that may not be separated by explicit page breaks or static delimiters.&lt;br /&gt;
*AI Transaction Detection’s core is its “anchor-based boundary detection”.&lt;br /&gt;
**The LLM is presented with a “detection window” (the starting N pages of the document) and is asked to identify a set of “anchor” features. &lt;br /&gt;
**Anchors could be static text labels, regular expressions or other structured patterns that reliably indicate where each transaction starts. &lt;br /&gt;
**The anchors are then matched against each line of the document, and each line is given a score based on how many anchors are matched. Lines must meet a minimum threshold to be considered a boundary point. &lt;br /&gt;
**For each detected boundary, a new section instance is created, representing a single transaction.&lt;br /&gt;
*AI Transaction Detection differs from AI Collection Reader in how section boundaries are detected and then extracted.&lt;br /&gt;
**AI Collection Reader splits the document into chunks of N pages and runs extraction on each chunk.&lt;br /&gt;
***Issues can occur where sections span pages.&lt;br /&gt;
***Works for a wide variety of documents.&lt;br /&gt;
**AI Transaction Detection splits the document into transactions, then runs extraction on each transaction.&lt;br /&gt;
***Handles sections that span pages well.&lt;br /&gt;
***Specialized for transaction-based documents.&lt;/div&gt;</summary>
		<author><name>Dgreenwood</name></author>
	</entry>
</feed>