Lost wages assistance calculator
A weekly benefit of 300 paid for 6 eligible weeks adds up to 1,800. Turn a FEMA supplement, an unemployment benefit or a stipulated weekly wage into the total you should receive before you call the claims office. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Weekly benefit amount
- 300
- Eligible weeks
- 6
- Total assistance
- 1,800
Claimants, case workers, unemployment desks, and personal-injury teams type lost wages assistance calculator when they already hold a weekly figure — a FEMA Lost Wages Assistance supplement, an unemployment weekly benefit amount, or a court-stipulated weekly wage — and a count of weeks that qualify, and they need the total assistance payment in one currency. This calculator accepts those two finite numbers, multiplies them, and returns the total rounded half-up to two decimal places. Zero weeks or a zero weekly amount is allowed and prints a total of zero.
How weekly benefit amount and eligible weeks become a total assistance payment
Lost wages assistance is the product people search for when they type lost wages assistance calculator: what a weekly benefit becomes after it is paid for a run of eligible weeks. Fractional weeks are allowed so a half week can be sent as one half without rounding the count first. Multiplying the two numbers is the whole job.
A three-hundred weekly amount for six eligible weeks prints a total of one thousand eight hundred. A four-hundred-twelve-point-seventy-five weekly amount for three weeks prints one thousand two hundred thirty-eight point twenty-five. Zero weeks or a zero weekly amount is legitimate and not an error: they print a total of zero.
A negative weekly benefit amount is rejected, and a negative week count is rejected, because a negative run of assistance is not a payment this calculator is asked to invent. You supply two finite numbers that already share one currency and one weekly convention; the calculator multiplies them and rounds the money total half-up to two decimal places so goldens compare byte-for-byte across runtimes.
Where a lost wages assistance calculator earns its keep
Unemployment claimants checking a FEMA Lost Wages Assistance window use a lost wages assistance calculator to turn a weekly supplement and a remaining week count into one lump before they call a claims office. A three-hundred-dollar federal week for six remaining weeks is not ranked by the weekly line; it is ranked by the one thousand eight hundred that should land if every week is paid.
Case workers pin the same two fields next to a determination letter so a one-line product can be checked against the live award without opening a full benefits engine. Personal-injury desks drop a stipulated weekly wage and the weeks a client could not work into one total so a demand letter is built on a reproducible product rather than on a spreadsheet that drifted. Failed validation does not consume balance.
What you can do with it
Pin an unemployment award to a week count
Multiply the awarded weekly benefit amount by the weeks still payable so a case file holds a reproducible product, not a drifted spreadsheet.
Build a personal-injury lost-wages line
Drop a stipulated weekly wage and the weeks a client could not work into one total for a demand letter without opening a payroll engine.
FAQ
What happens if the weekly benefit amount or the week count is negative?
A negative weekly line or a negative run of weeks is not an assistance payment this calculator produces. Zero is allowed and prints a total of zero.
Can I enter half a week?
Yes. Fractional weeks are accepted, so a half week is entered as 0.5 and you do not have to round the count first. The total is rounded to two decimals.
Does it look up FEMA amounts or deduct tax?
No. It does not consult FEMA tables, state supplement amounts or benefit duration limits, and it does not withhold tax or apply offsets. It multiplies the weekly amount you enter by the weeks.
Can I enter an hourly wage or an annual salary?
No. The calculator expects one weekly figure in one currency. Turn an hourly wage or a yearly salary into a weekly amount first, then enter it with the number of eligible weeks.
What if the weekly amount or the number of weeks is zero?
That is allowed and the total is simply zero. It fits a claim that has not started paying or a week count that has run out, and it is not treated as an error.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/fin/lost-wages-assistance \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"weekly_benefit_amount":300,"eligible_weeks":6}'const res = await fetch("https://api.kit.forhosting.com/fin/lost-wages-assistance", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"weekly_benefit_amount": 300,
"eligible_weeks": 6
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/fin/lost-wages-assistance",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"weekly_benefit_amount": 300,
"eligible_weeks": 6
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/fin/lost-wages-assistance", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"weekly_benefit_amount":300,"eligible_weeks":6}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"weekly_benefit_amount":300,"eligible_weeks":6}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/fin/lost-wages-assistance", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"weekly_benefit_amount": 300,
"eligible_weeks": 6
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "fin.lost_wages_assistance",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
Lost wages assistance is the lump that remains when a weekly benefit amount is paid for a run of eligible weeks: the product of those two numbers, not a guess at a grant. A negative weekly benefit amount or a negative week count fails with invalid_input and is not billed, because a negative run of benefits is not an assistance question this tool answers.
How weekly benefit amount and eligible weeks become a total assistance payment
The identity this calculator uses is total_assistance equals weekly_benefit_amount times eligible_weeks. weekly_benefit_amount is the weekly figure in one currency — a FEMA Lost Wages Assistance supplement of three hundred dollars a week, a four-hundred-dollar state-plus-federal week, an unemployment weekly benefit amount already awarded, or a weekly wage a court or insurer stipulated as the lost-earnings line. It is not an hourly rate, not an annual salary, and not a year-to-date running total unless you have already rolled those into one weekly number. eligible_weeks is the count of weeks that qualify under the rule you are applying: a six-week federal window, a three-week remaining entitlement, or the weeks a claimant could not work. This calculator does not look up FEMA tables, state $300 versus $400 supplements, unemployment duration caps, tax withholding, or personal-injury collateral offsets. It does not convert currencies or annualize an hourly wage.
Input contract, response shape, and error behaviour
Zero weeks and a zero weekly amount are allowed and print a total of zero. Fractional weeks are allowed. Example: three hundred of weekly benefit and six eligible weeks yield a total of one thousand eight hundred. Example: four hundred twelve point seventy-five of weekly benefit and three eligible weeks yield a total of one thousand two hundred thirty-eight point twenty-five. POST a JSON body with two required finite numbers that share one currency and one weekly convention. weekly_benefit_amount is the weekly line and must be greater than or equal to zero; aliases amount, weekly_benefit, benefit_amount, and wba map to the same field so a worksheet can keep its column names. eligible_weeks is the count of weeks that qualify and must be greater than or equal to zero; aliases weeks, number_of_weeks, and weeks_eligible are accepted. Each numeric field may arrive as a JSON number or a numeric string. Missing fields, empty strings, and non-finite values — NaN, Infinity, or text that does not parse as a number — fail with invalid_input naming the field. Those failures are not billed. Negative weekly_benefit_amount also fails with invalid_input, because a weekly line that starts below zero is not an assistance figure anyone is asking this calculator to produce. Negative eligible_weeks fail the same way. On success the body echoes weekly_benefit_amount and eligible_weeks, then reports total_assistance as the product rounded half-up to two decimal places, plus a formula string restating the identity. Pair the JSON with your own rule for which weekly amount matches the program you are modelling — a flat FEMA Lost Wages Assistance week, a state-plus-federal week, an unemployment weekly benefit, or a stipulated wage — because this endpoint multiplies the amount you send; it does not look up tables. Pricing is a flat $0.002 per successful request.
Where a lost wages assistance calculator earns its keep
Keep weekly_benefit_amount non-negative, keep eligible_weeks non-negative, pin the rounded total_assistance in tests, and you get a reproducible assistance lump for teasers, LMS plugins, and edge workers without standing up a benefits engine of your own.
Integration use cases
Check a FEMA Lost Wages Assistance window
Turn a weekly supplement and the remaining eligible weeks into one total_assistance lump before you call a claims office or pin a determination letter.
Technical questions
How is lost wages assistance calculated from a weekly benefit and eligible weeks?
Send two finite non-negative numbers: weekly_benefit_amount and eligible_weeks. The API returns total_assistance as their product, rounded half-up to two decimal places, from the identity total_assistance = weekly_benefit_amount × eligible_weeks.
Should I send the FEMA $300 LWA week or my unemployment weekly benefit amount?
Send the weekly figure that matches the program you are modelling. If the award is a flat three-hundred-dollar Lost Wages Assistance week, send 300. If you are totaling an unemployment weekly benefit, send that weekly amount. The calculator multiplies the amount you send; it does not look up FEMA or state tables.
Can eligible_weeks be a fraction, such as a half week?
Yes. Fractional weeks are allowed so a partial-week award can be modelled as 0.5 or 1.5 without rounding the count first. The product still rounds half-up to two decimal places.
What does a successful lost wages assistance call return, and what does it cost?
The body echoes weekly_benefit_amount and eligible_weeks, then reports total_assistance and a formula string. The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.