Multi-State Operations (MSO) and Centralized Payments
In this article
Related articles
Overview
This add-on functionality gives the user the ability to pay purchase invoices from a centralized payments company and will also allow new companies to be created easily with specific configurations and setup using a rapid start package.
This module allows for purchase invoices to be created and posted as normal in subsidiary companies with the added functionality of settling payments in a centralized payment company.
Centralized Payment Entries
The centralized payment entries page will provide details regarding transactions processed via centralized payments. Navigate to the Centralized Payment Entries list.
This page contains the centralized payment entries related to the entity you are in. Any errors related to the job queue processing will be listed in the Last Error Text field.
The payment journal posted in the central payment company will be automatically transferred and applied to the open vendor ledger entry in the entity company. Note: You will not see the payment entry listed on this page in the subsidiary company. See examples below regarding expected entries:
Centralized Payment Entries for Payment Company – this page will list the payments posted for entity invoices.
Centralized Payment Entries For Entity 1 – the page will list the invoices posted that were transferred to the centralized payment company:
The vendor ledger entries page will reflect the payment that was posted in the payment company and will automatically be applied to the invoice:
Entity Management
The user can control all new company creation and data management through the entity list page. This list is shared across all companies.
NOTE: When choosing to re-sync data it is important to note that all data in the company you are syncing is overwritten with data in the designated configuration package. This action can only be rolled back by the 365 development team by restoring a backup of the database, this action is billable.
Data Sync
In the Entity List page enter the following information for new company creation:
Entity Code – Specifies the entity code for the new company.
New Company Name – The name of the new company.
Use Template Company – The designated template company which will house the package used to transfer setups and configurations.
Allow Master Data Sync – When checked the user can choose to re-sync data.
Re-sync Company Using Package – The package used for data resyncs.
Company Name – Once the new company is created this field will populate with the new company name entered in step 2.
If the new company will be included in the centralized payment function the user must complete all fields listed in the configuration section of this document for Centralized Payments.
When the new company has been created the Company Created boolean will be checked and the date/time and user ID fields will populate.
The Re-sync Master Data function is designed to perform a simple copy of the configuration data from one company to another regularly to keep the same standardized configurations in place. For companies using consolidations within 365 Cannabis, this function will be useful when new accounts are added to the COA, the user will no longer need to manually update the chart in each company used in consolidations.
It may be beneficial to create a separate package used for resyncs rather than using the same package used for new company creation as all data entered in the tables and fields listed in the package will be overwritten and cannot be restored without development intervention.
When the data sync is successful the re-sync date and time and user fields will populate:
Common Issues
Note: The entity list in the Centralized company must include the record of the company from which you want to pull the data.
Note: The Purchase Invoice and payment no. series MUST be unique. They cannot be the same as the other companies because the system checks the vendor ledger entries Document No. and document type.
Microsoft changed functionality from RTC to BC which prohibits duplicate document numbers, which causes a background error. The number series needs to be modified and unique to each company for both payments and invoices.