Skip to content

Main content

Farm Payment Support Share Tool

Calculate farm payment support share from explicit caller-supplied inputs.

Loading tool…

Description

Sum all payments and those with all flags true; return supported/total, or zero with defined=false if total is zero.

Agricultural claim records combine declared areas, exclusions, duplicate units and supporting-evidence flags. Avoiding double counting requires the correct intersection or exclusion overlap. A reconciled area/count or verified-token share is bookkeeping rather than legal validation of a claim.

Sum all payments and those with all flags true; return supported/total, or zero with defined=false if total is zero.

When to use this tool

Use Farm Payment Support Share when checking the stated claim count, area or evidence-support convention.

How to use the tool and how it works

  1. Enter payments, eligibilityVerified, rateVerified, sourceCurrent. Follow any array-alignment requirements below. 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 paymentTotal, supportedTotal, share, defined. Inspect defined before interpreting the associated values.

Require aligned nonnegative payments and eligibility/rate/current-source flags. Sum all payments and those with all flags true; return supported/total, or zero with defined=false if total is zero.1

Input fieldMeaning and unitsAccepted input
paymentsPaymentsRequired. Array of finite number; minimum 0; maximum items 256.
eligibilityVerifiedCaller-supplied row flags, not a legal eligibility determination.Required. Array of boolean; maximum items 256.
rateVerifiedRate VerifiedRequired. Array of boolean; maximum items 256.
sourceCurrentSource CurrentRequired. Array of boolean; maximum items 256.
Output fieldInterpretationReturned shape
paymentTotalPayment TotalRequired. Finite number.
supportedTotalSupported TotalRequired. Finite number.
sharePayment-amount-weighted supported share, not a fraction of payment records.Required. Finite number.
definedWhether the corresponding reporting denominator/value is defined; inspect before interpreting zero placeholders.Required. Boolean.
json
{
  "input": {
    "payments": [
      2,
      3,
      5
    ],
    "eligibilityVerified": [
      true,
      true,
      true
    ],
    "rateVerified": [
      true,
      true,
      false
    ],
    "sourceCurrent": [
      true,
      false,
      true
    ]
  },
  "output": {
    "paymentTotal": 10,
    "supportedTotal": 2,
    "share": 0.2,
    "defined": true
  }
}

Limitations and assumptions

  • Verification flags are supplied assertions; repeated payments are not deduplicated and legal eligibility is not established.
  • 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

Review authoritative source records, parcel geometry and applicable program rules with the responsible professionals for actual claims or payments.

References

  1. Calculation and input contract: agricultural-policy/farm-payment-support-share — tool.io

Similar or alternative tools