Powers of attorney
eIDAS · RFC 3161
Evidence with a name on it.
Bastanteo is the formal check of what a power of attorney actually authorises. Bastanteo Lab takes the scanned deed and returns, structured, who may do what, within which limits and under which signature regime. Every field comes with its literal quote and its exact position in the document, so whoever reviews it does not have to take it on trust: they can see it.
Field Critical
Signature regime
Joint — any two attorneys-in-fact
Literal quote
«…será necesaria la firma conjunta de dos cualesquiera de los apoderados…»
p. 14 · offset 22,481
Stability 3 / 3 readings
Can be accepted without re-reading it. Fields that come out in two readings, or in one, are flagged for review.
Sealed to RFC 3161 · qualified eIDAS provider
226
Fields in the taxonomy
31 declared critical
92%
Agreement across the three readings
Measured on real deeds
3 min
Even the longest deed
While your client waits
3
Independent readings per deed
That do not influence one another
How it works
From scanned deed to signed bastanteo
What has to be cross-checked for a bastanteo to hold up? What the deed grants, under which signature regime, and whether the power is still in force at the Commercial Registry. Our guide explaining it is published in Spanish only.
01
The deed comes in
Through the inbox, by API or by webhook. Scanned, unprepared and with no prior formatting.
02
It is read three times
Three independent readings that do not influence one another. Each field comes out marked with how many of them returned the same value.
03
The cited evidence comes out
226 possible fields, each with the exact text it came from and its position. Whoever reviews it jumps to the point in the document; they do not hunt for it.
04
You sign, and it is sealed
The report is sealed by a qualified eIDAS provider and can be verified years later, offline, with the file itself.
Your review
What reaches you reaches you checked.
It is the feature that took the most work and the one you notice most. Every deed is read three times independently, and the system can tell what it has understood from what it has assumed.
That distinction is what lets us give you a concrete guarantee instead of a promise: you receive the bastanteo ready, not a list of fields somebody has to audit in full.
The vast majority of deeds come out clean first time.
And we do not leave it there. The part that does not come out clean first time is not simply handed over: it goes through our own review before it reaches you, to make sure nothing slips past.
Backed by extensive testing on real client deeds, not on examples prepared in advance. Every version of the engine is measured against that material before it goes into production.
92%
of fields agree across the three independent readings. That agreement is what marks a field as stable, and it is why what comes out clean really is clean: the mark was measured before we relied on it.
A signal measured, not declared
Stability across independent readings is what predicts the outcome, and it is what we use. We checked it against real deeds before leaning on it, which is why we can answer for what comes out.
Registry cross-check · BORME
The deed says what was granted. The BORME says whether it is still in force.
It is the gap no document closes on its own. A power granted four years ago may have been revoked last year, or the director who conferred it may have stepped down — and the deed in front of you still says exactly what it said on day one. The BORME, the Spanish official companies gazette, is the public record we check it against.
Which is why the cross-check is not an extra: it is what turns a reading of the document into a bastanteo that holds up.
01
What is cross-checked
The company's tax ID and the date of the deed against the data published in the Boletín Oficial del Registro Mercantil.
02
Why the date is critical
It is the field that determines whether the power is still in force, which is why it is declared critical: without it the cross-check means nothing. It is normalised before comparison.
03
What reaches you
The result of the cross-check with its source and its date, alongside the rest of the evidence. And if something could not be cross-checked, it is stated — we do not presume it is still in force.
The BORME publishes the names of company directors, so querying it brings third-party personal data into the file. That processing is covered in the data processing agreement and in the privacy policy (in Spanish), and it is carried out on behalf of the client, who is the data controller.
What is inside
Eight parts, and none of them decorative
01
A 226-field taxonomy
Structured group · field · subfield, with criticality declared. 31 are critical: identity, protocol number, date and signature regime.
02
Three independent readings
Every deed is read three times without the readings influencing one another, and each field comes out with its agreement mark.
03
Literal quote with position
Every value carries the exact text it came from and its offset in the transcription. You jump to the point; you do not search for it.
04
Confidence weighted by criticality
A doubtful tax ID is not diluted among dozens of correct powers. The index weights by what matters and applies minimums for each critical field.
05
Qualified timestamp
RFC 3161 with a qualified eIDAS provider. Legal presumption across the EU and verifiable offline.
06
Gaps stated explicitly
Whatever could not be verified is stated, where somebody is going to read it. It never stays in an internal field.
07
Structural coherence kept apart
A metric separate from the confidence index. They are two different questions and they get two numbers.
08
Inbox, API and webhook
Multi-tenant, with human review built in and integration for those who already have their own workflow. Data hosted in the European Union.
Traceability
A report that still holds up years later.
Two separate pieces that often get confused: the quote, which lets you check each field in the document itself, and the seal, which attests to the whole at a certain date.
The literal quote
Every value carries the exact text it was extracted from and where it sits. You do not have to believe the result: you check it in the document itself, and that check is within reach of anyone who opens the report.
The qualified seal
The report is sealed by a qualified provider under eIDAS, to the RFC 3161 standard. And if the provider does not respond, the report is issued anyway and the reason it carries no seal is recorded: an added guarantee cannot be allowed to become a single point of failure.
Why a qualified seal and not blockchain
A qualified seal has legal presumption across the European Union and is verified offline, with the file itself: it does not depend on a network continuing to exist, nor on anyone paying to keep it running. An entry on a blockchain has no such presumption, and checking it depends on a third party that can disappear.
The limits
Where the machine ends and you begin
These boundaries are design decisions, not pending features. They are here and not in the small print because they are the reason everything else can be stated with figures.
The bastanteo judgement is signed by you
No signal from the engine travels as a validity boolean. A bastanteo is a legal judgement and responsibility for it belongs to a person who can answer for it; a system that said «valid» would be moving that responsibility somewhere it cannot sit.
The flagged fields are still your work
The stability mark tells you which they are and saves you reviewing the rest. Not reviewing them.
An incomplete document is not delivered
If a stretch of the deed cannot be read, the whole document fails rather than being handed over half done. A bastanteo with a stretch missing is not incomplete: it is one that lies by omission.
We measure consistency, and we say so
Every figure on this page comes from measurements on real deeds, with the date recorded. None of them is an estimate presented as a fact, and that is the same discipline the rest is built with.
Pricing
Two models, and neither one leaves you without service
The volume of bastanteos at a professional services firm looks nothing like a notary's or a bank's, so the price is agreed with you. What does not change is how it is billed.
Model 1
Flat monthly fee
One fee a month and access with no volume cap. For those with a steady flow who would rather have a cost that does not move from one month to the next.
On request
Model 2
Per bastanteo
A price per deed processed, accrued through the month and invoiced in arrears. For those with irregular volume who do not want to pay for quiet months.
On request
No quota and no cut-off
In both models the counter is there to invoice and never to deny. There is no bundle to run out of and no service cut halfway through the month.
An error is not charged for
What is invoiced is the bastanteo analysed and returned with a result. A deed that could not be processed does not go on the invoice.
No set-up cost
And the maintenance fee is optional in both models, not a compulsory addition to the rate.
Why we do it this way
That it never says «valid» is not a shortcoming. It is the decision.
Just as a power that could not be cross-checked is not presumed to be in force: it is stated. Those two decisions are the same one, and they run through all three products. We build systems that know when they do not know, and say so.
The JRV Lab paradigm →Getting started
Your trial starts with a deed of your own
Not with a prepared example. You send us a real power of attorney, we return it structured with every field quoted and located, and you check it yourself against the document. That is where you see whether it is useful to you.