You choose who, when, how much, where and what for.
We have the solution. Earmarking is the rules you set before the spend: who, when, how much, where and what for. They are written before the first spend and applied to every operation, before execution. Anything outside the rules is refused, with a readable reason.
You want to…
You want to decide in advance the frame within which a budget may be spent, without having to check every spend weeks after the event.
- A funder pays a budget of 600,00 € into the account of beneficiary 05, out of the 7 200,00 € envelope of the Equipment 2026 programme. Every amount and every value in this animation is an example.
- Five rules are written before the spend: who, beneficiary 05; when, 1 March to 30 June; how much, 300,00 € per transaction; where, mainland France; what for, professional equipment.
- A payment of 120,00 € is presented at a referenced supplier: the five rules are satisfied, the payment is accepted.
- A second payment of 120,00 € is presented at a supplier outside the authorised area: the “where” rule is not satisfied, the payment is blocked before it is executed.
Concrete benefits
What this service changes for your teams.
Control before the spend
100% of operations are checked before execution. Checking no longer happens on paperwork, once the money has gone.
Eight rules, one readable matrix
Suppliers, geographic area, period, ceilings, online payments, cash withdrawals, activation, beneficiaries: the funder reads its own frame without jargon.
Dignity for the beneficiary
A refusal is immediate and gives a reason; an authorised spend goes through like any ordinary payment. Nobody has to justify a purchase at a counter.
Scope of the service
The core of the service, and what is set with you.
The core is the same for every programme. What varies from one programme to the next is set with your teams, before the first spend.
What the service covers
- A use framed by written rules, described by the Poto case study.
- The settings MAP presents: beneficiaries, suppliers, areas, periods, ceilings.
- The rule being applied at the moment of the operation, and the reason for refusal given back to the beneficiary.
What we set with you
- The rule matrix for your programme: suppliers or categories, area, dates, amounts, online payments, withdrawals.
- The accepted and refused test cases, rule by rule and then in combination.
- Exceptions, derogations and the procedure for changing the rules while the programme is running.
An example for a buyer
A company, responsible for an equipment budget for its staff.
A company funds a piece of equipment over a given period, with selected suppliers. Purchases outside the rules are refused, under rules tested before the programme opened.
- Envelope per beneficiary (example)
- €600.00
- Period (example)
- four months
- Area (example)
- France
- Ceiling per operation (example)
- €250.00
- Online payments (example)
- allowed
- Cash withdrawals (example)
- blocked
Situation and values given as an example. No result and no price is announced.
Deliverables and how it works
What we put in place with you.
- The rule matrix, written to be read by the funder.
- The configuration of the programme and the accepted and refused test cases.
- The reasons for refusal given back to the beneficiary and the handling of exceptions.
- The procedure for changing the rules and the retention of the version applied.
The eight rules of a programme
Every rule is written before the first spend. It is tested on its own, then in combination, and applied to the operation as it happens.
| Rule | What it controls | What it does not prove |
|---|---|---|
| Beneficiaries | The people or organisations designated by the programme, and them alone. | The identity of the person physically presenting the card, without dedicated authentication. |
| Suppliers | A named, referenced supplier, or a category of merchants. | The contents of the basket or the compliance of the service invoiced by that supplier. |
| Geographic area | The territory from which the spend can go through. | The place where the good or the service paid for is actually consumed. |
| Period | The window during which operations are possible. | The right to redeem the balance, which follows its own contractual rules. |
| Ceilings | The maximum amount, per operation, per day or over the whole period. | The economic relevance of a spend made under the ceiling. |
| Online payments | The authorisation or blocking of remote payments. | The reliability of the merchant site where the payment is presented. |
| Cash withdrawals | The authorisation or blocking of withdrawals. | The use made of the cash when a withdrawal is authorised. |
| Activation | The moment the budget becomes usable, and its suspension. | The actual handing over of the card to the beneficiary or its activation by them. |
Try a rule on a fictitious scenario
Choose a supplier and a ceiling, submit the operation, read the rule that explains the result.
Breakdown of the envelope: used, reserved, available. No negative balance is possible in the simulation.
Framework of use defined for this example
The funder has allocated the envelope to food expenditure, at the merchants it has listed, for holders enrolled in the programme, within a daily cap. These four elements make up the framework: they determine the outcome of every transaction.
Authorised beneficiary
Only beneficiaries enrolled in the programme have a usable balance.
Authorised merchant
The programme lists the accepted merchant categories.
Daily cap
Maximum cumulative amount of transactions over one day.
No transaction submitted yet. Open the “Rules” tab, choose a scenario, then submit the €24.50 transaction.
| Time | Amount | Recipient | Status | Reason | Action |
|---|
Educational simulation, fictitious data. It neither collects nor moves any funds, connects to no system and does not constitute the list of features offered commercially. Each rule available in a real programme is defined with your organisation and documented in the contract.
What has to be provided for explicitly
Can a refused operation be authorised afterwards?
What happens if a supplier changes category?
Can the rules of a running programme be changed?
What becomes of a balance left unused at the end of a period?
Conditions and proof
What this service is not, and what we demonstrate.
Proof expected before any commitment
Before any commitment, we test each rule on its own, then in combination: an authorised case, a refused case and an exception. We keep the version of the rule applied.
Frequently asked questions
The questions asked about this service.
What can I decide for my programme?
Who, when, how much, where and what for. You choose the registered beneficiaries, the ceilings per transaction, per day or per month, the period, the authorised suppliers or categories, the geographic area. You allow online payment and cash withdrawals, or you do not. For example: €600.00 per household, at food suppliers in the chosen area, for three months.
What happens if a payment is refused or refunded?
100% of operations are checked before execution. A payment outside the rules is refused, and the reason is recorded. The beneficiary knows why straight away. Refunds and remaining balances follow the programme contract. An end date does not make the funds disappear.
Is this a meal-voucher or mobility scheme?
What information do my teams get?
Every payment, its status and the rule applied, in real time, in the view set for each role. Authorisation and final settlement remain two distinct steps.
Programme and related services
The services that go with this one.
The services combine with one another. We decide with you which ones your programme needs, and the scope of each.
Look at this service with us
Tell us who funds the programme, who uses the funds and what it must allow people to pay for. We identify the rules, what you must be able to track and the points that need validation. A MAP expert answers you, with no commitment.