Invoice Terms Date Helper

Not legal or tax advice.

Batch explicit net-day and end-of-month invoice dates, with date-only ageing and optional weekend rolling.

Inputs and calculation

For each row, supply invoiceDate and asOfDate as real YYYY-MM-DD dates (years 1000–9999), an explicit term and days (integer 0–3660). No default date is taken from the clock.

net-days adds calendar days to the invoice date, excluding the starting date when days is positive. end-of-month-plus-days first selects the final date of the invoice month, then adds calendar days. These are the Actor’s explicit conventions; they do not interpret a contract or infer what free-text terms mean. Zero days means the base date itself.

weekendRoll is none by default. following-monday moves a Saturday or Sunday result to Monday; bank holidays are not considered. Due dates outside the supported year range are rejected.

Results include the base date, unadjusted and adjusted due dates, signed daysUntilDue (negative after the due date), non-negative daysOverdue, and status (not-due, due-today, overdue). Ageing compares calendar dates only and assumes no settlement information. It is not a statement that money remains unpaid. No interest, statutory deadlines, notice periods or legal entitlement are calculated. No invoice contents or customer details are accepted.

Example

{
  "items": [
    {
      "invoiceDate": "2026-01-15",
      "asOfDate": "2026-03-03",
      "term": "end-of-month-plus-days",
      "days": 30,
      "weekendRoll": "following-monday"
    }
  ]
}

The dataset and local CLI return these rows:

[
  {
    "rowIndex": 0,
    "invoiceDate": "2026-01-15",
    "asOfDate": "2026-03-03",
    "term": "end-of-month-plus-days",
    "days": 30,
    "weekendRoll": "following-monday",
    "baseDate": "2026-01-31",
    "unadjustedDueDate": "2026-03-02",
    "dueDate": "2026-03-02",
    "daysUntilDue": -1,
    "daysOverdue": 1,
    "status": "overdue"
  }
]

Batch and output behaviour

Supply 1–10,000 items. Unknown fields are rejected. Validation finishes for the whole batch before storage or billing. One invalid row fails the run with its zero-based index; input values are not included in the error. Duplicate rows are preserved and each stored row counts as a result. rowIndex preserves input order.

The Apify dataset holds results. The key-value store record OUTPUT contains requestedCount, storedCount, truncated and results. A configured charge limit may shorten the dataset; OUTPUT includes only those saved rows. Start a fresh run after an interruption: a non-empty dataset is rejected to prevent duplicate billing. Storage and billing are not a single transaction; infrastructure failures can leave partial storage or a charge requiring platform review.

Local use and tests

node cli.js examples/input.json
node tests/run.js

These commands need only Node and use no network or SDK installation. The deployment target is Node 22. main.js uses the Apify SDK for platform storage and billing. The container installs the declared dependency during a future build.

Pricing suggestion

Suggested pay-per-event price: $1 per 1,000 stored results ($0.001 per result-item event). No custom start fee. This is a proposed configuration, not active pricing. The manager must configure the exact event name and price in Apify before any release. The SDK call uses Actor.pushData(results, "result-item"); do not also add a separate charge for those rows. Apify billing documentation (accessed 2026-10-03).

Sources and data licences

No external dataset is used or redistributed. The cited API documentation is a reference for the workflow only. Calendar arithmetic is implemented locally.

1. Stripe invoice API: due-date fields — accessed 2026-10-03. Reference only; no Stripe data or text bundled.

AI-generated software draft for LandlordTools; manager review required before release.