<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tf/acp/tfacp0111m001" xml:lang="en">
   <Header>
      <Title>Discrepancy Reasons (tfacp0111m001)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to define discrepancy reason codes. You can use
		  the discrepancy codes to indicate the types of discrepancies.</Paragraph>
         <Paragraph>If ERP Enterprise detects a discrepancy between the procurement card
		  statement and the data against which it is matched, you can select a
		  discrepancy reason code. The statement line is added to the discrepancy report.</Paragraph>
         <Paragraph>To match statement lines of the <GUIRef href="" role="manual">Others</GUIRef> line
		  type category, the discrepancy reason is mandatory. Therefore, you must define
		  at least one discrepancy reason code. For example, you can define a discrepancy
		  reason code with the description Not Applicable, to be used if no specific
		  discrepancy reason can be indicated.</Paragraph>
      </AimSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/tf/onlinemanual/000318" role="manual">Procurement card payments</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/tf/onlinemanual/000319" role="manual">To set up procurement card processing</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tfacp011.code">
         <Header>
            <Title>Discrepancy Reason</Title>
         </Header>
         <FuncDesc>Create a code to identify discrepancies that can arise while
		  the transactions are being processed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="form.text">
         <Header>
            <Title>Text</Title>
         </Header>
         <FuncDesc>If this check box is selected, a text exists with details about the
		  discrepancy exists.</FuncDesc>
      </FieldHelp>
   </Fields>
</Session>