<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tp/onlinemanual/000324" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Costing posting types</Title>
	</Header>
	<GeneralSection><List><ListIntro>A posting type is used to clarify project processes and come from one of the following origins:</ListIntro>
			<ListItem>Manual Registration</ListItem>
			<ListItem>Invoicing via Finance without a purchase order.</ListItem>
			<ListItem>Hours Registration.</ListItem>
			<ListItem>Direct Delivery.</ListItem>
			<ListItem>Delivery via warehouse.</ListItem>
		</List>
		<Paragraph>The following list provides the transaction origin and the cost types: %PBO(C)</Paragraph>
		<TABLE border="1"><TBODY><TR><TD colspan="6">Commitments</TD>
				</TR>
				<TR><TD>-</TD>
					<TD>material</TD>
					<TD>labor</TD>
					<TD>equipment</TD>
					<TD>subcontracting</TD>
					<TD>sundry</TD>
				</TR>
				<TR><TD>1</TD>
					<TD>x</TD>
					<TD></TD>
					<TD>x</TD>
					<TD>x</TD>
					<TD>x</TD>
				</TR>
				<TR><TD>2</TD>
					<TD></TD>
					<TD></TD>
					<TD></TD>
					<TD></TD>
					<TD></TD>
				</TR>
				<TR><TD>3</TD>
					<TD></TD>
					<TD></TD>
					<TD></TD>
					<TD></TD>
					<TD></TD>
				</TR>
				<TR><TD>4</TD>
					<TD>x</TD>
					<TD></TD>
					<TD>x</TD>
					<TD>x</TD>
					<TD></TD>
				</TR>
				<TR><TD>5</TD>
					<TD>x</TD>
					<TD></TD>
					<TD></TD>
					<TD></TD>
					<TD></TD>
				</TR>
			</TBODY>
		</TABLE>
		<TABLE border="1"><TBODY><TR><TD colspan="6">Costs</TD>
				</TR>
				<TR><TD>-</TD>
					<TD>material</TD>
					<TD>labor</TD>
					<TD>equipment</TD>
					<TD>subcontracting</TD>
					<TD>sundry</TD>
				</TR>
				<TR><TD>1</TD>
					<TD>x</TD>
					<TD>x</TD>
					<TD>x</TD>
					<TD>x</TD>
					<TD>x</TD>
				</TR>
				<TR><TD>2</TD>
					<TD>x</TD>
					<TD></TD>
					<TD>x</TD>
					<TD>x</TD>
					<TD>x</TD>
				</TR>
				<TR><TD>3</TD>
					<TD></TD>
					<TD>x</TD>
					<TD></TD>
					<TD></TD>
					<TD>x</TD>
				</TR>
				<TR><TD>4</TD>
					<TD>x</TD>
					<TD></TD>
					<TD>x</TD>
					<TD>x</TD>
					<TD></TD>
				</TR>
				<TR><TD>5</TD>
					<TD>x</TD>
					<TD></TD>
					<TD></TD>
					<TD></TD>
					<TD></TD>
				</TR>
			</TBODY>
		</TABLE>
		<GeneralSection><SectionTitle>Manual Registration</SectionTitle>
			<Paragraph>Costs can be registered manually for all cost types. Commitments can be entered for all cost types except for Labor. The posting types are fairly simple. If the costs are processed, the Project Control posting type is found and if the costs are posted to history the same posting type is used. For commitments, the Soft Commitment posting type is found. For surcharges, the Surcharge Post to Fin. is used to clarify the origin</Paragraph>
			<Paragraph>of the costs. If actual costs are available at a later stage, the costs can be linked to commitments via reconciliation. The costs replace the commitments.</Paragraph>
		</GeneralSection>
		<GeneralSection><SectionTitle>Invoicing through Financials without a purchase order.</SectionTitle>
			<Paragraph>To work around the elaborate purchase procedure, you can enter purchases</Paragraph>
			<Paragraph>directly on a project in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>. The manually entered transactions from <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> are posted to the general ledger interim account, if the Extra WIP Entry in Finance check box in the <GUIRef href="/baanerp/tp/ppc/tpppc0100s000" role="session">PPC Parameters (tpppc0100s000)</GUIRef> session is selected. In the <GUIRef href="" role="manual">Transactions (tfgld1101m000)</GUIRef> session, you can book costs manually for different projects. After processing these costs with the <GUIRef href="/baanerp/tp/ppc/tpppc4202m000" role="session">Post Transactions (tpppc4202m000)</GUIRef> session the costs are booked to the general ledger account that is reserved for the specific project with the <GUIRef href="" role="manual">Integration Mapping Scheme (Project) (tfgld4102s000)</GUIRef> session. The amount entered in the GLD interim account will be counterposted.</Paragraph>
		</GeneralSection>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>Make sure that one of the entries in <GUIRef href="" role="manual">Integration Mapping Scheme (tfgld4500m000)</GUIRef> session has no project linked to it, otherwise, integration problems can occur if you create a new project.</Paragraph>
		</Note>
		<GeneralSection><SectionTitle>Parameter cleared</SectionTitle>
			<Paragraph>If the Extra WIP Entry in Finance check box in the <GUIRef href="/baanerp/tp/ppc/tpppc0100s000" role="session">PPC Parameters (tpppc0100s000)</GUIRef> session is cleared, no specific WIP account is reserved for the project and costs are booked to history and the general ledger WIP account for all projects.</Paragraph>
		</GeneralSection>
		<GeneralSection><SectionTitle>Hours Registration</SectionTitle>
			<Paragraph>Hours registration is carried out in the hours accounting sessions of <GUIRef href="/baanerp/bp" role="package">People</GUIRef>. If you process the hours to <GUIRef href="/baanerp/tp" role="package">Project</GUIRef>, eventually the hours are found in history with posting type: Hours Registration. Subcontracting hours are linked to a purchase order. For this purchase order a remittance agreement must be defined (which you can check in <GUIRef href="/baanerp/td" role="package">Order Management</GUIRef>, module PUR) and a remittance agreement must be defined on the project (which you can check in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>, module ACP). Subcontracting hours are not posted to the general ledger, but to Accounts Payable. In this <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> module, the number of spent hours on a purchase order is updated with the subcontracting hours. The subcontracting hours are posted to the labor cost history. Surcharges are not calculated for subcontracting hour transactions. Project history displays the succesful booking with the Subcontracting Hours posting type.</Paragraph>
		</GeneralSection>
		<GeneralSection><SectionTitle>Direct Delivery</SectionTitle>
			<Paragraph>Every placed order or registered receipt for a purchase order can be a commitment, and is recorded in the commitment accounting system. In case of a direct delivery to a project, the corresponding invoice is entered and matched with the order. At that moment the commitment becomes actual costs. In case of delivery to a project warehouse a soft commitment in the project warehouse becomes a hard commitment after a purchase order is received in the warehouse. The hard commitment becomes costs if the order is issued by a project. If the financial transaction is performed in the warehouse and not in the project, you can make a correction on the warehouse value this will show in the value correction posting type. You can only use the value correction if the purchase order is not yet matched.</Paragraph>
		</GeneralSection>
		<Note><SectionTitle>Note</SectionTitle>
			<List><ListIntro>Cost transactions caused by approval of the purchase invoice are never posted to <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> GLD. The posting types are:</ListIntro>
				<ListItem>Invoice (Purchase Order).</ListItem>
				<ListItem>The reverse transaction: Reverse Delivery (Proj) . The project WIP in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> is updated by the delivery transaction. Only a possible difference between the invoice amount during delivery and the invoice amount during approval is posted to the general ledger.</ListItem>
			</List>
		</Note>
		<Note><SectionTitle>Note</SectionTitle>
			<List><ListIntro>If an item of type Cost Item is ordered, this order line is always handled as a direct delivery. Even if the item can be released to a warehouse. In <GUIRef href="/baanerp/tp" role="package">Project</GUIRef>, a distinction is made between soft commitments (creating the purchase order), hard commitments (delivery to the project or project warehouse), and costs. Whether the soft and/or hard commitments are booked in <GUIRef href="/baanerp/tp" role="package">Project</GUIRef> depends on the Log Commitments (Purchase Transactions) enum, which can have the following values:</ListIntro>
				<ListItem>Order and Delivery: both soft and hard commitments are used.</ListItem>
				<ListItem>Delivery: only hard commitments are used.</ListItem>
				<ListItem>Not: no commitments are used. There is one exception: a delivery to a project always results in a hard commitment transaction in the Temporary Costs table, despite the enum. This is necessary to be able to make a WIP transaction in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> general ledger. The transaction is not posted to project history (costs). Costs are always booked.</ListItem>
			</List>
		</Note>
		<GeneralSection><SectionTitle>Delivery via warehouse</SectionTitle>
			<Paragraph>The same type of procedure as in Direct Delivery is valid if inventory in a project warehouse (commitment) is issued by the project (costs). The following cases results in a reverse commitments and, therefore, not</Paragraph>
			<List><ListIntro>in cost transactions:</ListIntro>
				<ListItem>Delivery to another warehouse.</ListItem>
				<ListItem>A return order.</ListItem>
				<ListItem>Or an adjustment order.</ListItem>
			</List>
		</GeneralSection>
		<Note><SectionTitle>Note</SectionTitle>
			<List><ListIntro>Cost transactions caused by deliveries to the project warehouse, by means of a purchase order, are never posted to the general ledger, but to <GUIRef href="/baanerp/tp" role="package">Project</GUIRef>. The posting types are:</ListIntro>
				<ListItem>Delivery to Project Warehouse.</ListItem>
				<ListItem>The reverse transaction: Order. The financial posting for this is carried out by <GUIRef href="/baanerp/wh" role="package">Warehouse Management</GUIRef>. The project work in progress (WIP) in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> is only updated if the project issues inventory from the project warehouse. The reverse cost transaction for posting type Delivery is not posted to the general ledger, but to a project.</ListItem>
			</List>
		</Note>
	</GeneralSection>
	<RelatedTopics><SectionTitle>Related topics</SectionTitle>
		<RelTopic><Link href="/baanerp/tp/onlinemanual/000322" role="manual">To use posting types</Link>
		</RelTopic>
	</RelatedTopics>
</ManualTopic>
