<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tf/integrations/400018" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">To determine the financial period</Title>
		<Keyword><Level1>Integration transactions</Level1>
			<Level2>financial period</Level2>
		</Keyword>
		<Keyword><Level1>Mapping scheme</Level1>
			<Level2>financial period</Level2>
		</Keyword>
		<Keyword><Level1>Financial period</Level1>
			<Level2>of integration transactions</Level2>
		</Keyword>
	</Header>
	<GeneralSection><List><ListIntro>For every integration transaction, the following financial period data is logged:</ListIntro>
			<ListItem>Fiscal year and Fiscal period.</ListItem>
			<ListItem>Reporting year and Reporting period.</ListItem>
			<ListItem>Tax year and Tax period.</ListItem>
		</List>
		<List><ListIntro>If <Link href="/baanerp/tf/glossary/glossary#000451" role="glossary">Operations Management</Link> transactions are posted to <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>, four types of dates are involved:</ListIntro>
			<ListItemHead>Transaction date</ListItemHead>
			<ListItem>The date you enter when you create the transaction such as a sales order or a warehouse receipt. Usually the transaction date is the current date except for backdated and antedated transactions. Internally, the transaction date is registered in <Link href="/baanerp/tc/glossary/glossary#100000" role="glossary">UTC time</Link>.</ListItem>
			<ListItemHead>Document date</ListItemHead>
			<ListItem>The transaction date in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>. The document date is always registered in local time. Usually the document date is the same date as the transaction date, except if you manually enter a different transaction date in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> or if the UTC time and the local time differ by a day.</ListItem>
			<ListItemHead>Creation date</ListItemHead>
			<ListItem>The date and time when the transaction is created. For backdated and antedated transactions, the creation date differs from the transaction date.</ListItem>
			<ListItemHead>Posting date</ListItemHead>
			<ListItem>The date and time (local time) when the transaction is posted.</ListItem>
		</List>
		<Paragraph>Usually, the financial transactions are posted in a fiscal period that corresponds with the transaction date. The posting date and the document date are in the same fiscal period. However, if a transaction is antedated or if the transaction date is near the end of a fiscal period, the fiscal period can be already Closed when the related financial transaction is posted. Usually, this is today’s date and year.</Paragraph>
		<Paragraph>To log the integration transactions, the financial period status must be <GUIRef href="/baanerp/tf/domains/gld.sper#open" role="enum">Open</GUIRef> for <GUIRef href="" role="manual">Integration transactions (INT)</GUIRef>. Usually, if the transaction date is the current date, the financial periods are <GUIRef href="/baanerp/tf/domains/gld.sper#open" role="enum">Open</GUIRef>. However, at the end of a fiscal period or a fiscal year, or if a transaction is backdated, the financial period status can be <GUIRef href="/baanerp/tf/domains/gld.sper#closed" role="enum">Closed</GUIRef>.</Paragraph>
		<Paragraph>You can view and maintain the financial period status in the <GUIRef href="/baanerp/tf/gld/tfgld0107m000" role="session">Period Status (tfgld0107m000)</GUIRef> session.</Paragraph>
		<GeneralSection><SectionTitle>If the period is <GUIRef href="/baanerp/tf/domains/gld.sper#closed" role="enum">Closed</GUIRef></SectionTitle>
			<Paragraph>For reconciliation, only the fiscal period is considered. Therefore, if a tax period or the reporting period is <GUIRef href="/baanerp/tf/domains/gld.sper#closed" role="enum">Closed</GUIRef>, SSA ERP automatically posts the transaction to the next open tax period or reporting period.</Paragraph>
			<Paragraph>If the fiscal period is <GUIRef href="/baanerp/tf/domains/gld.sper#closed" role="enum">Closed</GUIRef> for integration transactions (INT), the transaction cannot be logged. SSA ERP displays an error message on the user’s screen. The transaction is not logged. However, ift he period is still open for general ledger (GLD), you can still want to post the transaction to the period.</Paragraph>
			<List><ListIntro>To solve the problem, you can do one of the following:</ListIntro>
				<ListItem>In the <GUIRef href="/baanerp/tf/gld/tfgld4585m000" role="session">Requested Exceptions for Integration Transactions (tfgld4585m000)</GUIRef> session, enter a request to log to the Integration transactions logging period with status <GUIRef href="/baanerp/tf/domains/gld.sper#closed" role="enum">Closed</GUIRef> for integration transactions (INT). After an authorized user has approved the request, the transaction can be logged although the fiscal period is <GUIRef href="/baanerp/tf/domains/gld.sper#closed" role="enum">Closed</GUIRef> for Integration transactions. You do not need to set the period to <GUIRef href="/baanerp/tf/domains/gld.sper#open" role="enum">Open</GUIRef> to log the transaction. This is the usual solution to log and post transactions to the fiscal period that corresponds with the transaction date.</ListItem>
				<ListItem>Change the transaction date to a date in the next fiscal period that is <GUIRef href="/baanerp/tf/domains/gld.sper#open" role="enum">Open</GUIRef> for Integration transactions.</ListItem>
				<ListItem>In some cases, you can enter a request in the <GUIRef href="/baanerp/tf/gld/tfgld4585m000" role="session">Requested Exceptions for Integration Transactions (tfgld4585m000)</GUIRef> session to post the transaction to the next open fiscal period. As a result, the transaction date is outside the fiscal period to which the transaction is posted. This makes matching of logistic reports and financial reports more difficult. You can print a report of the requests for exceptions in the <GUIRef href="/baanerp/tf/gld/tfgld4485m000" role="session">Print Next-open-period Transactions (tfgld4485m000)</GUIRef> session, and use this during reconciliation.</ListItem>
			</List>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>You can only enter a request for exception if the <GUIRef href="/baanerp/tf/gld/tfgld4150s000#tfgld450.pnop" role="formfield" Update="No">Period Handling Exceptions Allowed</GUIRef> check box is selected in the <GUIRef href="/baanerp/tf/gld/tfgld4150s000" role="session">Integration Parameters (tfgld4150s000)</GUIRef> session.</Paragraph>
				<Paragraph>The employees who have permission to run the <GUIRef href="/baanerp/tf/gld/tfgld4585m100" role="session">Approve Requested Exceptions for Integration Transactions (tfgld4585m100)</GUIRef> session are authorized to approve the requests.</Paragraph>
				<Paragraph>You cannot log transactions for a financial period that has the <GUIRef href="/baanerp/tf/domains/gld.sper#finally.closed" role="enum">Finally Closed</GUIRef> status. Periods should only be set to <GUIRef href="/baanerp/tf/domains/gld.sper#finally.closed" role="enum">Finally Closed</GUIRef> when the financial year is closed.</Paragraph>
			</Note>
		</GeneralSection>
		<GeneralSection><SectionTitle>Period handling exceptions in reconciliation</SectionTitle>
			<Paragraph>If the transaction is posted to the next <GUIRef href="" role="manual">Open</GUIRef> period, the transaction date is outside the fiscal period. This makes the reconciliation process more complex.</Paragraph>
			<Paragraph>For the <GUIRef href="" role="manual">Invoice Accrual 3</GUIRef> reconciliation group which represents the Goods Received not Invoiced (GRNI), if you print reconciliation reports with the <GUIRef href="/baanerp/tf/gld/tfgld4495m200" role="session">Checklist Reconciliation Goods Received Not Invoiced (tfgld4495m200)</GUIRef> session, the financial transaction is reported in the fiscal period of the document date instead of the posting date.</Paragraph>
		</GeneralSection>
		<Note><SectionTitle>Note</SectionTitle>
			<List><ListIntro>In general, backdated transactions make the reconciliation process more complex. To avoid the generation of errors when the currency differences and rounding differences are calculated, logging antedated transactions with a transaction date earlier than the most recent archiving date of the reconciliation data is not allowed for the following reconciliation areas:</ListIntro>
				<ListItem>Inventory.</ListItem>
				<ListItem>Consignment Inventory.</ListItem>
				<ListItem>Assembly Line WIP.</ListItem>
			</List>
		</Note>
		<ExampleSection><SectionTitle>Example</SectionTitle>
			<Paragraph>If you received goods late on 31 January and you register the receipt on 1 February but with a transaction date of 31 January, the following situation occurs. The posting date and the document date differ.</Paragraph>
			<TABLE border="1"><TBODY><TR><TD></TD>
						<TD width="221">Fiscal period 101/01 – 01/31</TD>
						<TD width="217">Fiscal period 202/01 – 02/28</TD>
					</TR>
					<TR><TD>Operations Management transaction</TD>
						<TD width="221">Receipt: Transaction date = 01/30 Document date = 01/30</TD>
						<TD width="217"></TD>
					</TR>
					<TR><TD>Financial transaction</TD>
						<TD width="221"></TD>
						<TD width="217">Receipt: Posting date = 02/01 Backdated: Document date = 01/30</TD>
					</TR>
				</TBODY>
			</TABLE>
		</ExampleSection>
	</GeneralSection>
	<RelatedTopics><SectionTitle>Related topics</SectionTitle>
		<RelTopic><Link href="/baanerp/tf/integrations/400012" role="manual">To process integration transactions</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/tf/integrations/400034" role="manual">The reconciliation process</Link>
		</RelTopic>
	</RelatedTopics>
</ManualTopic>
