What’s available
Build your loader against the column names on this page, not column positions, and read the manifest first. When delivery starts, this page will say so, and the manifest’s
spec_version will tell you which version of the layout each batch follows.The daily file set
The suite works the same for disclosed and undisclosed account models. The core files carry no holder-level personal data. Clients on the disclosed model can receive one extra file,
compliance_profiles, with registration and holder information.
Account model and identifiers
The files use the same account model as the Accounts guide:account_idis the UUID Anchorage Digital assigned. It’s the primary key of every account-scoped row and the path parameter for the API.parent_account_idis, for aSEGREGATEDaccount, the FBO or omnibus it sits under. Empty for top-level accounts.external_idis the identifier you supplied when you created the account: your join key back to your own books. We treat it as opaque and return it unchanged.account_typeisSEGREGATED,FBO, orOMNIBUS. An FBO always has segregated accounts under it, and its positions and transactions are reported on those accounts, never on the FBO row. An omnibus withledgering: SEGREGATEDworks the same way. A pure omnibus (ledgering: SELF) has no child accounts, so its positions and transactions appear on the omnibus itself and customer-level reconciliation runs against your own subledger.- Disclosed or undisclosed is a property of the FBO or omnibus parent (
is_disclosed), inherited by the accounts under it. An undisclosed segregated account never references a compliance profile: the owner of record is your organization.
parent_account_id is yours, keyed by external_id.
Delivery
Files will be generated by Anchorage Digital and pushed to your SFTP server. Every file will be encrypted with your PGP public key before it leaves us and only ever transferred in that form. At rest inside Anchorage Digital, files are protected by our standard storage encryption and organization-scoped access controls.What you provide at onboarding
- The SFTP username we connect as.
- The host address, and the port if it isn’t 22.
- The upload directory, if files shouldn’t land in the directory the user starts in.
- Your PGP public key. See Set up a PGP key if you don’t have one.
- Your reconciliation cutoff preference. See below.
What Anchorage Digital provides
- The SSH public key our delivery service authenticates with. Register it against the SFTP username you created for us.
- Our egress IP addresses, if you restrict inbound SFTP connections by source.
- The short
org_idwe assign to your feed and use in file names. It isn’t the 64-character organization key ID the API uses.
Reconciliation cutoff
Each client has a daily cutoff: the moment positions are struck and the transaction window closes. The default is 00:00 UTC, which matches the valuation time of Anchorage Digital account statements, so files and statements agree by construction. A different cutoff can be agreed at onboarding.- The reconciliation date
Tof a batch is the calendar date, in the cutoff timezone, of the day that ends at its cutoff. With the default cutoff,T’s batch covers the UTC dayTand is struck at 00:00 UTC the next day. accounts,positions,assets,prices, andcompliance_profilesare snapshots as ofT’s cutoff.transactionscovers the window from the previous cutoff, exclusive, toT’s cutoff, inclusive.- Timestamps inside the files are always RFC 3339 UTC, whatever the cutoff timezone.
Schedule
- Files are produced every calendar day, seven days a week. If you reconcile on business days only, consume the weekend files together with Monday’s.
- Files are uploaded under temporary names and renamed on completion, so a file visible under its final name is complete. The
manifestis uploaded last. Its appearance means the batch is ready to consume. - An empty dataset still produces a file with a header row, so a missing file always means a delivery failure, never “there was nothing”.
Redelivery, backfill, and restatements
- Redelivery (same content, delivery failed): ask your Anchorage Digital operations contact and the files are pushed again.
- Backfill: a historical
transactionsfile covering any window back to account inception, in the same layout as the daily file, is available on request. Useful when you enable the feed for an organization with existing activity. - Restatement (content was wrong and is corrected): the affected files are reissued with a revision suffix (
_r1,_r2, and so on) and a new manifest listing the revised files. A restatement never patches individual rows. Reload the full file. Your operations contact is notified whenever a restatement is issued.
File conventions
- Format: RFC 4180 CSV, UTF-8, LF line endings, one header row of
snake_casecolumn names. Fields containing commas, quotes, or newlines are double-quoted, and embedded quotes are doubled. - Naming:
anchorage_<dataset>_<YYYYMMDD>_<org_id>[_rN].csv.gpg, for exampleanchorage_positions_20261105_a1b2c3.csv.gpg.YYYYMMDDis the reconciliation date,org_idis the short identifier assigned at onboarding, and_rNappears only on restatements. Decrypting with your private key yields the plain.csv. - Account statements (opt-in) land in a
statements/subdirectory as<account_id>_<statement_name>_<YYYYMMDD>[_corrected].pdf.gpg, whereYYYYMMDDis the date the statement became available and_correctedmarks a revised version. - Quantities are decimal strings in the asset’s native unit, full precision, no exponent notation, no thousands separators, for example
10.45234733. Don’t parse them as floats. Precision matters at 18 decimals. - USD values are decimal strings rounded to the cent.
- Timestamps are RFC 3339 UTC with microsecond precision, for example
2026-11-05T21:04:05.123456Z. Dates areYYYY-MM-DD. - Booleans are lowercase
trueandfalse. An empty string means null or not applicable. - Column contract: key on column names, not positions. Additive changes (new columns, new enum values) ship with advance notice. Breaking changes ship as a new major version delivered in parallel during a transition window. The manifest carries the version each batch was produced under.
Accounts file
A full snapshot of every account in your organization, all types, including recently closed accounts so that closures reconcile. One row per account.
Registration type, tax classification, and holder information are deliberately not on this file. See the
compliance_profiles file.
Positions file
A full snapshot of holdings as of the day’s cutoff. One row per account, asset, and balance type. The rows for one account and asset are views of a single holding, not parts to be summed: theTOTAL row is the holding, and the other rows break it down or qualify it.
Balance types
For every account and asset,
AVAILABLE_FOR_TRADING = TOTAL − HOLD + PENDING and AVAILABLE_FOR_WITHDRAWAL = min(TOTAL − HOLD, AVAILABLE_FOR_TRADING). These are the definitions GET /v4/accounts/{accountId}/balances uses, so a position row and the API agree on what each bucket means. Component rows appear only when non-zero. TOTAL always appears.
New balance types (for example staking states) ship as additive changes with notice. Each states its relation to TOTAL and never changes the five definitions above. Treat a balance_type you don’t recognize as informational: keep it out of your roll-forward and valuation checks, which run on TOTAL, and don’t fail the batch on it.
Population rules
- A position row appears while any balance type for the account and asset is non-zero, plus one final day after everything reaches zero (a
TOTALrow with quantity0), so you see a position close rather than vanish. - Accounts holding nothing produce no rows. They’re still in
accounts. - For a pure omnibus, positions exist only at the omnibus
account_id. For an omnibus withSEGREGATEDledgering, and for an FBO, positions are reported on the accounts under it, and no parent-level row is emitted, so nothing is double counted.
Transactions file
A delta file: everything that happened in dayT’s window. One row per transaction entry (leg). A single business transaction (transaction_id) has one row per account and asset movement it caused, so a transfer between segregated accounts has two rows and a trade has two or more.
Every row is a ledger entry booked within T’s window. booked_at is the criterion, not the transaction’s creation time. The ledger is append-only, so a transaction appears on every day it books something. A deposit books PENDING legs when detected. On the day it confirms, it books the legs that move the amount from PENDING to AVAILABLE, reported with status: POSTED. A cancellation books reversing legs, reported with status: CANCELED. status, created_at, and posted_at describe the transaction as a whole, as of the cutoff.
Rows are uniquely keyed by transaction_id and entry_seq.
Transaction types
Every transaction type the API lists appears in the file under the name the API returns. Like the API, the file reports a deposit that is a reward as
STAKING_REWARD or DELEGATION_REWARD.
- Trades: trade economics are on the
TRADErows themselves (order_id,avg_price, fees) rather than in a separate trades file. They’re the account’s pro rata share of the parent order, so allocation-level reconciliation works from this file. The orders API gives the order-level view. - Corrections: a mis-booked entry is corrected by a reversing transaction that references the original in
reversal_of_transaction_id. History is never mutated. A restated file corrects file-generation errors, not bookings. - In the undisclosed model,
counterparty_addressis still populated. It’s chain data, not personal data. Originator and beneficiary names never appear in the suite.
Assets file
A full snapshot of every asset enabled for your organization: the reference data needed to readpositions, transactions, and prices. One row per asset.
Crypto assets have no CUSIP or ISIN.
asset_type is the identifier. If you keep your own security master, map from it.
Prices file
A full snapshot of end-of-day reference prices for every asset enabled for your organization: the prices used to value that day’spositions file. One row per asset.
These are reference prices for valuation and reconciliation, not execution prices. Trade rows in
transactions carry their own avg_price.
Compliance profiles file
Holder-level data is deliberately not onaccounts. In the undisclosed model it doesn’t exist at Anchorage Digital. Clients on the disclosed model receive this extra snapshot. Undisclosed clients don’t, and the manifest simply won’t list it.
A compliance profile carries the registration type, tax classification, owners, and authorized signers for one or more accounts that reference it through accounts.compliance_profile_id. A profile can be shared by several accounts, such as one investor’s taxable and IRA accounts.
One row per profile and party. Profile-level columns repeat on every row of the profile. A profile with no parties yet still produces one row with the party columns empty.
Manifest file
A control file, uploaded last, that makes the batch verifiable. One row per file delivered for the date (itself excluded), including any statement PDFs.
Verify presence, counts, and checksums against the manifest before consuming anything. Treat a missing manifest past the agreed delivery window as an incident and contact your operations contact.
Run the daily reconciliation
The intended flow on your side, once the manifest arrives:1
Completeness
Verify every file the manifest lists is present with a matching
record_count and sha256, then decrypt.2
Account reconciliation
Diff
accounts against your master: every expected external_id present, statuses as expected, hierarchy (parent_account_id) intact.3
Position roll-forward
For every account and asset,
TOTAL(T) − TOTAL(T−1) must equal the signed sum (CREDIT positive, DEBIT negative) of quantity over transactions rows with balance_type = AVAILABLE.4
Valuation check
market_value_usd = quantity × price_usd on every position row, and price_usd matches prices.price_usd for the same date.5
Trade reconciliation
Match
TRADE rows to your order records through order_id or order_external_id. Verify allocation quantities, avg_price, and fees.6
Funding reconciliation
Match
DEPOSIT and WITHDRAWAL rows to expected flows through onchain_tx_hash and transaction_id. PENDING rows explain the PENDING and HOLD balances in positions.7
Breaks
Raise them with your Anchorage Digital operations contact, quoting
as_of_date, account_id, and the transaction_id values or account and asset pairs involved.Set up a PGP key
Every file is encrypted with your PGP public key before transmission. You can provide a key generated with any PGP or GPG-compatible tool. If you don’t have one, the steps below use GnuPG. On Windows, substitutegpg.exe for gpg.
1
Install GPG
Check whether it’s already available with
gpg --version. If not: sudo apt install gnupg on Ubuntu or Debian, brew install gnupg on macOS, or Gpg4win on Windows.2
Generate a key pair
Anchorage recon files), an email address, and an optional passphrase. A blank passphrase makes automated decryption easier, but a private key without one is less protected if someone gains access to the system holding it. Confirm the key exists with gpg --list-secret-keys.3
Export the public key
.asc file to Anchorage Digital. The public key is safe to share over any channel. Never export or send your private key.4
Test decryption
decrypted-test-file.txt matches the original. The same decryption applies to every file you receive from Anchorage Digital.