Brokerage statements do not all look alike. One gives you a CSV with clear columns; another gives you a PDF with transactions spread across several pages. Some use unfamiliar abbreviations or leave important details out.
The Prepare Adjustibl Statement skill helps an AI turn those records into a CSV you can review and upload. It also gives you a report explaining what it found, what it added with your approval and what still needs attention.
You stay involved in decisions about missing or ambiguous information. The aim is to make the statement easier to use while keeping its original transaction details intact.
What is a skill?
A skill is a reusable set of instructions and supporting tools for your AI. This one explains Adjustibl's upload fields and guides the AI through reading the statement, proposing column mappings and checking the result.
It does not need access to your Adjustibl account. It works with the files you provide and produces files for you to upload yourself.
Get the skill
Download Prepare Adjustibl Statement (ZIP)
Use an AI environment that supports custom skills, can read your statement format and can run the skill's file checks. A connection to Adjustibl alone does not install the skill.
In Claude, enable code execution and file creation, then open Customize → Skills. Select + → Create skill → Upload a skill, upload the skill ZIP and enable it. Anthropic documents the current steps in Use skills in Claude.
For another AI environment, use its supported skill installation process. Before attaching your statement, ask it to confirm that it can use prepare-adjustibl-statement, read its supporting files and run its checks. Simply attaching a ZIP does not guarantee that the AI has installed or used the skill.
Start with the original statement
Attach your brokerage PDF or CSV and ask:
Use prepare-adjustibl-statement to prepare this file for Adjustibl. Explain the proposed column mapping, ask me to confirm missing or ambiguous information, and give me the CSV and a report of anything I need to check.
Keep the original file. If several files cover overlapping dates, tell the AI what each file contains. It should discuss the overlap before leaving any transactions out.
Your statement will be processed by the AI provider. Review its privacy settings before sharing financial information. Removing personal information from the final CSV does not remove it from a source file you already uploaded to the AI.
Answer the questions that matter
The skill should investigate the statement first, then ask focused questions where your confirmation is needed.
For example, a statement may show amounts without a currency column. The AI might explain the evidence for INR and ask whether INR applies to every transaction. If you confirm, it can add a currency column while preserving the original amounts.
Or a statement might list brokerage and another transaction charge separately. The AI should explain what each charge represents, how it proposes to include them in the upload and which rows are affected. It should ask before adding a calculated column.
Do not confirm an interpretation just to get past a warning. If you are unsure, ask the AI to show the statement entries supporting its proposal. It can leave a question unresolved and explain what information is still needed.
What happens to the original data?
For a CSV, the skill is instructed to preserve the original cell contents, transaction order and legitimate repeated rows. Approved interpretations and calculations go into additional columns.
For a PDF, it reconstructs the transaction table. A name wrapped over two printed lines should become one cell, while its actual words and identifiers remain intact. The AI should check dates, numbers and continued pages against the source.
If a statement uses an unfamiliar security identifier, the skill may research the instrument and propose a supported symbol while retaining the source identifier. It should explain the match and leave uncertain identities unresolved.
The skill should flag differences such as a net amount that does not agree with the listed charges. It should not change the statement's numbers or omit a charge just to make the arithmetic agree.
Review the files you receive
You should receive one or more CSVs and a readable report. Separate accounts should remain distinguishable.
Read the report before uploading. It should tell you:
- Which accounts and periods the files cover.
- Which information was added with your approval and why.
- Which Adjustibl field corresponds to each selected CSV column.
- Which amounts could be checked and any differences that remain.
- Which instruments, currencies or other details still need attention.
Compare several transactions with the original statement, including purchases, sales and any unusual activity. Check every issue the report identifies. Passing the file checks does not prove that every PDF entry or interpretation is correct.
Upload the CSV to Adjustibl
Open the intended account in Adjustibl and start a CSV upload. Select the prepared file and use the report's mapping table to match the columns.
Review the validation results and instrument matches. Supply opening positions and cash balances where your history needs a starting point, then review the import before finishing.
A statement's closing balance or holdings summary is not automatically the historical cost you need for an opening position. Keep those decisions separate from preparing the transaction file.
After importing, compare the resulting transactions and balances with your statement. The skill prepares the data; Adjustibl validates the import and calculates the results.
If something still needs attention
Keep the generated report alongside your original statement. It gives you a record of the assumptions you approved and the questions left open.
If Adjustibl reports a problem, return to the AI with the exact message and the relevant transaction details. Ask it to explain whether the issue comes from the original statement, the proposed mapping or the prepared file. Review a corrected file before uploading it, and check for transactions already imported so you do not add them twice.