You set the rules. 100% of operations are checked before execution.
Your compliance officer wants to know what is checked, when, by whom, and what the check does not demonstrate. We have the solution: every operation is measured against the rules of your programme before it is executed. An operation outside the framework is blocked, not regularised afterwards.
Control of operations
The check happens before the payment, not in a monthly report
That is the difference with reporting produced after the event: the rule applies at the moment of the operation, and the proof is written in the same movement.
Your rules are set
You choose who, when, how much, where and what for: beneficiaries, suppliers or categories, geographic area, period, ceilings, online payments, cash withdrawals.
An operation is presented
A payment in store, online or by QR code, a transfer, a request for reimbursement against an invoice.
It is checked before execution
The operation is measured against the rules of the programme and the institution’s own controls, under AI supervision.
It is executed or blocked
If it complies with the framework, it goes through in real time. If not, it is refused, with a reason.
It is recorded on the blockchain
Amount, supplier, date, rule applied and reason for a refusal: the record is tamper-proof, and every authorised role sees it.
AI supervision
AI supervision comes in at two points. First, the analysis of the documents received at onboarding. Second, the check of every operation before execution, with detection and blocking of anomalies. It does not lighten the institution’s obligations: it makes it possible to meet them on 100% of operations rather than on a sample.
What the check establishes, and what it does not
The check and the proof cover the payment: the amount, the supplier, the date and the rule applied. A supplier category does not demonstrate the contents of the basket, and line-by-line control requires specific data and integration. We say so before signature, not after.
Exceptions and remedies
A refusal is justified by a rule of the programme. If the reason does not match the situation, the funder or the operator can adjust the rule. The beneficiary, for their part, can ask for their case to be reviewed through the complaints route. No operation is released without a record: an adjustment to a rule is dated and recorded as such.
Onboarding
What is requested, and from whom
Onboarding means providing the identification elements matching your organisation’s role, and appointing the persons authorised to act. This step comes before the programme opens: it is not an end-of-project formality.
| Role | Nature of the elements requested |
|---|---|
| Client organisation | Identification of the legal entity, of its representatives and of its beneficial owners; purpose of the programme and origin of the funds. |
| Authorised persons | Identification of the persons authorised to administer the programme and to commit the organisation. |
| Beneficiaries | Elements required to open their account and link them to the programme, to the extent provided for by the programme adopted. |
| Listed suppliers | Elements required to list them among the authorised suppliers of the programme. |
Allocation of responsibilities
Some obligations fall on MAP by virtue of its activity. Others fall on your organisation, by virtue of its role in the programme, in particular the assessment of the individual situations it reviews. That allocation is established at the first discussion and written into the contract.
What is shown, and to whom
The detail of the monitoring measures is not public: publishing it would reduce their effectiveness. We present it, to the extent useful, to organisations carrying out a supplier assessment, together with the documents in the assessment file.
Move your assessment forward
Tell us what your compliance department expects. We will specify what can be provided, and under which mode of access. A MAP expert will get back to you, with no commitment.