These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Crop Insurance Platform
- Features
- Premium receipts
Premium receipts
Follow recorded premium money to its policy and provider event. Payment Operator records a premium receipt under its policy and checks the provider event identifier. The received date, amount and verification value show what was recorded and what still needs confirmation.
OverviewPremium receipt verification×
Crop Insurance Platform · Premium receipts
New
Premium receipt verification
Premium receipts
| Policy | Amount USD | Received at | Provider event ID | Verified | |
|---|---|---|---|---|---|
| PLC-53376 | 290 | 09 Oct | PEI-682 | No | |
| PLC-25001 | 880 | 14 Oct | PEI-224 | No | |
| PLC-86050 | 450 | 05 Oct | PEI-247 | No | |
| PLC-18772 | 910 | 12 Oct | PEI-499 | No | |
| PLC-72121 | 290 | 12 Oct | PEI-168 | No |
6 of 6 records
PEI-682Premium receipts · PR-78509
NoPolicyPLC-53376
Amount USD290
Received at09 Oct
What you can do
Premium receipts in practice
A premium receipt connects an amount, received date and provider event identifier to a policy. Its verification value distinguishes an entered receipt from one checked against the provider result. The policy owner can read the record beside the premium on the policy; the payment operator checks the event identity and outcome.
A receipt leaves the policy status to the issuance process. Keep payment event identity stable when a provider retries delivery, and compare the amount and date before marking the record verified. An operational review should separate an unverified premium receipt from an issued policy rather than assuming one establishes the other.
How the work is organized
- Link the policy. Match the premium receipt to the correct policy number.
- Keep the event. Record the provider identifier, amount and received date.
- Check verification. Compare the receipt with the provider result before marking it checked.
What to agree during setup
Agree how provider events reach the team and who checks the verification value. Decide how a repeated event identifier is recognized so a retry is not read as another premium. Keep the policy owner informed when a receipt needs review. Rehearse a mismatched amount and date, and decide who corrects the record while keeping the original event identity traceable.
Check the handoff on an actual case
Use a policy issued for the coming season. Record the premium receipt with its provider event identifier and received date. Ask the payment operator to check the provider result and set the verification value. If the same event arrives again, compare identifiers and amounts before recording another receipt. The policy owner can then see the policy and receipt together while handling a coverage question.
Payment Operator should open unverified receipts, follow each one to its policy and compare the provider identifier with the source event. Policy Owner can read the policy premium beside the received amount. A receipt records money received; the policy status and issuance operation should be checked on their own records.
What your team sees
- Premium receipt verification — Find premium receipts whose provider event still needs checking.
- Issued policy register — Open issued policies to compare the premium with linked receipts.
Follow the work through
Follow the related operating process and use the record definitions when checking a field or relationship.
What it keeps track of
Data model- Premium receipts
- Premium Receipts records; retain actual linked evidence and role scope.
- Policies
- Policies records; retain actual linked evidence and role scope.
Who uses it
Permissions- Payment Operator
- Checks receipts and provider events.
- Policy Owner
- Reads the policy context.
- Admin
- Manages access.
Set up Crop Insurance Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.