New educational worksheet draft. No customer data or verified product integration is included.
Existing workflow: Payment allocation and invoice matching
Fill in
- Payment identifier, amount, currency, date: fill in; keep unknown where unavailable
- Reference supplied: fill in; keep unknown where unavailable
- Invoice identifier, amount, currency, date: fill in; keep unknown where unavailable
- Confirmed match rule: fill in; keep unknown where unavailable
- Source rows and their timestamps: fill in; keep unknown where unavailable
- Unmatched or ambiguous items: fill in; keep unknown where unavailable
- Information needed to confirm: fill in; keep unknown where unavailable
- Person who verifies: fill in; keep unknown where unavailable
- Actual accepted record update: fill in; keep unknown where unavailable
- Next review: fill in; keep unknown where unavailable
Fit AI into the existing work
Describe the existing input, repeated manual effort, AI task, person who decides, actual working destination, completion evidence, and next run. Identify whether the workflow is manually started, scheduled, or event-triggered only after observing the supported behavior.
Question to adapt
Using only these supplied records, prepare a brief for this workflow. Cite each conclusion, retain missing information, flag conflicting records, and state what a person must confirm. Separate proposed actions from completed actions.
Check before using the answer
Verify one conclusion against a source row. Confirm scope, dates, units, and record meanings. Do not infer that a missing event never happened, or match records solely because their amounts look similar.