AI in the Tax Function: What Corporate Tax Teams Can Automate, and Where Judgement Stays
AI in corporate tax: what to automate, what needs preparer review, what stays with senior judgement, plus a data-readiness check for heads of tax and CFOs.
Strategic intelligence across AI, infrastructure, payments, and technology leadership.
AI in corporate tax: what to automate, what needs preparer review, what stays with senior judgement, plus a data-readiness check for heads of tax and CFOs.
AI requests arrive from every function at once, priced in seats, consumption and services. Fund AI like a staged portfolio, not a software line item.
Buyers now send AI agents to research, compare, negotiate and complain. The advantage shifts from persuasion to machine-readable truth. How to get ready.
AI legacy code migration for executives: what agents do well, where COBOL rewrites still fail, and when to wrap, translate, rewrite or retire a system.
AI assistant seats are up for renewal. Keep them for power users and proven workflows, pool the rest, and renegotiate with your own usage data.
AI in marketing for executives: what generative AI changes in content, campaigns and search, where brand risk sits, and what to automate or keep human.
Agents with 95 percent reliable steps finish 60 percent of ten-step tasks. A practitioner guide to failure classes, recovery patterns, and reversibility.
AI in internal audit: full-population testing, continuous monitoring, where evidence breaks down, and an assurance checklist for the AI your business runs.
Accounting treatment quietly decides which AI projects look attractive. What can be capitalized, what cannot, and the policy a CFO should set first.
AI exclusions now appear in thousands of US policy filings. The renewal questionnaire, not a regulator, will set your first enforceable AI controls.
AI SOC agents explained for CISOs: which security tasks to automate, which to keep human, the new attack surface, and how to measure an agentic SOC.
Snowflake, Databricks and the hyperscalers want to host your agents. Keep data controls there; keep the agent runtime separable. A layer-by-layer guide.
Computer-use agents reach systems with no API, but they are the slowest, least reliable way in. When to use them, the benchmarks, and the controls.
AI contract review for in-house legal: which tasks to automate, what the evidence shows, where hallucination and privilege risk sit, and who signs off.
Boards ask the CFO what AI returns, and most cannot say. Why hours saved fails, which metrics hold up, and a funding model that kills what does not pay.
What AI in FP&A changes: where forecasting and planning AI works, where it fails, the controls the board needs, and a maturity path for the finance team.
RPA vs AI agents for enterprise automation: where bots still win, where agents earn their cost, the hybrid pattern, and how to triage a bot portfolio.
A chief AI officer works only if it holds three things: the platform and its controls, the funding gates and risk sign-off. Otherwise it is a demo team.
Agents attack the labour IT services and BPO contracts bill for. Why buyers hold the leverage at renewal, and the terms to demand before providers reprice.
Agent evals must score a sequence of actions, not one answer. The five test layers, pass^k reliability, graders and release gates by action risk.
Do AI SDRs work? What AI sales agents deliver, where they burn domains and brand, the compliance rules, and when to assist, automate or replace by motion.
Buying an agent from every system of record recreates SaaS sprawl one layer up. How CIOs should choose, and which controls must stay central.
AI-generated fake receipts now beat visual review. How expense fraud changed, which detection still works, and the controls to use by company size.
Agents act through integrations. iPaaS and API vendors hold the connectors, credentials and audit trails, and MCP makes governing that layer worth more.
Every AI feature copies company data into prompts, logs, embeddings and memory. Where each copy lives, what vendors retain, and how to make deletion real.
AI is taking the bottleneck work out of the month-end close. The close becomes continuous with a short sign-off, and finance, audit and the board change.
Where AI helps in hiring and HR, where legal risk concentrates, what NYC, the EU, Colorado, Illinois and California require, and which controls hold up.
Most tasks run better on one well-tooled agent. Multi-agent systems pay off only for parallel work, isolated context or independent checks.
AI spend is moving from central IT to business lines. That ties cost to outcomes but breaks controls built for an IT-held purse. The model that works.
What AI can take over in accounts payable, step by step from capture to payment, where the fraud risk grows, and which controls must stay outside the model.
The first agents trusted with company money will buy for the enterprise. Control moves from approval chains to policy as code and card-level limits.
Why AI assistants expose overshared data, how data classification fixes it, what to label first, and a 90-day plan for executives.
Enterprise search failed for twenty years. Now the permission-aware index behind every AI assistant is the control point, and its owner wins.
Which IT operations actions AI agents can safely take, at what autonomy level, with which controls, and how to measure it without fooling yourself.
Agent approvals catch errors only at irreversible actions, with a clear diff, at a pace reviewers can read. Where to put them, and how to tell they work.
The model layer is commoditizing faster than any software layer before it. The margin is moving to scarce inputs and to whoever owns the workflow.
Why card payments get declined, soft vs hard declines, and the levers that raise authorization rates without letting fraud and chargebacks rise with them.
Running one workload across two clouds rarely pays for itself. A second cloud's real value is leverage and exit evidence. Which workloads need what.
Why banks still run mainframes, the real cost of COBOL estates, and which modernization paths work: rehost, refactor, strangler or full core replacement.
Mandatory APP scam reimbursement turns fraud into a line in instant-payment unit economics, and the receiving firm now pays half. What it costs, and who.
An LLM feature has four parts that change on their own. Release them as one versioned artifact behind an eval gate. The rules, tables and build order.
Why LLMs hallucinate, the three kinds of AI hallucination, and which controls actually reduce it, ranked by cost and matched to the cost of an error.
SaaS vendors keep the service up. Keeping your records recoverable is usually your job. The shared-responsibility gap, and how boards should close it.
Credit card surcharge rules differ by network, state and country. When a surcharge is legal, what it does to sales, and cheaper ways to cut card costs.
Much of payments profit is interest on money in transit. Instant rails remove the transit, rates swing the yield. How to find float dependence.
Passkeys remove phishable passwords, but enterprise rollout hinges on synced vs device-bound keys and account recovery. A phased plan by user population.
Deflection counts every chat that never reached a human, including the customer who gave up. What to measure instead, and what to ask vendors.
Most systems called agents should be workflows with a model call inside. The four shapes, a scoring rubric, and when autonomy is worth what it costs.
LLM document extraction reads layouts OCR templates cannot, and invents fields it cannot read. When it beats IDP, what it costs, and the controls it needs.
The AI platform mandate lands on the team that owns the gates. It is the second platform consolidation, and the scope has to be renegotiated on the way in.
A company has no biometric and no single registry. Why KYB still takes days, what beneficial ownership really requires, and how to tier verification by risk.
Embedded lending is a credit business with a software channel, not a software business with a credit feature. The models differ by who eats the loss.
SLI, SLO, and SLA are three different things. How to pick targets users can perceive, and why the error budget policy is the only part that changes behavior.
When an agent moves money or promises a customer something, the loss lands wherever the contract is silent. That gap is a deployment constraint.
Prompts, completions, embeddings, and logs land in four different places. What a regional endpoint guarantees, what it only implies, and how to decide.
When an agent fails in production the cause is usually a badly designed tool, not a weak model. The granularity, description, parameter and return rules.
Observability was sold as a product and is being re-architected as a data pipeline. That is what breaks the pricing model, not the customer anger.
Vault, gateway, and network tokens are three different things. How network tokenization lifts authorization rates, and the processor lock-in nobody flags.
Interchange is not being abolished, it is being unbundled. The losers are not the networks. They are issuers whose products are funded by a fee going soft.
An SBOM answers one question well and three not at all. What provenance, signing, admission policy, and reachability add, and the order to build them in.
The best vertical AI companies stopped selling assistants beside the suite. They are taking over the record itself, and the record owns the renewal.
Container, microVM, or separate account: what each agent sandbox rung actually stops, why egress policy matters most, and how to scope agent credentials.
Agent memory is a retention policy, not a database. The four memory classes, write and read rules, forgetting as a feature, and the store-or-recompute math.
The SSO tax is not a price for SSO. It is a segmentation fence, and the features behind it are chosen for willingness to pay, not cost to build.
Processors underwrite credit risk, not just fraud. Why delivery timing drives rejections, how reserves work, and the founder playbook for approval.
Correspondent banking survives every challenger because it is not a technology. It is a socialized compliance liability structure, and challengers rebuild it.
Technical debt has no principal and no fixed rate. The proxy metrics that work, why dedicated debt sprints fail, and how to frame it for a CFO.
Machine learning rewrote credit decisioning, but the binding constraint is not accuracy. It is the compliance machinery needed to deploy a model.
Why prompt injection has no parameterized-query fix, how indirect injection turns agents into attack tools, and the patterns that bound the damage.
Three LLM cache types solve different problems teams routinely conflate. What each saves, the hit rates you should actually expect, and where each one breaks.
Owned accelerators beat rented ones above a utilization threshold most teams never compute. The break-even math, and why idle GPUs are the expensive asset.
The four layers behind every fintech card: network, sponsor bank, issuer processor, program manager. Who earns what, and what it takes to launch.
The middleware era of banking as a service is over. What replaces it is fewer, larger, compliance-first programs, and a harder diligence bar for founders.
Zero trust explained without the vendor gloss: the real principle, the NIST 800-207 components in plain language, and what a migration actually costs.
Training data went from free scrape to priced asset in three years. Who sets the price, who captures the value, and why enterprises are giving theirs away.
What an AI gateway does, how it differs from an API gateway, build versus buy options, the failure modes, and a rollout sequence for enterprises.
Constrained decoding against a schema, not prompt-and-parse, is how to get reliable JSON from an LLM. Schema design, validation layers, and failure modes.
Multi-region is the most expensive default in modern infrastructure. The real bill is not the second region's compute, it is the permanent engineering tax.
Fraud losses land where the rules put them. How liability differs across cards, ACH, real-time rails, and wires, and what shifts it.
Private credit grew into a multi-trillion asset class on spreadsheets and email. The plumbing is being rebuilt as software, and that is the real story.
Postgres is replacing vector stores, queues, document databases, and search clusters. Where each substitution holds, where it breaks, and the switch triggers.
Models are commodities. The accumulated context a vendor holds about your organization is not, and it is becoming the stickiest layer in the AI stack.
Classic LLM observability breaks for agents. The telemetry model, four failure classes, trajectory evaluation, and a build order a platform team can ship.
Why API keys break for AI agents, the delegation patterns replacing them, how to scope authorization, and the audit trail attribution requires.
Inference is a real, usage-scaling cost of goods sold. It is pulling software gross margins toward infrastructure territory, and buyers pay for it either way.
How virtual cards work in B2B payments: issuance, control types, rebate economics, the supplier acceptance problem, and where they beat ACH.
Stablecoins were supposed to disintermediate the card networks. Instead Visa and Mastercard are running an incumbent defense: co-opt, contain, collect.
What a data contract contains, where enforcement lives, how it differs from a catalog, a pragmatic adoption sequence, and the failure modes to avoid.
Agent interop standards are not neutral plumbing. Whoever owns the protocol layer between agents and enterprise systems owns the distribution chokepoint.
Route 60-80 percent of production traffic to small models with a quality fallback. The four routing architectures, the eval signals, and the failure modes.
Shadow AI explained: the three exposure classes, why bans fail, how to detect unsanctioned tools, and the tiered governance model that survives contact.
AI capacity is consolidating into a utility with three chokepoints. The strategic question is no longer which model to use, it is who controls your inference.
Treasury for growing companies: the maturity progression, the lessons that stuck after 2023, operational controls, new instruments, and when to buy a TMS.
Tech hiring is barbelling: fierce competition for senior talent and cheap junior capacity, with the middle squeezed out. This is structural, not a hype cycle.
API versioning strategies compared, what a credible deprecation policy contains, the consumer-side defenses, what AI changes, and the metrics that matter.
Consumer agentic commerce is stalled on liability and mandate problems. B2B receivables is not, and that is where agent-initiated payments are shipping now.
AI build versus buy is not one decision but six, one per stack layer. A decision matrix with defaults, override conditions, and traps for each.
Synthetic data explained: the three generation families, four jobs it does well, where it fails quietly, the regulatory read, and a fit-assessment framework.
Open weights do not commoditize AI. They relocate the toll booth to compute, distribution, and evaluation, and reshape who captures the AI margin.
Payment reconciliation explained: what actually gets matched, why the lump-sum deposit is hard to decompose, failure modes, automation, and health metrics.
Deep analysis across the systems, strategies, and economics that shape modern technology.
Premium Members Get: Exclusive deep-dive research · Architecture playbooks · Executive briefings · Full archive access