<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tp/onlinemanual/000322" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">To use posting types</Title>
		<Keyword><Level1>Post to Finance</Level1>
		</Keyword>
		<Keyword><Level1>Entry types</Level1>
		</Keyword>
	</Header>
	<GeneralSection><GeneralSection><SectionTitle>Posting Types (introduction)</SectionTitle>
			<Paragraph>Posting types are used to recognize transactions. Posting types indicate where the transaction originates from, and combine certain related posting types in project history. In the process of posting, most posting types are a temporary display in project history of what happens to, for example, an order. If the order is manually entered, the posting type is Project Control. If the order is actually entered in Finance, the posting type becomes Soft Commitment in project history.If the goods are received on the project for direct delivery, the Soft Commitment becomes a Hard Commitment in project history.</Paragraph>
			<List><ListIntro>The posting type of the transaction determines:</ListIntro>
				<ListItem>The posting type that is used in history.</ListItem>
				<ListItem>The posting type of the surcharge, if applicable.</ListItem>
				<ListItem>The financial transactions that are made in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> in the general ledger.</ListItem>
			</List>
			<Paragraph><GUIRef href="/baanerp/tp" role="package">Project</GUIRef> uses many different posting types, and therefore the following explanation describes the various possibilities for costs, commitments, and revenues. For example, to find out what happens with sundry costs in ERP, the posting types clarify from where the costs originate. For every posting type, the history posting type is provided. The history posting types are self-explanatory, or have the same characteristics as the actual posting types.</Paragraph>
		</GeneralSection>
		<GeneralSection><SectionTitle>Commitment posting types</SectionTitle>
			<List><ListIntro>Material/Equipment/Subcontracting:</ListIntro>
				<ListItem>Project Control. The commitment is entered in the cost object s commitment session. History posting type: Soft Commitment.</ListItem>
				<ListItem>Order. ERP generates the commitment from a created purchase order. History posting type: Soft Commitment.</ListItem>
				<ListItem>Delivery to Project. ERP generates the commitment on delivery of a purchase order to the project. History posting type: Hard Commitment (project).</ListItem>
				<ListItem>Project Control (Rev.Ent). The commitment is already posted through the <GUIRef href="/baanerp/tp/ppc/tpppc4802m000" role="session">Process Transactions (tpppc4802m000)</GUIRef> session, but a reverse entry must still be made. History posting type: Soft Commitment.</ListItem>
				<ListItem>Delivery to Proj. Wareh. ERP generates the commitment on delivery of a purchase order to the project warehouse. History posting type: Hard Commitment Wh.</ListItem>
				<ListItem>Reverse Delivery (Proj). A reverse entry is made for the commitment generated from a purchase order delivery when a purchase invoice is processed in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>. History posting type: Hard Commitment (project). Sundry Cost:</ListItem>
				<ListItem>Project Control. The sundry cost commitment is entered in the <GUIRef href="/baanerp/tp/ppc/tpppc2190s000" role="session">Commitments (Sundry Cost) (tpppc2190s000)</GUIRef> session. History posting type: Soft Commitment.</ListItem>
				<ListItem>Proj. Control (Rev.Entry). The sundry cost commitment is already posted through the <GUIRef href="/baanerp/tp/ppc/tpppc4802m000" role="session">Process Transactions (tpppc4802m000)</GUIRef> session, but a reverse entry must still be made. History posting type: Soft Commitment.</ListItem>
				<ListItem>Charge Soft Commitment/ Charge Soft Comm. Reverse/ Charge Delivery to Proj./ Charge Delivery to Proj. Wh./ Charge Reverse Delivery: These charges are surcharges on commitments posted with the <GUIRef href="/baanerp/tp/ppc/tpppc4802m000" role="session">Process Transactions (tpppc4802m000)</GUIRef> session. At project completion, these surcharges are settled and removed from the Sundry Cost Commitment table. History posting type: Charge Soft Commitment/ Charge Soft Comm. Reverse becomes Surcharge Soft Commitment. History posting type: Charge Delivery to Proj./ Charge Delivery to Proj. Wh./ Charge Reverse Delivery becomes Surcharge Hard Commitment.</ListItem>
			</List>
		</GeneralSection>
		<GeneralSection><SectionTitle>Cost posting types</SectionTitle>
			<List><ListIntro>Material Cost:</ListIntro>
				<ListItem>Project Control. The material costs are entered in the <GUIRef href="/baanerp/tp/ppc/tpppc2111s000" role="session">Material Costs (tpppc2111s000)</GUIRef> session. History posting type: Project Control.</ListItem>
				<ListItem>Inventory. The material costs are generated when the <GUIRef href="/baanerp/tp/pss/tppss6235m000" role="session">Transfer Planned PRP Warehouse Orders (tppss6235m000)</GUIRef> session is run. History posting type: Inventory.</ListItem>
				<ListItem>Purchase Invoice (Fin.). The material costs are posted to <GUIRef href="/baanerp/tp" role="package">Project</GUIRef> by subdividing a cost invoice in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>. History posting type: Purchase Inv. Fin.</ListItem>
				<ListItem>Invoice (Purchase Order). ERP generates the material costs during the processing of a purchase invoice in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> based on a purchase order. History posting type: Invoice (Purchase Order).</ListItem>
				<ListItem>Price Variance. Differences between the order price and the purchase invoice amount are posted as project cost transactions. History posting type: Invoice (Purchase Order).</ListItem>
				<ListItem><Link href="/baanerp/tp/glossary/glossary#000369" role="glossary">expense tax</Link>. Direct deliveries to a project are posted as project cost transactions. History posting type: Expense Tax.</ListItem>
				<ListItem>Price Variance. If the purchase invoice is booked, and the project warehouse issue to the project is performed, the price variance of the purchase invoice causes a correction order in Warehousing for the already issued items. History posting type: Value Corrections.</ListItem>
			</List>
			<List><ListIntro>Labor Cost:</ListIntro>
				<ListItem>Project Control. The labor cost transactions are entered in the <GUIRef href="/baanerp/tp/ppc/tpppc2131s000" role="session">Labor Costs (tpppc2131s000)</GUIRef> session. History posting type: Project Control.</ListItem>
				<ListItem>Hours Registration. The labor cost transaction is recorded in <GUIRef href="/baanerp/tp" role="package">Project</GUIRef> from <GUIRef href="/baanerp/bp" role="package">People</GUIRef>. History posting type: Hours Registration.</ListItem>
				<ListItem>Subcontracting Hours. Subcontracting transactions are entered in the <GUIRef href="/baanerp/tp/ppc/tpppc2132s000" role="session">Subcontracting Hours (tpppc2132s000)</GUIRef> session and have no posting type. In history, the Subcontracting Hours posting type is displayed.</ListItem>
			</List>
			<List><ListIntro>Subcontracting Costs/ Equipment Cost:</ListIntro>
				<ListItem>Project Control. The subcontracting costs are entered in the <GUIRef href="/baanerp/tp/ppc/tpppc2171s000" role="session">Subcontracting Costs (tpppc2171s000)</GUIRef> session. History posting type: Project Control.</ListItem>
				<ListItem>Purchase Invoice (Fin.). The subcontracting costs are posted to <GUIRef href="/baanerp/tp" role="package">Project</GUIRef> by subdividing a cost invoice in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>. History posting type: Purchase Invoice (Fin).</ListItem>
				<ListItem>Invoice (Purchase Order). ERP generates the subcontracting costs by processing a purchase invoice in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>, which is based on a purchase order. History posting type: Invoice (Purchase Order).</ListItem>
				<ListItem>Invoice Difference. Differences between the order price and the purchase invoice amount are posted as project cost transactions. History posting type: Invoice (Purchase Order).</ListItem>
				<ListItem><Link href="/baanerp/tp/glossary/glossary#000369" role="glossary">expense tax</Link> History posting type: Expense Tax.</ListItem>
			</List>
			<List><ListIntro>Sundry Cost:</ListIntro>
				<ListItem>Project Control. The sundry costs are entered in the <Link href="/baanerp/tp/ppc/tpppc2191s000" role="session">Sundry Costs (tpppc2191s000)</Link> session. History posting type: Project Control.</ListItem>
				<ListItem>Purchase Invoice (Fin.). The sundry costs are allocated to projects in <GUIRef href="/baanerp/tp" role="package">Project</GUIRef> by a breaking down a cost invoice in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>. History posting type: Purchase Invoice (Fin).</ListItem>
				<ListItem>Expenses (BP). The sundry costs are generated with the <Link href="/baanerp/bp/tmm/bptmm1100m000" role="session">Hours and Expenses by Employee Overview (bptmm1100m000)</Link> session. History posting type: Expenses (BP).</ListItem>
				<ListItem>Surcharge Post to Finance/ Surcharge Don't Post to Finance Surcharges are entered in the <GUIRef href="/baanerp/tp/ppc/tpppc4802m000" role="session">Process Transactions (tpppc4802m000)</GUIRef> session, the costs are surcharges over costs posted with the post-transactions-process. At the end of this process, the surcharges are removed from the Sundry Costs table. History posting type: Surcharge on Costs <Emphasis>Revenues posting types</Emphasis>
				</ListItem>
				<ListItem>Project Control. The revenue is manually entered in the <GUIRef href="/baanerp/tp/ppc/tpppc3101s000" role="session">Revenues (tpppc3101s000)</GUIRef> session. History posting type: Project Control.</ListItem>
				<ListItem>Sales Invoice (Proj.). The revenue is based on a project invoice. History posting type: Invoicing.</ListItem>
				<ListItem>Sales Invoice (Fin.). The revenues are posted to <GUIRef href="/baanerp/tp" role="package">Project</GUIRef> by subdividing a sales invoice in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>. History posting type: Sales Invoice (Fin.).</ListItem>
				<ListItem>Sales Invoice Holdback. The revenue is accounted for, but is not yet invoiced. History posting type: Invoicing.</ListItem>
				<ListItem>Sales Inv. Holdback (Rev). The holdback is released and invoiced reversely. History posting type: Invoicing.</ListItem>
				<ListItem>Sales Invoice Advance. The revenue originates from an advanced payment. History posting type: Invoicing.</ListItem>
				<ListItem>Sales Inv. Advance (Rev). The invoice that originated from an advanced payment is reversed. History posting type: Invoicing.</ListItem>
			</List>
		</GeneralSection>
	</GeneralSection>
	<RelatedTopics><SectionTitle>Related topics</SectionTitle>
		<RelTopic><Link href="/baanerp/tp/onlinemanual/000324" role="manual">Costing posting types</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/tp/onlinemanual/000327" role="manual">To post revenues</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/tf/integrations/10024_lst" role="manual">Integration document types - Project Costs and Commitments</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/tf/integrations/10025_lst" role="manual">Integration document types - Project Revenues</Link>
		</RelTopic>
	</RelatedTopics>
</ManualTopic>
