| Description | Manage Journal Entries |
| Name | ManageJournalEntryIn |
| Namespace | http://sap.com/xi/A1S/Global |
| Process Component Description | Financial Accounting |
| Process Component Name | Accounting |
| Process Component Namespace | http://sap.com/xi/AP/FinancialAccounting/Global |
| Deployment Unit Description | Financials |
| Endpoint Activation | By Scoping of Process Component | Operations |
| Release Status | Released |
An interface to create journal entries from a source system or file.
In SAP Cloud for Financials the data of a business transaction which is relevant for financials processing are stored in different business objects. The most prominent business object is Journal Entry (General Ledger -> Journal Entries). Additional business objects where data can be stored are:
Accounts Receivable Item (Receivables -> Customers -> Customer Accounts, choose View)
Accounts Payable Item (Payables -> Suppliers -> Supplier Accounts, choose View)
Tax Item (Tax Management -> Reporting)
Cash Item (Payment Management -> Payment Monitor)
To ensure a consistent insertion of data into all of these business objects, a further business object Business Transaction for Accounting was introduced that serves as the input channel for business transaction data. This means that financials-relevant data of a business transaction is submitted and stored in Business Transaction for Accounting and from there transferred to the business objects Journal Entry, Accounts Receivable Item, and so on automatically. From a technical point of view, this interface therefore creates business transactions for accounting, but from business point of view it creates journal entries.
You can navigate to the screen of business transactions for accounting with the following paths:
General Ledger -> Closing Cockpit -> Source Documents, choose View -> Business Transaction
From a journal entry you can navigate with You Can Also -> View Business Transaction for Accounting.
The web service interface Manage Journal Entry In enables you to connect external applications to your system and to create journal entries (and their assigned accounts receivable, accounts payable, tax, or cash items) in your system. The web service interface Manage Journal Entry In is relevant if your company wants to access journal entries from external applications.
The web service interface Manage Journal Entry In offers the operation CreateBundle.
Here is an example of a simple web service request:
<n0:JournalEntryBundleCreateRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <ID>ABCDEF000000001</ID> </BasicMessageHeader> <JournalEntry> <ObjectNodeSenderTechnicalID>1</ObjectNodeSenderTechnicalID> <CompanyID>MC10000</CompanyID> <OriginalEntryDocumentReferenceID>2013-1000000123</OriginalEntryDocumentReferenceID> <OriginalEntryDocumentReferenceBusinessSystemID>A33SL57</OriginalEntryDocumentReferenceBusinessSystemID> <AccountingBusinessTransactionDate>2013-05-24</AccountingBusinessTransactionDate> <AccountingBusinessTransactionTypeCode>701</AccountingBusinessTransactionTypeCode> <AccountingDocumentTypeCode>00107</AccountingDocumentTypeCode> <Item> <ObjectNodeSenderTechnicalID>2</ObjectNodeSenderTechnicalID> <OriginalEntryDocumentItemReferenceItemID>1</OriginalEntryDocumentItemReferenceItemID> <GeneralLedgerAccountAliasCode>A-7330</GeneralLedgerAccountAliasCode> <BusinessTransactionCurrencyAmount currencyCode="USD">100</BusinessTransactionCurrencyAmount> </Item> <Item> <ObjectNodeSenderTechnicalID>3</ObjectNodeSenderTechnicalID> <OriginalEntryDocumentItemReferenceItemID>2</OriginalEntryDocumentItemReferenceItemID> <GeneralLedgerAccountAliasCode>A-7999</GeneralLedgerAccountAliasCode> <BusinessTransactionCurrencyAmount currencyCode="USD">-100</BusinessTransactionCurrencyAmount> </Item> </JournalEntry> </n0:JournalEntryBundleCreateRequest>
Codes and IDs have to be handed over with internal values from the SAP Cloud for Financials system. Code or ID mapping is not currently supported.
You can find general information about Web services, their structure and consumption in the Web Services documentation. Please open the Web Services document in a new window.
Possible scenarios include the following:
Create Journal Entries
The CreateBundle operation is used to create journal entries.
Create Journal Entries with tax data
The CreateBundle operation is used to create journal entries including tax data.
Create customer invoice like Journal Entries
The CreateBundle operation is used to create customer invoice like or customer credit memo like journal entries.
Create supplier invoice like Journal Entries
The CreateBundle operation is used to create supplier invoice like or supplier credit memo like journal entries.
Examples
Web service request to create a journal entry with items posted to cost centers:
Show full documentation
Show full documentation
<n0:JournalEntryBundleCreateRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<ID>ABCDEF000000001</ID>
</BasicMessageHeader>
<JournalEntry>
<ObjectNodeSenderTechnicalID>1</ObjectNodeSenderTechnicalID>
<CompanyID>MC10000</CompanyID>
<OriginalEntryDocumentReferenceID>2013-1000000124</OriginalEntryDocumentReferenceID>
<OriginalEntryDocumentReferenceBusinessSystemID>A33SL57</OriginalEntryDocumentReferenceBusinessSystemID>
<AccountingBusinessTransactionDate>2013-05-24</AccountingBusinessTransactionDate>
<AccountingBusinessTransactionTypeCode>701</AccountingBusinessTransactionTypeCode>
<AccountingDocumentTypeCode>00107</AccountingDocumentTypeCode>
<Item>
<ProductInternalID>10000000</ProductInternalID>
<ProductTypeCode>2</ProductTypeCode>
<ObjectNodeSenderTechnicalID>2</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>1</OriginalEntryDocumentItemReferenceItemID>
<GeneralLedgerAccountAliasCode>A-7330</GeneralLedgerAccountAliasCode>
<AccountingCodingBlock>
<CostCentreID>MC40000</CostCentreID>
</AccountingCodingBlock>
<BusinessTransactionCurrencyAmount currencyCode="USD">100</BusinessTransactionCurrencyAmount>
</Item>
<Item>
<ProductInternalID>10000000</ProductInternalID>
<ProductTypeCode>2</ProductTypeCode>
<ObjectNodeSenderTechnicalID>3</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>2</OriginalEntryDocumentItemReferenceItemID>
<GeneralLedgerAccountAliasCode>A-7999</GeneralLedgerAccountAliasCode>
<AccountingCodingBlock>
<CostCentreID>MC10000</CostCentreID>
</AccountingCodingBlock>
<BusinessTransactionCurrencyAmount currencyCode="USD">-100</BusinessTransactionCurrencyAmount>
</Item>
</JournalEntry>
</n0:JournalEntryBundleCreateRequest>
Web service request to create a journal entry that post costs from cost center to sales order item:
<n0:JournalEntryBundleCreateRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<ID>ABCDEF000000001</ID>
</BasicMessageHeader>
<JournalEntry>
<ObjectNodeSenderTechnicalID>1</ObjectNodeSenderTechnicalID>
<CompanyID>MC10000</CompanyID>
<OriginalEntryDocumentReferenceID>2013-1000000125</OriginalEntryDocumentReferenceID>
<OriginalEntryDocumentReferenceBusinessSystemID>A33SL57</OriginalEntryDocumentReferenceBusinessSystemID>
<AccountingBusinessTransactionDate>2013-05-24</AccountingBusinessTransactionDate>
<AccountingBusinessTransactionTypeCode>701</AccountingBusinessTransactionTypeCode>
<AccountingDocumentTypeCode>00107</AccountingDocumentTypeCode>
<Item>
<ObjectNodeSenderTechnicalID>2</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>1</OriginalEntryDocumentItemReferenceItemID>
<GeneralLedgerAccountAliasCode>A-7330</GeneralLedgerAccountAliasCode>
<AccountingCodingBlock>
<SalesOrderReference>
<ID>646</ID>
<UUID>00163E02-8660-1ED2-A1C7-0CBA519062CB</UUID>
<TypeCode>114</TypeCode>
<ItemID>10</ItemID>
<ItemUUID>00163E02-8660-1ED2-A1C7-192468B4E2F9</ItemUUID>
<ItemTypeCode>16777</ItemTypeCode>
</SalesOrderReference>
</AccountingCodingBlock>
<BusinessTransactionCurrencyAmount currencyCode="USD">100</BusinessTransactionCurrencyAmount>
</Item>
<Item>
<ObjectNodeSenderTechnicalID>3</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>2</OriginalEntryDocumentItemReferenceItemID>
<GeneralLedgerAccountAliasCode>A-7330</GeneralLedgerAccountAliasCode>
<AccountingCodingBlock>
<CostCentreID>MC10000</CostCentreID>
</AccountingCodingBlock>
<BusinessTransactionCurrencyAmount currencyCode="USD">-100</BusinessTransactionCurrencyAmount>
</Item>
</JournalEntry>
</n0:JournalEntryBundleCreateRequest>
Web service request to create a journal entry with five items:
<n0:JournalEntryBundleCreateRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<ID>ABCDEF000000001</ID>
</BasicMessageHeader>
<JournalEntry>
<ObjectNodeSenderTechnicalID>1</ObjectNodeSenderTechnicalID>
<CompanyID>MC10000</CompanyID>
<OriginalEntryDocumentReferenceID>2013-1000000126</OriginalEntryDocumentReferenceID>
<OriginalEntryDocumentReferenceBusinessSystemID>A33SL57</OriginalEntryDocumentReferenceBusinessSystemID>
<AccountingBusinessTransactionDate>2013-05-24</AccountingBusinessTransactionDate>
<AccountingBusinessTransactionTypeCode>701</AccountingBusinessTransactionTypeCode>
<AccountingDocumentTypeCode>00107</AccountingDocumentTypeCode>
<Item>
<ProductInternalID>10000000</ProductInternalID>
<ProductTypeCode>2</ProductTypeCode>
<ObjectNodeSenderTechnicalID>2</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>1</OriginalEntryDocumentItemReferenceItemID>
<GeneralLedgerAccountAliasCode>A-7330</GeneralLedgerAccountAliasCode>
<BusinessTransactionCurrencyAmount currencyCode="USD">100</BusinessTransactionCurrencyAmount>
</Item>
<Item>
<ProductInternalID>10000000</ProductInternalID>
<ProductTypeCode>2</ProductTypeCode>
<ObjectNodeSenderTechnicalID>3</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>2</OriginalEntryDocumentItemReferenceItemID>
<GeneralLedgerAccountAliasCode>A-7330</GeneralLedgerAccountAliasCode>
<AccountingCodingBlock>
<CostCentreID>MC10000</CostCentreID>
</AccountingCodingBlock>
<BusinessTransactionCurrencyAmount currencyCode="USD">-10</BusinessTransactionCurrencyAmount>
</Item>
<Item>
<ProductInternalID>10000000</ProductInternalID>
<ProductTypeCode>2</ProductTypeCode>
<ObjectNodeSenderTechnicalID>4</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>3</OriginalEntryDocumentItemReferenceItemID>
<GeneralLedgerAccountAliasCode>A-7330</GeneralLedgerAccountAliasCode>
<AccountingCodingBlock>
<CostCentreID>MC40000</CostCentreID>
</AccountingCodingBlock>
<BusinessTransactionCurrencyAmount currencyCode="USD">-20</BusinessTransactionCurrencyAmount>
</Item>
<Item>
<ProductInternalID>10000000</ProductInternalID>
<ProductTypeCode>2</ProductTypeCode>
<ObjectNodeSenderTechnicalID>5</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>4</OriginalEntryDocumentItemReferenceItemID>
<GeneralLedgerAccountAliasCode>A-7330</GeneralLedgerAccountAliasCode>
<AccountingCodingBlock>
<CostCentreID>MC41000</CostCentreID>
</AccountingCodingBlock>
<BusinessTransactionCurrencyAmount currencyCode="USD">-30</BusinessTransactionCurrencyAmount>
</Item>
<Item>
<ProductInternalID>10000000</ProductInternalID>
<ProductTypeCode>2</ProductTypeCode>
<ObjectNodeSenderTechnicalID>6</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>5</OriginalEntryDocumentItemReferenceItemID>
<GeneralLedgerAccountAliasCode>A-7330</GeneralLedgerAccountAliasCode>
<AccountingCodingBlock>
<CostCentreID>MC42000</CostCentreID>
</AccountingCodingBlock>
<BusinessTransactionCurrencyAmount currencyCode="USD">-40</BusinessTransactionCurrencyAmount>
</Item>
</JournalEntry>
</n0:JournalEntryBundleCreateRequest>
Web service request to create a journal entry with tax:
<n0:JournalEntryBundleCreateRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<ID>ABCDEF000000001</ID>
</BasicMessageHeader>
<JournalEntry>
<ObjectNodeSenderTechnicalID>1</ObjectNodeSenderTechnicalID>
<CompanyID>MC10000</CompanyID>
<OriginalEntryDocumentReferenceID>2013-1000000127</OriginalEntryDocumentReferenceID>
<OriginalEntryDocumentReferenceBusinessSystemID>A33SL57</OriginalEntryDocumentReferenceBusinessSystemID>
<AccountingBusinessTransactionDate>2013-05-24</AccountingBusinessTransactionDate>
<AccountingBusinessTransactionTypeCode>701</AccountingBusinessTransactionTypeCode>
<AccountingDocumentTypeCode>00107</AccountingDocumentTypeCode>
<Item>
<ObjectNodeSenderTechnicalID>2</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>1</OriginalEntryDocumentItemReferenceItemID>
<GeneralLedgerAccountAliasCode>A-1700</GeneralLedgerAccountAliasCode>
<AccountingCodingBlock>
<ProfitCentreID>MC40000</ProfitCentreID>
</AccountingCodingBlock>
<BusinessTransactionCurrencyAmount currencyCode="USD">-106.25</BusinessTransactionCurrencyAmount>
</Item>
<Item>
<ObjectNodeSenderTechnicalID>3</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>2</OriginalEntryDocumentItemReferenceItemID>
<Tax>
<TaxCountryCode>US</TaxCountryCode>
<ProductTaxationCharacteristicsCode listID="US">2</ProductTaxationCharacteristicsCode>
<TaxJurisdictionCode>OH 77</TaxJurisdictionCode>
</Tax>
<GeneralLedgerAccountAliasCode>A-7330</GeneralLedgerAccountAliasCode>
<AccountingCodingBlock>
<CostCentreID>MC40000</CostCentreID>
</AccountingCodingBlock>
<BusinessTransactionCurrencyAmount currencyCode="USD">100</BusinessTransactionCurrencyAmount>
</Item>
<TaxItem>
<ObjectNodeSenderTechnicalID>4</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>3</OriginalEntryDocumentItemReferenceItemID>
<TaxCountryCode>US</TaxCountryCode>
<ProductTaxationCharacteristicsCode listID="US">2</ProductTaxationCharacteristicsCode>
<TaxJurisdictionCode>OH 77</TaxJurisdictionCode>
<BusinessTransactionCurrencyAmount currencyCode="USD">6.25</BusinessTransactionCurrencyAmount>
</TaxItem>
</JournalEntry>
</n0:JournalEntryBundleCreateRequest>
Web service request to create three journal entries:
<n0:JournalEntryBundleCreateRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<ID>ABCDEF000000001</ID>
</BasicMessageHeader>
<JournalEntry>
<ObjectNodeSenderTechnicalID>1</ObjectNodeSenderTechnicalID>
<CompanyID>MC10000</CompanyID>
<OriginalEntryDocumentReferenceID>2013-1000000128-1</OriginalEntryDocumentReferenceID>
<OriginalEntryDocumentReferenceBusinessSystemID>A33SL57</OriginalEntryDocumentReferenceBusinessSystemID>
<AccountingBusinessTransactionDate>2013-05-24</AccountingBusinessTransactionDate>
<AccountingBusinessTransactionTypeCode>701</AccountingBusinessTransactionTypeCode>
<AccountingDocumentTypeCode>00107</AccountingDocumentTypeCode>
<Item>
<ObjectNodeSenderTechnicalID>2</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>1</OriginalEntryDocumentItemReferenceItemID>
<GeneralLedgerAccountAliasCode>A-7330</GeneralLedgerAccountAliasCode>
<AccountingCodingBlock>
<CostCentreID>MC40000</CostCentreID>
</AccountingCodingBlock>
<BusinessTransactionCurrencyAmount currencyCode="USD">100</BusinessTransactionCurrencyAmount>
</Item>
<Item>
<ObjectNodeSenderTechnicalID>3</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>2</OriginalEntryDocumentItemReferenceItemID>
<GeneralLedgerAccountAliasCode>A-7999</GeneralLedgerAccountAliasCode>
<AccountingCodingBlock>
<CostCentreID>MC10000</CostCentreID>
</AccountingCodingBlock>
<BusinessTransactionCurrencyAmount currencyCode="USD">-100</BusinessTransactionCurrencyAmount>
</Item>
</JournalEntry>
<JournalEntry>
<ObjectNodeSenderTechnicalID>4</ObjectNodeSenderTechnicalID>
<CompanyID>MC10000</CompanyID>
<OriginalEntryDocumentReferenceID>2013-1000000128-2</OriginalEntryDocumentReferenceID>
<OriginalEntryDocumentReferenceBusinessSystemID>A33SL57</OriginalEntryDocumentReferenceBusinessSystemID>
<AccountingBusinessTransactionDate>2013-05-25</AccountingBusinessTransactionDate>
<AccountingBusinessTransactionTypeCode>701</AccountingBusinessTransactionTypeCode>
<AccountingDocumentTypeCode>00107</AccountingDocumentTypeCode>
<Item>
<ObjectNodeSenderTechnicalID>5</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>1</OriginalEntryDocumentItemReferenceItemID>
<GeneralLedgerAccountAliasCode>A-7330</GeneralLedgerAccountAliasCode>
<AccountingCodingBlock>
<CostCentreID>MC40000</CostCentreID>
</AccountingCodingBlock>
<BusinessTransactionCurrencyAmount currencyCode="EUR">200</BusinessTransactionCurrencyAmount>
</Item>
<Item>
<ObjectNodeSenderTechnicalID>6</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>2</OriginalEntryDocumentItemReferenceItemID>
<GeneralLedgerAccountAliasCode>A-7999</GeneralLedgerAccountAliasCode>
<AccountingCodingBlock>
<CostCentreID>MC10000</CostCentreID>
</AccountingCodingBlock>
<BusinessTransactionCurrencyAmount currencyCode="EUR">-200</BusinessTransactionCurrencyAmount>
</Item>
</JournalEntry>
<JournalEntry>
<ObjectNodeSenderTechnicalID>7</ObjectNodeSenderTechnicalID>
<CompanyID>MC10000</CompanyID>
<OriginalEntryDocumentReferenceID>2013-1000000128-3</OriginalEntryDocumentReferenceID>
<OriginalEntryDocumentReferenceBusinessSystemID>A33SL57</OriginalEntryDocumentReferenceBusinessSystemID>
<AccountingBusinessTransactionDate>2013-05-27</AccountingBusinessTransactionDate>
<AccountingBusinessTransactionTypeCode>701</AccountingBusinessTransactionTypeCode>
<AccountingDocumentTypeCode>00107</AccountingDocumentTypeCode>
<Item>
<ObjectNodeSenderTechnicalID>8</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>1</OriginalEntryDocumentItemReferenceItemID>
<GeneralLedgerAccountAliasCode>A-7330</GeneralLedgerAccountAliasCode>
<AccountingCodingBlock>
<CostCentreID>MC40000</CostCentreID>
</AccountingCodingBlock>
<BusinessTransactionCurrencyAmount currencyCode="USD">100</BusinessTransactionCurrencyAmount>
</Item>
<Item>
<ObjectNodeSenderTechnicalID>9</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>2</OriginalEntryDocumentItemReferenceItemID>
<GeneralLedgerAccountAliasCode>A-7999</GeneralLedgerAccountAliasCode>
<AccountingCodingBlock>
<CostCentreID>MC10000</CostCentreID>
</AccountingCodingBlock>
<BusinessTransactionCurrencyAmount currencyCode="USD">-100</BusinessTransactionCurrencyAmount>
</Item>
<Item>
<ObjectNodeSenderTechnicalID>10</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>3</OriginalEntryDocumentItemReferenceItemID>
<GeneralLedgerAccountAliasCode>A-7330</GeneralLedgerAccountAliasCode>
<AccountingCodingBlock>
<CostCentreID>MC10000</CostCentreID>
</AccountingCodingBlock>
<BusinessTransactionCurrencyAmount currencyCode="USD">50</BusinessTransactionCurrencyAmount>
</Item>
<Item>
<ObjectNodeSenderTechnicalID>11</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>4</OriginalEntryDocumentItemReferenceItemID>
<GeneralLedgerAccountAliasCode>A-7999</GeneralLedgerAccountAliasCode>
<AccountingCodingBlock>
<CostCentreID>MC41000</CostCentreID>
</AccountingCodingBlock>
<BusinessTransactionCurrencyAmount currencyCode="USD">-50</BusinessTransactionCurrencyAmount>
</Item>
</JournalEntry>
</n0:JournalEntryBundleCreateRequest>
Web service request to create a customer invoice like journal entry with tax:
<n0:JournalEntryBundleCreateRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<ID>ABCDEF000000001</ID>
</BasicMessageHeader>
<JournalEntry>
<ObjectNodeSenderTechnicalID>1</ObjectNodeSenderTechnicalID>
<CompanyID>MC10000</CompanyID>
<OriginalEntryDocumentReferenceID>2013-3000000129</OriginalEntryDocumentReferenceID>
<OriginalEntryDocumentReferenceBusinessSystemID>0HS6KT8</OriginalEntryDocumentReferenceBusinessSystemID>
<AccountingBusinessTransactionDate>2013-04-24</AccountingBusinessTransactionDate>
<AccountingBusinessTransactionTypeCode>211</AccountingBusinessTransactionTypeCode>
<AccountingDocumentTypeCode>00025</AccountingDocumentTypeCode>
<Item>
<ObjectNodeSenderTechnicalID>2</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>2</OriginalEntryDocumentItemReferenceItemID>
<Tax>
<TaxCountryCode>US</TaxCountryCode>
<ProductTaxationCharacteristicsCode listID="US">501</ProductTaxationCharacteristicsCode>
<TaxJurisdictionCode>OH 77</TaxJurisdictionCode>
</Tax>
<GeneralLedgerAccountAliasCode>A-1500</GeneralLedgerAccountAliasCode>
<AccountingCodingBlock>
<ProjectTaskID>MC-1239-9</ProjectTaskID>
</AccountingCodingBlock>
<BusinessTransactionCurrencyAmount currencyCode="USD">-60</BusinessTransactionCurrencyAmount>
</Item>
<Item>
<ObjectNodeSenderTechnicalID>3</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>3</OriginalEntryDocumentItemReferenceItemID>
<Tax>
<TaxCountryCode>US</TaxCountryCode>
<ProductTaxationCharacteristicsCode listID="US">501</ProductTaxationCharacteristicsCode>
<TaxJurisdictionCode>OH 77</TaxJurisdictionCode>
</Tax>
<GeneralLedgerAccountAliasCode>A-1520</GeneralLedgerAccountAliasCode>
<AccountingCodingBlock>
<ProjectTaskID>MC-1239-7</ProjectTaskID>
</AccountingCodingBlock>
<BusinessTransactionCurrencyAmount currencyCode="USD">-40</BusinessTransactionCurrencyAmount>
</Item>
<TaxItem>
<ObjectNodeSenderTechnicalID>4</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>4</OriginalEntryDocumentItemReferenceItemID>
<TaxCountryCode>US</TaxCountryCode>
<ProductTaxationCharacteristicsCode listID="US">501</ProductTaxationCharacteristicsCode>
<TaxJurisdictionCode>OH 77</TaxJurisdictionCode>
<DueCategoryCode>1</DueCategoryCode>
<BusinessTransactionCurrencyAmount currencyCode="USD">-6.25</BusinessTransactionCurrencyAmount>
</TaxItem>
<DebtorItem>
<ObjectNodeSenderTechnicalID>5</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>1</OriginalEntryDocumentItemReferenceItemID>
<BusinessPartnerInternalID>MC9785</BusinessPartnerInternalID>
<FullPaymentEndDate>2013-05-12</FullPaymentEndDate>
<Note>External created</Note>
<BusinessTransactionCurrencyAmount currencyCode="USD">106.25</BusinessTransactionCurrencyAmount>
</DebtorItem>
</JournalEntry>
</n0:JournalEntryBundleCreateRequest>
Web service request to create a supplier invoice like journal entry with tax:
<n0:JournalEntryBundleCreateRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<ID>ABCDEF000000001</ID>
</BasicMessageHeader>
<JournalEntry>
<ObjectNodeSenderTechnicalID>1</ObjectNodeSenderTechnicalID>
<CompanyID>MC10000</CompanyID>
<OriginalEntryDocumentReferenceID>2013-1000000129</OriginalEntryDocumentReferenceID>
<OriginalEntryDocumentReferenceBusinessSystemID>A33SL57</OriginalEntryDocumentReferenceBusinessSystemID>
<AccountingBusinessTransactionDate>2013-04-24</AccountingBusinessTransactionDate>
<AccountingBusinessTransactionTypeCode>201</AccountingBusinessTransactionTypeCode>
<AccountingDocumentTypeCode>00023</AccountingDocumentTypeCode>
<Item>
<ObjectNodeSenderTechnicalID>2</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>2</OriginalEntryDocumentItemReferenceItemID>
<Tax>
<TaxCountryCode>US</TaxCountryCode>
<ProductTaxationCharacteristicsCode listID="US">2</ProductTaxationCharacteristicsCode>
<TaxJurisdictionCode>OH 77</TaxJurisdictionCode>
</Tax>
<GeneralLedgerAccountAliasCode>A-7330</GeneralLedgerAccountAliasCode>
<AccountingCodingBlock>
<CostCentreID>MC40000</CostCentreID>
</AccountingCodingBlock>
<BusinessTransactionCurrencyAmount currencyCode="USD">60</BusinessTransactionCurrencyAmount>
</Item>
<Item>
<ObjectNodeSenderTechnicalID>3</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>3</OriginalEntryDocumentItemReferenceItemID>
<Tax>
<TaxCountryCode>US</TaxCountryCode>
<ProductTaxationCharacteristicsCode listID="US">2</ProductTaxationCharacteristicsCode>
<TaxJurisdictionCode>OH 77</TaxJurisdictionCode>
</Tax>
<GeneralLedgerAccountAliasCode>A-7999</GeneralLedgerAccountAliasCode>
<AccountingCodingBlock>
<CostCentreID>MC10000</CostCentreID>
</AccountingCodingBlock>
<BusinessTransactionCurrencyAmount currencyCode="USD">40</BusinessTransactionCurrencyAmount>
</Item>
<TaxItem>
<ObjectNodeSenderTechnicalID>4</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>4</OriginalEntryDocumentItemReferenceItemID>
<TaxCountryCode>US</TaxCountryCode>
<ProductTaxationCharacteristicsCode listID="US">2</ProductTaxationCharacteristicsCode>
<TaxJurisdictionCode>OH 77</TaxJurisdictionCode>
<DueCategoryCode>1</DueCategoryCode>
<BusinessTransactionCurrencyAmount currencyCode="USD">6.25</BusinessTransactionCurrencyAmount>
</TaxItem>
<CreditorItem>
<ObjectNodeSenderTechnicalID>5</ObjectNodeSenderTechnicalID>
<OriginalEntryDocumentItemReferenceItemID>1</OriginalEntryDocumentItemReferenceItemID>
<BusinessPartnerInternalID>MC2000</BusinessPartnerInternalID>
<FullPaymentEndDate>2013-05-12</FullPaymentEndDate>
<Note>External created</Note>
<BusinessTransactionCurrencyAmount currencyCode="USD">-106.25</BusinessTransactionCurrencyAmount>
</CreditorItem>
</JournalEntry>
</n0:JournalEntryBundleCreateRequest>
| Description | Create journal entries |
| Name | CreateBundle |
| Synchronous | yes |
| Release Status | Released |
To create journal entries
As described in definition part of service interface documentation, the technical object that is created directly is Business Transaction for Accounting. Journal Entry is created as a follow-on object automatically.
The request message of the CreateBundle operation contains a BasicMessageHeader node element as well as a JournalEntry node element that contains the journal entry data to be created. The detailed structure of the journal entry node will be explained in the following subsections. The journal entry node can occur multiple times in the request message – this means that multiple journal entries can be created through a single Web service request.
In addition, based on the multi-valuation capability of SAP Cloud for Financials one company can be assigned to multiple sets of books. Every single journal entry node would create one journal entry in each assigned set of books.
The response message type of the operation CreateBundle contains log items, processing information and a journal entry-specific node with ReferenceObjectNodeSenderTechnicalID and business transaction for accounting UUID.
Note:
Element Names marked with an asterisk (*) are mandatory.
The JournalEntry node element contains all general journal entry information such as the company and posting date.
The data for this node is related to General Information area on the journal entry UI.
The element names correspond to the names shown on the UI as follows:
| Element Name | Name on UI |
|---|---|
| CompanyID * | Company |
| OriginalEntryDocumentReferenceID * | Source Document ID |
| OriginalEntryDocumentReferenceBusinessSystemID * | Business System ID |
| OrginalEntryDocumentExternalID | External Reference |
| AccountingBusinessTransactionDate * | Posting Date |
| AccountingBusinessTransactionTypeCode * | - see below - |
| AccountingDocumentTypeCode | Journal Entry Type |
| Note | Header Text |
The OriginalEntryDocumentReferenceBusinessSystemID element has to be filled with value of system instance ID as defined in communication system that represents the external source system or file (see Application and User Management -> Input and Output Management -> Communication Systems).
The Combination of the OriginalEntryDocumentReferenceID and OriginalEntryDocumentReferenceBusinessSystemID elements has to be unique.
The AccountingBusinessTransactionTypeCode element is not visible on the UI, but can be shown in the general ledger line item report (UI name Business Transaction Type). It checks which item types of the journal entry are allowed, mandatory, or forbidden. Currently allowed code values are the following:
| Accounting Business Transaction Type Code | Description | Allowed Item Types | Mandatory Item Types |
|---|---|---|---|
| 701 | General Ledger Posting from External System | Tax Item* | Item |
| 211 | Customer Invoice | Tax Item | Debtor Item or Cash Item (exactly one) / Item |
| 232 | Customer Credit Memo | Tax Item | Debtor Item or Cash Item (exactly one) / Item |
| 201 | Supplier Invoice | Tax Item | Creditor Item or Cash Item (exactly one) / Item |
| 231 | Supplier Credit Memo | Tax Item | Creditor Item or Cash Item (exactly one) / Item |
- Please note, when the external postings includes tax payable postings, this web service cannot be used. In this case please use web service ManageTaxReceivablesPayablesEN
The Item node element can be used to create items in the journal entry.
The data for this node is related to Line Items area (including Item Details areas) on the journal entry UI.
The element names correspond to the names shown on the UI as follows:
| Element Name | Name on UI |
|---|---|
| OriginalEntryDocumentItemReferenceItemID | Source Document Item ID |
| EntryQuantity | Entry Quantity |
| ProductInternalID | Material / Service |
| ProductTypeCode | - see below - |
| Tax | - see chapter Sub-structure Tax - |
| GeneralLedgerAccountAliasCode * | - see below - |
| AccountingCodingBlock | - see chapter Sub-structure Accounting Coding Block - |
| Note | Item Text |
| BusinessTransactionCurrencyAmount * | Transaction Currency Amount |
The ProductTypeCode element is not shown on the journal entry UI. It is used to determine the type of the product filled into element ProductInternalID.
Allowed code values:
| ProductTypeCode | Descriptions |
|---|---|
| 1 | Material |
| 2 | Service |
| 3 | Individual Product |
| 6 | Entitlement |
Note:
Individual Product is allowed for accounting business transaction types 211 - Customer Invoice and 232 - Customer Credit Memo only and will be interpret as fixed asset sale. Retirement of assigned fixed asset will be posted automatically.
The GeneralLedgerAccountAliasCode element is not shown on the journal entry UI. It is used to determine the general ledger account. The allowed values can be found in the Business Configuration work center, Charts of Accounts, Financial Reporting Structures, Account Determination activity -> Edit Account Determination Groups. Relevant groups are Costs -> Groups for General Expenses and all three groups of General Ledger.
Sub-structure Tax has to be filled if an item is tax relevant.
Values are used to link the Item to the related TaxItem. Link is performed by value-equality of all elements except BusinessTransactionCurrencyNonDeductibleAmount.
| Element Name |
|---|
| TaxCountryCode * |
| ProductTaxationCharacteristicsCode * |
| DeferredIndicator |
| TaxJurisdictionCode |
| TaxRegionCode |
| ProductTaxStandardClassificationSystemCode |
| ProductTaxStandardClassificationCode |
| TaxReportingUnitID |
| TaxItemGroupID |
| BusinessTransactionCurrencyNonDeductibleAmount |
For general information about this elements see chapter Tax Item.
The BusinessTransactionCurrencyNonDeductibleAmount element is only applicable for items related to input taxes, US use taxes, or US vendor collected sales taxes. If the tax is (fully or partially) non deductible, the part of the non deductible tax amount which is related to this item has to be filled here. Depending of the configuration this amount will be added to the BusinessTransactionCurrencyAmount of this item or posted as an additional item in the journal entry.
Sub-structure AccountingCodingBlock encapsulates all elements that can be used as cost objects in accounting.
Constraints and Integrity Conditions
At most one element can be filled.
The element names within correspond to the names shown on the journal entry UI as follows:
| Element Name | Name on UI |
|---|---|
| CostCentreID | Cost Center |
| ProjectTaskID | Project Task |
| SalesOrderReference | Sales Document ID / Sales Document Item ID / Sales Document Type |
| CostObjectKey | Cost Object ID / Cost Object Type |
| IndividualMaterialInternalID | Individual Material |
| ProfitCentreID | Profit Center |
The SalesOrderReference element is typed by structure that is used in SAP Cloud for Financials as general structure to reference to business transaction documents like orders, invoices, and so on. Elements of this structure have to be filled as follows:
| Element Name | Value |
|---|---|
| ID * | ID of the sales order, for example '12345' |
| UUID * | UUID of the sales order, for example '00163E02-8660-1ED2-A1C7-0CBA519062CB' |
| TypeCode * | '114' |
| BusinessSystemID | has to be empty if sales order is originated in this SAP Cloud for Financials system |
| ItemID * | ID of the sales order item, for example '10' |
| ItemUUID * | UUID of the sales order item, for example '00163E02-8660-1ED2-A1C7-192468B4E2F9' |
| ItemTypeCode * | - see table below - |
Allowed item type codes are
| ItemTypeCode | Description |
|---|---|
| '28' | Sales Item |
| '76' | Customer Expense Item |
| '16777' | Sales Service Item |
The CostObjectKey element references to Free Cost Objects. Structure of this element is
| Element Name | Value |
|---|---|
| CostObjectTypeCode * | Type code as defined individually within this SAP Cloud for Financials system, for example 'Z1' |
| CostObjectID * | ID of the free cost object, for example 'ABC_1003' |
The allowed values can be found in Cost and Revenue -> Free Cost Objects.
If the IndividualMaterialInternalID element is filled and if a fixed asset exists for this individual material, this item is posted as acquisition to or retirement from this fixed asset.
Note:
Assignment to IndividualMaterialInternalID is not allowed for accounting business transaction types 211 - Customer Invoice and 232 - Customer Credit Memo.
The TaxItem node element can be used to create items in the journal entry together with tax items in the Tax Management work center.
The data for this node is related to Line Items area (including Tax area) on the journal entry UI.
The element names correspond to the names shown on the UI as follows:
| Element Name | Name on Journal Entry UI |
|---|---|
| OriginalEntryDocumentItemReferenceItemID | Source Document Item ID |
| TaxCountryCode * | Country |
| ProductTaxationCharacteristicsCode * | - see below - |
| DeferredIndicator | - see below - |
| TaxJurisdictionCode | Tax Jurisdiction |
| TaxRegionCode | Region |
| ProductTaxStandardClassificationSystemCode | - see below - |
| ProductTaxStandardClassificationCode | - see below - |
| TaxReportingUnitID | Tax Reporting Unit |
| DueCategoryCode | Due Category |
| TaxTypeCode | Tax Type |
| TaxRateTypeCode | Rate Type |
| TaxDeductibilityCode | - see below - |
| TaxItemGroupID | Tax Group ID |
| Note | Item Text |
| BusinessTransactionCurrencyAmount * | Transaction Currency Amount |
| BusinessTransactionCurrencyNonDeductibleAmount | - see below - |
Values of the ProductTaxationCharacteristicsCode, TaxJurisdictionCode, TaxRegionCode, TaxTypeCode, TaxRateTypeCode, and TaxDeductibilityCode elements exist only in relation to the tax country. Therefore these elements are structured with listID attribute. It is not necessary to fill this attribute, it is filled with the tax country automatically.
The ProductTaxationCharacteristicsCode element is not shown on the journal entry UI. It is used to determine the detailed tax attributes like Event Type. The allowed values can be found in Business Configuration work center, Tax on Goods and Services activity -> Define Tax Codes.
The DeferredIndicator element is only applicable for tax countries where the tax deferral is supported, for example France. It is not shown on the journal entry UI but a specific general ledger account is taken in the posted tax item.
The TaxJurisdictionCode element is only applicable for tax country United States. There it is mandatory. The allowed values can be found in Business Configuration work center, Tax on Goods and Services - US activity -> Define Tax Jurisdictions.
The TaxRegionCode element is only applicable for tax countries United States and Canada. For tax country Canada is the reagion mandatory. For the United States is the tax region optional. If it is not filled, it will be derived from the tax jurisdiction code.
The ProductTaxStandardClassificationSystemCode element is not shown on the journal entry UI. It is only applicable for tax countries United States, Mexico, and India.
Allowed code values:
| ProductTaxStandardClassificationSystemCode | Description |
|---|---|
| 1 | Vertex Sales Tax |
| 2 | Vertex Use Tax |
| 3 | Service Tax Account Code for India |
| 4 | Material Type Code for India |
| 5 | Transaction Type Code for Mexico |
The ProductTaxStandardClassificationCode element is not shown on the journal entry UI. It is only applicable for tax countries United States, Mexico, and India. The allowed values can be found in Business Configuration work center.
United States
Tax on Goods and Services - US
Mexico
Product Tax Standard Classification Code for Mexico - Service activity -> Product Tax Standard Classification Code Mexico SERV
India
Product Tax Standard Classification Code for India - Service activity -> Product Tax Standard Classification Code India SERV
The TaxReportingUnitID element is only applicable for tax country India. There it is mandatory. The allowed values can be found in Tax Management -> Tax Authorities -> Company Tax Arrangements. For an Indian company an additional tab Assigned Tax Reporting Units exists.
The DueCategoryCode element is only applicable for reversed charge taxes, for example European Union aquisition tax. For this type of taxes it is mandatory. It differentiates the payable tax item and the receivable tax item.
Allowed code values:
| DueCategoryCode | Description |
|---|---|
| 1 | Payable |
| 2 | Receivable |
The TaxTypeCode and TaxRateTypeCode elements are only applicable for tax countries Canada, Mexico, and India.
The TaxDeductibilityCode element is not shown on the journal entry UI. It is only applicable for tax countries Canada, Mexico, and India. The allowed values can be found in Business Configuration work center, Tax Settings for Purchasing activity.
The TaxItemGroupID element is only applicable for tax countries Canada, Mexico, and India. There it is mandatory. It is used to assign tax items with potentially multiple code values for TaxTypeCode, TaxRateTypeCode, and TaxDeductibilityCode elements to related item(s).
The BusinessTransactionCurrencyNonDeductibleAmount element is only applicable for tax items related to input taxes. If the tax is (fully or partially) non deductible, the non deductible tax amount has to be filled here. In the journal entry this amount will be subtracted from the BusinessTransactionCurrencyAmount of this tax item.
Constraints and Integrity Conditions
The ProductTaxStandardClassificationSystemCode and ProductTaxStandardClassificationCode elements have to be both filled or both empty.
The TaxTypeCode and TaxRateTypeCode elements have to be both filled or both empty.
The TaxDeductibilityCode element has to be filled for input taxes if TaxTypeCode and TaxRateTypeCode elements are filled. In all other cases it has to be empty.
For the ProductTaxationCharacteristicsCode, TaxTypeCode, TaxRateTypeCode, and TaxDeductibilityCode elements only specific combinations are allowed. You can find this allowed combinations if you create a Manual Tax Entry in tax management work center by pressing the related value help.
The DebtorItem node element can be used to create items in the journal entry together with accounts receivable items in the Receivables work center.
The data for this node is related to Line Items area (including Item Details areas) on the journal entry UI and to Trade Receivables area on the customer accounts UI.
The element names correspond to the names shown on the UI as follows:
| Element Name | Name on Journal Entry UI | Name on Customer Accounts UI |
|---|---|---|
| OriginalEntryDocumentItemReferenceItemID | Source Document Item ID | External Reference |
| BusinessPartnerInternalID * | Business Partner | Customer |
| CashDiscountTerms | - not shown - | - see chapter Sub-structure Cash Discount Terms - |
| FullPaymentEndDate | - not shown - | Net Due Date |
| AccountsReceivableDueItemTypeCode | - see below - | Reconciliation Account |
| PaymentControl | - not shown - | - see chapter Sub-structure Payment Control - |
| Note | Item Text | Document Description |
| BusinessTransactionCurrencyAmount * | Transaction Currency Amount | Document Amount in Transaction Currency |
The AccountsReceivableDueItemTypeCode element is not shown on the journal entry UI. It is used to determine the general ledger account. The allowed values can be found in the Business Configuration work center, Charts of Accounts, Financial Reporting Structures, Account Determination activity -> Maintain settings for reconciliation accounts on the Accounts Receivable tab. If it is not filled, default value AR001 - Standard receivable is taken automatically.
Constraints and Integrity Conditions
Exactly one of the BusinessPartnerInternalID and EmployeeID elements has to be filled.
Sub-structure CashDiscountTerms encapsulates all elements that control the calculation of cash discount for the accounts receivable item. It has to be filled only if cash discount is agreed.
The element names correspond to the names shown on the customer accounts UI as follows:
| Element Name | Name on UI |
|---|---|
| Percent | Maximum Cash Discount |
| BusinessTransactionCurrencyAmount | Maximum Cash Discount |
| EndDate * | Maximum Cash Discount Due Date |
Constraints and Integrity Conditions
Exactly one of the Percent and BusinessTransactionCurrencyAmount elements has to be filled.
Sub-structure PaymentControl encapsulates all elements that control the payment of the accounts receivable item. If it is not filled, payment will be processed according to the settings in the customer master data.
The element names correspond to the names shown on the customer accounts UI as follows:
| Element Name | Name on UI |
|---|---|
| PaymentFormCode | Agreed Payment Method |
| PaymentReferenceID | Payment Reference Number |
| PaymentReferenceTypeCode | Payment Reference Type |
Allowed payment form codes:
| PaymentFormCode | Description |
|---|---|
| 04 | Direct Debit |
| 05 | Bank Transfer |
| 06 | Check |
| 12 | Wire Transfer |
| 13 | Direct Debit (Authorization for Payer’s Bank) |
| 21 | Cash Outpayment |
Allowed payment reference type codes:
| PaymentReferenceTypeCode | Description |
|---|---|
| 1 | Inpayment Form 71 – Denmark |
| 2 | Inpayment Form 75 – Denmark |
| 3 | ISR – Switzerland |
| 4 | Golden Tax Invoice Number – China |
| 5 | Transaction Reference Number of externally paid e-commerce order |
| 6 | Acceptgiro – Netherlands |
The CreditorItem node element can be used to create items in the journal entry together with accounts payable items in the Payables work center.
The data for this node is related to Line Items area (including Item Details areas) on the journal entry UI and to Trade Payables area on the supplier accounts UI.
The element names correspond to the names shown on the UI as follows:
| Element Name | Name on Journal Entry UI | Name on Supplier Accounts UI |
|---|---|---|
| OriginalEntryDocumentItemReferenceItemID | Source Document Item ID | External Reference |
| BusinessPartnerInternalID | Business Partner | Supplier |
| EmployeeID | Employee | Employee |
| CashDiscountTerms | - not shown - | - see chapter Sub-structure Cash Discount Terms - |
| FullPaymentEndDate | - not shown - | Net Due Date |
| AccountsPayableDueItemTypeCode | - see below - | Reconciliation Account |
| PaymentControl | - not shown - | - see chapter Sub-structure Payment Control - |
| Note | Item Text | Document Description |
| BusinessTransactionCurrencyAmount * | Transaction Currency Amount | Document Amount in Transaction Currency |
The AccountsPayableDueItemTypeCode element is not shown on the journal entry UI. It is used to determine the general ledger account. The allowed values can be found in the Business Configuration work center, Charts of Accounts, Financial Reporting Structures, Account Determination activity -> Maintain settings for reconciliation accounts on the Accounts Payable tab. If it is not filled, default value AP001 - Standard payable is taken automatically.
Constraints and Integrity Conditions
Exactly one of the BusinessPartnerInternalID and EmployeeID elements has to be filled.
Sub-structure CashDiscountTerms encapsulates all elements that control the calculation of cash discount for the accounts payable item. It has to be filled only if cash discount is agreed.
The element names correspond to the names shown on the supplier accounts UI as follows:
| Element Name | Name on UI |
|---|---|
| Percent | Maximum Cash Discount |
| BusinessTransactionCurrencyAmount | Maximum Cash Discount |
| EndDate * | Maximum Cash Discount Due Date |
Constraints and Integrity Conditions
Exactly one of the Percent and BusinessTransactionCurrencyAmount elements has to be filled.
Sub-structure PaymentControl encapsulates all elements that control the payment of the accounts payable item. If it is not filled, payment will be processed according to the settings in the supplier master data.
The element names correspond to the names shown on the supplier accounts UI as follows:
| Element Name | Name on UI |
|---|---|
| PaymentFormCode | Agreed Payment Method |
| PaymentReferenceID | Payment Reference Number |
| PaymentReferenceTypeCode | Payment Reference Type |
Allowed payment form codes:
| PaymentFormCode | Description |
|---|---|
| 04 | Direct Debit |
| 05 | Bank Transfer |
| 06 | Check |
| 12 | Wire Transfer |
| 13 | Direct Debit (Authorization for Payer’s Bank) |
| 21 | Cash Outpayment |
Allowed payment reference type codes:
| PaymentReferenceTypeCode | Description |
|---|---|
| 1 | Inpayment Form 71 – Denmark |
| 2 | Inpayment Form 75 – Denmark |
| 3 | ISR – Switzerland |
| 4 | Golden Tax Invoice Number – China |
| 5 | Transaction Reference Number of externally paid e-commerce order |
| 6 | Acceptgiro – Netherlands |
The CashItem node element can be used to create items in the journal entry together with cash items in the Payment Management work center.
The data for this node is related to Line Items area (including Item Details areas) on the journal entry UI and to the payment monitor UI.
The element names correspond to the names shown on the UI as follows:
| Element Name | Name on Journal Entry UI | Name on Payment Monitor UI |
|---|---|---|
| OriginalEntryDocumentItemReferenceItemID | Source Document Item ID | External Reference |
| CashPayment * | - see chapter Sub-structure Cash Payment - | - see chapter Sub-structure Cash Payment - |
| PayerBusinessPartnerInternalID | Debtor / Creditor | Payer |
| PayeeBusinessPartnerInternalID | Debtor / Creditor | Payee |
| Note | Item Text | Document Description |
| BusinessTransactionCurrencyAmount * | Transaction Currency Amount | Payment Amount in Transaction Currency |
Constraints and Integrity Conditions
At most one of the PayerBusinessPartnerInternalID and PayeeBusinessPartnerInternalID elements can be filled.
Sub-structure CashPayment encapsulates all elements that are specific for a cash payment.
The element names correspond to the names shown on the payment monitor UI as follows:
| Element Name | Name on UI |
|---|---|
| CashStorageID * | Petty Cash ID |
The allowed values can be found in Liquidity Management -> Master Data -> Petty Cash.
In all elements of the amount type, the currencyCode attribute has to be filled.
The currencyCode attribute of all BusinessTransactionCurrencyAmount elements has to be unique.
The sum of all BusinessTransactionCurrencyAmount elements has to be zero.
BusinessTransactionCurrencyNonDeductibleAmount of a tax item has to be equal to sum of BusinessTransactionCurrencyNonDeductibleAmount of all related items.
In all elements of the quantity type, the unitCode attribute has to be filled.
If the Tax sub-structure is filled within an item, at least one related TaxItem has to exist.
For each TaxItem at least one related Item has to exist.
For each combination of the elements TaxCountryCode, ProductTaxationCharacteristicsCode, TaxJurisdictionCode, and DueCategoryCode, at most one tax item exists.