Accounts - Revision history

Anw: Categorisation

2024-06-10T09:14:58Z

Categorisation

← Older revision		Revision as of 11:14, 10 June 2024
Line 338:		Line 338:
	[[Category:C-TMS Modules\|C-100]]		[[Category:C-TMS Modules\|C-100]]
	[[Category:C-TMS User Guide\|BC-100]]		[[Category:C-TMS User Guide\|BC-100]]
	~~[[Category:TEST\|C-100]]~~
	</noinclude>		</noinclude>

Anw: Merged from training document

2024-06-10T09:10:09Z

Merged from training document

← Older revision		Revision as of 11:10, 10 June 2024
Line 256:		Line 256:
	* Activity one of Load, Unload or Blank.		* Activity one of Load, Unload or Blank.
	* Text		* Text

			To generate payments, the service type should also be set up as a payment type.

			If a service type is set to Service event Order, service charges are applied to the order, if the service event is set to trip, the service charges are applied to the trip. Services may be set to an event type Both, where both are applicable.


	You can enter sliding charges against appropriate services:		You can enter sliding charges against appropriate services:
Line 263:		Line 268:

	== Services Capture ==		== Services Capture ==
	You can enter charges captured against services here.		In addition to defining the service, you must also define how the service is charged.

			You can enter charges captured against services here.

	<center>[[Image:account_services_capture.png\|800px]]</center>		<center>[[Image:account_services_capture.png\|800px]]</center>

	You can enter:		You can enter:
	* Service Name		* Service Name - the service.
	* Debit Account		* Debit Account - the debit account is set to Customer for revenue payments. You can define different charges for different customers. If the service is charged as the same amount for every customer, a single record may be created for all customers (selecting "ALL").
	* Credit Account		* Credit Account - the credit account is set to the cost centre.
	* Effective Date		* Effective Date
	* Charge Type		* Charge Type - one of:
			** Fixed - A Fixed charge type means the payment is generated for the amount defined in the services capture.
			** Hours - An Hours charge type means the payment amount is based on the number of hours required multiplied by the amount defined. Hours may only be defined for those services that are provided in time.
			** KG - A KG charge type means the amount is based on the weight on the order multiplied by the amount defined for the service.
	* Amount		* Amount

Anw: Added cross-reference to associated imports

2024-06-04T08:57:46Z

Added cross-reference to associated imports

← Older revision		Revision as of 10:57, 4 June 2024
Line 3:		Line 3:

	Accounts can be created manually using the Accounts screen or they can be created automatically when payments are generated - if the user has been given access to the function.		Accounts can be created manually using the Accounts screen or they can be created automatically when payments are generated - if the user has been given access to the function.

			Accounts (and associated configurations) may also be created through [[Imports]]:
			* [[Imports_Details#ACCOUNT\|ACCOUNT]]
			* [[Imports_Details#ACC_SERVICES\|ACC_SERVICES]]
			* [[Imports_Details#ACC_SRV_RTS\|ACC_SRV_RTS]]
			* [[Imports_Details#CURR_USAGE\|CURR_USAGE]]
			* [[Imports_Details#INVOICE_RQTS\|INVOICE_RQTS]]

	<center>[[Image:accounts.png\|800px]]</center>		<center>[[Image:accounts.png\|800px]]</center>

Anw: test

2024-05-17T06:42:48Z

test

← Older revision		Revision as of 08:42, 17 May 2024
Line 321:		Line 321:
	[[Category:C-TMS Modules\|C-100]]		[[Category:C-TMS Modules\|C-100]]
	[[Category:C-TMS User Guide\|BC-100]]		[[Category:C-TMS User Guide\|BC-100]]
			[[Category:TEST\|C-100]]
	</noinclude>		</noinclude>

Anw: Categorisation

2024-05-14T09:43:03Z

Categorisation

← Older revision		Revision as of 11:43, 14 May 2024
Line 317:		Line 317:


			<noinclude>
	[[Category:Accounts\|100]]		[[Category:Accounts\|100]]
	[[Category:C-TMS Modules\|C-100]]		[[Category:C-TMS Modules\|C-100]]
	[[Category:C-TMS User Guide\|BC-100]]		[[Category:C-TMS User Guide\|BC-100]]
			</noinclude>

Anw: Merged from training document

2024-05-13T07:16:07Z

Merged from training document

← Older revision		Revision as of 09:16, 13 May 2024
Line 1:		Line 1:
	The Accounts screen is used to maintain ~~Accounts~~, Invoice ~~Requirements;~~ Payment Types and Accounting Periods (used for Oracle Financials Interface).		The Accounts screen is used to maintain the account type of a particular entity such as Customer, Carrier or a Cost Centre.
			This function is also used to maintain the Invoice requirements of a particular entity, along with Payment Types and Accounting Periods (used for Oracle Financials Interface).. Accounts Maintenance form can be accessed from Maintenance Menu.

	Accounts can be created manually using the Accounts screen or they can be created automatically when payments are generated - if the user has been given access to the function.		Accounts can be created manually using the Accounts screen or they can be created automatically when payments are generated - if the user has been given access to the function.
Line 8:		Line 9:
	== Accounts ==		== Accounts ==
	An account record needs to be set up for each carrier, customer, and cost centre that is used within the C-TMS System.		An account record needs to be set up for each carrier, customer, and cost centre that is used within the C-TMS System.

			To enable successful financial tracking, every entity involved such as customer, carriers must be set up in the Accounts Maintenance form.
			To create a New Account, click on the 'New' button which will take you to Add New Account popup shown above.

	{{Note}} Customers added through the [[Customer Onboarding Interface]] will have had an account and currency configured for it automatically.		{{Note}} Customers added through the [[Customer Onboarding Interface]] will have had an account and currency configured for it automatically.

	~~You must enter~~ the ~~following~~ information to ~~create an~~ account:		If you are setting up a Customer Account, then select the Customer option from the Account Type drop down box. The Owner would be the Customer ID and the Account ID field will be populated from the Customer ID field. Populate the VAT Country code accordingly. These 4 fields are the minimum information required to set up a new account.
	* Account Type - one of Customer, Carrier, Centre, Group.		* Account Type - one of Customer, Carrier, Centre, Group.
	* Owner - the owner of the account, either a Customer, Carrier, Centre, Group, selected from a lookup.		* Owner - the owner of the account, either a Customer, Carrier, Centre, Group, selected from a lookup.
Line 17:		Line 21:
	* Inactive - unchecked for an active account.		* Inactive - unchecked for an active account.

	~~You~~ may also ~~enter~~ the ~~following~~ information:
			The external system reference allows you define references and codes for the account to be used in external systems for example Oracle Financials. The external references are not required fields.

			External systems may be used to automatically transfer funds. ln this instance bank account information may also be defined for the account.

			Bank information:
	* Bank Name		* Bank Name
	* Bank Acc Name		* Bank Acc Name
Line 25:		Line 34:
	* VAT Reg No		* VAT Reg No

	External System References ~~may also be entered~~:		External System References information:
	* Vendor Code		* Vendor Code
	* Vendor Site ID		* Vendor Site ID
Line 36:		Line 45:

	== Invoice Requirements ==		== Invoice Requirements ==
			This form allows the set up of the Account that needs to be Debited and the Account that needs to be created for a given transaction.

	Invoice Requirements are used to define the type of invoice that will be created for a customer or carrier and the frequency with which they will be generated. The Debit and Credit accounts are required along with the invoice period - which can be Daily, Weekly or Monthly; this influences how often the invoice is created. Invoices can be generated automatically or manually.		Invoice Requirements are used to define the type of invoice that will be created for a customer or carrier and the frequency with which they will be generated. The Debit and Credit accounts are required along with the invoice period - which can be Daily, Weekly or Monthly; this influences how often the invoice is created. Invoices can be generated automatically or manually.

Line 44:		Line 55:
	* Credit Account		* Credit Account
	* Inactive - unchecked for an active account.		* Inactive - unchecked for an active account.

			In case of Customer receivables, the Debit Account must be the Customer Account and the Credit Account must the ‘Own’ Account.

			In case of Vendor/Carrier payment, the Debit Account must be the ‘Own Account’ and the Credit Account must be that of the Vendor/Carrier.


	You may also enter the following information:		You may also enter the following information:
	* Create Provisional		* Create Provisional
	* Create File Ref		* Create File Ref
	* Non-POD payments		* Non-POD payments- Can payments for an order with no POD be included on Invoices?
	* Action - one of Generate, Manual, Reconcile, Self Bill, Self Bill-Cust		* Action - How are the payments applied to an invoice, one of Generate, Manual, Reconcile, Self Bill, Self Bill-Cust
	* Self Billing Eff Date		* Self Billing Eff Date
	* Accounting Date - one of:		* Accounting Date - Indicates how the revenue date is set and when a payment may be actualised. Only actualised payments may be invoiced. See below for settings, one of:
	** Approval		** Approval - The payment is available one the payment is approved.
	** Creation		** Creation - The payment is available once the delivery trip has been completed and the revenue date is set to creation date
	** Collection		** Collection - The payment is available once the delivery trip has been completed and the revenue date is set to the start time of the collection trip
	** Delivery		** Delivery - The payment is available once the delivery date has been completed and the revenue date is set to the end time of the delivery trip
	** Order Collection		** Order Collection - The payment is available after the early available date and time has passed. The revenue date is set to the early_avail date
	** Schedule		** Schedule - The payment is available once the order is scheduled and the revenue date is set to the start of the collection trip.
	** Service		** Service - The payment is available once the order is scheduled and the service level is Standard. Non Standard orders must be released manually
	** Manual		** Manual -The release payment flag must be set to Y to allow the payment to be available. This flag can only be set manually in the payment screen. The revenue date will be set to the date the manual release flag was set.
	** Order Delivery		** Order Delivery - The payment is available after the early delivery date and time has passed. The revenue date is set to the early_del date.
	* Generation Delay - a number of days delay in generating the invoice from an approved payment.		* Generation Delay - a number of days delay in generating the invoice from an approved payment.
	* Terms - ~~payment terms~~, selected from a lookup of payment terms that are maintained in this screen on the ''Invoice Terms'' tab.		* Terms - Terms indicates the amount of time a customer is allowed before the invoice must be settled, selected from a lookup of payment terms that are maintained in this screen on the ''Invoice Terms'' tab.
	* Payment Method - one of Cash, Cheque, Credit Card, Direct Debit, Other Directs.		* Payment Method - How the invoice will be settled, one of Cash, Cheque, Credit Card, Direct Debit, Other Directs.
	* VAT Country		* VAT Country
	* VAT Reg No		* VAT Reg No
	* Base Cost Invoicing		* Base Cost Invoicing
	* Journal - a lookup of available journal numbers.		* Journal - a lookup of available journal numbers.
	* Invoice Period - one of Daily, Weekly, Monthly, Date List.		* Invoice Period - How often the customer is invoiced, one of Daily, Weekly, Monthly, Date List.
	* Day in Period		* Day in Period - Values entered are dependent upon the period selected.
	* Export - an export ~~format~~ from the available values in the drop-down list.		* Export - The type of export that is generated and sent to the external system, selected from the available values in the drop-down list.


Line 98:		Line 114:

	== Payment (Transaction) Types ==		== Payment (Transaction) Types ==
	~~Every~~ payment ~~must be of~~ a ~~particular~~ payment type.		For every type of payment, a payment type must exist in the reference table. The payment records are maintained in the Accounts Maintenance screen. To create a new record, click '''New'''.

	<center>[[Image:accounts_payment_types.png\|800px]]</center>		<center>[[Image:accounts_payment_types.png\|800px]]</center>

	Payment types are configured in the following way:		Payment types are configured in the following way:

	* Payment Type		* Payment Type
	* Screening		* Screening
	* Inactive		* Inactive
	* Description		* Description
	* Event Type - This may be set to No Event, Order, Trip, Alloc or blank (miscellaneous).		* Event Type - This may be set to No Event, Order, Trip, Alloc or blank (miscellaneous). This dictates the information that is saved in the event reference on the payment record. For orders, the oms_ref is stored as the revent reference, for trips, the trip id and schedule is stored.
	* Alloc To		* Alloc To
	* Alloc Method - one of Base Cost, Weight and Distance, RPE and Distance, Specified Order, Specified Customer.		* Alloc Method - one of Base Cost, Weight and Distance, RPE and Distance, Specified Order, Specified Customer.
Line 126:		Line 141:
	* Security Surcharge		* Security Surcharge
	* Scheduled Order Split		* Scheduled Order Split

			Example Payment Types

			ORD CHARGE, SECURITY, PACKAGE and all service types (eg TAILGATE, DG, LABOUR)

	{{Note\|		{{Note\|

Anw: Updated to latest screen version

2024-05-08T14:13:28Z

Updated to latest screen version

Show changes

Anw: Categorisation

2024-05-08T11:56:10Z

Categorisation

← Older revision		Revision as of 13:56, 8 May 2024
Line 1:		Line 1:
			{{Incomplete}}

	The Accounts screen is used to maintain Accounts, Invoice Requirements; Payment Types and Accounting Periods (used for Oracle Financials Interface).		The Accounts screen is used to maintain Accounts, Invoice Requirements; Payment Types and Accounting Periods (used for Oracle Financials Interface).

Anw at 11:44, 11 May 2011

2011-05-11T11:44:39Z

← Older revision		Revision as of 13:44, 11 May 2011
Line 49:		Line 49:

	This status can be changed by users who have access to new function ACC_AMEND_FUELSURCH_PYTTYPE_STATUS using the Edit pop-up. The Fuel Surcharge check box can be toggled for all trip level payment types except Fuel Surcharge (which messages and prevents self fuel surcharging). Setting this flag to checked only results in its associated trip payments being surcharged if the associated carrier is attached to a currently valid surcharge for that trip’s parametrised validity date (SCH_TRIP.START_TIME – Start date or SCH_TRIP_AUDIT.ACTION_DATE for trip_status of ENABLED).		This status can be changed by users who have access to new function ACC_AMEND_FUELSURCH_PYTTYPE_STATUS using the Edit pop-up. The Fuel Surcharge check box can be toggled for all trip level payment types except Fuel Surcharge (which messages and prevents self fuel surcharging). Setting this flag to checked only results in its associated trip payments being surcharged if the associated carrier is attached to a currently valid surcharge for that trip’s parametrised validity date (SCH_TRIP.START_TIME – Start date or SCH_TRIP_AUDIT.ACTION_DATE for trip_status of ENABLED).

			[[Category:Accounts\|100]]
			[[Category:C-TMS Modules\|C-100]]
			[[Category:C-TMS User Guide\|BC-100]]

Admin at 13:42, 12 November 2010

2010-11-12T13:42:22Z

← Older revision		Revision as of 15:42, 12 November 2010
Line 8:		Line 8:
	== Account Setup ==		== Account Setup ==

	An account record needs to be set up for each carrier, customer, and cost centre that is used within the [[~~MTS~~]] System. The OF Segments and OF Id is specific for the interface between [[~~MTS~~]] and Oracle Financials and should be populated if the package is used.		An account record needs to be set up for each carrier, customer, and cost centre that is used within the [[C-TMS]] System. The OF Segments and OF Id is specific for the interface between [[C-TMS]] and Oracle Financials and should be populated if the package is used.

	== Invoice Requirements ==		== Invoice Requirements ==
Line 16:		Line 16:
	<ul>		<ul>
	<li>'''Automatically generated Invoices''' <br/>		<li>'''Automatically generated Invoices''' <br/>
	If the invoice requirement for a given debit/credit account pair is set to Auto Generate (or self bill in the case of a Carrier), then payments are added to invoices by invoking the Generate Invoices process. This process is done in the invoices form. For Self Bill Carriers a list of completed trips and an Invoice will be emailed to the Carrier at appropriate times. For each invoice that is generated, [[~~MTS~~]] will automatically apply all payments not already invoiced and occurring before the invoice date.</li>		If the invoice requirement for a given debit/credit account pair is set to Auto Generate (or self bill in the case of a Carrier), then payments are added to invoices by invoking the Generate Invoices process. This process is done in the invoices form. For Self Bill Carriers a list of completed trips and an Invoice will be emailed to the Carrier at appropriate times. For each invoice that is generated, [[C-TMS]] will automatically apply all payments not already invoiced and occurring before the invoice date.</li>

	<li>'''Manual Invoice Reconciliation''' <br/>		<li>'''Manual Invoice Reconciliation''' <br/>
Line 40:		Line 40:
	== Accounting Periods ==		== Accounting Periods ==

	The interface between Oracle Financials and [[~~MTS~~]] require Accounting Period names to be set up (they need to match exactly those which are used in the package). When a Period is created, the accruals created flag is set to false, this flag is populated by the interface program and indicates which months have had accruals generated and sent to the OF System.		The interface between Oracle Financials and [[C-TMS]] require Accounting Period names to be set up (they need to match exactly those which are used in the package). When a Period is created, the accruals created flag is set to false, this flag is populated by the interface program and indicates which months have had accruals generated and sent to the OF System.

	== Journals ==		== Journals ==

	The interface between Exact and [[~~MTS~~]] require journal number. The journal number is set according to the country code of the customer. When an invoice is created, the journal is got from Journals table.		The interface between Exact and [[C-TMS]] require journal number. The journal number is set according to the country code of the customer. When an invoice is created, the journal is got from Journals table.

	== Payments surcharging flag ==		== Payments surcharging flag ==

	This status can be changed by users who have access to new function ACC_AMEND_FUELSURCH_PYTTYPE_STATUS using the Edit pop-up. The Fuel Surcharge check box can be toggled for all trip level payment types except Fuel Surcharge (which messages and prevents self fuel surcharging). Setting this flag to checked only results in its associated trip payments being surcharged if the associated carrier is attached to a currently valid surcharge for that trip’s parametrised validity date (SCH_TRIP.START_TIME – Start date or SCH_TRIP_AUDIT.ACTION_DATE for trip_status of ENABLED).		This status can be changed by users who have access to new function ACC_AMEND_FUELSURCH_PYTTYPE_STATUS using the Edit pop-up. The Fuel Surcharge check box can be toggled for all trip level payment types except Fuel Surcharge (which messages and prevents self fuel surcharging). Setting this flag to checked only results in its associated trip payments being surcharged if the associated carrier is attached to a currently valid surcharge for that trip’s parametrised validity date (SCH_TRIP.START_TIME – Start date or SCH_TRIP_AUDIT.ACTION_DATE for trip_status of ENABLED).