Extended GRC
MeshPulse
Continuous monitoring of operational data, with test rules that run on their own and exceptions that reach whoever needs to act.
- MeshPulse
- Monitoring rules
| Rule | Exceptions |
|---|---|
| Payment without an approved purchase order | 0Approved |
| Supplier sharing an owner with an employee | 2Attention |
| Duplicate payment (same amount, supplier and date) | 1Pending |
| Active access for a departed employee | 3Rejected |
If your monitoring still works like this
- Sample testing once a year?The problem happens in March and is found in November.
- A continuous audit script running on someone's laptop?When that person goes on vacation, monitoring stops.
- Exceptions in a spreadsheet no one handles?The rule finds the problem, but there is no queue, owner or deadline.
- Monitoring separate from risks and controls?The indicator worsens and the risk stays at the same level in the register.
What MeshPulse does
Rules over 100% of the data
Tests that run over the full population, not a sample.
Connection to sources
Reading from ERP, HR and other systems through connectors or file loads.
Exception queue
Every exception with an owner, deadline and justification, until it is handled.
Risk indicators
Results feed MeshRisk indicators and control testing in MeshControl.
History by rule
How many exceptions, who handled them and how long it took, by period.
Rule library
Ready-made, adjustable templates for payments, procurement, payroll and access.
The exception reaches whoever can resolve it.
Each exception goes to the process owner with a deadline. They justify or fix it, and audit sees the handling without asking for a report.
- MeshPulse
- Exceptions
- Duplicate payment
- Payments
- PG-90233 · PG-90241
- Supplier
- Contábil Delta
- Amount
- R$ 18,400.00
- Date
- 03/12
- Answer
- Payment reversed on 03/14, receipt attached
Continuous testing becomes control evidence.
Each rule's result is available as evidence on the linked control and as an indicator on the risk. No one redoes the test by hand.
- MeshPulse
- Payment without an approved purchase order
- Control
- CTR-052 Block on payments without an approved purchase order
- Risk
- R-012 Fraud in supplier payments
Illustrative screens with fictitious data.
Continuous auditing as the IIA describes it
Continuous monitoring by management and continuous auditing by the third line, with the same rule and separate roles, as in the Global Internal Audit Standards.
The AI suggests, the analyst decides
Mesh Intelligence suggests rules from the risks in the register and groups similar exceptions. No rule goes live without approval.
Fits with
- MeshControlDesign, testing and effectiveness of internal controls, linked to the risks they mitigate.
- MeshAuditFrom the annual plan to follow-up: programs, work papers, findings and action plans in one flow, with regulatory profiles such as BACEN and ANS.
- MeshRiskA living risk matrix, linked to the controls that mitigate each risk and the findings that challenge it.
Questions from monitoring teams
How does the data arrive?
Through connectors to existing systems or scheduled file loads. Data stays in Brazil, isolated per customer.
Do I need to code to create rules?
No. Library rules are adjusted through parameters. Custom rules can be written in SQL by those who know how.
Who sees the exceptions?
The process owner sees their own exceptions. Audit and risk see the whole set, with the handling.
See MeshPulse with a case from your industry
The demo is led by the founder, who has seven years of internal and external audit experience.
Modules are licensed separately. The platform comes with all of them.