Managing Manual Journals
Manual journals can be used for any transaction the accountant wishes to post directly to the General Ledger. For example, additional costs other than the landing costs of sold inventory belong in a manual journal. You can add a manual journal in Cin7 Core, save it as a draft or authorize it for posting to the general ledger and edit it if required. Manual Journals can be linked to a specific operation (sale, purchase, inventory, etc.) or a standalone journal entry.
Manual Journals are always processed in your base currency.
Note: If you are using Xero as your accounting system, this function will not be available in Cin7 Core. In this case, you can manage your manual journals through your accounting system.
Prerequisites
Set up the Chart of Accounts and Bank Accounts
Manual Journal permissions
Cin7 Core offers fine-grained control over user permissions. Cin7 Core allows you to set the following permissions for the financial module (Settings → Users and Roles), under Financial:
Journals - List & Tasks: Create, save and view journal tasks. View the list of journals.
Journal Task - Authorize: Authorize journal talks. List & Tasks permission must be granted.
Journal Task - Undo: All of Journal Tasks, but can also Undo approved/completed journal tasks. List & Tasks permission must be granted with full access.
Journal Task - Void: All of Journal Tasks, but can also Void approved/completed journal tasks. List & Tasks permission must be granted with full access.
Add a Manual Journal to an operation
Manual Journals can be added to Cin7 Core operations such as sale, purchase, inventory, etc. Each operation has a Manual Journals tab where they can be added.
Note: Sale/purchase invoices must be authorized, and inventory/production actions must be completed before a manual journal can be added.
To add a Manual Journal to an operation:
Go to the operation you wish to add a manual journal to.
Enter the Date the transaction occurs.
Click + or Add more items to add line items to the journal. Lines require a Description, Amount, and Accounts to be debited/credited.
Create a standalone Manual Journal
Manual journals can also be created that are not linked to any particular transaction or operation. To enter a new Manual Journal:
Go to Financials → New → Journal.
In the Narration field, enter the title or purpose of the journal entry. Keep narrations clear and specific.
Enter the Date the transaction occurs.
Click + or Add more items to add line items to the journal. Lines require a Description, Amount, and Accounts to be debited/credited.
Once the journal entry has been authorized, supporting images/documents can be attached to the Manual Journal from the Attachments tab if required.
Authorized journals will display under Financials → Journals.
Note: Journals should show up on the Sales by Product Details report unless the line total is 0, in which case the journal value will also be 0.
Clone a manual journal
Manual journal entries can be cloned for easier input of repeated or regular journal entries. Only standalone manual journals can be cloned, not manual journals added to another task (sale, purchases, production, etc.)
Go to Financials → Journals and select the manual journal to clone. Click Clone to create a draft journal with the same details. Fields can be edited before saving or authorizing the journal.
View Activity Logs
Activity Logs show changes made to journals (including creation, edits and voids) and identify which user performed each action. They can be viewed in the Activity Logs tab of each journal entry
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB