The Lexicon is a working vocabulary for accounting and finance: the precise word in place of a loose phrase.
Software, engineering, mathematics, and data science already have exact words for things that show up in accounting and finance too. The Lexicon takes the best of them and puts them to work here.
The Lexicon is Native Constraint in practice: Systems, Clarity, Posture.
The three pillars, on the vocabulary itself
SystemsThe vocabulary is a system. One shared lexicon replaces arbitrary phrasing, and the team reaches the exact thing faster, because every person in the room holds the same word.
ClarityThe exact thing is said instead of circled with five near-words. The precise term is taken by a colleague exactly, not approximately, with nothing left to interpret.
PostureThe standard does not slip. The vocabulary keeps sharpening instead of sliding back into loose phrases, and the team holds to it, because command of the language is part of the profession.
The terms are listed below in alphabetical order. Each entry gives the word's source, what it means in its field and in accounting and finance, its part of speech, and the word in use, the same idea before and after the term is adopted.
The vocabulary gathers around five concerns: how you know a figure is true (provenance, lineage, ground truth, base rate), where the work lives (abstraction, coupling, normalization, single source of truth), how a system fails and holds (fail-closed, failure mode, invariant, single point of failure), how an operator directs and checks it (dry run, rollback, versioning, attestation), and how the function reports its own condition (compensatory effort, coordination dependence, latency, drift).
A – Z
Source · systems design
Abstraction noun
In its fieldHiding complexity behind a clean interface, so the user works with what a thing does, not how it works. A driver turns a wheel without knowing the steering linkage beneath it.
In accounting and financeA good financial system abstracts: the board sees position and movement, not the reconciliation and computation underneath. The skill is choosing the interface, exposing exactly what the reader must decide on and concealing the machinery they should not have to hold in their head. Done well, abstraction is what lets a board govern without drowning in detail. Done badly, it either buries what matters or surfaces what does not.
In use
Before"Can we give the board something more high-level, like a summary view, without all the detail and the backup and everything underneath it?"After"The report is an abstraction over the engine."
Source · databases, transactions
Atomicity noun
In its fieldAn operation is atomic when it happens completely or not at all, never half-done. A transfer that debits one account must credit the other, or neither, with no state in between.
In accounting and financeFinance is full of operations that must be all-or-nothing and has no word for the property. A journal entry that posts one side but not the other leaves the books in an impossible state. Atomicity is the guarantee that a multi-part action either lands whole or rolls back entirely, so a process can fail without leaving a mess to find later. A close step that can stop halfway and strand the ledger is not atomic, and that is a design flaw, not bad luck.
In use
Before"I keep worrying this thing could stop partway through and leave us with one side posted and the other side just missing."After"The entry has to be atomic."
Source · security, audit
Attestation noun
In its fieldA signed statement that something is true, made by a party who stands behind it. It binds a claim to an identity, so the assertion can be checked and traced to who made it.
In accounting and financeAn attestation is stronger than a note in a file: it is a named person putting their name to a specific claim at a specific time. Finance leans on attestations constantly, the management representation letter, the sign-off on a reconciliation, without naming the form. Naming it sharpens a design question: which figures carry an explicit attestation, and which are merely assumed correct because no one objected.
In use
Before"Shouldn't somebody actually sign off on this, like formally put their name on it, instead of us all just assuming it's fine?"After"That figure needs an attestation."
Source · statistics, probability
Base rate noun
In its fieldThe underlying frequency of something in the population, before any specific evidence. Ignoring it, the base-rate fallacy, is judging a single case as if the general odds did not exist.
In accounting and financeA board told a single number with no base rate is being asked to react to it blind. A five percent expense overrun means one thing if comparable organizations run one percent and another if they run eight, and the base rate is what tells them which. Carrying the base rate is the difference between a figure and a judgment.
In use
Before"Is five percent actually bad here, or is that kind of normal, like what do places like us usually run?"After"What's the base rate?"
Source · site reliability engineering
Blast radius noun
In its fieldThe reach of a failure: everything affected when one component goes down. Engineers design to contain it, so one failure cannot take the whole system with it.
In accounting and financeEvery process and every person has a blast radius, and finance rarely maps one until the day it detonates. The question is asked before the failure: if this workbook corrupts, if this person resigns, if this import runs twice, what else goes down. A wide blast radius is a design finding, the cue to decouple, stage, and contain, so a single failure stays a single failure. The size of the blast radius, not the odds of the blast, is what sets how much care a component deserves.
In use
Before"If that file gets messed up, I honestly don't know how much other stuff breaks along with it, probably a lot?"After"What's the blast radius?"
Source · data, mathematics, computing
Canonical adjective
In its fieldThe one standard, authoritative form of a thing, against which all others are judged. A canonical version is the definitive one, not a copy or a variant.
In accounting and financeFinance needs this word and reaches for vaguer ones, "official," "the real one." A canonical figure is the single authoritative value every report must match, the canonical chart of accounts the one all entities map to. It is close kin to the single source of truth, but where that names the place a fact lives, canonical names the status of the fact itself: the version that settles disagreement by definition. Without a canonical form, reconciliation is endless, because there is no agreed answer to reconcile toward.
In use
Before"There are like four copies of this floating around and I'm never totally sure which one is supposed to be the official one."After"Which is the canonical version?"
Source · IT operations, quality systems
Change control noun
In its fieldA disciplined process for making changes: proposed, reviewed, recorded, and reversible, so no change happens silently and every change can be traced.
In accounting and financeFinance changes its own machinery constantly, a close procedure here, a mapping there, usually with no record of who changed what or why. Change control names the missing discipline: a change to a financial system is logged, justified, and reversible, the same care a controller demands of a change to the ledger applied to the process around it. Its absence is why a close can break and no one can say what changed. The point is not bureaucracy, it is traceability, so a regression can be tied to the change that caused it.
In use
Before"Somebody must have changed something in there at some point, but honestly there's no record of who did it or when or why."After"We have no change control."
Source · computing, data integrity
Checksum noun
In its fieldA small value computed from data so that any later corruption shows up: if the data changes, the checksum no longer matches. It detects error or tampering without re-examining everything.
In accounting and financeA checksum is a cheap, total integrity test, and finance improvises them without the word, the control total, the hash total, the count that must tie. Naming the idea generalizes it: attach a value to any dataset that proves at a glance whether it is intact, so a corrupted import announces itself instead of flowing through silently. A figure that ties to its checksum is whole, a figure that does not is not to be trusted, no judgment required. It is the fast cousin of an invariantA condition that must always hold, whose violation is itself the proof of error.In the Lexicon →, checked in an instant rather than re-derived.
In use
Before"Is there some quick total or count we could look at that would tell us right away if the file came in wrong?"After"Does it match the checksum?"
Source · Native Constraint
Compensatory effort noun
In the methodOutcomes produced by a person compensating for what the design does not carry. The close lands because someone stayed. The error is caught because someone remembers to look. The effort is real and the praise is earned, and the condition underneath is a system not producing its outcome.
In accounting and financeCompensatory effort is the most respected failure in the profession, because it looks like its opposite. The function rewards the save and misses what the save reports: burden that belongs in design, sitting on a person. Read effort as a meter. Where hours spike, where vigilance is required, where one individual is the reason it works, the design has a gap exactly that shape. The correction is never more effort. It is to remove the need for the save.
In use
Before"She basically holds the whole close together herself, honestly if she ever left I don't know what we'd do."After"The close runs on compensatory effort."
Source · Native Constraint
Coordination dependence noun
In the methodWork that moves only through live conversation: the recurring meeting, the status thread, the sync before the sync. Alignment produced in real time, every time, because the structure does not hold it.
In accounting and financeA recurring meeting on the same subject is the function coordinating by hand. Ownership is not fully defined, information is not structured to move alone, and the decisions are not embedded, so people convene to supply what the design lacks. The meeting is not the waste. It is the meter of it. Structure replaces coordination: name the owner, set the decision rights, wire the information to travel, and reserve the room for the decisions that cannot be made in advance.
In use
Before"We have the weekly touch-base, then the pre-close call, then usually a follow-up to sort out who's doing what."After"That's coordination dependence."
Source · systems design
Coupling noun
In its fieldHow dependent two parts are on each other. Tightly coupled parts cannot change independently, a change in one forces a change in the other. Loosely coupled parts can each change on their own.
In accounting and financeTight coupling is why one small change cascades into a week of rework, and finance feels it without naming it: a report wired directly to a specific spreadsheet layout breaks the moment the layout moves. Loose coupling is the cure, connect parts through a stable interface so each can change behind it. The most expensive coupling is to a person: a process tightly coupled to one individual's knowledge cannot change, or survive, without them. Designing for loose coupling is designing so the pieces, and the people, can move without breaking everything below.
In use
Before"Every time somebody touches that one spreadsheet, a bunch of other reports somehow break, because everything is sort of wired into everything else."After"These are too tightly coupled."
Source · programming paradigms
Declarative versus imperative adjectives
In its fieldImperative code specifies how: every step, in sequence, to reach a result. Declarative code specifies what: the outcome that must hold, leaving the engine to work out the steps. Telling a driver every turn is imperative. Giving the address is declarative.
In accounting and financeThis single distinction is the whole Native Constraint method. A standard operating procedure is imperative, it lists every step a person must perform, and depends on that person performing each one correctly, every time. Encoding a rule is declarative, it sets the outcome that must hold and lets the environment enforce it. Imperative process is carried by human execution and fails when attention does. Declarative structure produces the outcome by default. The move from imperative to declarative is the move from vigilance to design, and it is what separates a procedure someone has to follow from a rule that simply holds.
In use
Before"Instead of writing out every single step for someone to follow, couldn't we just set it up so the right thing kind of has to happen?"After"Make it declarative, not imperative."
Source · computer science, mathematics
Deterministic adjective
In its fieldA process is deterministic when the same inputs always produce the same output, with no randomness. Run it a thousand times, get the identical result every time.
In accounting and financeThe word the field reaches for is "consistent," which is softer and vaguer. Deterministic is exact and stronger: same data in, same answer out, always, by construction. It is the precise opposite of a black box, and the precise opposite of a tool that answers differently each time it is asked. Determinism is the property that makes a result auditable and reproducible at all, because a number that could come out differently on a second run cannot be verified by re-running it. A report produced by a deterministic method is the same tomorrow and checkable today, which is the whole basis of trusting it without an authority's stamp.
In use
Before"If we ran the exact same thing again on the exact same data, would we even get the same answer out, or not necessarily?"After"Is the process deterministic?"
Source · Native Constraint
Diffused ownership noun
In the methodResponsibility spread until no one holds it. The email copies the room, the task belongs to the team, and every reader is a little less accountable for every name beside theirs.
In accounting and financeCopying everyone reads as diligence and functions as its opposite: when all are included, each can reasonably assume another will act. Hesitation follows, then the reminder, then the escalation, and the volume itself is mistaken for rigor. The signal underneath is undefined decision rights. One outcome, one owner, named before the work begins. Visibility can be broad. Ownership cannot.
In use
Before"I copied everybody on it just so we're all on the same page and somebody can jump in on it."After"That's diffused ownership."
Source · control theory, statistics
Drift noun
In its fieldSlow, unnoticed movement away from a baseline over time. No single step looks wrong, but the cumulative shift carries the system far from where it started.
In accounting and financeDrift is the failure that hides because nothing ever breaks, the mapping that grows stale assumption by assumption, the reserve policy the organization quietly stops meeting a little more each year. Finance has "scope creep" for one flavor and no general term. Naming drift makes it a thing to watch for deliberately, because by definition no alarm will fire, the whole danger is that each increment sits below the threshold of notice. The remedy is to re-anchor to the baseline on a cadence, which is part of what posture means.
In use
Before"It's not that anything went wrong exactly, we've just sort of gradually ended up further from the policy than we meant to be."After"That's drift."
Source · software, operations
Dry run noun
In its fieldExecuting a process with everything real except the commit, to see exactly what it would do before it does it. Nothing changes, but the full result is shown.
In accounting and financeA dry run is the safe way to make a consequential change, and finance does it by hand and ad hoc, the test posting, the what-if copy of the workbook. Naming it as a property to build in changes the standard: any process that alters the books should be runnable in a mode that shows its effect and changes nothing. The dry run is the proof before the act, the difference between knowing what a re-run will do and hoping. It is the operator's first defense, look before you commit.
In use
Before"Is there some way to sort of try this first and see what it would actually do, without it really touching anything yet?"After"Do a dry run."
Source · software engineering
Edge case noun
In its fieldA rare input at the boundary of what a system handles, where normal logic tends to break. The first of the month, a zero, a negative, the leap day.
In accounting and financeEdge cases are where clean processes quietly produce wrong numbers, the thirteenth period, the refund larger than the original, the grant that spans two fiscal years. Finance meets them constantly and calls them, dismissively, "exceptions." The word edge case is more useful because it points at design: a robust process is judged by how it handles its edges, not its typical case, and the edge is exactly where it should be tested. A rule that works on ordinary data and fails at the boundary is not done.
In use
Before"It works fine most of the time, it's just the weird ones, the zeros and refunds and year-end stuff, that seem to trip it up."After"Have we handled the edge cases?"
Source · safety engineering
Fail-closed adjective
In its fieldOn failure, a fail-closed system moves to a safe state rather than continuing in an unsafe one. The failure stops the process instead of letting it run on and produce a wrong or dangerous result. Its opposite, fail-open, keeps going.
In accounting and financeA fail-closed process, when something does not reconcile, stops and raises the break rather than producing a number that looks clean but is wrong. Fail-open is the dangerous and common default: the process runs to completion and emits a figure no one knows to distrust. The principle a finance leader should demand of any automated process is that when it is uncertain, it refuses to produce an answer rather than guessing one, because a withheld number invites a question while a wrong number that looks finished invites a decision.
In use
Before"If something doesn't tie out, I'd honestly rather the whole thing just stop than keep going and hand us a number anyway."After"The process is fail-closed."
Source · reliability engineering
Failure mode noun
In its fieldThe specific way a component fails, enumerable in advance. A part does not simply break, it breaks in characteristic ways, and each way can be anticipated, detected, and designed against.
In accounting and financeFinance treats error as weather, arriving from nowhere. The word replaces that with a discipline: every process has a finite set of ways it goes wrong, the late feed, the duplicate posting, the stale mapping, the silent truncation, and they can be listed before any of them happens. A process whose failure modes are enumerated can be built to detect each one. A process whose failures still surprise its owner was never fully designed.
In use
Before"Something went wrong with the import again, it's always something different, you can never really predict it."After"List the failure modes."
Source · control theory, systems
Feedback loop noun
In its fieldWhen a system's output is fed back to adjust its input, so it self-corrects toward a target. A thermostat reads the room and changes the heat, then reads again.
In accounting and financeA function with a feedback loop corrects itself, the variance report read and acted on, the result checked next period, the correction confirmed. Without the loop, a number is produced, filed, and never closes back on the behavior that produced it, so the same miss repeats. Finance has the parts, reporting, review, and rarely names the circuit that joins them. The design instruction is to close the loop: every figure that matters should feed a decision whose effect is measured by the same figure, so the system learns instead of merely recording.
In use
Before"We write up the variance every month, but I'm not sure anything ever actually comes back around to tell us whether the fix worked."After"There's no feedback loop."
Source · machine learning, surveying
Ground truth noun
In its fieldThe directly verified reality a measurement is checked against, not an estimate or a proxy, the actual fact on the ground.
In accounting and financeGround truth is the bank statement behind the cash figure, the signed contract behind the revenue, the count behind the inventory, the real thing a number claims to represent. Finance works with proxies constantly and can forget which is which, treating the schedule as the fact rather than the trace of it. Naming ground truth keeps the distinction sharp: every figure should be traceable to something directly verifiable, and a number with no ground truth beneath it is an assertion wearing the clothes of a measurement. ProvenanceA figure's traceable origin, the document it ties to.In the Lexicon → is the path to it, ground truth is what waits at the end.
In use
Before"Is there an actual bank statement or contract or something real behind this, or does it just trace back to another schedule somewhere?"After"What's the ground truth?"
Source · functional programming, mathematics
Idempotent adjective
In its fieldAn operation is idempotent when running it more than once produces the same final state as running it once. Setting a record to PAID twice leaves it PAID. Adding one to a counter twice does not. Idempotency is what makes an operation safe to retry.
In accounting and financeThe field has no word for this and needs one. A well-designed posting or reconciliation is idempotent: run it once, or run it again after a crash, and the books land in the same correct state. A process that double-counts when it runs twice is not idempotent, and that fragility is a design flaw with no name, the reason a controller is afraid to re-run a job and instead unwinds it by hand. Idempotency is the precondition for safe automation: a process you cannot run twice without harm is a process you cannot trust a machine to run at all.
In use
Before"I'm scared to run that job again, because honestly I don't know if it would double everything up or just land the same."After"Is the posting idempotent?"
Source · Native Constraint
Instruction dependence noun
In the methodReliability that lives in a document a person must read, interpret, and follow correctly every time. The procedure is thorough, and the outcome still depends entirely on execution.
In accounting and financeA thick procedure library reads as maturity and records the opposite: every page describes work the design has not absorbed, decisions still resolved inside execution instead of upstream of it. More detail is the reflex, and more detail deepens the dependence, because the corrective is aimed at the reader instead of the process. Constrain the inputs, embed the logic, and let the procedure keep only what genuinely requires a person: the edge, the exception, the judgment. Vigilance is not a control.
In use
Before"The steps are all documented, people just have to actually read the procedure and follow it exactly every time."After"That's instruction dependence."
Source · mathematics, software
Invariant noun
In its fieldA condition that must hold true at all times, regardless of what else changes. If an invariant is ever violated, something is wrong by definition, no further judgment required.
In accounting and financeThe function is full of invariants and has no word for them. Assets equal liabilities plus net assets, always. The functional expense categories sum to total expense, always. An invariant is not something you check and hope, it is something that must be true, and whose violation is itself the proof of error. Naming invariants changes how a leader designs: a system can be built to enforce an invariant by construction, refusing to produce output that breaks it, rather than producing the output and testing for the break afterward.
In use
Before"There are certain things in here that just always have to hold, like if one of them ever doesn't, something is definitely wrong somewhere."After"That identity is an invariant."
Source · systems engineering
Latency noun
In its fieldThe delay between an event and its effect becoming visible: the gap between when something happens and when the system shows it.
In accounting and financeEvery financial fact has latency, the spend that surfaces at month-end, the receivable aging seen at review, the position known as of three weeks ago. Finance calls it timeliness and treats it as a virtue to pursue, which hides the sharper design question: for each figure, how much delay is tolerable before the decision it feeds goes wrong. A board steering on sixty-day-old numbers has sixty days of latency in the wheel. Some latency is structural and priced in. Unexamined latency is a decision made on a picture that no longer exists.
In use
Before"By the time we actually see those numbers, the month's over and whatever happened already happened."After"The read carries thirty days of latency."
Source · statistics, management cybernetics
Leading and lagging indicators nouns
In its fieldA leading indicator moves before the outcome and hints at what is coming. A lagging indicator moves after, confirming what already happened. One predicts, the other records.
In accounting and financeAlmost every figure on a financial statement is lagging, it reports a period that is over, and finance often treats lagging numbers as if they could steer the future. Naming the distinction disciplines that: pipeline, commitments, and runway lead, while revenue and surplus lag. A board watching only lagging indicators is driving by the mirror, and the useful design question is which leading indicators exist at all, since a function that produces only lagging numbers can explain the past but cannot see the turn ahead.
In use
Before"All these numbers are about months that are already over, so what do we actually have that tells us anything about what's coming?"After"Those are lagging indicators, what leads?"
Source · data engineering
Lineage noun
In its fieldThe record of how data was transformed from its source to its final form, every calculation and movement in between. Where provenance is the origin, lineage is the path. It answers how a number was produced.
In accounting and financeA computed figure has lineage when every transformation from source numbers to final result is traceable and reproducible. Finance collapses origin and derivation together under "audit trail." Separating them is more precise and more useful, because the two failures are different. A figure can have clean provenanceA figure's traceable origin, a filing or contract, not a schedule no one can source.In the Lexicon →, real sources, and still have broken lineage, an error in the math between source and result. When a measure is challenged, lineage is what lets you show the derivation step by step rather than asserting the answer.
In use
Before"Could somebody walk me through how this total actually got built, like every step from the source numbers all the way to here?"After"Show me the lineage."
Source · structural engineering
Load-bearing adjective
In its fieldCarrying weight the structure depends on. A load-bearing wall cannot be removed casually: the building stands on it, whether or not it looks important.
In accounting and financeFunctions are full of load-bearing elements no one designated: the spreadsheet feeding three reports, the tab nobody understands, the person whose memory is the mapping. Load-bearing is the property discovered at removal, which is the most expensive moment to learn it. The discipline is to find the load paths on purpose, name what carries weight, and either reinforce it deliberately or move the load into structure. What a function leans on should be chosen, not archaeological.
In use
Before"Careful with that tab, I'm pretty sure a bunch of other stuff pulls from it somehow."After"That tab is load-bearing."
Source · Native Constraint
Mechanical execution noun
In the methodWork performed as steps without possession of the outcome: the sequence known, the purpose not. Execution proceeds while conditions hold, and stops the moment they change.
In accounting and financeThe function mistakes mechanical execution for competence because the output arrives on time, until the first variation, when the work halts and the question travels upward. The person is not the flaw. The design gave them steps and withheld meaning: what the work produces, why it exists, what matters, what can flex, and what cannot. Comprehension is the difference between an operator and a professional, because judgment can only be exercised inside work that is understood. Meaning over mechanics.
In use
Before"He does it exactly the way he was shown, but the second anything's different he has to stop and come ask."After"That's mechanical execution."
Source · database design
Normalization noun
In its fieldStructuring data so each fact is stored once, in one place, with no redundancy. A normalized design makes contradiction impossible because nothing is duplicated to disagree with itself.
In accounting and financeNormalization is the structural cure for the most common finance error, the same fact maintained in several places that drift apart. A vendor's terms kept in one record, referenced everywhere, cannot contradict themselves, the way the same terms retyped across five workbooks inevitably will. It is the architecture that makes a single source of truthOne authoritative record every other view reconciles to.In the Lexicon → real rather than aspirational. Where reconciliation cleans up duplication after the fact, normalization prevents the duplication that made reconciliation necessary.
In use
Before"The same vendor detail is typed into like five different workbooks, and of course they don't all match anymore, it should really just live once."After"The data isn't normalized."
Source · safety engineering
Normalization of deviance noun
In its fieldThe gradual acceptance of departures from standard, each tolerated because the last one was, until the deviation is the practice. Named in the investigation of the Challenger loss, where the abnormal had become routine one flight at a time.
In accounting and financeDrift is the movement. Normalization of deviance is the moment the movement stops being noticed: the reconciliation signed with the same unexplained difference, the deadline that slides every quarter until the slide is the schedule, the policy exception granted so often it functions as the policy. Nothing announces the transition, which is the entire danger. Each acceptance recalibrates what normal means, so the standard erodes with every pass and the books show no event to point to. The countermeasure is the written standard consulted as written, because memory renegotiates and the document does not.
In use
Before"Yeah it's technically out of policy, but honestly that's just kind of how we've always ended up doing it."After"That's normalization of deviance."
Source · statistics
Outlier noun
In its fieldA data point far outside the rest of the distribution. It demands a decision: a real signal worth attention, or an error to exclude, never silently averaged in.
In accounting and financeFinance meets outliers constantly, the month with the one-time grant, the account ten times its neighbors, and too often buries them in a total or a mean. The word carries a discipline: an outlier is identified, then explained, then either kept as signal or set aside as error, but never quietly absorbed. An average that hides an outlier is a number that misleads on purpose. Reading them well is half of reading a distribution at all.
In use
Before"That one account is like ten times bigger than everything around it, so it feels wrong to just average it in and move on."After"That's an outlier, flag it."
Source · data engineering
Provenance noun
In its fieldThe record of a data point's origin: who created it, when, and from what source. It answers whether the data's source can be trusted, distinct from how the data was later changed.
In accounting and financeA figure has provenance when it traces to a specific, authoritative origin, a filing, a contract, a bank record, rather than appearing from a schedule no one can source. The audit trail is the nearest existing term, but provenance is sharper, because it is a claim about the trustworthiness of the origin itself, not merely the existence of a paper path. A number a controller cannot source has no provenance, and a number without provenance cannot be defended, however reasonable it looks.
In use
Before"Where is this number even from? Like who put it together, is there something behind it, or is it just on the schedule?"After"What is the provenance of this figure?"
Source · concurrent computing
Race condition noun
In its fieldWhen the result depends on the timing of two actions that overlap, so the same steps can produce different outcomes depending on which happens to finish first.
In accounting and financeA race condition is the bug behind "the numbers changed while I was working," two people editing the same close, an import landing mid-report, a balance read at the wrong instant. Finance blames the person and misses the design flaw: a process where overlapping work can corrupt the result is unsafe no matter how careful everyone is. Naming it points at the fix, sequence the work or lock the record, so timing cannot change the answer. A result that depends on who saved last is not a result.
In use
Before"We were both in the file at the same time, and I think our changes sort of collided, because now the totals look off."After"That's a race condition."
Source · software engineering
Regression noun
In its fieldWhen a change breaks something that previously worked. Software guards against it with regression tests, a stored set of known-correct results that must still hold after any change.
In accounting and financeThe function has regressions constantly and no word for them. A change to the close that fixes one schedule and silently breaks a reconciliation that tied last month is a regression. The value of the term is that it carries its own remedy: once you can name a regression, you can build the guard against it, a known-good result the process must still reproduce after any change. This is how a finance system becomes safe to modify.
In use
Before"The thing we fixed last month fixed that one schedule, but it looks like it quietly broke something else that used to tie out fine."After"We introduced a regression."
Source · science, computing
Reproducible adjective
In its fieldA result is reproducible when someone else, starting from the same inputs and method, can independently arrive at the same answer. Determinism is the same process repeating, reproducibility is a different hand getting there.
In accounting and financeA reproducible figure can be re-derived by a reviewer who was not there when it was made, which is the real test of whether it can be trusted without trusting the maker. Finance assumes reproducibility and rarely engineers it, so a number often dies with the workbook and the person who built it. The standard it sets is exacting and clarifying: hand the sources and the method to a stranger, and the same number comes out.
In use
Before"If somebody who wasn't involved took the same sources and the same method, would they actually land on this exact number themselves?"After"Is it reproducible?"
Source · databases, deployment
Rollback noun
In its fieldReturning a system to a known good prior state, cleanly undoing a change as if it never happened. The escape hatch that makes a risky change survivable.
In accounting and financeThe ability to roll back is what separates a change you can make confidently from one you fear, and finance usually lacks it, a close adjustment pushed with no clean way back but to reconstruct by hand. Naming rollback as a requirement raises the bar: a consequential change to the books should be reversible to the exact prior state, not approximately, not from memory. It is the partner of the dry run, one shows the effect before, the other undoes it after. Together they make change safe, which is what lets a system improve instead of ossifying out of fear.
In use
Before"If this adjustment turns out to be wrong, can we actually get back to exactly where we were, or is it stuck?"After"Can we roll it back?"
Source · software architecture
Separation of concerns noun
In its fieldKeeping distinct responsibilities in distinct parts, so each does one thing and can be understood, changed, and checked on its own.
In accounting and financeSeparation of concerns is the design principle beneath segregation of duties, and broader than it, the same logic of keeping things apart applied to systems, not only people. The spreadsheet that imports, computes, presents, and stores all at once cannot be changed in one respect without risking the others, because its concerns are tangled. Pulling them apart, one part sources, another calculates, another presents, makes each checkable and replaceable alone.
In use
Before"That one workbook pulls the data in, does the math, formats the report, stores everything, so touching any piece of it risks all of it."After"It needs separation of concerns."
Source · control theory
Setpoint noun
In its fieldThe target value a controlled system holds to. The system measures itself against the setpoint and corrects whenever it drifts off it.
In accounting and financeA setpoint is a policy made operational, the reserve target, the liquidity floor, the maximum a category may reach, stated as a number a system can hold to rather than an intention people remember. Finance sets goals and rarely wires them as setpoints, so the target exists on paper while the actual quietly drifts. Naming it makes the policy enforceable: declare the setpoint, measure against it, correct when the gap opens. It is the fixed point a feedback loopOutput fed back to adjust input, so a system self-corrects toward a target.In the Lexicon → steers toward, the difference between having a policy and running to one.
In use
Before"We keep saying we want three months of reserves, but nothing really holds us to that number, so we just quietly slip under it."After"Three months is the setpoint."
Source · science, signal processing
Signal and noise nouns
In its fieldSignal is meaningful variation. Noise is random fluctuation that carries no information. The discipline is separating them, and never mistaking noise for signal.
In accounting and financeA five-point trend with small wobbles is mostly noise, and the leader who reads every wobble as a movement is reacting to nothing and asking the room to do the same. Naming the distinction disciplines interpretation: state the signal, suppress the noise, and refuse to narrate randomness as a trend. It is also a design instruction for any report, set the threshold below which a change is treated as noise and left unmentioned. The same discipline reads the function itself. Effort is the loudest signal: hours spiking, a manual thickening, the same meeting recurring, each reporting work the design has not yet absorbed.
In use
Before"I don't know if that little movement actually means anything, or if it's just the normal wobble these numbers always have."After"That is noise, not signal."
Source · reliability engineering
Single point of failure noun
In its fieldOne element whose failure brings down the whole system, with no backup to take over. The part that, alone, can stop everything.
In accounting and financeIn finance the single point of failure is usually a person, the one who knows how the close works, holds the model, remembers the quirks, and key-person risk is the half of it everyone already names. The term is broader and more useful: the one undocumented spreadsheet, the process only one machine can run. Naming it turns a vague worry into a design task, find the single points of failure and build a path around each. A function that works only because one specific thing never fails is not reliable, it is lucky.
In use
Before"If that one person is out, the close basically just stops, because nobody else really knows how to run the whole thing."After"That's a single point of failure."
Source · data architecture, governance
Single source of truth noun
In its fieldOne authoritative record that every other view must reconcile to, so the same fact is never independently maintained in two places that can disagree.
In accounting and financeThe field lives this, the general ledger is meant to be it, but uses the phrase loosely and then violates it constantly. Held rigorously, it means one authoritative figure, with every report, schedule, and statement deriving from it rather than restating it. The failure it names is ordinary and expensive: the same number carried in two spreadsheets that quietly drift apart until no one knows which is right. When there is a true single source of truth, disagreement between two documents is impossible by construction, not something caught later in review. Most reconciliation work exists precisely because the single source of truth was not held.
In use
Before"This figure lives in three different spreadsheets and they don't agree, so which one is everything else actually supposed to match?"After"Which is the single source of truth?"
Source · software deployment
Staging and production nouns
In its fieldProduction is the live system of record. Staging is an identical copy where changes are tried first, so nothing is tested on the real thing.
In accounting and financeThe discipline finance lacks a word for is never experimenting on the live books. Staging is a faithful copy of the environment where a new close step, a remapping, a rate change can be run and checked before it touches production. Most finance teams test in production by necessity and call the fallout "issues." Naming the separation makes the safer practice nameable and demandable: prove the change in staging, then promote it to production, so the system of record is only ever changed by something already shown to work.
In use
Before"Are we seriously trying this new process straight on the live books, without some safe copy to prove it out on first?"After"Test it in staging, not production."
Source · software engineering
Technical debt noun
In its fieldThe future cost of a shortcut taken now: a quick fix that works today but makes the system harder and more expensive to change later. Like financial debt, it accrues interest until it is paid down.
In accounting and financeThe most natural import of all, because the metaphor is already financial. The manual workaround that becomes permanent, the spreadsheet no one can replace, the close step that works only because one person remembers its quirks, each is debt, taken on under deadline and paid forever in fragility and key-person risk. Naming it lets a leader treat it as what it is: a liability on the operational balance sheet, accruing interest every period, to be paid down deliberately rather than carried silently and rediscovered when the person who understood it leaves.
In use
Before"That workaround gets us through this month, I guess, but it feels like something we'll be paying for over and over later."After"That is technical debt."
Source · engineering, manufacturing
Tolerance noun
In its fieldThe allowable deviation from a target before something is out of spec. Within tolerance is acceptable variation, outside it is a defect, and the band is set deliberately in advance.
In accounting and financeFinance makes tolerance decisions constantly and rarely states them, how far off a reconciliation can be before it matters, how large a variance before it is investigated. Naming tolerance forces the band to be set on purpose rather than improvised case by case, which is both more rigorous and less arbitrary. It is the disciplined cousin of materiality, applied to a process, the threshold below which a difference is accepted and above which it is worked. A reconciliation with no stated tolerance is one where "close enough" is decided, differently, every time.
In use
Before"How far off can this actually be before we have to chase it, and are we just deciding that fresh every single time?"After"What's the tolerance?"
Source · software architecture, data pipelines
Upstream and downstream adjective, adverb
In its fieldIn a pipeline, upstream is near the source, downstream is near the output. An error upstream propagates to everything downstream, so the leverage is upstream: fix it once at the source instead of repeatedly at every point below.
In accounting and financeA choice resolved upstream, in the design, the threshold, the rule, never has to be made again downstream in daily execution. A choice left open upstream becomes a decision someone must make repeatedly, everywhere, forever. This is why a recurring exception is a signal, not a routine: approving the same out-of-policy spend every month means a boundary was never set upstream, so the decision keeps reappearing downstream. Moving work upstream is the highest-leverage move a finance leader has, because an upstream fix is made once and holds, while a downstream fix is made without end.
In use
Before"We keep fixing this same thing every month in the close, when really it should get fixed once, back where it starts."After"Fix it upstream."
Source · data engineering, software
Validation noun
In its fieldChecking that data meets defined rules before it is accepted, at the point of entry, so bad input is caught at the door rather than discovered downstream.
In accounting and financeValidation is the discipline of refusing bad data at the boundary, and finance mostly does the opposite, accepting whatever arrives and catching errors much later in reconciliation, far from where they entered. The word names a design move, define what valid looks like, check it on the way in, reject what fails, so an error is caught at the source instead of propagated downstream and hunted later. It is the everyday form of fail-closedOn failure, stop in a safe state rather than run on and emit a wrong result.In the Lexicon →, applied to input. Most reconciliation effort is validation deferred, paid later at higher cost.
In use
Before"Bad data just walks right in the door, and we only ever catch it like three steps later when something doesn't reconcile."After"There's no validation at entry."
Source · software, version control
Versioning noun
In its fieldKeeping every change as a distinct, labeled, recoverable version, so you can see what changed, when, by whom, and return to any earlier state.
In accounting and financeVersioning is what "final_v3_REVISED" is reaching for and failing to achieve. Done properly, every change to a model or a report is captured as a recoverable version with its history intact, so the document's whole past is legible and any prior state can be restored exactly. Finance lives in fear of the unrecoverable overwrite precisely because it improvises versioning by filename. Naming it as a property to build in is what makes change auditable, who changed what, when, and why, and it is the partner of rollback, since you cannot return to a version you never kept.
In use
Before"I honestly can't tell which copy is the current one, what changed between them, or whether the old one is even still anywhere."After"We have no real versioning."