# 6. Regulatory Reports
Regulatory Reports holds the reports the institution files with the AMLC. It has two tabs, switched at the top right of the page. **STR** is the register of Suspicious Transaction Reports (STRs) filed on the platform, one row per STR: find a filed STR, download its CSV, and open it to read what was reported in each of its six steps. STRs are filed from a case in [Case Manager](#case-manager), not from this page. **CTR** lists the Covered Transaction Reports (CTRs) that the platform creates by itself once a day from ingested transactions, each with a CSV file in the GoTRACS format (see [The CTR register](#s-6-11)).
For
Analysts, supervisors and team leads
In the menu
Fyscal ARCX → Regulatory Reports
Reading time
About 19 min
::: checks
- [The STR register](#s-6-1): read the list of filed STRs and its columns.
- [Search and filter the register](#s-6-2): find an STR by case or STR ID, filter by date or creator, and download its CSV.
- [Open a filed STR](#s-6-3): open an STR read-only and move between its steps.
- [Step 1: Select Alerts](#s-6-4): see which of the case's alerts the STR covers.
- [Step 2: Report Type](#s-6-5): check the STR type, filing details and filing deadline.
- [Step 3: Reason for suspicion](#s-6-6): see the reason codes the STR cites.
- [Step 4: Transaction](#s-6-7): see the transactions included and their total amount.
- [Step 5: Subject parties](#s-6-8): check the parties named in the STR and their details.
- [Step 6: Narratives](#s-6-9): read the STR narrative and the alerts it covers.
- [Where STRs come from](#s-6-10): find out where STRs are filed and where else they appear.
- [The CTR register](#s-6-11): read the list of CTRs and its columns.
- [How CTRs are generated](#s-6-12): see when CTRs are created, the ₱500,000 threshold and the filing deadline.
- [Find and download a CTR](#s-6-13): find a CTR, download its CSV and file it with the AMLC.
:::
CaseFile STR, or Preview STR for a draft
STR wizardSix steps, Select Alerts to Narratives
STR Created caseDownload STR on the case
Regulatory ReportsSTR tab: download CSV; open read-only
Customer 360STR History tab of the customer
Diagram 6.1 — Where an STR is filed and where it appears afterwards
An STR is prepared from a case in [Case Manager](#s-3-13) with the six-step STR wizard. A filed STR appears as a row on the **STR** tab. In the examples, the case then shows the status **STR Created** with **Download STR**, and STRs are also listed on the [STR History](#s-5-8) tab of a customer in Customer 360. The field-by-field reference for the six steps is in Case Manager ([Step 1](#s-3-15) to [Step 6](#s-3-20)); this chapter shows what a filed STR looks like, using STR 694.
::: note AML context
Institutions keep a record of every STR they file, with the evidence behind it, so that they can answer follow-up requests from the financial intelligence unit and show supervisors and auditors what was reported and when. The register is that record on the platform.
:::
## The STR register {#s-6-1}
::path[Fyscal ARCX → Regulatory Reports → STR]
Use the register to see the filed STRs and pick the one you need. **Regulatory Reports** opens on the **STR** tab, which shows the filed STRs, newest first, with a search box, a **Refresh** button and a **Show Filters** button above the table. Use the **STR** / **CTR** switch at the top right to change tab.
::figure[The STR tab of Regulatory Reports: search (1), Refresh (2), Show Filters (3), an STR row (4), Download CSV (5), the count line (6) and the STR / CTR switch (7); user names are blurred]{src="str-listing/01-str-register.png" id="fig-str-listing-str-register"}
::: legend
1. **Search by Case Title / Case ID / STR ID**: finds STRs by the case title, the case ID or the STR ID.
2. **Refresh**: reloads the register.
3. **Show Filters**: opens the filters **Creation Period** and **Created By**. The button then reads **Hide Filters**.
4. An STR row. Click a row to open that STR (see [Open a filed STR](#s-6-3)).
5. **Download CSV**: the download icon on each row downloads a CSV file for that STR.
6. The count line (**Showing 1-10 of 127**) and, at the right, **Page 1 of 13** with first, previous, next and last page buttons. The register shows 10 STRs per page.
7. **STR** / **CTR**: switches between the STR register and the [CTR register](#s-6-11). The selected tab is highlighted.
:::
| Column | What it shows | Example |
| --- | --- | --- |
| **Case Title / ID** | The title of the case the STR was filed from, with the case ID and a copy icon below it. The case title is often the customer's name; it can also be an alert ID. | Harish Sinha, CASE-2026-0000075; ALT-TMS-21072026-041467, CASE-2026-0034611 |
| **STR ID** | The STR's ID number, with a copy icon. | 694 |
| **Created At** | Date and time the STR was created. | 24 Aug 2026, 05:59:00 PM |
| **Created By** | The user who created the STR. | (hidden in the figures) |
| **Subjects** | The parties named in the STR, as name tags. When there are more than fit, a **+***n* tag shows how many more. | Harish Sinha, Leena Banerjee, Girish Agarwal, +8 |
| **Amount** | The amount shown for the STR, in Philippine pesos. | ₱6,773,770.75 |
| **Download CSV** | A download icon for the STR's CSV file. | download icon |
## Search and filter the register {#s-6-2}
::path[Fyscal ARCX → Regulatory Reports → STR → Show Filters]
Use the search box when you know the case title, case ID or STR ID, and the filters to narrow the register by creation date or by the user who created the STR.
| Filter | Default | Options or format |
| --- | --- | --- |
| **Creation Period** | **Pick a date range** | A two-month calendar (for example October 2026 and November 2026) with arrows to move between months. Today's date is highlighted. |
| **Created By** | **All Assignees** | A list of users. Your own entry is marked **(You)**; in testing it was the only entry. |
::: step Search for an STR
Click the **Search by Case Title / Case ID / STR ID** box and type a case title (for example **Harish Sinha**), a case ID (for example **CASE-2026-0000075**) or an STR ID (for example **694**).
:::
::: step Open the filters
Click **Show Filters**. The **Creation Period** (1) and **Created By** (2) filters appear below the search box, and the button reads **Hide Filters** (3). Click **Hide Filters** to close them.
::figure[The STR tab filters: Creation Period (1) and Created By (2), with Hide Filters (3)]{src="str-listing/02-filters-open.png" id="fig-str-listing-filters-open"}
:::
::: step Filter by the user who created the STR
Click the **Created By** box (1) (it shows **All Assignees**) and click a user in the list (2). In testing, the list showed one entry, the signed-in user, marked **(You)**.
::figure[The Created By filter (1) open, with one entry marked (You) (2); the user name is hidden]{src="str-listing/03-filter-created-by.png" id="fig-str-listing-filter-created-by"}
:::
::: step Filter by creation date
Click the **Creation Period** box (it shows **Pick a date range**). A two-month calendar opens. Pick the start and end dates of the range. Use the arrows (1, 2) beside the month names to change month. Today's date is highlighted (3).
::figure[The Creation Period calendar, October and November 2026: previous month (1), next month (2) and today's date highlighted (3)]{src="str-listing/04-filter-creation-period.png" id="fig-str-listing-filter-creation-period"}
:::
::: step Download an STR's CSV
In the row of the STR, click the download icon in the **Download CSV** column (5 in [](#fig-str-listing-str-register)).
:::
## Open a filed STR {#s-6-3}
::path[Fyscal ARCX → Regulatory Reports → STR → *STR row*]
Open a filed STR to read exactly what was reported, step by step. Click an STR row to open it. The STR opens in a dialog over the page, titled **Suspicious Transaction Report (STR)**, with the subtitle **GoTRACS-compliant STR filing for AMLC** and the case ID. The dialog has six steps, the same steps used to file an STR from a case: **Select Alerts**, **Report Type**, **Reason for suspicion**, **Transaction**, **Subject parties** and **Narratives**. A filed STR opens read-only: its values are shown in greyed fields and ticked or unticked boxes, and there is no save or submit button. Behind the dialog, the sidebar is shown collapsed to a narrow strip of icons.
The figures below show STR **694**, filed from case **CASE-2026-0000075** (Harish Sinha).
| Control | What it does |
| --- | --- |
| Step bar | Shows the six steps. The current step has a blue number; steps already passed show a green tick. |
| **Next Step** | Moves to the next step. Not shown on step 6. |
| **Previous Step** | Moves back one step. Not shown on step 1. |
| × (top right) | Closes the dialog. |
## Step 1: Select Alerts {#s-6-4}
This step shows which of the case's alerts the STR covers. It lists the case's alerts under the heading **Alerts to include in STR**, with the instruction **Transactions and parties from selected alerts appear in subsequent steps.** A ticked box marks each alert included in the STR.
::figure[Step 1, Select Alerts, for STR 694: the title and case ID (1), the current step (2), an included alert (3), the one alert not included (4) and Next Step (5)]{src="str-listing/05-step1-select-alerts.png" id="fig-str-listing-step1-select-alerts"}
::: legend
1. Dialog title, subtitle and case ID (**CASE-2026-0000075**).
2. Step bar, with **Select Alerts** as the current step.
3. An included alert: a ticked box, the customer name and the alert's disposition (here **Harish Sinha**, **False Match**), then the alert ID, the customer ID, the rule and, for transaction-monitoring alerts, the number of transactions.
4. The alert that is not included: its box is unticked (**ALT-NS-20260827104653114064**, Aman Singh, in the example).
5. **Next Step**.
:::
Each alert shows the customer name, the alert's disposition (for example **False Match** or **True Match**; none when the alert has no disposition), its alert ID (for example **ALT-TMS-20260626072003.357618915-d24534**), the customer ID (for example **TEM-CUST-10L847**), the rule (for example **Rule: TMR-26062026-000367**) and, for transaction-monitoring alerts, the number of transactions (for example **1 transactions**). Name-screening alerts (IDs starting ALT-NS) show **Rule:** with no value.
## Step 2: Report Type {#s-6-5}
This step shows the type of report and its filing details, including the date of determination from which the filing deadline is worked out.
::figure[Step 2, Report Type: STR Type (1), Institution code (2), Supervising agency (3), Submission type (4), STR trigger (5), Date of determination (6) and the Filing deadline message (7)]{src="str-listing/06-step2-report-type.png" id="fig-str-listing-step2-report-type"}
| # | Field | Value in STR 694 |
| --- | --- | --- |
| 1 | **STR Type** | STRR - Regular STR |
| 2 | **Institution code** H-3 | FYSCALTECH20260001 (marked **auto-filled**) |
| 3 | **Supervising agency** H-2 | Securities and Exchange Commission |
| 4 | **Submission type** H-6 | Delete |
| 5 | **STR trigger** D-SD-3 | PPP (Public Private Partnership) |
| 6 | **Date of determination** D-SD-2 | 24/08/2026 |
| 7 | Filing deadline message | Filing deadline: August 31, 2026 (Overdue by 44 days) |
For each field's options, required marker and help text, see [Step 2: Report Type](#s-3-16) in Case Manager. The five STR types are compared in [STR types compared](#s-3-16-types).
Next to the date, a message shows the filing deadline worked out from it: in the example, **Filing deadline: August 31, 2026 (Overdue by 44 days)** on 14 October 2026, in red (7 in the figure). The number of days overdue grows each day. The codes after each label (H-3, D-SD-2 and so on) are the field codes shown on screen for the AMLC GoTRACS report.
## Step 3: Reason for suspicion {#s-6-6}
This step shows the reason codes the STR cites, as primary codes and as additional codes.
::figure[Step 3, Reason for suspicion: the reason codes (1) with SC 3 ticked (2), and Additional reason codes (3) with SC 3 shown dimmed (4)]{src="str-listing/07-step3-reason-for-suspicion.png" id="fig-str-listing-step3-reason-for-suspicion"}
::: legend
1. **Reason for suspicion codes** D-SD-2 (required, \*): "Select one or more SC, PC, or MC codes. Multiple selections allowed."
2. In STR 694, **SC 3** is ticked.
3. **Additional reason codes** D-SD-5 (optional): "Secondary suspicion codes beyond primary codes from Step 3. Codes already selected as primary are shown dimmed." The same code lists repeat here.
4. SC 3 is shown dimmed in the additional list.
:::
A filed STR shows no selection counter on this step.
Each section has three groups, which scroll inside the dialog: **Suspicious circumstances — SC1-SC6**, **Predicate crimes — PC1-PC36** and **Transnational organized crime — MC1**.
The description of every code, and which predicate-crime codes carry a **KYC REQ** tag, is listed once in [Step 3: Reason for suspicion](#s-3-17) in Case Manager.
## Step 4: Transaction {#s-6-7}
This step shows which of the case's transactions are included in the STR, their total amount, and the role of each party in them.
::figure[Step 4, Transaction: filters (1), Selected 3 (2), total amount Mixed 627,513.17 (3), Select Suspicious Transactions (4) and the Party Role legend (5)]{src="str-listing/08-step4-transaction.png" id="fig-str-listing-step4-transaction"}
::: legend
1. Filters: **Type** (**All type**), **Period From** and **Period To** (dd/mm/yyyy).
2. **Selected**: the number of transactions included (3).
3. **total amount (D-TD-6)**: the total of the included transactions. When they are in different currencies it is labelled **Mixed** (here **Mixed 627,513.17**).
4. **Select Suspicious Transactions** (required, \*): "Triggered transactions for this case. All are selected by default - deselect any you want to exclude from the STR".
5. **Party Role** legend.
:::
| Column | What it shows | Example |
| --- | --- | --- |
| (check box) | Ticked when the transaction is included. | ticked |
| **Transaction** | Transaction ID, with the alert ID below it. | TXN-029E18C666DE, ALT-TMS-20260626072003.357618915-d24534 |
| **Amount** | Amount and currency. | SGD 500.00; EUR 324,666.22; AED 302,346.95 |
| **Type** | Transaction type. | INVESTMENT, RETAIL, ENTERTAINMENT |
| **Sender** | Sender name, party-role letter and customer ID. | Girish Agarwal, S, TEM-CUST-96U702 |
| **Receiver** | Receiver name, party-role letter and customer ID. | Kunal Dubey, B, TEM-CUST-49F974 |
| **MOT** | Mode of transaction. | MOBILE, POS |
| **Product** | Product code, or - when none. | 5812, 6011, 5999 |
| **Date** | Transaction date (dd/mm/yyyy). | 20/06/2026 |
The party-role letters next to each sender and receiver (**S**, **B**, **C**, **T**, **O**) are explained in the **Party Role** table in [Step 4: Transaction](#s-3-18).
The note below the legend reads: "MOT, Product Type, Purpose of Remittance, and Transaction Code are sourced from ingested data and included automatically in the Format X CSV per selected transaction. Total amount can be manually overridden below."
## Step 5: Subject parties {#s-6-8}
This step shows the parties named in the STR and their identity details. It lists the parties under the heading **Subject parties**: "Auto-derived from selected transactions. Click a row to expand and edit." Each party row shows a tag (**AH**), the name in the form *Last, First* (or *Last, First, Middle*) and the customer ID. Click a row to expand it.
::figure[Step 5, Subject parties: Sinha, Harish expanded (1), Party role (2), Account holder (3), Entity (4), IDENTITY (5), ID DOCUMENTS (6) and ADDITIONAL DETAILS (7)]{src="str-listing/09-step5-subject-parties.png" id="fig-str-listing-step5-subject-parties"}
::: legend
1. The party row: **Sinha, Harish**. The arrow at the right collapses the row.
2. **Party role**: **S - Subject of Suspicion**.
3. **Account holder** check box, labelled "(emits A-block in CSV)": ticked.
4. **Entity** D-A-3: **N - Natural Person**.
5. **IDENTITY** fields.
6. **ID DOCUMENTS** fields.
7. **ADDITIONAL DETAILS** fields, below the visible area (scroll the dialog).
:::
| Group | Field (code) | Value or placeholder in STR 694 |
| --- | --- | --- |
| IDENTITY | **Last name** D-A-4a | Sinha |
| IDENTITY | **First name** D-A-4b | Harish |
| IDENTITY | **Middle name** D-A-4c | empty (placeholder "e.g. Salamanca") |
| IDENTITY | **CRN** D-A-2 | TEM-CUST-10L847 |
| IDENTITY | **Account no.** D-A-8 | empty (placeholder "e.g. 1238444223") |
| ID DOCUMENTS | **ID type** D-A-12 | Others (drop-down) |
| ID DOCUMENTS | **ID number** D-A-13 | empty (placeholder "e.g. 045223411") |
| ID DOCUMENTS | **Date of birth** D-A-4c | a date (hidden in the figure) |
| ID DOCUMENTS | **Nationality** D-A-11 | empty (placeholder "e.g. PH") |
| ADDITIONAL DETAILS | **Complete address** D-A-5 | not visible in the capture |
| ADDITIONAL DETAILS | **Country code** D-A-6 | PH - Philippines |
| ADDITIONAL DETAILS | **ID City code — PSGC** D-A-7 | not visible in the capture |
| ADDITIONAL DETAILS | **Place of birth** D-A-10 | not visible in the capture |
| ADDITIONAL DETAILS | **Source of fund** D-A-6 | Employed |
| ADDITIONAL DETAILS | **Contact no.** D-A-15 | not visible in the capture |
| ADDITIONAL DETAILS | **Old account no.** D-A-16 | not visible in the capture |
For each field's required marker and placeholder, see [Step 5: Subject parties](#s-3-19) in Case Manager.
STR 694 lists 11 parties: Sinha, Harish; Banerjee, Leena; Agarwal, Girish; Dubey, Kunal; Mishra, Smita; Villacorta, Rodolfo, Aguilar; Halili, Cristina, Garcia; Domingo, Benedict, Abella; Valdez, Ella, Fajardo; Singh, Aman; Joshi, Neha. These are the parties behind the **+8** tag in the register's **Subjects** column (three names shown plus eight more).
## Step 6: Narratives {#s-6-9}
This last step shows the written narrative of the STR and the alerts it covers.
::figure[Step 6, Narratives: the STR Narrative, text hidden (1), its character counter (2), the alerts covered by the STR (3) and Previous Step (4)]{src="str-listing/10-step6-narratives.png" id="fig-str-listing-step6-narratives"}
::: legend
1. **STR Narrative** (D-SD-6, required, \*): the written narrative of the STR, in a text box.
2. Character counter: in the example **254 / 4000 — meets GoTRACS recommendation**, in green with a tick. The maximum shown is 4000 characters.
3. **ALERTS COVERED BY THIS STR**: the IDs of the alerts included in step 1, each with a copy icon. STR 694 covers six alerts.
4. **Previous Step**. This is the last step, so there is no **Next Step** button.
:::
Close the dialog with the × at its top right to return to the register.
## Where STRs come from {#s-6-10}
Read this if you want to file a new STR. The **STR** tab has no button to create an STR. An STR is filed from a case in [Case Manager](#case-manager), using the same six steps shown above; see that chapter for how to file one, and Diagram 6.1 at the top of this chapter for the path an STR takes. A case whose STR has been filed shows the status **STR Created**, as in [Figure 5.12](#s-5-6). To see the STRs linked to one customer, open the customer's [STR History](#s-5-8) tab in Customer 360.
## The CTR register {#s-6-11}
::path[Fyscal ARCX → Regulatory Reports → CTR]
A Covered Transaction Report (CTR) tells the AMLC about a covered transaction. In general, that is a transaction of more than ₱500,000 (see [How CTRs are generated](#s-6-12)). Fyscal ARCX creates CTRs by itself from the transactions it ingests; nobody types in filing data. Use the **CTR** tab to find a CTR, check its filing deadline and download its CSV for filing.
Click **CTR** in the switch at the top right of **Regulatory Reports**. The tab shows the CTRs, newest first.
::figure[The CTR tab of Regulatory Reports: the STR / CTR switch (1), the schedule message (2), search (3), a CTR ID (4), its filing deadline (5), the download icon (6) and the count line (7)]{src="str-listing/11-ctr-register.png" id="fig-str-listing-ctr-register"}
::: legend
1. **STR** / **CTR**: switches between the [STR register](#s-6-1) and the CTR register. The selected tab is highlighted.
2. The message *CTR reports are generated once a day at 3:00 AM. New transactions will appear in the next scheduled run.* CTRs are created by a daily run, not as soon as a transaction arrives.
3. **Search by CTR ID or Date**: finds CTRs by their ID or date.
4. The CTR ID, with a copy icon.
5. **Filing Deadline**: the last day to file the CTR with the AMLC.
6. The download icon: downloads the CTR's CSV file. The column has no heading.
7. The count line (**Showing 1-10 of 150**) and, at the right, **Page 1 of 15** with first, previous, next and last page buttons. The register shows 10 CTRs per page.
:::
| Column | What it shows | Example |
| --- | --- | --- |
| **CTR ID** | The CTR's ID: *CTR-*, the date as YYYYMMDD and a number for each CTR of that date, with a copy icon. | CTR-20261014-0001; CTR-20261012-0002 |
| **Date** | The date of the transactions the CTR reports. One date can have more than one CTR. | 2026-10-14 |
| **Customers** | The number of customers in the CTR. | 8 |
| **Transactions** | The number of transactions in the CTR. In the examples it equals **Customers**. | 8 |
| **Filing Deadline** | The last day to file the CTR. In the examples it is five working days after **Date**. | 2026-10-21 |
| **Created At** | Date and time the platform created the CTR. | 14 Oct 2026, 02:49:20 PM |
| (download icon) | Downloads the CTR's CSV file in the GoTRACS format. | download icon |
::: todo
Confirm with engineering before publishing. (1) What one CTR row represents: the register shows one CTR per date covering several customers and transactions, while the product requirements describe one CTR per reportable unit, with one detail record per CSV file. (2) The examples were created in the afternoon (for example 02:49:20 PM) although the run is scheduled for 3:00 AM; check whether these were test runs.
:::
::: not-covered
This edition does not cover what happens when you click a CTR row, or how the register shows a CTR that could not be completed, for example because customer data is missing. The product requirements describe the statuses **PROCESSING**, **BLOCKED**, **READY** and **FAILED** for this, but they were not shown in the register when it was documented.
:::
## How CTRs are generated {#s-6-12}
Transaction fileUploaded in Data Ingestion
Daily runOnce a day at 3:00 AM
Threshold checkMore than ₱500,000, or the equivalent
CTR createdA row on the CTR tab, with its filing deadline
CSVGoTRACS format, ready to download
Diagram 6.2 — How a transaction becomes a CTR
You don't create CTRs by hand. When a transaction file is uploaded in [Data Ingestion](#data-ingestion), its transactions are stored on the platform. Once a day, at 3:00 AM, the CTR run checks the stored transactions against the institution's approved CTR rules. Each covered transaction it finds goes into a CTR, and the platform creates the CTR's CSV file in the AMLC GoTRACS format. Transactions uploaded after a run, including late transactions for earlier dates, are picked up by the next run.
**The threshold.** The general rule is an amount of **more than ₱500,000**. An amount of exactly ₱500,000 is not over it. Amounts in other currencies are converted to pesos before they are compared.
| Amount in PHP | Over the general threshold? |
| --- | --- |
| 400,000 | No |
| 500,000 | No. The amount must be more than ₱500,000. |
| 500,001 | Yes |
| 750,000 | Yes |
::: important
Not every transaction above ₱500,000 is reported, and the threshold is not the same for every institution. Which transactions are covered depends on the institution's sector, the AMLC transaction code and the mode of transaction (MOT), and some sectors, such as jewellery dealers, real estate developers and brokers, and casinos, have their own thresholds. These rules are approved by compliance and set up on the platform; they are not set on this page.
:::
**The filing deadline.** A CTR must be filed by the fifth working day after the transaction. Weekends and Philippine non-working days are not counted. For example, transactions dated Wednesday 2026-10-14 have the deadline Wednesday 2026-10-21. The deadline is counted from the transaction date, so a late upload or a later run does not move it.
**Missing data.** A CTR is built only from transaction, customer and account data; there is no screen for typing in missing details. If a transaction or customer record is missing required data, correct it in the source data and upload it again so that the next run can use it.
::: note AML context
Covered persons, such as banks, must report covered transactions to the AMLC within five working days. The CTR is filed through the AMLC's GoTRACS portal as a CSV file in the prescribed layout (Annex A of the GoTRACS guidelines). Fyscal ARCX prepares the file; filing it is still done in GoTRACS.
:::
## Find and download a CTR {#s-6-13}
::path[Fyscal ARCX → Regulatory Reports → CTR]
Use these steps to get a CTR's file ready for the AMLC before its filing deadline.
::: step Open the CTR tab
Open **Regulatory Reports** and click **CTR** at the top right (1 in [](#fig-str-listing-ctr-register)).
:::
::: step Find the CTR
Click the **Search by CTR ID or Date** box and type a CTR ID (for example **CTR-20261014-0001**) or a date as shown in the **Date** column (for example **2026-10-14**). To work through the CTRs that are due soonest, check the **Filing Deadline** column.
:::
::: step Download the CSV
In the row of the CTR, click the download icon (6 in [](#fig-str-listing-ctr-register)). The CSV file downloads.
:::
::: step File it with the AMLC
Upload the CSV in the AMLC's GoTRACS portal before the filing deadline. Downloading the file does not file the CTR: Fyscal ARCX does not send CTRs to the AMLC, and the register does not record whether a CTR has been filed.
:::
The CSV follows the GoTRACS CTR layout. It has no heading row; each line is a record that starts with a letter.
| Record | What it contains |
| --- | --- |
| `H` (header) | The first line: the supervising agency code, the institution's 18-digit code, `CTR`, `X` and `A`. `A` means a new submission. |
| `D` (detail) | The transaction: date, AMLC transaction code, transaction reference, mode of transaction (MOT), amount in pesos and, for foreign currency, the amount and currency code. It is followed by the parties, such as the account holder, with their name, address, account, date of birth or registration, ID and source of funds. |
| `T` (trailer) | The last line: `T` and the number of detail records. |
Amounts have no currency sign and no thousands separators, for example `650000.00`. The platform creates new submissions only: correcting or deleting a CTR that has already been filed is not done from this page.