Skip to content

Main content

Invoice Aging Part Paid Exposure Term Tool

Calculate invoice aging part paid exposure term from explicit caller-supplied inputs.

Loading tool…

Description

Return unpaid/uncredited invoice exposure and overdue exposure.

Business accounting and analytics distinguish gross, net, allocated, recognized and forecast amounts. Currency, period, eligibility and interaction-allocation conventions determine a reported contribution; reconciling one term does not verify revenue, payment rights or future commercial outcomes.

Return unpaid/uncredited invoice exposure and overdue exposure.

When to use this tool

Use Invoice Aging Part Paid Exposure Term when reconciling the stated business amount, share, bridge or forecast convention.

How to use the tool and how it works

  1. Enter invoice, paid, credited, dueDate, referenceDate. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read exposure, daysPastDue, overdueExposure. Use the output convention below.

Return unpaid/uncredited invoice exposure and overdue exposure. Require invoice >= paid+credited >= 0; exposure = invoice-paid-credited, daysPastDue = max(0,UTC date difference), overdueExposure equals exposure only when referenceDate strictly after dueDate.1

Input fieldMeaning and unitsAccepted input
invoiceInvoiceRequired. Finite number; minimum 0.
paidPaidRequired. Finite number; minimum 0.
creditedCreditedRequired. Finite number; minimum 0.
dueDateDue DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
referenceDateReference DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
Output fieldInterpretationReturned shape
exposureExposureRequired. Finite number.
daysPastDueZero on the exact due day; positive exposure requires a strictly later day.Required. Safe integer.
overdueExposureOverdue ExposureRequired. Finite number.
json
{
  "input": {
    "invoice": 1000,
    "paid": 300,
    "credited": 100,
    "dueDate": "2026-10-01",
    "referenceDate": "2026-10-26"
  },
  "output": {
    "exposure": 600,
    "daysPastDue": 25,
    "overdueExposure": 600
  }
}

Limitations and assumptions

  • Date-only years 0000-9999 are accepted; legal due-date rules, collection rights and impairment are not determined.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Use complete verified accounts and governing commercial terms, and apply the appropriate accounting and financial judgment for actual reporting, payment or investment decisions.

References

  1. Calculation and input contract: business-analytics/invoice-aging-part-paid-exposure-term — tool.io

Similar or alternative tools