Filing with a CENTIF

In short

In the eight UEMOA states and in Guinea, reports go to the national CENTIF (Cellule nationale de traitement des informations financières), the country’s financial intelligence unit. None of them is known to use goAML. For a workspace whose jurisdiction is one of these countries, SpeculaPro exports a report as a CENTIF declaration:

• a déclaration de soupçon (DOS) for a suspicious transaction report;
• a déclaration de transaction en espèces (DTE; Côte d’Ivoire calls it DSTE) for a cash transaction report.

The export is one ZIP file holding the declaration as a French form to print, sign and file, the same declaration as XML, and the schema of that XML.

The layout is SpeculaPro’s own. No CENTIF has confirmed it

The form’s sections follow the content of the model declaration form in the UEMOA uniform AML/CFT law, which Guinea’s law mirrors. But the page layout and the XML schema (SpeculaPro CENTIF declaration 1.0) are SpeculaPro’s own. They are not official CENTIF stationery, no CENTIF publishes a machine format they could be checked against, and no CENTIF has confirmed that it accepts them. Each CENTIF takes filings its own way: Senegal through its e-Delta platform, Côte d’Ivoire through Mon Espace CENTIF with its own Word and Excel forms, and the others by channels still to be established.

Before your first filing, confirm with your CENTIF how it takes declarations and whether it accepts this form. If it requires its own portal or template, use the printed declaration as your record and copy from it. This page is not legal advice: confirm your filing duties with counsel and your CENTIF.

A report is filed in five steps:

1. List the attachments on the draft, before it is sent for approval.
2. Export the approved report. This writes the ZIP once and keeps it, byte for byte.
3. Download it, print the form (or save it as PDF), and have it signed and stamped.
4. File it the way your CENTIF takes filings, and record the submission in SpeculaPro.
5. When the CENTIF answers, record the outcome.

SpeculaPro never sends anything to a CENTIF itself. Steps 3 and 4 are done by a person.

Step	Needs	Default role
List attachments on a draft	reports.draft and entities.view_pii	Senior analyst, L2 investigator, MLRO
Export and download	reports.approve or reports.submit, and entities.view_pii	MLRO
Record the submission and the outcome	reports.submit and entities.view_pii	MLRO

Drafting and approval work as for any report: see Drafting an STR, Cash transaction reports and Approving a report.

Before your first declaration

The declaration is addressed to your CENTIF and names your institution and the compliance officer who signs it. Those come from two places:

On the form	Comes from
The CENTIF’s name, city and country, and the law the declaration is made under (Déclaration faite en application de…)	Your jurisdiction. Only the city is given as the address today, and the law’s exact reference is to confirm: write the full postal address on the printed form if your CENTIF expects it
I. Déclarant: your institution’s name, identifier or institution code, BIC, branch and address	Reporting settings: institution name, reporting entity id, institution code, SWIFT / BIC, branch, and the location
II. Correspondant de la CENTIF: the compliance officer’s name, job title, phone and email	Reporting settings: the reporting person
The declaration’s code (DOS, DTE, or DSTE)	Reporting settings: the report codes, which start from your jurisdiction’s
The French names of identity documents (CNI, passeport, RCCM…)	Your jurisdiction’s identifier types

Fill in the reporting settings before the first report: see Before you go live.

How to list the attachments

A declaration ends with the list of documents you send with it (pièces jointes): an account statement, a copy of an identity document, a contract. This list holds titles only, and it is what the form prints.

The documents themselves can be kept on the case as evidence files and chosen on the draft to go with the declaration: see Choosing the evidence files. The two are separate. Choosing a file doesn’t add its title to this list, and typing a title doesn’t attach a file, so do both for a document you send.

1. Open the draft report.
2. In the Attachments panel, under Documents sent with the report, one per line, type one title per line, for example Account statement from 1 to 14 September 2026.
3. Select Save draft.

Limits: at most 50 titles, each up to 200 characters. Empty lines are dropped.

The list is frozen with the rest of the report

You can change the list only while the report is a draft. Once it is sent for approval, the attachments are part of what the approver approves, and they can’t change afterwards, like the narrative and the transactions. To change them, the approver sends the report back.

A DOS with no attachments listed gets a validation warning, not an error: no attachments are listed: name the supporting documents sent with the declaration (pièces jointes), or confirm there are none. The form then prints Aucune pièce jointe.

What validation checks

The Validation panel on the report page lists the problems below, and the same checks run again at approval and at export. An error blocks approval and export; a warning doesn’t. The rules are SpeculaPro’s own, read from what the model form requires: no CENTIF publishes rejection rules.

Every CENTIF declaration carries this warning, so nobody forgets the layout is unconfirmed: The declaration follows the content of the model declaration form, but its layout and its XML schema (version 1.0) are SpeculaPro’s own: confirm with the CENTIF how it takes filings (portal, forms or files) before the first one.

What is missing or wrong	DOS	DTE
The report code, the declaration number or date, or a valid base currency	Error	Error
Your jurisdiction names no CENTIF	Error	Error
The CENTIF has no address in the jurisdiction	Warning: write it on the printed form	Warning
Your institution’s name; the city the declaration is made from	Error	Error
No reporting entity id and no institution code; no street address	Warning	Warning
No compliance officer, or one with neither phone nor email	Error	Error
The compliance officer’s job title	Warning	Warning
The declaration names no person at all	Error	Error
Your customer has no name on file	Error	Error
Your customer has no identity document on file (a person), or no RCCM number or tax identifier (a business)	Warning	Error
Your customer’s date of birth or nationality	Warning	Warning
An operation without your reference, a date, an amount above zero, or either party’s name	Error	Error
An operation that isn’t cash under your workspace’s cash rules	Not checked	Warning
No operations	Allowed: the declaration then names the persons concerned	Error
The grounds for suspicion (motifs du soupçon): the narrative	Error	Not required
No attachments listed	Warning	Not checked

Why a missing identity document blocks a DTE but not a DOS

A cash transaction is made at a counter, where the customer is identified, so a cash declaration can’t go without the document. A suspicion can be about someone who withheld it, so a DOS only warns. The identity document is the customer’s national identifier: send it with the customer record.

How to export and download

1. Select Reports, then the To file tab, and open the approved report.
2. Select Export CENTIF declaration. SpeculaPro checks the report once more and writes the archive. It refuses while the report has validation errors.
3. The Exported file panel appears, with the file name (such as DOS-2026-000003-centif.zip), its size, who exported it and when, and its SHA-256 fingerprint. Under it: The archive holds the declaration to print, sign and file (HTML), the same declaration as XML, and the schema of the XML. Its layout is SpeculaPro’s own: confirm with the CENTIF that it accepts it.
4. Select Download the file and save it somewhere only authorised people can read: it holds your customer’s identity in full.

The archive is made once. Exporting again returns the same file, and every later download gives you exactly the same bytes, checked against the fingerprint recorded at export. Each export and download is written to the audit log with the fingerprint.

When evidence files go with the declaration, Filing package downloads one ZIP with this archive, the files and a list of their fingerprints (DOS-2026-000003-centif-package.zip). See The filing package.

What’s in the archive

File	What it is
DOS-2026-000003-declaration.html	The declaration, laid out for A4, in French. One self-contained page with no scripts and nothing loaded from outside. This is what you print, sign and file
DOS-2026-000003-declaration.xml	The same declaration as structured data (schema version 1.0), for the day a CENTIF takes files. Both files are made from the same content, so they can’t disagree
centif-declaration-1.0.xsd	The schema of the XML, with a description of every element

The form is marked CONFIDENTIEL and has these sections:

Section	Holds
Heading	Your institution, the CENTIF it is addressed to, the title (Déclaration de soupçon or Déclaration de transaction en espèces) with its code, your reference (the report number), the date and the legal basis
I. Déclarant	Your institution
II. Correspondant de la CENTIF	The compliance officer who signs
III. Personne(s) concernée(s)	Each person or business in the report, marked as your customer or as another party, with identity document, date of birth, nationality and contact details where you hold them
IV. Compte(s) concerné(s)	The accounts and wallets involved, with their holders
V. Opération(s)	Each transaction: your reference, date, kind, channel, whether it is cash, the amount in your base currency (and in the original currency, with the rate, when different), who paid and who was paid
VI. Motifs du soupçon (on a DTE: Observations du déclarant)	The indicators, the narrative, and the action taken (Mesures prises par le déclarant)
VII. Pièces jointes	The numbered list of attachments
Signature	Fait à (your city), the date, the compliance officer’s name and title, and a box for Signature et cachet du déclarant

It ends with a confidentiality notice, and a line saying the document was produced with SpeculaPro and is not an official CENTIF form. Anything SpeculaPro doesn’t hold is left empty; a missing name prints as INCONNU.

How to print, sign and file

1. Unzip the archive and open the .html file in a browser.
2. Print it on A4, or choose Save as PDF in the print dialog.
3. Have the compliance officer sign it and add your institution’s stamp in the box at the end.
4. File it the way your CENTIF takes filings, with the attachments you listed. If the CENTIF takes declarations only through its own portal or forms, enter the declaration there from the printed form.
5. Note the reference the CENTIF gives you and the date and time you filed.

Tipping off

A declaration is strictly confidential. Don’t tell the customer or anyone outside the people who must know that a declaration exists or what it says. Keep the printed form and the downloaded archive where only authorised people can reach them.

How to record the submission

1. Open the report. It must be Approved · to file and exported.
2. Select Record submission. The panel is titled after your CENTIF, for example Record the submission to CENTIF-CI (CENTIF declaration): File the declaration with the CENTIF-CI first: print the form from the downloaded archive (or save it as PDF), have it signed and stamped, and send it the way the CENTIF-CI takes filings. Then record the reference it gave you.
3. Enter the CENTIF’s reference (up to 100 characters), and check Submitted at. It starts at the current time and can’t be in the future.
4. Select Record submission.

The report becomes Submitted. The reference and time can’t be changed afterwards. SpeculaPro refuses to record a submission for a report that was never exported: export the file before recording the submission.

How to record the CENTIF’s answer

1. Open the submitted report and select the button named after your CENTIF, for example Record the CENTIF-CI outcome. The panel and its labels name it too: What the CENTIF-CI said, Reason given by the CENTIF-CI.
2. Choose Acknowledged (Accepted by the CENTIF-CI) or Rejected. For a rejection, enter the reason the CENTIF gave (required, at least 3 characters).
3. Select Record outcome.

Either answer is final. The rest of the report names your CENTIF as well: the status reads Rejected by the CENTIF-CI, the reference field CENTIF-CI reference number, and the approval trail Filed with the CENTIF-CI. goAML isn’t mentioned on a CENTIF declaration. See What the app calls your FIU. For a rejected DOS, draft a new one from the case; for a DTE, file the correction as the CENTIF instructs and record what you did. See If the FIC rejects a report: the same applies here.

Limits

• Unconfirmed layout and schema, as above, for every CENTIF.
• The form is in French only, whatever language you use SpeculaPro in. The names of transaction kinds, channels and account statuses are SpeculaPro’s own vocabulary translated into French, not a CENTIF’s code list.
• The form lists attachment titles only. The documents can be kept as evidence files and downloaded with the declaration in the filing package, but SpeculaPro doesn’t send them, and the list of titles isn’t filled from them.
• The CENTIF’s address is the city only, and the legal basis is a general wording, until each is confirmed.
• A report keeps the format it was drafted in. After a change of report format, older reports still export in the old one.
• No direct connection to e-Delta, Mon Espace CENTIF or any CENTIF system.

Related

• Reporting settings
• Before you go live
• Approving a report
• Filing with goAML
• Jurisdictions
• Reports API