<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tf/gld/tfgld1251m100" xml:lang="en">
   <Header>
      <Title>Approve/Process Matched Transactions (tfgld1251m100)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph> Use this session to approve or process
		  matching transactions. You can also use this session to cancel unapproved
		  (status Matched), approved or processed matching transactions.</Paragraph>
      </AimSection>
      <Note>
         <SectionTitle> Note</SectionTitle>
         <List>
            <ListItem>Users who are authorized to approve matching transactions,
			 can only approve transactions within the tolerances that are defined for their
			 ledger accounts.</ListItem>
            <ListItem>One or more users can be authorized to approve other users'
			 matching transactions for their own ledger accounts and within their
			 tolerances.</ListItem>
            <ListItem>Any user can process matching transactions for their own set
			 of ledger accounts.</ListItem>
            <ListItem>A <Emphasis>super user</Emphasis> can match, approve, and
			 process matching transactions for any ledger account and for any
			 tolerance.</ListItem>
         </List>
      </Note>
      <RelatedTopics>
         <SectionTitle> Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/tf/onlinemanual/000348" role="manual">Account matching</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/tf/onlinemanual/000345" role="manual">The account matching process</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldGroup>
         <Title> Selection</Title>
         <FieldGroup>
            <Title> Selection Range</Title>
            <FieldHelp ID="leac.f" OtherIDs="leac.t">
               <Header>
                  <Title>Ledger Account</Title>
               </Header>
               <FuncDesc>A register used to record financial transactions and to
		accumulate the values of the transactions for reporting and analysis. The
		ledger accounts classify the transactions into categories such as revenues,
		expenses, assets, and liabilities.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="mcde.f" OtherIDs="mcde.t">
               <Header>
                  <Title>Matching Code</Title>
               </Header>
               <FuncDesc>A generated code used to group matched
		transactions.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="mtrn.f" OtherIDs="mtrn.t">
               <Header>
                  <Title>Match</Title>
               </Header>
               <FuncDesc>The type of match.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="maus.f" OtherIDs="maus.t">
               <Header>
                  <Title>Matched by</Title>
               </Header>
               <FuncDesc>The account matching user whose transactions must be
				approved or processed.</FuncDesc>
               <Note>
                  <SectionTitle> Note</SectionTitle>
                  <Paragraph>For users who can approve only their own matches, this
				  field shows their name.</Paragraph>
               </Note>
            </FieldHelp>
            <FieldHelp ID="madt.f" OtherIDs="madt.t">
               <Header>
                  <Title>Match Date</Title>
               </Header>
               <FuncDesc>The date when the transaction was matched.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="apus.f" OtherIDs="apus.t">
               <Header>
                  <Title>Approved by</Title>
               </Header>
               <FuncDesc>The account matching user who approved the
				transactions.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="apdt.f" OtherIDs="apdt.t">
               <Header>
                  <Title>Approval Date</Title>
               </Header>
               <FuncDesc>The date when the transaction was approved.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Report Options</Title>
            <FieldHelp ID="f.simulate">
               <Header>
                  <Title>Simulate</Title>
               </Header>
               <FuncDesc> If this check box is selected, ERP Enterprise approves or
				processes the matching transactions without storing the resulting transactions.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="f.print.report">
               <Header>
                  <Title>Print Report</Title>
               </Header>
               <FuncDesc> If this check box is selected, ERP Enterprise prints a report with the
				approved and processed transactions.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="f.print.errors">
               <Header>
                  <Title>Print Error Report</Title>
               </Header>
               <FuncDesc> If this check box is selected, ERP Enterprise prints an error report.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
      <FieldGroup>
         <Title> Processing</Title>
         <FieldGroup>
            <Title> Options</Title>
            <FieldHelp ID="f.approve">
               <Header>
                  <Title>Approve Matched Transactions</Title>
               </Header>
               <FuncDesc> If this check box is selected, matching transactions
				must be approved.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="f.process">
               <Header>
                  <Title>Process Approved Transactions</Title>
               </Header>
               <FuncDesc> If this check box is selected, matching transactions
				must be processed.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Options</Title>
            <FieldHelp ID="f.unapprove">
               <Header>
                  <Title>Unapprove Approved Transactions</Title>
               </Header>
               <FuncDesc> If this check box is selected, approved matching
				transactions must be unapproved.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="f.unmatch">
               <Header>
                  <Title>Unmatch Matched Transactions</Title>
               </Header>
               <FuncDesc> If this check box is selected, matching transactions
				that have not yet been approved, must be canceled.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="f.reset">
               <Header>
                  <Title>Reset Processed Transactions</Title>
               </Header>
               <FuncDesc> If this check box is selected, processed transactions
				are reset to the Matched status and the balance of the original match is
				changed. Any additional matching transactions created when those transactions
				were processed, will not be reversed.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Posting Data</Title>
            <FieldHelp ID="f.mtyp" OtherIDs="f.mtyp.desc">
               <Header>
                  <Title>Transaction Type</Title>
               </Header>
               <FuncDesc>A user-defined three-position code used to identify documents.
		The series linked to the transaction type give documents the sequence number.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="f.dsrn" OtherIDs="f.dsrn.desc">
               <Header>
                  <Title>Transaction Series</Title>
               </Header>
               <FuncDesc>A series of maximum four digits that is used to identify the
		transaction generated during the general ledger matching process.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="f.tref">
               <Header>
                  <Title>Transaction Reference</Title>
               </Header>
               <FuncDesc>A user-defined description of the transaction.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="f.tedt">
               <Header>
                  <Title>Transaction Entry Date</Title>
               </Header>
               <FuncDesc>The date you enter when you create the batch. Usually the
		transaction entry date is the current date. Only for backdated and antedated
		transactions, the transaction entry date differs from the current date.
		Internally, the transaction entry date is registered in local time.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="f.fyer" OtherIDs="f.fprd">
               <Header>
                  <Title>Fiscal/Reporting/Tax Year / Period</Title>
               </Header>
               <FuncDesc>A separate period, or year for financial purposes.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListIntro>There are three types of periods:</ListIntro>
                     <ListItem>Fiscal, in which all transactions are recorded (for example,
			 12 months).</ListItem>
                     <ListItem>Reporting, for management requirements (for example, 52
			 weeks).</ListItem>
                     <ListItem>Tax, for tax regulations (for example, 4 quarters).</ListItem>
                  </List>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="f.ryer" OtherIDs="f.rprd">
               <Header>
                  <Title>Reporting Year / Period</Title>
               </Header>
               <FuncDesc>A separate period, or year for financial purposes.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListIntro>There are three types of periods:</ListIntro>
                     <ListItem>Fiscal, in which all transactions are recorded (for example,
			 12 months).</ListItem>
                     <ListItem>Reporting, for management requirements (for example, 52
			 weeks).</ListItem>
                     <ListItem>Tax, for tax regulations (for example, 4 quarters).</ListItem>
                  </List>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="f.vyer" OtherIDs="f.vprd">
               <Header>
                  <Title>Tax Year / Period</Title>
               </Header>
               <FuncDesc>A separate period, or year for financial purposes.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListIntro>There are three types of periods:</ListIntro>
                     <ListItem>Fiscal, in which all transactions are recorded (for example,
			 12 months).</ListItem>
                     <ListItem>Reporting, for management requirements (for example, 52
			 weeks).</ListItem>
                     <ListItem>Tax, for tax regulations (for example, 4 quarters).</ListItem>
                  </List>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="f.bref">
               <Header>
                  <Title>Batch Reference</Title>
               </Header>
               <FuncDesc/>
               <SimpleSection>
                  <List>
                     <ListIntro>Any informative description field used to refer to, for
			 example:</ListIntro>
                     <ListItem>The person or department with authorization to perform a
			 specific task.</ListItem>
                     <ListItem>The business partner's contact.</ListItem>
                     <ListItem>The original invoice number.</ListItem>
                  </List>
               </SimpleSection>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
   </Fields>
</Session>