<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tp/onlinemanual/000327" xml:lang="en">
   <Header>
      <Title>To post revenues</Title>
      <Keyword type="header" order="d1e2275702">
         <Level1>posting type</Level1>
      </Keyword>
   </Header>
   <GeneralSection>
      <GeneralSection>
         <SectionTitle>Revenues</SectionTitle>
         <Paragraph>The manually entered transactions in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> are only posted to the
general ledger if the Extra WIP Entry in Finance check box is
selected in the <GUIRef href="/baanerp/tp/ppc/tpppc0100s000" role="session">PPC Parameters (tpppc0100s000)</GUIRef> session. The project provisional
revenue transaction, without project key elements and project
integration options, that is already completed in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>, are
reversed and a new project provisional revenue transaction with project
key elements and project integration options  are made.
Revenue transactions caused by an advance payment are never posted to
the general ledger. The transaction is used to send a sales invoice to
the customer in advance, but the invoice amount is not recognized as
turnover, yet.</Paragraph>
         <Paragraph>The revenue transaction from Sales Invoicing (SLI) (in case of invoicing
by means of PIN) is created when transfering the invoice information to
SLI. If
the invoice is processed in SLI, the transaction in the Temporary
Revenues table is updated with the invoice number.
Revenue transactions originating from SLI must have an invoice number,
which must be filled by SLI, before the transactions can be posted.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Interim Results</SectionTitle>
         <Paragraph>In contrast with costs and revenues, the interim results are not stored
in a temporary entity type. Posted and not yet posted transactions are
both stored in entity type Interim Results. Posted interim results
cannot be changed or deleted. These results are used to do a reverse
posting.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Invoicing</SectionTitle>
         <Paragraph>This process is also used for handling sales invoices from <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>,
which are not linked to invoices from the Invoicing (PIN) module. <GUIRef href="/baanerp/tp" role="package">Project</GUIRef> is triggered if you use a ledger account with the integration
indicator Project Sales. The invoice amount can be distributed online to
several project attributes such as element and cost component in the
relevant project session. After this process, a check is performed if
the
sales invoice amount is fully matched in <GUIRef href="/baanerp/tp" role="package">Project</GUIRef>. If the sales amount
is not fully matched, a
warning message is given.
The online created transactions can also be deleted.</Paragraph>
      </GeneralSection>
   </GeneralSection>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/tp/onlinemanual/000096" role="manual">To register costs and commitments</Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>