MHC provides a documented integration layer for organizations using Infor Lawson and Infor CloudSuite. Current MHC materials say its solutions complement Infor by extending document, payment, accounts-payable, payroll and employee self-service processes rather than requiring organizations to abandon their Infor environment.
This relationship explains why employees and finance staff sometimes encounter both names in the same workflow.
Infor and MHC are not the same system.
They can work together.
Infor as the Core Enterprise Environment
Infor products can serve as core systems for finance, supply chain, HR and related enterprise functions.
MHC’s integration page specifically addresses organizations:
- already using Infor Lawson;
- upgrading toward Infor CloudSuite;
- implementing Infor as a new customer.
MHC then adds automation around processes where organizations want additional document or workflow capability.
Payroll and HR
The current MHC Infor page specifically describes using the integration to generate and distribute:
- payroll documents;
- tax documents;
- other key employee documents;
- secure 24/7 self-service access.
This gives us a clear employee-side architecture.
Infor may hold core workforce information.
MHC can produce and distribute documents based on that information.
Accounts Payable
The same integration also serves finance teams.
MHC describes AP invoice capture, OCR, web forms, purchase-order workflows and AP payment automation working around the Infor environment.
That means the exact same MHC/Infor relationship can touch both an employee W-2 and a vendor invoice.
Pre-Built Interfaces
MHC currently says it offers pre-built interfaces designed to simplify implementations with Infor Lawson and CloudSuite.
That matters because integration costs are not just about whether an API theoretically exists.
Organizations care about how much implementation work is required to make real business processes function.
Lawson to CloudSuite Migration
MHC also positions its integration as supporting organizations moving from Lawson toward CloudSuite.
Its current documentation says the MHC layer can preserve complementary functionality while allowing customers to continue using Infor standards during the upgrade path.
This can be important for organizations with mature document processes that do not want an ERP modernization project to force a simultaneous redesign of every output.
Cloud and On-Premises Environments
MHC states that its Infor experience covers both cloud and on-premises deployments.
That reflects the reality of Lawson’s long history.
Some organizations remain on older architectures while others have moved further into Infor’s cloud products.
Infor Does Not Become the MHC Portal
From an employee perspective, the system names can blur.
A worker may know that payroll “comes from Lawson” but retrieve the document through an MHC-powered self-service interface.
Those statements are not contradictory.
One system can be the data source while another handles document delivery.
Why Pay Stubs Can Look Different From the Payroll System
MHC’s current payroll product specifically promotes customizable document design and even references making payroll output more readable than the raw descriptions inside the payroll system.
This illustrates the value of the document layer.
The source system stores accounting and payroll data.
MHC can turn that data into a user-facing document optimized for the employee.
AP Follows the Same Pattern
The finance side is structurally similar.
Infor may contain purchase-order, invoice and accounting information.
MHC can add:
- invoice capture;
- routing;
- document imaging;
- payment output;
- remittance communication.
Again, integration extends rather than necessarily replaces.
Which System Should Be Troubleshot?
Classify the problem.
Employee record is wrong
→ likely core HR/payroll data issue.
Correct data exists but document was not produced
→ document-generation/workflow issue.
Document exists but employee cannot access it
→ self-service/access issue.
Invoice approval is stuck
→ AP workflow issue.
The MHC/Infor relationship contains several layers, and the visible symptom does not always identify which one failed.
Why This Integration Is an Important MHC Topic
Infor is not merely one logo on a generic integrations page.
MHC maintains a dedicated current page describing Lawson and CloudSuite support across both finance and employee workflows.
That source depth makes the relationship substantial enough for its own article.