fewzen. limited
Published work · A2V · Compliance and project systems

Connecting compliance data with Sage 200 and Monday.com

I created a single source of truth for supply-chain compliance and project data in the A2V compliance management system. The published project brings together departmental information with Sage 200 and Monday.com integrations and a live management dashboard.

By Founder, Fewzen Limited

Actual delivered work

What is already public.

Source: the selected work summary and homepage evidence. The detail below stays within those published facts.

  • Created a single source of truth for supply-chain compliance and project data.
  • Included a live management dashboard and integrations with Sage 200 and Monday.com.
  • Replaced fragmented departmental workflows with connected data, staged requirements and role-based access.

Published outcomeA shared source of project and compliance data in place of fragmented departmental workflows.

For buyers planning similar work

Recommended design considerations.

The following is guidance for a new project. It is not a reconstruction of this client’s implementation or a claim that these specific controls were delivered.

01 /

Define the shared record and its boundaries

For a similar integration, start by deciding what a project or compliance record means across the departments involved. Agree which platform owns each field, which users can update it and how mismatched identifiers will be reconciled.

The objective is a coherent operational view, not copying everything everywhere. Your Sage 200 configuration, Monday.com boards and API access need investigation before a field mapping or implementation scope can be agreed. A published integration does not mean every edition or board design works identically.

02 /

Match access to responsibility

Role-based access is part of the published project description. For a new implementation, decide the actual roles with the people responsible for the data. Reading a dashboard, changing a compliance record and administering an integration may need different permissions.

Plan how users join, change role and leave. Define what evidence must be retained for decisions and who may inspect it. Connected data is not itself a certification of compliance; the business still needs appropriate policies, responsibilities and specialist advice where required.

03 /

Treat reconciliation and handover as design work

For future delivery, test stale records, conflicting edits, missing links and service outages. Make it clear when information was last confirmed and which items need attention. Avoid letting a dashboard look authoritative when an upstream connection has failed.

Agree the exception owner, credentials, monitoring, documentation and recovery procedure before launch. A staged approach lets users verify the shared record before more workflows depend on it. These are recommended commissioning considerations; the public summary does not disclose the original handover artefacts or detailed recovery design.

Related reading & support

From published work to your next decision.

Work directly with Matthew

Have a similar workflow to connect?

Bring the systems, the hand-off that is causing difficulty and the outcome you need. We can discuss a scoped project directly; a discovery review is an option, not a requirement.

Discuss your project with me ↗Prefer to write? Send a message. No sensitive records needed for an initial enquiry.