Accounts Payable
Multi-Muni Relational Databases Overview
Multi-muni functionality was created to allow two related entities to have separate financial operations with integration between financial systems to share/sync relevant data between the two databases.
The relationship consists of a parent system (i.e. the Town/City finance department) and a child system (i.e. a school finance department). The table below shows the different areas of the product suite that, when configured for multi-muni functionality, will sync data between the two systems.
Application Area | Functionality Description | Data Integrations/Synchronization |
---|---|---|
Vendors | Vendors will be managed only within the parent database. | Vendor data changed in the parent database will be synced to the child database. |
General Ledger | The Reference Account field within the child general ledger will be used to link to parent GL accounts. For example, multiple child expense accounts will roll up to a single parent GL account. The parent GL account will be included in the Reference Account field on the related child GL accounts. | Journal entry data will be automatically be created in the parent database for related child GL activity. |
AP Invoices | Parent and child entities will process AP separately. | Invoices committed in the child database will be copied into the parent database in order to process AP checks. Journal entries related to the child AP Invoices will be created in the parent database when the invoices are copied from child to parent. |
AP Checks | AP checks will be processed in the parent database. | After AP checks are processed in the parent database, they will be copied into the child database and linked to related invoices in order for child users to view AP check information. |
Payroll | Payroll and employee records will be managed separately in the child and parent databases. | When Payroll is processed, journal entries for the payroll activity will be created in the parent database. Payroll benefits payments will also be created in the child database as invoices, then copied into the parent system to be processed as AP invoice/checks described above. |
W-2s | W-2s will be managed separately in the child and parent databases. | When a W-2s or W-2 Adjustments batch is committed in the child database, an encrypted JSON file will be created with all the pr_w2_print records for the batch and drop it in the archive for the associated parent database. After the encrypted file is imported into the parent database, it will be deleted from the archive. |
Bank Reconciliation | Bank reconciliation will happen only in the parent database. | BR checks will be created in the parent database for related bank reconciliation activity generated in the child database. |
Cash Receipts | Revenue entries will be made separately in the parent and child databases. | Journal entries will be created in the parent database for related revenue activity in the child database. |