Owing

Owing audio micro-course (transcript)

Three short podcasts about “Owing”. Listen with the interactive player.

Podcast 1 — Introduction & meaning

Narrator: Owing. Adjective and preposition in the phrase owing to. Pronounced /ˈəʊ.ɪŋ/.

Narrator: Owing is the present participle and adjective of owe — from Old English āgan, to possess, to be obliged. Owing meaning in the state of being owed — the amount owing being the outstanding unpaid balance, the sum still in the state of being owed rather than yet paid.

Narrator: As an adjective, owing being a precise financial term: the amount owing on the account, the sum owing to the creditor, the balance owing at the end of the month. The word being equivalent to outstanding or unpaid but with a slightly more formal, accounting register. Invoices and statements using owing with this precision.

Narrator: As part of the prepositional phrase owing to, the word performing a different function — equivalent to because of or due to. The match was cancelled owing to the weather. Owing to a clerical error, the payment was delayed. Owing to having a slightly formal, written register — more at home in official correspondence, reports, and formal announcements than in casual speech.

Narrator: The traditional grammar prescription distinguishing owing to from due to — due to being originally an adjectival phrase requiring a noun to modify, while owing to being a preposition — has been largely abandoned in modern usage, with both phrases now functioning interchangeably as prepositions meaning because of. The distinction being of interest mainly to grammar traditionalists.

Narrator: Owing. The still-unpaid word — from the outstanding invoice to the formal announcement of delay — wherever what was not yet given remains in the state of being owed.

Speaker A: Owing to being one of those phrases that people sometimes worry about using incorrectly — is it different from due to?

Speaker B: The traditional grammar prescription being that due to is adjectival — it should follow a form of the verb to be and modify a noun. His absence was due to illness — here due to is adjectival, modifying absence. He was absent owing to illness — here owing to is a preposition, introducing a cause. The traditionalist rule being: if you can replace it with caused by, use due to. If you would use because of, use owing to. The modern reality being that the distinction has largely collapsed in contemporary usage: due to is used prepositionally in virtually all registers and no serious modern style guide insists on the traditional distinction. The practical advice being that owing to is always safe and always correct; due to is safe in all but the most formal grammar-prescriptivist contexts.

Speaker A: The adjective owing in financial and accounting contexts being worth examining — it's a precise term.

Speaker B: The balance owing being one of those specific accounting expressions that has a precise meaning: the amount that remains to be paid on a debt, invoice, or account — as distinct from the total amount owed (which might include future instalments not yet due) and the overdue amount (past the payment date). A mortgage statement might show: total outstanding balance — the full amount remaining on the mortgage. Amount owing this month — the specific instalment currently due. Overdue amount — any amount past its payment date. Each being distinct. Owing also appearing in legal contexts: sums owing to the deceased's estate, debts owing at the date of bankruptcy. The precision of the word in these contexts being its value: it names a specific financial state rather than a general condition.

Speaker A: The prepositional use of owing to in formal communication being worth practising.

Speaker B: Owing to being one of those formal connectives that does useful work in professional and official writing. The alternatives — because of, as a result of, on account of, due to — each having slightly different registers. Because of being neutral and entirely appropriate in all contexts. As a result of being slightly more formal, implying a logical or causal sequence. On account of being quite formal, with a slightly archaic quality. Owing to being formal and appropriate for official announcements, apologies, and explanations in written communication: we regret to inform you that the service will be delayed owing to essential maintenance. The word fitting naturally into the language of institutional communication — reports, notices, correspondence — where a slightly elevated register signals seriousness and formality without being pompous.

Speaker B: Build a Next.js invoice management system — businesses create invoices, track amounts owing per client, mark payments as received, flag overdue invoices, calculate aged debt reports (30/60/90 days), and generate a cash flow forecast based on outstanding amounts owing.

Speaker A: Invoice management requirements: Next.js 14, TypeScript, localStorage. Client: {id, name: string, email: string, paymentTermsDays: number}. Invoice: {id, clientId, number: string, issueDate: string, dueDate: string, lineItems: {description, quantity, unitPrice, total}[], subtotal, vatRate: number, vatAmount, total, amountPaid: number, status: 'draft'|'sent'|'partial'|'paid'|'overdue'}. amountOwing(invoice): invoice.total - invoice.amountPaid. AgingReport: {under30: {count, total}, 30to60: {count, total}, 60to90: {count, total}, over90: {count, total}}. CashFlowForecast: for each week of next 8 weeks, sum amounts owing with dueDate in that week. Dashboard: outstanding invoices list with owing badges, aging report table, cash flow SVG bar chart. Log payment form: partial or full payment with date.

Speaker B: Create a TypeScript API for a tenancy management system — tracking rent owing per property and tenant, logging payments, generating arrears reports, calculating the total owed across a portfolio, and producing formal rent owing letters for tenants in arrears.

Speaker A: Tenancy management API requirements: TypeScript, Express. Property: {id, address: string, monthlyRent: number}. Tenant: {id, name: string, email: string, propertyId, leaseStart: string, leaseEnd: string, depositPaid: number}. RentRecord: {id, tenantId, month: string (YYYY-MM), amountDue: number, amountPaid: number, paidAt?: string, status: 'paid'|'partial'|'owing'|'overdue'}. TenantArrearsReport: {tenant, property, totalOwing: number, monthsInArrears: number, records: RentRecord[]}. PortfolioReport: {totalProperties, totalMonthlyRent, totalOwing, tenantsInArrears: TenantArrearsReport[], collectionRate: number}. ArrearsLetter(tenantId): string — formal letter text with tenant name, property, total owing, months in arrears, payment instructions. Endpoints: POST/GET properties, tenants, rent records, POST /api/rent/:id/payment, GET /api/tenant/:id/arrears, GET /api/portfolio-report, GET /api/tenant/:id/arrears-letter.

Speaker B: Implement a Vue 3 cause-and-effect map builder using 'owing to' relationships — users define events and outcomes, connect them with causal 'owing to' links (each with a strength rating), visualise the causal chain, and identify which root causes are most responsible for the final outcome.

Speaker A: Causal map requirements: Vue 3 Composition API, TypeScript. CausalNode: {id, label: string, type: 'cause'|'intermediary'|'outcome', description?: string}. CausalLink: {id, fromId: string, toId: string, strength: 1-5, description: string}. CausalMap: {nodes: CausalNode[], links: CausalLink[]}. Analysis: rootCauses(map): CausalNode[] — nodes with no incoming links. PathsToOutcome(outcomeId): CausalPath[] — all paths from root causes to outcome. CausalPath: {nodes: CausalNode[], totalStrength: number (product or sum of link strengths)}. MostInfluentialCause: path with highest totalStrength. SVG layout: layered layout — root causes on left, outcome on right, intermediaries in middle. Edge arrows with thickness proportional to strength. Node colours by type. Click node: highlight all paths through it. Add/edit nodes and links via forms. Export: JSON of full map.

Speaker B: Write a Node.js REST API for a project dependency tracker — project tasks have prerequisite tasks they are owed completion by (owing to dependencies), the system detects circular dependencies, calculates the critical path, identifies tasks blocking the most others, and generates a dependency risk report.

Speaker A: Dependency tracker requirements: TypeScript, Express. Task: {id, name: string, estimatedHours: number, assignedTo?: string, status: 'not-started'|'in-progress'|'complete', dependencies: string[] (task IDs this task owes completion to)}. CircularDependency: detect using DFS — if visiting a node already in the current path, circular dependency found. CriticalPath: topological sort, then for each task calculate earliestStart = max(dependencies' earliestFinish). CriticalPath = tasks on the longest path. BlockingScore(taskId): count of tasks that (transitively) depend on this task. DependencyReport: {totalTasks, criticalPath: Task[], criticalPathHours, circularDependencies: {cycle: string[]}[], blockingScores: {task, score}[], bottlenecks: Task[] (blocking > 3 others), readyTasks: Task[] (no incomplete dependencies)}. Endpoints: POST/GET tasks, POST /api/tasks/:id/status, GET /api/critical-path, GET /api/dependency-report, GET /api/circular-deps. Demo: 10 tasks with complex deps.