Page History

...

• "Chart Of Accounts": this is where you define all the available GL Accounts; there is also a screen to associate the accounts to the organizations (this is a many-to-many relationship)
• "Companies": this is the entry point for all the GL operations; first of all you have to select the organization in which you want to work on GL tasks; once you have selected an organization you'll see new submenus:
  • Setup: this is where you setup the Account available to the organization, the accounting time periods, general accounting preferences, journals, transaction specific accounting preferences, etc. (there are submenu items for each of these tasks)
  • Accounting: this is where you operate your everyday GL activities: run accounting reports, view/edit/post accounting transactions and accounting transactions entries, etc...

How to setup and use a journal to group failed automatic accounting transactions

1. Go to the Companies>Setup>Journals menu and create a new journal using the form the screen: enter the journal name (e.g. "Error Journal")
2. Go to the Companies>Setup>Accounting Preferences menu and select the journal created at point 1 in the "error journal id" drop down field
3. You can filter the transactions/transaction entries in the error journal using the Companies>Accounting>Accounting Transactions or Companies>Accounting>Accounting Transaction Entries screens

Discussions about design decisions

...

All the screens under the Accounting-->Companies Accounting>Companies menu are specific for one internal organization (the one you select from the list in the "companies" menu). For this reason, when we implement new screens/forms/menu/links/etc... here we should always follow the following guidelines:

• the name of the variable that contains the id of the selected organization is: "organizationPartyId"
• all the links/menu etc,.. in this area should contain the "organizationPartyId" as the a get/post attribute
• all the forms in this area should have the "organizationPartyId" as an hidden field
• all the links in this area should point to screens in the same area: if a user is working in the GL of an organization, the links should always point to screen in the same context
• if the screen's purpose is to setup the GL (configuration) then it should reside under the "Companies">"Setup" Companies>Setup menu; if the screen's purpose is to perform an operational (everyday) GL task (running reports, browsing accounting transactions, account balances, etc...) then it should reside under the "Companies">"Accounting" Companies>Accounting menu

Should we create two new menu items under the

...

Companies>Accounting menu: AR and AP ?

Then each one of the menu items will have its own submenu: AR (sales invoices, customer payments, reports etc...), AP (purchase invoices, etc...)
These organization specific screens will be similar to the existing generic screens ("Invoices", "Payments" etc...) and so this will introduce some redundancy; is this acceptable?

...

• move and refactor the existing generic screens under the organization specific menus ("Companies"-->"Accounting"Companies>Accounting) and...
• ... split them into screens focused on AR or AP tasks (for example the existing "New Payment" screen currently shows two forms for incoming/outgoing payments; we could split it into two independent screens)
• or keep the existing screens and create new ones (extending where possible the existing artifacts, forms/scripts) specific for one organization and task's class (AR/AP)
• other ideas?

...