|
||||
Journal Entries![]() |
The application enables the creation of manual journal entries for G/L accounts and business partners. The journal entry is recorded directly to the database and, therefore, cannot be deleted. Journal entries that were created automatically can also be viewed when a specific document, such as an invoice, is added. |
|||||||||||
To fully utilize this functionality, the following products should be evaluated |
||||||||||||
Journal Vouchers![]() |
This feature enables users to record journal transactions and save
them in draft form, so these transactions do not affect balances
and reports. The accountant can review these transactions and
verify that they are accurate and correctly placed before they are
added to the database. In addition, each journal voucher can
contain more than one transaction
|
|||||||||||
To fully utilize this functionality, the following products should be evaluated |
||||||||||||
Reverse Transactions![]() |
SAP Business One automatically creates reverse transactions for selected journal entries. These transactions are added to the database only after users approve them. To specify if a manual journal entry should be reversed, mark the specific checkbox found in the header of the journal entry. |
|||||||||||
To fully utilize this functionality, the following products should be evaluated |
||||||||||||
Recurring Postings![]() |
This feature enables users to define postings for regular execution in accounting. When users specify a frequency for each recurring posting, SAP Business One automatically reminds them to enter these postings. The transaction amounts do not have to be the same each time, nor do the percentages have to be fixed (although they recur on dates that are known in advance, and they usually comprise the same objects). Examples of recurring journal entries can be payroll orders or standing instructions that are paid by the bank every month. Users can change the default control account in business partner rows when creating templates of recurring postings. |
|||||||||||
To fully utilize this functionality, the following products should be evaluated |
||||||||||||
Posting Templates![]() |
This feature simplifies entering a journal entry, so that users can create templates of common and/or complicated journal entry structures. Users can specify accounts and business partners, and organize them according to debit or credit sides. When adding journal entries, users can call up the relevant template and specify the amounts without defining the account structure. It is possible to change the default control account in business partner rows when creating posting templates. Then, when users create journal entries based on a posting template, the relevant amounts are posted to the selected control accounts. |
|||||||||||
To fully utilize this functionality, the following products should be evaluated |
||||||||||||
Posting Periods![]() |
Multiple Periods - enables users to create and organize posting periods that are compatible with the company's accountancy requirements. Transactions can be entered into all open periods. Posting periods can be closed when a period or calendar year has ended, using the period-end closing function, thus creating relevant postings in the accounting system. Users can define various types of periods: for the entire year, by quarters or months, or by a certain range of days. Period-End Closing - enables users to create postings in the accounting system when a fiscal year or posting period ends. This function allows the transfer of previous G/L account balances from one fiscal year or period to another, as retained gain. |
|||||||||||
To fully utilize this functionality, the following products should be evaluated |
||||||||||||
Exchange Rate Differences![]() |
SAP Business One can recommend which automatic journal entries should be created for exchange rate differences, up to specific dates. These journal entries are required to reconcile between the foreign currency balance and the local currency balance of each foreign currency account or business partner. |
|||||||||||
To fully utilize this functionality, the following products should be evaluated |
||||||||||||
Conversion Differences![]() |
This function is relevant for companies whose defined system currency is different from the local currency. SAP Business One can recommend which journal entries should be made automatically for differences in system currency. The task of the Calculate Conversion Differences function is to make adjustments between the accounts and business partner balances in the system currency and their balances in the account/business partner currency. |
|||||||||||
To fully utilize this functionality, the following products should be evaluated |
||||||||||||
Chart of Accounts![]() |
This feature enables users to build and maintain a chart of accounts according to the special needs of the company. In addition, SAP Business One provides a chart of accounts template for every country, according to the company's defined localization. Companies can adapt the chart of accounts to their own business requirements. This feature also enables users to characterize the accounts, using various parameters such as sales/expenditure, tax exemptions, relevance to budget, and so on. |
|||||||||||
To fully utilize this functionality, the following products should be evaluated |
||||||||||||
Account Segmentation![]() |
Account segments are
used to distinguish between functional divisions or areas of
responsibility within a business. Typical segments are division,
department, product line, and geographic area. This option is used
mainly in the United States.
|
|||||||||||
To fully utilize this functionality, the following products should be evaluated |
||||||||||||
Account Code Generator![]() |
This feature enables users to create, with the click of a button, multiple numbers of active accounts composed from a combination of different segments. In addition, they can create a specific G/L account in a number of different account groups simultaneously, for example, a separate account for each department. Account Code Generation is available only when the chart of accounts is based on segmentation accounts. |
|||||||||||
To fully utilize this functionality, the following products should be evaluated |
||||||||||||
Purchase Accounting![]() |
This feature enables companies that manage a continuous stock system to include the recording of expense accounts in journal entries. The relevant journal entries are created automatically due to the creation of the following purchasing documents that affect the inventory valuation: A/P invoice (not based on a goods receipt PO), A/P credit memo, goods receipt |
|||||||||||
To fully utilize this functionality, the following products should be evaluated |
||||||||||||
Budget Management![]() |
Companies use this feature to define and manage budgets. Users can configure budget allocation methods, define budget figures in any currency (local, foreign, or both), and create budget scenarios. The budget scenarios can be imported and exported from one company to another. SAP Business One enables users to activate online alerts that inform them whenever a transaction exceeds the monthly or annual budget limit. In addition, budget reports enable users to generate profit and loss statements, balance sheets, and trial balances within the framework of the defined budget. |
|||||||||||
To fully utilize this functionality, the following products should be evaluated |
||||||||||||
Project Code![]() |
Enables the user to define projects and link them to journal
transactions. Analysis can then be made of the business results
according to the projects run by the company.
|
|||||||||||
To fully utilize this functionality, the following products should be evaluated |
||||||||||||
Fixed Assets![]() |
As a subsidiary ledger to the general ledger in Financial Accounting, Fixed Assets for SAP Business One enables users to manage and monitor tangible fixed assets. Important processes such as acquisition, credit memo, retirement, and transfer are supported. The system calculates planned depreciations according to the costs of acquisition and production, as well as the useful life. In the fixed assets master data, users can monitor the change of values over the course of a year as a quick overview, while the depreciation forecast can simulate the future depreciation. As an important supplement to the balance sheet, the asset history sheet displays all changes to the asset portfolio (transactions) in a fiscal year. The data import functionality makes available historical data and beginning values of a fiscal year. |
|||||||||||
Financial Reports![]() |
||||||||||||
To fully utilize this functionality, the following products should be evaluated |
||||||||||||
Transaction Journal![]() |
This document lists journal transactions according to the transaction type, such as incoming payment and A/R invoice. The transaction type is automatically assigned to each transaction when it is created. |
|||||||||||
To fully utilize this functionality, the following products should be evaluated |
||||||||||||
Document Journal![]() |
Enables the user to generate a detailed report, which displays, journal entries that were automatically created by documents produced in SAP Business One, or manually, by the users. |
|||||||||||
To fully utilize this functionality, the following products should be evaluated |
||||||||||||
General Ledger![]() |
Enables the user to generate a report which summarizes all the
journal transactions posted, including manual transactions and
transactions that were created automatically. The report can be
generated according to a large range of selection
criteria, to fit the company needs.
|
|||||||||||
To fully utilize this functionality, the following products should be evaluated |
||||||||||||
G/L Accounts & Business Partners![]() |
Enables the user to create list of G/L accounts and/or business
partners according to selection criteria defined by the user.
|
|||||||||||
To fully utilize this functionality, the following products should be evaluated |
||||||||||||
Aging Reports![]() |
Contain information about the number of open
receivables/liabilities for a customer/vendor, as well as how old
the receivable/liability is. Analyzes receivables owed by
customers/liabilities to vendors. Sorts receivables/liabilities
according to age.
The aging reports can be generated according to a defined range of document date, due date and posting date. The interval can be calculated according to days, months or posting periods. In addition, it is possible to print the detailed ageing report consecutively for each business partner. The selection criteria of the report can be printed together with the report results, on a separate page. |
|||||||||||
To fully utilize this functionality, the following products should be evaluated |
||||||||||||
Customer Statement Report![]() |
This document lets users generate customer statements through the Customer Aging report. Customer statements display detailed account activity based on a user-defined cut-off date, as well as an aging of current and past due activity. The report displays both the customer reference and the document number. |
|||||||||||
To fully utilize this functionality, the following products should be evaluated |
||||||||||||
Transaction Report by Projects![]() |
Users can generate a report that lists journal transactions according to the projects linked to them. |
|||||||||||
To fully utilize this functionality, the following products should be evaluated |
||||||||||||
| ||||||||||||