Rules engine with business-day deadlines and checklists (Spanish procedural law)
A module to build into your legal software: 70 validation rules on document data, 38 checklists by transaction type and business-day deadline calculation under Spain's Civil Procedure Act (LEC) and Judiciary Act (LOPJ).
People who build legal software write the same checks again and again: that the owner shown on the land registry extract (nota simple) is the seller, or that a deadline does not fall due in August. This legal rules engine takes the data extracted from the documents in a case, applies validation rules, generates the checklist for the transaction and calculates procedural due dates in business days.
Who it is for
Legal software companies and legaltech, law firm development teams and document management integrators.
Built for Spanish law: deadlines follow Spain's Civil Procedure Act (Ley de Enjuiciamiento Civil, LEC) and Judiciary Act (Ley Orgánica del Poder Judicial, LOPJ), and the texts of the rules, checklists and alerts are in Spanish.
What a legal rules engine solves
- Checks that keep repeating. The rules are already written.
- Inconsistencies spotted too late. Data is compared across documents.
- Miscounted deadlines. The calculation leaves out weekends, August, the Christmas period and national holidays.
What it does
- Applies 70 validation rules for real estate, corporate, employment, data protection, international transfers, digital compliance and AI compliance.
- Lets you set, for each rule, which documents and areas it applies to, when it runs (when a document is uploaded, in the daily review or manually) and which cases trigger it, for example when sensitive data is processed or the business operates outside the EU.
- Generates alerts with severity, finding type (missing, incomplete, contradictory or unverifiable), related documents and whether they need human review.
- Detects missing documents and compares names, tax IDs (NIF), amounts and dates.
- Offers 38 checklists by transaction type, such as a property sale, a lease, company formation, due diligence, dismissal, data breaches, high-risk AI or divorce.
- Marks checklist items as suggested when the extracted data supports it, and accepts your own checklists.
- Calculates business days under Article 130.2 LEC and Article 183 LOPJ, leaving out weekends, August, December 24 to January 6 and national holidays, with each year's Easter dates.
- Gives the due date of a deadline, the business days between two dates and the alert tier: 15 days, 7 days, 24 hours or overdue.
Benefits
- Your team does not have to write these rules from scratch.
- Your users see inconsistencies as soon as they upload the document.
- You offer deadline calculation based on the LEC and the LOPJ, with alerts before each due date.
Industry context
General industry data with its public source. These are not results of this product.
- August and the days from December 24 to January 6 are non-business days for all court proceedings, except those that procedural laws declare urgent. Source: Organic Law 6/1985 on the Judiciary (Ley Orgánica 6/1985, del Poder Judicial), Article 183, as worded by Organic Law 14/2022.
- The LEC adds Saturdays, Sundays and national, regional and local holidays as non-business days. Source: Law 1/2000 on Civil Procedure (Ley 1/2000, de Enjuiciamiento Civil), Article 130.2.
What you get with each license
Price upon request, depending on license type and scope. Integration support and maintenance are contracted separately.
- The module code, ready to add to your application.
- Integration examples and documentation.
- A warranty against defects for the agreed period.
- Everything above, with the right to extend it with your own rules and checklists and maintain it inside your product.
- The right to integrate the asset into a commercial product of your own, identified in the contract.
- The right to distribute it to your customers as part of that product, without requesting authorization for each installation and with no limit on end customers, unless otherwise agreed.
- It does not include reselling or sublicensing the asset on its own.
- It is not exclusive, unless otherwise agreed.
- Maintenance, support and adaptations are contracted separately.
Technical specifications
Language and runtime: TypeScript 5.9 (the version it ships with). It runs on Node.js or in the browser.
Frameworks: None. Its only dependency is Zod 4.6, which validates the input data of the deadline calculation.
Database: Not needed.
Operating systems: Any with Node.js or a current browser.
Interface languages: It has no interface of its own; the texts of the rules, checklists and alerts are in Spanish.
Required infrastructure:
- None. Your application provides the reading of the document data.
Private deployment: It runs on its own, with no connection to third-party services.
Main libraries:
| Library | Version | License |
|---|---|---|
| zod | 4.6.7 | MIT |
Dependencies with specific license terms: None.
Compatibility and integrations: JavaScript or TypeScript applications, on the server (Node.js) or in the browser.
Redistribution terms
The asset's own code can be integrated into the licensee's commercial products under the embeddable module license, the source code license and the OEM license, on the terms of the contract. None of the production dependencies has a copyleft license or specific commercial terms.
Installation requirements
A JavaScript or TypeScript application, on the server (Node.js) or in the browser. It needs no database or external services. You provide the document reading: OCR, AI or a form.
Frequently asked questions
Does it need AI?
No. The rules are fixed and only need data that has already been extracted, whether it comes from OCR, from AI or from a form.
Can I add my own rules?
Yes. Each rule is added on its own, without touching the others.
Does it include regional and local holidays?
No, and it does not include the exceptions for urgent proceedings either. They can be added with a table of holidays by jurisdiction.
Is maintenance included?
No. Maintenance and integration support are contracted separately. The rules reflect the law as of a given date, so their review should be part of maintenance or be done by your team.
They fit with this asset
Request
Request information on M-REG-01
Fill in the form with the asset reference and the license type you're considering. I reply in writing. If you need to review code, tick the NDA box and we'll sign one before anything is shared.