# Bankster API > Financial systems, data access and the boundaries between them. All articles are public. Each entry states its mechanism, scope, sources and related concepts. Constructed examples are hypothetical. Conditional deductions retain their stated assumptions. ## Formats - [Article index](https://bankster-api.com/articles/) - [Editorial categories](https://bankster-api.com/categories/) - [Publication and editorial method](https://bankster-api.com/about/) - [Full article data in JSON](https://bankster-api.com/articles.json) - [RSS](https://bankster-api.com/rss.xml) - [Institutional data source access map](https://bankster-api.com/access-map/) ## Articles - [AI assistants connect permissions as well as data](https://bankster-api.com/articles/ai-assistants-permissions/index.md): Connecting an AI assistant to financial tools also connects permissions. Trace the authority behind retrieval, recommendations and actions. - [More automated fraud screening can create more manual work](https://bankster-api.com/articles/automated-fraud-screening-manual-review/index.md): Better screening rates can still create a larger review queue. Work through how transaction volume and alert rates interact. - [Cloud, on-premises and SaaS describe different choices](https://bankster-api.com/articles/cloud-on-premises-saas/index.md): Cloud location, infrastructure ownership and SaaS delivery answer different questions. See how they intersect in financial systems. - [Concurrent orders and shared risk limits](https://bankster-api.com/articles/concurrent-orders-shared-risk-limits/index.md): Two valid order checks can exceed one shared limit. Work through reservations, concurrent decisions and the state needed to enforce a cap. - [Continuous payments create a continuous funding problem](https://bankster-api.com/articles/continuous-payments-funding/index.md): Continuous payment acceptance does not ensure continuous funding. Explore the timing mismatch between outgoing flows and replenishment. - [Counterparty exposure: from trades to netting sets and collateral](https://bankster-api.com/articles/counterparty-exposure-netting-collateral/index.md): Trade values become counterparty exposure through agreement scope, netting and collateral. Follow the calculation boundaries. - [Where CRM and ERP sit in a financial institution](https://bankster-api.com/articles/crm-erp-financial-systems/index.md): Client records and business accounts do not replace trading or settlement systems. Explore where CRM and ERP connect to financial workflows. - [Decimal arithmetic does not choose a rounding policy](https://bankster-api.com/articles/decimal-rounding-financial-reconciliation/index.md): Decimal arithmetic cannot decide when to round. A worked example shows why line-item and aggregate rounding produce different balances. - [Exactly-once delivery and exactly-once financial effects](https://bankster-api.com/articles/exactly-once-financial-effects/index.md): Delivering an event once and applying its financial effect once are different guarantees. Explore retries, deduplication and ledger boundaries. - [Execution benchmarks can reward unfinished orders](https://bankster-api.com/articles/execution-benchmarks-unfinished-orders/index.md): A benchmark based on filled orders can hide the cost of unfinished work. See how residual orders can reverse an execution ranking. - [Transaction databases, tick stores and search indexes](https://bankster-api.com/articles/financial-database-roles/index.md): Ledgers, tick stores and search indexes preserve different facts. Learn why one database rarely serves every financial workload. - [LEI, ISIN, FIGI and MIC: identifying the entity, instrument and venue](https://bankster-api.com/articles/financial-identifiers-entity-instrument-venue/index.md): LEI, ISIN, FIGI and MIC identify different things. Learn why matching an entity, security or venue does not establish permission. - [FIX, ISO 20022 and FDC3: what each standard connects](https://bankster-api.com/articles/financial-interoperability-standards/index.md): FIX, ISO 20022 and FDC3 connect different parts of finance. Compare message exchange, business meaning and desktop context. - [Why financial firms use several programming languages](https://bankster-api.com/articles/financial-programming-languages/index.md): Why trading, pricing and operations use different languages—and how memory, latency and numerical workloads shape the choice. - [Gross settlement can reduce waiting while increasing funding needs](https://bankster-api.com/articles/gross-settlement-netting-liquidity/index.md): Settling payments sooner can require more funding. Compare gross settlement, netting and the timing of incoming and outgoing cash. - [KYC, AML and sanctions screening answer different questions](https://bankster-api.com/articles/kyc-aml-sanctions-workflows/index.md): Customer identity, suspicious activity and sanctions restrictions need different controls. Follow the handoffs between KYC, AML and screening. - [Lakehouse interoperability: files, tables, catalogs and writers](https://bankster-api.com/articles/lakehouse-interoperability/index.md): Shared file formats do not guarantee shared table behavior. Examine the catalogs, metadata and writer rules behind lakehouse interoperability. - [Data lineage, quality checks and reconciliation establish different facts](https://bankster-api.com/articles/lineage-quality-reconciliation/index.md): Knowing where data came from does not prove it is complete or correct. Compare lineage, quality checks and reconciliation. - [How an approved loan becomes a serviced account](https://bankster-api.com/articles/loan-origination-servicing-ledger-handoff/index.md): An approved loan still needs contracts, servicing records and ledger entries. Follow the handoff from lending decision to account operation. - [What does a market-data API actually give you?](https://bankster-api.com/articles/market-data-api-access/index.md): A market-data endpoint does not define your coverage or rights. Understand feeds, timing, entitlements and the limits of API access. - [Two clouds can share one failure dependency](https://bankster-api.com/articles/multi-cloud-common-dependencies/index.md): Two cloud deployments can fail through one shared dependency. Examine the identity, network and recovery systems behind apparent redundancy. - [From notebook to model service: preserving a financial calculation](https://bankster-api.com/articles/notebook-to-model-service/index.md): Moving a calculation into production requires more than packaging code. Preserve inputs, versions, units and execution assumptions. - [From order to settlement: the systems that change a trade’s state](https://bankster-api.com/articles/order-to-settlement-systems/index.md): An accepted order, a fill and a settled trade are different events. Follow the systems and handoffs that change a trade’s state. - [Payment accepted, account posted, funds settled: three different states](https://bankster-api.com/articles/payment-status-ledger-settlement/index.md): Payment accepted does not mean funds settled. Separate an interface response, a customer ledger posting and the settlement event. - [Point-in-time data: the history a backtest was allowed to know](https://bankster-api.com/articles/point-in-time-backtest-data/index.md): A backtest must use what was knowable at the time. Separate event dates, publication times, revisions and historical data availability. - [Positions, accounting balances and risk exposures](https://bankster-api.com/articles/positions-balances-risk/index.md): A position, an accounting balance and a risk exposure describe different views of a trade. See where their numbers diverge. - [Private connectivity, encryption and authorization protect different boundaries](https://bankster-api.com/articles/private-connectivity-encryption-authorization/index.md): A private connection is not encryption or permission. Trace the separate boundaries protected by network paths, cryptography and identity. - [Recovery time includes transaction reconciliation](https://bankster-api.com/articles/recovery-transaction-reconciliation/index.md): Restarting a service does not restore a trusted transaction state. See why reconciliation belongs inside the recovery timeline. - [A reproducible model needs reproducible data rights](https://bankster-api.com/articles/reproducible-data-rights/index.md): Saved code does not guarantee a repeatable model run. Data retention, access and licensing rights can determine what can be reproduced. - [Electronic recordkeeping: retention, legal hold and eDiscovery](https://bankster-api.com/articles/retention-hold-ediscovery/index.md): Keeping records, preserving them under legal hold and retrieving evidence are distinct jobs. Map their storage and workflow requirements. - [Why healthy services can produce incomplete financial reports](https://bankster-api.com/articles/telemetry-reporting-population-completeness/index.md): Healthy services can still omit financial events. Learn why operational monitoring needs separate checks for reporting completeness. - [Low-latency trading: separating delay from clock error](https://bankster-api.com/articles/trading-latency-clock-error/index.md): A timestamp difference can mix processing delay with clock error. See how synchronization changes what a trading latency measurement means. - [Trading shutdowns have a completeness problem](https://bankster-api.com/articles/trading-shutdown-completeness/index.md): Stopping one gateway does not prove all trading activity has stopped. Trace in-flight orders, acknowledgments and shutdown completeness. - [Vendor exit costs depend on reconstructing financial state](https://bankster-api.com/articles/vendor-exit-financial-state/index.md): Exported files are only part of a vendor exit. Reconstructing balances, history and operating state can determine the real migration cost. - [Workload identity and privileged access](https://bankster-api.com/articles/workload-identity-privileged-access/index.md): A service identity and a privileged session grant different powers. See how machine identity, secrets and administrative access fit together.