Payment institutions
The channel nobody included
“A new product or channel is added, and the reporting query still points only to the old ones.”
Systematic Reporting to SEPBLAC
In addition to suspicious transaction reporting, many obliged entities must send SEPBLAC mandatory periodic reports on certain transactions, whether or not there is any suspicion. These are two separate obligations, and they are breached in different ways.
Does systematic reporting apply to you? Free assessment
Tell us your business activity and volume, and we will tell you what you must submit and how often.
- 50+ entities advised
- Reply within 24 h
- No commitment
- Legal basis (Law 10/2010)
- Art. 20
- Minimum fine, very serious infringement
- €150,000
- Fine for a minor infringement
- Up to €60,000
- Implementing regulation
- Royal Decree 304/2014
Services
What we do for you in systematic reporting
Systematic reporting is a data problem before it is a legal one: you have to extract the data correctly, reconcile it and submit it on time.
Scope
Determining the scope of reporting
We analyze which of your transactions fall within systematic reporting, which fall outside it and where the gray areas are that are best resolved in writing before the first submission.
Learn more →
Art. 20Royal Decree 304/2014Scope
Data
Data extraction and reconciliation
We define the query that feeds the report and its reconciliation against the entity’s records, so that the figure submitted is reproducible and defensible if SEPBLAC asks where it comes from.
Learn more →
ExtractionReconciliationReproducible
Suspicion
The boundary with suspicious transaction reporting
Including a transaction in systematic reporting does not replace the duty to report it on suspicion.
Learn more →
Art. 18Boundary
OCI
Person responsible for submission
Who signs the report, who reviews it and how the prior validation is documented.
Learn more →
OCIValidation
Audit
Review of submitted reports
Checking that submissions from recent years are complete and consistent.
Learn more →
CompletenessHistory
Inspection
Preparing for a request for information
What is requested about systematic reports in an inspection, and how to arrive with everything reconciled.
Learn more →
SEPBLACRequest for information
Concept
What systematic reporting is
Reporting by objective criterion, not by suspicion. And at fixed intervals.
Systematic reporting, also known as the systematic report or monthly reporting, is the obligation to send SEPBLAC, at the set frequency, information on certain categories of transactions, whether or not there is any suspicion. It is based on Article 20 of Law 10/2010 and implemented by Royal Decree 304/2014.
The difference from suspicious transaction reporting under Article 18 is one of nature, not of degree. A suspicious transaction report stems from a judgment: someone has analyzed a transaction and concluded that there are grounds for suspicion. Systematic reporting stems from an objective criterion: the transaction has certain characteristics (amount, type, country) and is reported for that reason, with no assessment involved.
This has an important operational consequence: systematic reporting is a data extraction problem, not an analysis problem. It is almost always breached in the same way (a badly built query that leaves out a type of transaction, or a month that nobody submitted), not through a lack of legal judgment. It is also the easiest obligation to audit from outside: all it takes is to cross-check your records against what you submitted.
Scope
Which transactions must be reported
The categories are defined by objective criteria, and that is where errors creep in.
| Category | Objective criterion | Where it fails in practice |
|---|---|---|
| Transactions involving banknotes or metals | Movements of cash or precious metals above the regulatory thresholds | Structuring: several transactions by the same customer on nearby days that individually do not reach the threshold. |
| Transfers involving certain territories | Payments sent to or received from jurisdictions designated by the regulations or by SEPBLAC itself | The list of territories changes, and the query that feeds the report keeps the old version. |
| Activity of certain obliged entities | Specific activities that the rules subject to reporting because of their sector risk profile | It is assumed that “this does not apply to us” without this ever having been documented in writing. |
| Negative declaration | No reportable transactions in the period | It is not submitted. And the absence of a submission is read as non-compliance, not as an absence of transactions. |
Indicative table. The specific categories, thresholds and frequency that apply to each obliged entity must be checked against Royal Decree 304/2014 as currently in force and against SEPBLAC’s technical communications, which are the operational reference for the format and content of each submission.
The negative declaration is also an obligation
If there were no reportable transactions in the period, in many cases you must still submit a report saying so. Silence does not mean “there was nothing”: it means “did not submit”, and that is how it appears in the supervisor’s records.
Reporting does not exempt you from suspicious transaction reporting
A transaction may fall within systematic reporting and also raise suspicion. In that case, you must do both. Treating Article 18 as complied with because the transaction “was already in the monthly report” is one of the costliest mistakes made.
Comparison
Systematic vs. suspicious transaction reporting: what sets them apart
Two duties that share a recipient and little else.
| Element | Systematic (Art. 20) | On suspicion (Art. 18) |
|---|---|---|
| What triggers it | An objective criterion: amount, type, territory | A judgment: reasonable suspicion |
| Frequency | Fixed, as set for each obliged entity | Immediate, as soon as the indication arises |
| Prior assessment | No suspicion analysis required | Requires analysis and a documented conclusion |
| Typical volume | High and stable | Low and variable |
| Triggers the duty to refrain | Not by itself | Yes, Art. 19 |
| Prohibition of disclosure | Yes | Yes |
| How it is breached | Not submitting, submitting late or submitting incomplete data | Failing to detect, analyze or report |
| How it is audited | Cross-checking internal records against what was submitted | Reviewing alerts closed without a report |
These are cumulative obligations, not alternatives. A transaction can and must go through both routes when both situations apply.
Sectors
How systematic reporting breaks down in each sector
The failure is almost always in the query that extracts the data, not in the decision to report.
Currency exchange
Structuring
“Three transactions by the same customer in four days that separately fall below the threshold and together exceed it comfortably.”
Jewelers and high-value goods
Residual cash
“It is assumed that cash is no longer accepted, and a channel remains open that nobody has reviewed for years.”
Tax and administrative advisors
The negative declaration
“There were no reportable transactions and nobody submitted anything. In the supervisor’s records, this appears as an omission.”
Consequences
What happens if you don’t report, or report wrongly
Systematic reporting is objective, and so is non-compliance: it can be proven with a query.
It is the easiest breach to detect from outside. The supervisor does not need to examine your judgment: it only has to cross-check your own records against what you submitted.
It builds up over time. A badly built query does not fail for one month: it fails every month since it was built, and when it is discovered you have to remediate retroactively.
And it coexists with the duty to report on suspicion. Having included a transaction in systematic reporting does not satisfy the Article 18 obligation if there was also suspicion.
| Severity | Amount | Basis or alternative |
|---|---|---|
| Minor infringements | up to €60,000 | Less significant breaches, or breaches with no appreciable impact on the prevention system. |
| Serious infringements | €60,000 – €5,000,000 | Or 10% of the company’s total resources. |
| Very serious infringements | €150,000 – €10,000,000 | Or 10% of the entity’s own funds. |
Does what you submit match what is in your systems?
We rebuild the query that feeds your report, cross-check it against your records for recent years and tell you whether anything needs to be remediated before the supervisor sees it.
Frequently asked questions
Systematic reporting: common questions
What is systematic reporting to SEPBLAC?
It is the obligation to send SEPBLAC, at regular intervals, information on certain categories of transactions that meet objective criteria (amount, type, territory), whether or not there is any suspicion. It is provided for in Article 20 of Law 10/2010 and developed in implementing regulations.
Is it the same as reporting a suspicious transaction?
No. Suspicious transaction reporting stems from a judgment of suspicion and is immediate. Systematic reporting stems from an objective criterion and is periodic. They are cumulative obligations: if a transaction meets both conditions, you must do both.
Which obliged entities does it apply to?
It depends on the activity and the type of transactions. Not all obliged entities are subject to the same systematic reporting obligations. What matters is that the conclusion that “it does not apply to me” is documented in writing and reasoned, not an inherited assumption.
Do you have to submit anything if there were no transactions?
In many cases, yes: the negative declaration. The absence of a submission is not interpreted as an absence of reportable transactions, but as non-compliance. You should check the specific regime that applies to your type of obliged entity.
Who should sign or validate the report?
Whoever your procedure specifies, usually the SEPBLAC representative, with prior validation by the internal control body (OCI). What matters is that there is a record of who reviewed the content before submission, because that is the first question asked when an inconsistency appears.
What if I find that I have been reporting incorrectly for months?
You correct it and document it. A supplementary submission with an explanatory note on the cause of the error and the corrective measure taken is very different, for the purpose of grading any penalty, from an error that the supervisor discovers and that the entity had not detected.
Does structuring have to be reported?
That is precisely the trap. Thresholds refer to transactions, but monitoring for structuring is an obligation in its own right: several linked transactions that individually fall below the threshold but together exceed it must be detected by your monitoring system. And if they also raise suspicion, they must be reported on suspicion.
How do you prove that the report is correct?
With the documented query that generates it, the reconciliation against the entity’s records and the acknowledgment of receipt. Together, these three elements make it possible to reconstruct the figure submitted. Without the documented query, the report cannot be reproduced and cannot be defended.
Does it change with the AMLR in 2027?
The EU package strengthens the harmonization of reporting to financial intelligence units and the coordinating role of the new EU authority. Greater standardization of formats and categories across Member States is to be expected. Avoid building your data extraction so rigidly that rewriting it in 2027 becomes unworkable.
And with ANIFI?
The draft bill (anteproyecto) provides for ANIFI to take over SEPBLAC’s functions as financial intelligence unit. This would affect the recipient of submissions and, probably, the technical channels. It is a change of counterpart, not of obligation: what is reported today will still be reported.
Operational guide
Practical guide to systematic reporting
Systematic reporting is done well when it is boring: a stable query, a monthly reconciliation and an archived acknowledgment. Ten steps to get there.
First, what applies to you
Document in writing which reporting categories apply to you and which do not, with the reasoning. A negative conclusion must also be justified.
Then, how it is extracted
The query that feeds the report is the critical control. It must be documented, versioned and reviewed every time a new product or channel is launched.
And always, the reconciliation
Before submitting, cross-check the result against the entity’s records. It is the only thing that detects a query that has become outdated.
Systematic reporting checklist in 10 steps
- Determine and document which systematic reporting obligations apply to your type of obliged entity.
- Identify the transaction categories concerned and the thresholds and criteria that apply to each.
- Build the extraction query and document it: tables, filters, period and owner.
- Version the query and require it to be reviewed for every new product, channel or territory.
- Define the procedure for reconciling against internal records before each submission.
- Set the submission calendar and assign an owner and a backup for each submission.
- Establish the prior validation workflow and keep a record of who reviews the content.
- Systematically archive acknowledgments of receipt together with the query and reconciliation for each period.
- Check that reported transactions that also raise suspicion are reported on suspicion separately.
- Review the full submission history every year to detect periods with no report or an incomplete report.
If you would like us to review your submission history, start with an AML/CFT audit or an external expert report.
Systematic reporting in operation
From a database query to an archived acknowledgment
Systematic reporting is the most mechanical control in the AML system and, for that very reason, the one that can keep failing the longest without anyone noticing.
1) ScopeWhat is in and what is out
Decided in writing and with reasoning, not by habit. This includes the conclusion that a category does not apply to you.
- Applicable categories
- Current thresholds
- Documented conclusion
2) ExtractionThe query that generates it
It is the critical control. If the query does not cover a channel, that channel has gone unreported for years and nobody knows.
- Versioned query
- Review when things change
- Assigned owner
3) ReconciliationCross-check before submitting
Cross-check the result against the entity’s records. It is the only point at which an incomplete extraction can be detected before it becomes a breach.
- Documented reconciliation
- Differences explained
- Prior validation
4) ArchivingThe acknowledgment and its context
Keeping the acknowledgment is not enough. You need to keep it together with the query that generated that report and the corresponding reconciliation, so that the figure can be reconstructed years later.
Tip: for each period, archive one folder with three items: query, reconciliation and acknowledgment. That is what you will be asked for, and almost nobody keeps them together.
Quick decisionPractical map: what do I do with this transaction?
Three situations and the route that applies to each.
Meets the objective criterion
Included in systematic reporting for the period. No suspicion analysis.
Meets the criterion and raises suspicion
Both routes: systematic reporting and suspicious transaction reporting.
Only raises suspicion
Immediate suspicious transaction report, and refrain from executing the transaction where appropriate.
Reporting playbook
Systematic reporting in practice
Scope determination
A document setting out, with reasons, which categories apply and which do not.
Scope note approved by the OCI, dated.
Extraction query
Documented, versioned query, reviewed when products or channels change.
Technical documentation of the query and version log.
Prior reconciliation
Cross-checking the result against internal records before submitting.
Reconciliation sheet for each period, with differences explained.
Timely submission
Submission within the set calendar, including the negative declaration.
Acknowledgment of receipt archived for each period.
Independence from Art. 18
Reported transactions that raise suspicion are also reported on suspicion.
Cross-traceability between both records.
Signs that your systematic reporting has a problem
Any one of these justifies a review of the full history.
- Nobody can explain exactly how the submitted figure is generated.
- The extraction query has not been touched since the latest products were launched.
- There are periods in the history with no archived acknowledgment of receipt.
- No negative declaration is submitted when there are no reportable transactions.
- A category is assumed not to apply without a written note setting out the reasons.
Working glossary
Key concepts in systematic reporting
Terms that appear in procedures, SEPBLAC technical communications and requests for information.
Art. 20Basis
Systematic reporting
The obligation to report, at regular intervals, categories of transactions defined by objective criteria.
Law 10/2010, Article 20.
Art. 18Different
Suspicious transaction reporting
The obligation to report immediately when there is suspicion. Cumulative with systematic reporting.
NegativeTrap
Negative declaration
A submission stating that there were no reportable transactions in the period.
Not submitting is not the same as having nothing to report.
ThresholdCriterion
Reference amount
The figure above which a transaction falls into the reportable category.
Always check the version in force.
StructuringRisk
Artificial splitting
Several linked transactions below the threshold that together exceed it.
A monitoring obligation in its own right.
ReconciliationControl
Prior cross-check
Checking the extraction result against the entity’s records before submitting.
It is what detects an outdated query.
AcknowledgmentEvidence
Proof of submission
Proof that the report was sent, and when. It must be archived together with the query and the reconciliation.
Archived by period, not loose.
SEPBLACRecipient
Financial intelligence unit
The body that receives reports, both systematic and suspicious transaction reports.
See: SEPBLAC inspection.
ANIFIFuture
National Financial Integrity Authority
The draft bill (anteproyecto) provides for it to take over SEPBLAC’s functions as Spain’s FIU.
See: ANIFI.
COMPLIANCE CONTROL CENTER · REPORTING
Decision matrix: which route does this transaction take?
Cross-check whether the transaction meets the objective criterion against whether it also raises suspicion. The two routes are independent and can overlap.
Reporting route matrix
Green: one route only. Red: both, plus refraining.
Suspicion \ Criterion
Not met
Criterion met
Met and structured
No suspicion
Nothingrecord only
Systematicin the period
Analyzepossible indication
Mild suspicion
Analyzedocument
Systematic+ analysis
Both+ analysis
Clear indication
Art. 18+ refrain
Both+ refrain
Both+ refrain
Obliged entities
Who does systematic reporting apply to?
It depends on the activity and the transactions. What does not depend on anything is the obligation to document the conclusion.
General
Obliged entities under Law 10/2010
We determine which periodic reporting obligations apply to your activity and set out the reasoned conclusion in writing.
See obliged entities →
Law 10/2010Art. 20
Fintech
Payment institutions and fintechs
Each new channel or product requires the extraction query to be reviewed. This is where something is most often left out.
See our fintech approach →
ChannelsExtraction
High value
Jewelers and precious metals
Cash and precious metals transactions: a classic reporting category and a common focus of requests for information.
See AML for jewelers →
CashMetals
Advisors
Tax and administrative advisors
The most common mistake here is the negative declaration that is never submitted because nobody knows it exists.
See AML for advisors →
NegativeCalendar
Common mistakes
The six failures we see most often in systematic reporting
They are process errors, not errors of legal judgment, and that is why they go undetected for years.
The query that is never updated
It is built correctly on day one and never reviewed again. Every product or channel launched afterwards is left out of the report without anyone noticing.
Not submitting the negative declaration
The assumption is that if there are no transactions, there is nothing to send. In the supervisor’s records, this appears as a period with no submission.
Treating Article 18 as complied with
“That transaction was already in the monthly report” does not satisfy the duty to report on suspicion. These are cumulative obligations.
Archiving the acknowledgment without context
The acknowledgment only proves that something was sent. Without the query and reconciliation for the same period, the figure submitted cannot be reconstructed.
Assuming a category does not apply
The conclusion may be perfectly correct, but if it is not written down and reasoned, in an inspection it is as if you had never considered the question.
Ignoring structuring
The threshold is checked transaction by transaction and nobody monitors the whole. It is the most obvious way to evade the threshold and the easiest to detect from outside.
Official sources
Where all of the above comes from
Direct links to the consolidated texts and to the competent bodies. SEPBLAC also publishes technical communications on the format and content of submissions, which are the operational reference.
BOE
Law 10/2010 of April 28
Consolidated text. Article 18 (suspicious transaction reporting) and Article 20 (systematic reporting).
BOERoyal Decree 304/2014 of May 5
Implementing regulation: categories, thresholds and frequency of systematic reporting.
SEPBLACExecutive Service of the Commission for the Prevention of Money Laundering
Technical communications, submission formats and filing channel.
TreasuryCommission for the Prevention of Money Laundering
Institutional information and penalty regime.
EUR-LexRegulation (EU) 2024/1624 (AMLR)
EU harmonization of reporting to financial intelligence units from July 2027.
FATFFATF Recommendations
International standard on transaction reporting and thresholds.
Initial publication, with the operational distinction between systematic reporting and suspicious transaction reporting.
Planned review: application of the AMLR and harmonization of reporting formats.
Contact
Book a call
Tell us what you currently report to SEPBLAC and how often, and we will tell you if anything is missing.
Legal framework for systematic reporting in Spain
Systematic reporting to SEPBLAC is based on Article 20 of Law 10/2010 of April 28 on the prevention of money laundering and terrorist financing, and on the implementing provisions of Royal Decree 304/2014. It requires certain obliged entities to send, at regular intervals, information on categories of transactions defined by objective criteria, whether or not there is any suspicion of money laundering.
An obligation of process, not of judgment
Unlike suspicious transaction reporting, which requires a value judgment on each transaction, systematic reporting is essentially a matter of extracting and processing data. This has two practical consequences. First, it is breached silently: a query that does not cover a channel can fail for years without anyone noticing. Second, it is particularly easy to audit from outside, because all it takes is to cross-check the entity’s internal records against what was actually submitted.
The negative declaration
One of the most widespread mistakes is submitting nothing when there were no reportable transactions in the period. Under the regime that applies to many obliged entities, having no transactions does not exempt you from submitting: a negative declaration is required. The records the supervisor keeps do not distinguish between “there were no transactions” and “did not submit” unless there is an express record of the former.
Independence from the duty to report on suspicion
Both obligations are cumulative. A transaction may meet the objective criterion that brings it into the periodic report and also raise suspicion. In that case, a suspicious transaction report under Article 18 is also required, along with the related duty to refrain where applicable. Taking the view that inclusion in the monthly report satisfies Article 18 is a conceptual error with significant consequences in terms of penalties.
What changes with the AMLR and ANIFI
The EU anti-money laundering package strengthens the harmonization of reporting formats and categories for financial intelligence units and gives the new EU authority coordination and technical development functions. At national level, the draft bill (anteproyecto) creating the National Financial Integrity Authority (ANIFI) provides for it to take over SEPBLAC’s functions as financial intelligence unit. This will affect the recipient of submissions and the technical channels, but not the nature of the obligation. You should therefore design your data extraction to be flexible enough to absorb a change of format without rebuilding it entirely. More details on our ANIFI page.
Related obligations
AML/CFT system
Official sources
Key legislation, linked to the official text:
- Law 10/2010 of April 28 on the prevention of money laundering and terrorist financingBOE · consolidated text
- Royal Decree 304/2014 of May 5 approving the Regulations implementing Law 10/2010 of April 28 on the prevention of money laundering and terrorist financingBOE · consolidated text
- Regulation (EU) 2024/1624 of May 31, 2024 on the prevention of the use of the financial system for the purposes of money laundering or terrorist financingEUR-Lex · Official Journal of the EU
Legislation and links reviewed in .