Differences

This shows you the differences between two versions of the page.

--- other_stuff:transaction_categories [2019/11/29 16:40] – Gary Willetts
+++ other_stuff:transaction_categories [2024/01/15 06:13] (current) – [26.06. Transaction categories] Mark Glover
@@ Line 1: / Line 1: @@
-{{indexmenu_n>70}}
+{{indexmenu_n>60}}
-====== 22.07. Transaction categories ======
+====== 26.06. Transaction categories ======
 Categorising transactions allows you to group transactions together when reviewing or reporting them. Each type of transaction can have its own list of categories. For example customer invoices might have a category "normal" and "urgent". Inventory adjustements might have categories "expired", "damaged", "stocktake", "annual stockatake" or "monthly stocktake" etc.
@@ Line 14: / Line 14: @@
 Here you enter the details of the category:
-  * **Master category**: select the master category that this one will belong to. Master categories are a way of grouping other transaction categories together, even categories of different types, to make reporting easier (see section [[reports:transactions|11.03. Transaction reports]] for details of how master transaction categories can be used in reporting). Master transaction categories are fixed in the system and cannot be edited; those available are Damaged, Expired, Found, Lost, Stocktake, Stolen and Other.
+  * **Master category**: select the master category that this one will belong to. Master categories are a way of grouping other transaction categories together, even categories of different types, to make reporting easier (see section [[reports:transactions#transaction_category_filter|11.03. Transaction reports, Transaction category filter]] for details of how master transaction categories can be used in reporting). Master transaction categories are fixed in the system and cannot be edited.  Those available are:
+    * Damaged
+    * Expired
+    * Found
+    * Lost
+    * Stocktake
+    * Stolen
+    * Other
   * **Category code**: the code of the transaction category. Not displayed in mSupply but you can filter categories by this so it provides another way to select relevant categories when reporting.
   * **Category Description**: the name of the category, visible throughout mSupply. Also filterable when reporting.
@@ Line 21: / Line 28: @@
 <WRAP center round tip 60%>
-For systems using [[other_stuff:remote_sync#remote_synchronisation|Remote Synchronisation]], Transaction Categories are '**System**' data and can only be edited on the Primary Server. Any edits then synchronise to all relevant satellites.
+For systems using [[synchronisation:introduction|Remote Synchronisation]], Transaction Categories are '**System**' data and can only be edited on the Primary Server. Any edits then synchronise to all relevant satellites.
 </WRAP>
 <WRAP center round info 60%>
-There is a preference to [[preferences:invoices#require_category_entry_on_customer_invoices|Require category entry on customer invoices]].  This would apply to all customer invoices issued for all stores **Active** on the server.
+There is a 'server' preference to [[preferences:invoices#require_category_entry_on_customer_invoices|Require category entry on customer invoices]].  This would apply to all customer invoices issued for all stores **Active** on the server.
 </WRAP>
-See the [[faq:how_to_report_by_invoice_category|How to report by invoice category]] section for details on how to use the transactino categories in reporting.
+See the [[faq:how_to_report_by_invoice_category]] section for details on how to use the transaction categories in reporting.
 \\
 \\
-|  //  Previous:  **[[other_stuff:edit_menu |22.06. Edit menu]]** | | Next: **[[other_stuff:virtual_stores |22.08. Virtual stores]]** //  |
+|  //  Previous:  **[[other_stuff:edit_menu]]** | | Next: **[[other_stuff:virtual_stores]]** //  |
 ---- struct data ----
+pagestatus.status    :
 ----